|
*** CuteFTP 7.0 - build Jun 7 2005 ***
*** CuteFTP 7.0 - build Jun 7 2005 ***' X- {5 s$ j2 ?' b! o9 I
- a$ j: C7 m9 HSTATUS:> Getting listing ""...# h# q" g& W, p8 i( d) c7 k
STATUS:> Resolving host name ftp.pcbtech.net...9 [' c* @& L- z* M8 G' i
STATUS:> Host name ftp.pcbtech.net resolved: ip = 221.130.202.73.% l: R6 f( }) I+ W% [/ }4 n7 }
STATUS:> Connecting to FTP server ftp.pcbtech.net:2006 (ip = 221.130.202.73)...
- N' s# U) h, Z- R7 B3 F0 nERROR:> The connection failed due to an error or timeout.
* I% N# t+ p, l' b, f' d 1) Verify that the destination IP address is correct.
- L. b1 x, t# s9 O" @ 2) Increase the connection timeout threshold under Global Settings | Connection.5 X4 \4 ^1 x+ n w$ L
3) Switch to the opposite data connection type (PASV or PORT) under Site Settings | Type tab.
. O! T8 v+ ]4 Z- ` 4) Verify that the problem is not local by trying to connect to an alternate server.7 D! w. X% \; | n/ ?6 ]" ~5 C
5) If a server name was used, verify it resolves to the correct address.
. k1 `2 a7 S! {* P7 | 6) If using a local server table for server name resolution, check to see that it doesn't resolve to an obsolete address. }' i+ @3 `: O) d& N q1 o5 U- B
7) Try pinging the address.3 x1 t! m, Y! S C+ Y
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).+ ?/ d X8 m! t/ B" d
9) Do a traceroute to the destination to verify all routers along the connection path are operational.0 }+ w; F& _/ G- Q
10) Verify that your subnet mask is setup properly.
" v8 ]# t4 }5 A6 P U W 11) Verify that your local software or hardware firewall is not blocking outbound connections originating from CuteFTP.
' z, v4 J1 G7 X. h 12) Verify that your anti-virus software is not at fault (try disabling it). |
|