|
*** CuteFTP 7.0 - build Jun 7 2005 ***
*** CuteFTP 7.0 - build Jun 7 2005 ***- ^; m) f0 c. z% p" ^- R
# s+ ]8 _5 Z3 Z" q# \- n
STATUS:> Getting listing ""...; F* b+ G5 D: t0 {' A* j
STATUS:> Resolving host name ftp.pcbtech.net...
0 v6 {7 t. ?$ k# ?1 R% mSTATUS:> Host name ftp.pcbtech.net resolved: ip = 221.130.202.73.
2 R3 N' H. |2 t) n# F2 A2 QSTATUS:> Connecting to FTP server ftp.pcbtech.net:2006 (ip = 221.130.202.73)...
) Q5 a3 l% N/ U1 K8 PERROR:> The connection failed due to an error or timeout.
% y% K! Y9 q8 g; g1 ?( `" W3 { 1) Verify that the destination IP address is correct., |* ^! u7 R( T: }& e2 M
2) Increase the connection timeout threshold under Global Settings | Connection.3 M8 r( ?) c) t$ z; S7 L$ ^
3) Switch to the opposite data connection type (PASV or PORT) under Site Settings | Type tab.+ u$ C5 b( g/ {: G1 G9 T3 Z
4) Verify that the problem is not local by trying to connect to an alternate server.
) @ ?1 u4 Y+ T& ] 5) If a server name was used, verify it resolves to the correct address./ X# N+ \6 v' ]; s: O1 R7 ]
6) If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address.
$ [( [- S5 E# j( _8 x2 F. Z 7) Try pinging the address.! F, i5 R: d# V; Z( z1 d
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).
! c$ y) u& p# D: B } 9) Do a traceroute to the destination to verify all routers along the connection path are operational.
( D2 }6 i$ }% S4 Z' Y 10) Verify that your subnet mask is setup properly.$ ^' `) a' H0 F. J; y
11) Verify that your local software or hardware firewall is not blocking outbound connections originating from CuteFTP.
8 d# h, v0 ]8 i7 E ]3 ^: d/ \6 T* j 12) Verify that your anti-virus software is not at fault (try disabling it). |
|