Archived Forum Post

Index of archived forum posts

Question:

iOS FTPS over LTE Socket Error

Dec 17 '12 at 18:34

[UPDATED WITH NEW LOG from iOS6 library]

Hello,

I am able to connect to an ftps server over WiFi (the same network the ftp server resides on, as well as an external network), but for some reason I am unable to connect using an LTE connection with AT&T. I am getting the following error, any help would be appreciated. Thanks in advance.

 Connect_Ftp2:
DllDate: Dec 12 2012
UnlockPrefix: xxxx
Username: xxxx-iPad:mobile
Architecture: Little Endian; 32-bit
Language: IOS Objective-C
VerboseLogging: 0
ProgressMonitoring:
  enabled: yes
  heartbeatMs: 0
  sendBufferSize: 65536
--ProgressMonitoring
ImplicitSsl: 0
AuthTls: 1
AuthSsl: 0
Hostname: xxxx.xxx.net
Port: 21
IdleTimeoutMs: 60000
ConnectTimeout: 60
HeartbeatMs: 0
ConnectTimeoutMs_1: 60000
calling ConnectSocket2
IPV6 enabled connect with NO heartbeat.
connectingTo: xxxx.xxxx.net
socketErrno: 4
socketError: Interrupted system call
gethostbyname_arg: xxxx.xxxx.net
GetHostByNameHB_ipv4: Elapsed time: 30005 millisec
Cannot get host by name..
hostname: xxxx.xxxx.net
ConnectFailReason: 2
Failed to connect to FTP server.
Failed.

--Connect_Ftp2 --ChilkatLog


Answer

This new build should have just a bit more information in the LastErrorText that may help identify the problem:

http://www.chilkatsoft.com/download/Chilkat-9.4.0-IOS-6.0.zip


Answer

So I swapped out the host name with the IP address and now I'm getting this error:

 Connect_Ftp2:
DllDate: Dec 12 2012
UnlockPrefix: unlockprefix
Username: AllDigital-iPad:mobile
Architecture: Little Endian; 32-bit
Language: IOS Objective-C
VerboseLogging: 0
ProgressMonitoring:
  enabled: yes
  heartbeatMs: 0
  sendBufferSize: 65536
--ProgressMonitoring
ImplicitSsl: 0
AuthTls: 1
AuthSsl: 0
Hostname: xx.xx.xx.xx
Port: 21
IdleTimeoutMs: 60000
ConnectTimeout: 60
HeartbeatMs: 0
ConnectTimeoutMs_1: 60000
calling ConnectSocket2
IPV6 enabled connect with NO heartbeat.
This is an IPV4 numeric address...
AddrInfoList:
  AddrInfo:
    ai_flags: 0
    ai_family: 2
    ai_socktype: 1
    ai_protocol: 6
    ai_addrlen: 16
    ai_canonname: (NULL)
  --AddrInfo
--AddrInfoList
Connect using IPV4.
ipAddress1: xx.xx.xx.xx
Info: Socket operation in progress..
myIP_3: xx.xx.xx.xxx
myPort_3: 53831
connect successful (2)
Turning on TCP_NODELAY.
socketOptions:
  SO_SNDBUF: 131920
  SO_RCVBUF: 131920
  TCP_NODELAY: 4
--socketOptions
initialStatus: 220
initialResponse: 220 (vsFTPd 2.0.5)
converting to secure connection...
sentCommand: AUTH TLS
receivedResponse: 234 Proceed with negotiation.
ssl_protocol_3: default
ConvertToTls_4:
  establishChannel2_1:
    clientHandshake:
      clientHelloMajorMinorVersion: 3.1
      buildClientHello:
        majorVersion: 3
        minorVersion: 1
        numRandomBytes: 32
        sessionIdSize: 0
        numCipherSuites: 10
        numCompressionMethods: 1
      --buildClientHello
      readIncomingTls_serverHello:
        Timeout waiting to read socket or accept connection
        timeoutMs: 60000
        Timed out waiting for incoming SSL/TLS messages.
        timeoutMs: 60000
      --readIncomingTls_serverHello
      Expected ServerHello but did not receive it.
    --clientHandshake
    Client handshake failed. (1)
    connectionClosed: 0
  --establishChannel2_1
--ConvertToTls_4
Failed to convert channel to SSL/TLS
Failed to connect to FTP server.
Failed.

--Connect_Ftp2 --ChilkatLog

This is over AT&T's LTE network. What's interesting is that I was able to connect to my ftps over a tethered verizon connection. Again, everything works fine over WiFi.