|
*** CuteFTP 7.0 - build Jun 7 2005 ***
*** CuteFTP 7.0 - build Jun 7 2005 ***' q( _; [1 ?# }& Y' u6 t* C. D( k8 B4 i
: ?3 S+ O& w& ^8 C- V2 GSTATUS:> Getting listing ""...
- H* L' c3 n+ F5 VSTATUS:> Resolving host name ftp.pcbtech.net...
8 X! B! G4 C. k) ESTATUS:> Host name ftp.pcbtech.net resolved: ip = 221.130.202.73.- @: F. R0 m* G' ~& d
STATUS:> Connecting to FTP server ftp.pcbtech.net:2006 (ip = 221.130.202.73)...
- k; [. m* ` g) Q6 CERROR:> The connection failed due to an error or timeout.
, m. z& {7 {. T. Q0 Z' r" [ 1) Verify that the destination IP address is correct.* }: B* k; }8 c3 w1 x
2) Increase the connection timeout threshold under Global Settings | Connection.# B( q! B8 F3 w! c1 k0 K. K
3) Switch to the opposite data connection type (PASV or PORT) under Site Settings | Type tab.
! v' x. k# N1 J, J 4) Verify that the problem is not local by trying to connect to an alternate server.
, C/ t; P! T( Y, f& \ L% N1 R' Y 5) If a server name was used, verify it resolves to the correct address.( b8 Q m" J* J1 b
6) If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address.
6 t) L1 _6 S6 C) A# y 7) Try pinging the address.
- o* g& G, i$ W* ] 8) If you are using a router, verify the router is up and running (check by pinging it and then ping an address outside of the router).# u/ Y7 J' F& F0 T4 u* n# u6 u
9) Do a traceroute to the destination to verify all routers along the connection path are operational.- A5 L2 _0 ^$ _
10) Verify that your subnet mask is setup properly.% U' T* p g' {$ y
11) Verify that your local software or hardware firewall is not blocking outbound connections originating from CuteFTP.
- A9 o0 ?$ S( V3 \; ]9 X0 Y 12) Verify that your anti-virus software is not at fault (try disabling it). |
|