Can't ping or log-on to my buddy's FTP server

[Yzzim]

I can't seem to ping or log-on to my bud's FTP server. We've tried everything possible on his end and nothing works. Other people have no problem logging onto his ftp server.

I have no firewall installed (not using WinXP's firewall either) or anti-virus software or anything. Only non-Microsoft programs I have installed on this computer are cuteFTP, Nero, and Kazaa.

I've tried to ping him and log-on from 2 different machines at my home with no success. Both machines are using Windows XP.

Just before I reinstalled Windows I could log-on to his server no problem. After I reinstalled I haven't been able to do anything. I can log-on to other ftps though, such as ftp.cuteftp.com

Any idea what the problem is?

I posted this in the Networking forum but didn't get any answer as to what the problem was

 

[gopunk]

how long has this problem been occuring? are you trying to connect via IP address or some domain name?

 

[Yzzim]

Originally posted by: gopunk
how long has this problem been occuring? are you trying to connect via IP address or some domain name?

I've had the problem for the past week or so. I've tried a couple times everyday with no success.

Connecting via IP#

Port # is 21

 

[Kadarin]

Verify that you're connected to the internet, and verify the ip address you're using to connect to him. If you can't ping that ip, can you verify that others are able to ping him and log in? If others are able to ping him, run a traceroute to that ip and find out who's dropping the traffic.

 

[Yzzim]

Originally posted by: Astaroth33
Verify that you're connected to the internet, and verify the ip address you're using to connect to him. If you can't ping that ip, can you verify that others are able to ping him and log in? If others are able to ping him, run a traceroute to that ip and find out who's dropping the traffic.

I am connected to the internet, lol. I was talking with him while we were trying to figure it out.

His IP# and the port # are correct. I've check it at least a dozen times.

Others can login to his server just fine. I tried to ping him but was unable to. Even with his firewall down I wasn't able to ping him.

 

[Kadarin]

Originally posted by: Yzzim

Originally posted by: Astaroth33
Verify that you're connected to the internet, and verify the ip address you're using to connect to him. If you can't ping that ip, can you verify that others are able to ping him and log in? If others are able to ping him, run a traceroute to that ip and find out who's dropping the traffic.

I am connected to the internet, lol. I was talking with him while we were trying to figure it out.

His IP# and the port # are correct. I've check it at least a dozen times.

Others can login to his server just fine. I tried to ping him but was unable to. Even with his firewall down I wasn't able to ping him.

With his firewall down, run a traceroute to his ip address (from the windows "cmd" command shell, it's "tracert <ip address>"). This could be a temporary routing issue between your ISP and his (very possible, given the weekend and the current time, since it's about right for a scheduled maintenance). Alternatively, verify that neither you nor he has any filters in place that will prevent your access to his ip (even via ping).

 

[Yzzim]

Originally posted by: Astaroth33

Originally posted by: Yzzim

Originally posted by: Astaroth33
Verify that you're connected to the internet, and verify the ip address you're using to connect to him. If you can't ping that ip, can you verify that others are able to ping him and log in? If others are able to ping him, run a traceroute to that ip and find out who's dropping the traffic.

I am connected to the internet, lol. I was talking with him while we were trying to figure it out.

His IP# and the port # are correct. I've check it at least a dozen times.

Others can login to his server just fine. I tried to ping him but was unable to. Even with his firewall down I wasn't able to ping him.

With his firewall down, run a traceroute to his ip address (from the windows "cmd" command shell, it's "tracert <ip address>"). This could be a temporary routing issue between your ISP and his (very possible, given the weekend and the current time, since it's about right for a scheduled maintenance). Alternatively, verify that neither you nor he has any filters in place that will prevent your access to his ip (even via ping).

But would those routing issues be the case for a whole week?

I'll do that when I get home...I'll let you know what happens

thanks

 

[Kadarin]

Originally posted by: Yzzim

Originally posted by: Astaroth33

Originally posted by: Yzzim

Originally posted by: Astaroth33
Verify that you're connected to the internet, and verify the ip address you're using to connect to him. If you can't ping that ip, can you verify that others are able to ping him and log in? If others are able to ping him, run a traceroute to that ip and find out who's dropping the traffic.

I am connected to the internet, lol. I was talking with him while we were trying to figure it out.

His IP# and the port # are correct. I've check it at least a dozen times.

Others can login to his server just fine. I tried to ping him but was unable to. Even with his firewall down I wasn't able to ping him.

With his firewall down, run a traceroute to his ip address (from the windows "cmd" command shell, it's "tracert <ip address>"). This could be a temporary routing issue between your ISP and his (very possible, given the weekend and the current time, since it's about right for a scheduled maintenance). Alternatively, verify that neither you nor he has any filters in place that will prevent your access to his ip (even via ping).

But would those routing issues be the case for a whole week?

I'll do that when I get home...I'll let you know what happens

thanks

It's not likely that you'd have such routing issues for a full week, but it's still worth checking into. You might also want to check with a WinXP expert to see if there are any firewall settings on your box that might be affecting you. I can't help you there, unfortunately.

 

[Yzzim]

I can't ping him right now cause he has his firewall up. I asked him once before and he said that it isn't possible for me to ping him once it is up.
The tracert does show me getting close to him though.

 

[Yzzim]

bump

 

[Yzzim]

up

 

[GoSharks]

Originally posted by: Yzzim

But would those routing issues be the case for a whole week?

yes. for the past 1.5 years i have not been able to ping or access my friend's ip on the other side of town. (ATT@home, then ATTBI)

 

[dethman]

are you both behind routers? i've found that with certain routers, if both the server and the client are behind them the ftp will only work on port 21 and on no other ports, even with the whole schmiddly of settings in the router. i still dont know why.

 

[Yzzim]

Originally posted by: dethman
are you both behind routers? i've found that with certain routers, if both the server and the client are behind them the ftp will only work on port 21 and on no other ports, even with the whole schmiddly of settings in the router. i still dont know why.

AFAIK he's not behind a router....just a software firewall. I'm not behind a router. I do have my connection going through a different computer if that matters at all.

His server port is 21

 

[spiridion]

what program are u using? Are you using passive or active transfers? What error message do you get when connecting?

 

[Yzzim]

what program are u using?

CuteFTP

Are you using passive or active transfers?

Using Passive I think. I've tried turning it on and off but nothing seems to help.

What error message do you get when connecting?

I get "Socket connected. Waiting for welcome message..." (at first, like normal) and then it doesn't do anything from there except:

ERROR:> Timeout
ERROR:> Can't log in. Disconnecting...

It retries and I get the same message everytime.

 

[Yzzim]

up

 

[Yomicron]

open a command prompt and type:

ftp His_IP_Address

what error do you get?

 

[Yzzim]

Originally posted by: Yomicron
open a command prompt and type:

ftp His_IP_Address

what error do you get?

ftp His_IP_Address

Connected to His_IP_Address.
Connection closed by remote host.

???

 

[thomsbrain]

i'll bet money his ISP blocks all incoming connections to port 21 (probably 80 as well). switch the port (on the server and client) to something random and watch as you connect like magic. i've NEVER been on an ISP that didn't block ports 21 and 80, and even my college connection had them blocked.

 

[Yzzim]

Originally posted by: thomsbrain
i'll bet money his ISP blocks all incoming connections to port 21 (probably 80 as well). switch the port (on the server and client) to something random and watch as you connect like magic. i've NEVER been on an ISP that didn't block ports 21 and 80, and even my college connection had them blocked.

He's had other people connect though when I've been unable to

all on port 21

 

[dabuddha]

Originally posted by: Yzzim

Originally posted by: Yomicron
open a command prompt and type:

ftp His_IP_Address

what error do you get?

ftp His_IP_Address

Connected to His_IP_Address.
Connection closed by remote host.

???

lol

what happens when you tried the traceroute?

 

[Yzzim]

C:\Documents and Settings\ME>tracert His_IP_Address

Tracing route to His_Longer_IP_Address [His_IP_Address]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DialupServer.mshome.net [192.168.0.1]
2 153 ms 160 ms 149 ms pmwind1.rconnect.com [209.163.18.1]
3 150 ms 150 ms 140 ms gwwind1-e0.rconnect.com [209.163.18.126]
4 185 ms 171 ms 159 ms gwroch1-se5-0-0-24.rconnect.com [209.163.28.125]

5 188 ms 190 ms 209 ms dir01-se-1-0-0.il-chicago0.ne.earthlink.net [209
.165.105.149]
6 178 ms 210 ms 210 ms bor02-g6-1.il-chicago0.ne.earthlink.net [209.165
.97.18]
7 174 ms 190 ms 170 ms 209.165.105.170
8 212 ms 168 ms 190 ms p0-1.br01.ord10.atlas.psi.net [154.54.2.126]
9 182 ms 190 ms 190 ms 154.13.70.26
10 229 ms 240 ms 240 ms wnpgmbabbr00.bb.telus.com [154.11.11.181]
11 239 ms 260 ms 229 ms wnpgmb38br00.bb.telus.com [154.11.11.50]
12 246 ms 239 ms 239 ms clgrab21br01.bb.telus.com [154.11.10.157]
13 258 ms 261 ms 258 ms vancbc01br01.bb.telus.com [154.11.10.21]
14 324 ms 229 ms 250 ms vancbc01gr01.bb.telus.com [154.11.10.50]
15 313 ms 230 ms 220 ms vancbc01dr01.bb.telus.com [154.11.4.67]
16 250 ms 258 ms 230 ms vancbc01dr11.bb.telus.com [154.11.10.70]
17 237 ms 239 ms 240 ms 209.53.1.167
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 209.53.1.167 reports: Destination host unreachable.

Trace complete.

209.53.1.167 is not his IP address, btw.

 

[dabuddha]

hmmm

btw for some reason, i thought you had literally typed:
ftp His_IP_Address

Connected to His_IP_Address.
Connection closed by remote host.

???

 

[Yzzim]

Originally posted by: dabuddha
hmmm

btw for some reason, i thought you had literally typed:
ftp His_IP_Address

Connected to His_IP_Address.
Connection closed by remote host.

???

lol, I'm not that dumb