PDA

View Full Version : No one can Ping me


Dethredic
Aug 11th, 2007, 07:03 PM
Ok, my friend tried to ping me and couldn't. (he kept getting request timed out)

I then got other friends to try with no success.

He did a traceroute (from CMD) on my IP this was his results:

C:\Documents and Settings\Dandymcgee>tracert 24.57.211.254

Tracing route to d57-211-254.home.cgocable.net [24.57.211.254]
over a maximum of 30 hops:

1 5 ms 1 ms <1 ms 192.168.2.1
2 6 ms 1 ms 1 ms 192.168.1.1
3 36 ms 35 ms 35 ms 10.20.10.1
4 34 ms 33 ms 33 ms P0-1.LCR-01.CNCDNH.verizon-gni.net [130.81.35.230]
5 60 ms 44 ms 43 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.81.17.131]
6 47 ms 45 ms 46 ms 130.81.15.138
7 52 ms 51 ms 49 ms p5-0.core01.bos01.atlas.cogentco.com [66.28.4.117]
8 53 ms 55 ms 55 ms p13-0.core01.alb02.atlas.cogentco.com [154.54.7.41]
9 69 ms 69 ms 68 ms p14-0.core01.yyz01.atlas.cogentco.com [66.28.4.218]
10 238 ms 113 ms 209 ms v3491.mpd01.yyz01.atlas.cogentco.com [154.54.5.78]
11 68 ms 68 ms 68 ms v3493.mpd01.yyz02.atlas.cogentco.com [154.54.5.86]
12 69 ms 71 ms 68 ms cogeco-cable-canada.demarc.cogentco.com [38.99.220.154]
13 73 ms 71 ms 72 ms cgowave-0-114.cgocable.net [24.226.0.114]
14 72 ms 73 ms 74 ms d226-8-198.home.cgocable.net [24.226.8.198]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I then ran a traceroute on him

C:\Documents and Settings\Philip>tracert 72.64.9.67
Tracing route to pool-72-64-9-67.cncdnh.east.verizon.net [72.64.9.67]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 8 ms 8 ms 10.67.176.1
3 8 ms 15 ms 9 ms d226-9-129.home.cgocable.net [24.226.9.129]
4 10 ms 9 ms 11 ms cgowave-0-105.cgocable.net [24.226.0.105]
5 45 ms 12 ms * g8-11.mpd01.yyz02.atlas.cogentco.com [38.99.220.153]
6 9 ms 9 ms 9 ms v3493.mpd01.yyz01.atlas.cogentco.com [154.54.5.85]
7 25 ms 24 ms 26 ms t7-4.mpd01.ord01.atlas.cogentco.com [154.54.7.73]
8 25 ms 25 ms 25 ms v3489.mpd01.ord03.atlas.cogentco.com [154.54.5.18]
9 24 ms 23 ms 21 ms g15-0-0-3493.core01.ord03.atlas.cogentco.com [154.54.3.245]
10 24 ms 23 ms 25 ms so-0-1-0-0.PEER-RTR1.CHI80.verizon-gni.net [130.81.15.85]
11 26 ms 25 ms 23 ms so-7-0-0-0.BB-RTR2.CHI01.verizon-gni.net [130.81.16.78]
12 44 ms 43 ms 42 ms so-6-0-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.19.64]
13 42 ms 44 ms 43 ms so-0-0-0-0.BB-RTR2.BOS.verizon-gni.net [130.81.19.73]
14 45 ms 44 ms 46 ms P14-0.LCR-01.CNCDNH.verizon-gni.net [130.81.28.77]
15 46 ms 49 ms 45 ms P9-0.MNCHNHCO-ERXG01.CNCDNH.verizon-gni.net [130.81.35.231]
16 88 ms 78 ms 79 ms pool-72-64-9-67.cncdnh.east.verizon.net [72.64.9.67]

Trace complete.

It appears to not get past my modem.

Is this correct? How can i fix this?

goofball
Aug 11th, 2007, 07:10 PM
doublecheck to see if ICMP reply or the like is set for the security in your router. I believe many will block pings by default.

Jucius Maximus
Aug 11th, 2007, 07:58 PM
Not responding to pings is a security measure that helps defeat the Smurf Attack (http://en.wikipedia.org/wiki/Smurf_attack) technique. This may be something built into your cable modem or any firewall you have.

Dethredic
Aug 11th, 2007, 08:43 PM
Ok, well, I don't really wan't to be able to be pinged, I was sorta just curious.

Well, the main reason i was asking is because me and my friend both set up UltraVNC, and he can connect to me but i can't connect to him. (Same guy as above). Pinging was one of our troubleshooting ideas.

Do you think this problem would be related to the firewall in the modem?

IoannI
Aug 11th, 2007, 09:04 PM
Your friend can't ping to you because you do not have a IP address. The 192 IP address you have is the Windows XP PRO default (I'm not sure if the 192 IP is default for all version of Windows as well as on other versions of XP beside Pro). I get the same IP many times, usually when I reformat my Windows XP Pro SPK-1 Hard drive

Dethredic
Aug 11th, 2007, 09:12 PM
Your friend can't ping to you because you do not have a IP address. The 192 IP address you have is the Windows XP PRO default (I'm not sure if the 192 IP is default for all version of Windows as well as on other versions of XP beside Pro). I get the same IP many times, usually when I reformat my Windows XP Pro SPK-1 Hard drive

Hmm either my knowledge of this stuff is really off, or you are really wrong.

Doesn't everyone have an IP (if they have an ISP, aka internet)?
The 192.168.1.1.. is the router ip isn't it?

IoannI
Aug 11th, 2007, 09:53 PM
Hmm either my knowledge of this stuff is really off, or you are really wrong.

Nah man I know what I'm talking about



Doesn't everyone have an IP (if they have an ISP, aka internet)?

You are somewhat correct their. Everyone does have a IP address, which you are correct. However where you are wrong is where you say if the have a ISP. You have a IP address. Windows comes with its own IP address which is the 192.162 IP address that the user is connected to. There 2 types of IP address. 1 for the computer itself = e.g. 192.168.1.0, and the other for the internet = e.g. 220.xxx.xxx.x.
The 192.x.x.x is your private local address. The 220.x.x.x is your public address. The basic function of a router is to connect two networks; in this case the internet and your private network. When you check your IP address within your network, you see your actual computer's private address. When you check it online, you see your WAN address, as that's what everyone else sees outside your network.
Your Wan address is the one that your ISP issues you so that you can use the internet and this address is given to your router. each computer inside your network then has its won address.

The 192.168.1.1.. is the router ip isn't it?

That should be the Windows IP address.

goofball
Aug 11th, 2007, 09:58 PM
Your friend can't ping to you because you do not have a IP address. The 192 IP address you have is the Windows XP PRO default (I'm not sure if the 192 IP is default for all version of Windows as well as on other versions of XP beside Pro). I get the same IP many times, usually when I reformat my Windows XP Pro SPK-1 Hard drive

Windows doesn't have a "default" IP address. 192.168.x.x is a Class C reserved private address space. Much like 10.x.x.x is a Class A address space.

Thing is, if the OP had given then their internal IP address to someone outside of their network, the other person would not even get close to the other person's network. The other computer would not understand how to get to 192.168.1.1 or any class C address since that address space (192.168.x.x) is private and not for use on a "public" network like the Internet.

haveblue
Aug 11th, 2007, 10:04 PM
Windows doesn't have a "default" IP address. 192.168.x.x is a Class C reserved private address space. Much like 10.x.x.x is a Class A address space.

Thing is, if the OP had given then their internal IP address to someone outside of their network, the other person would not even get close to the other person's network. The other computer would not understand how to get to 192.168.1.1 or any class C address since that address space (192.168.x.x) is private and not for use on a "public" network like the Internet.

You are correct.

The OP posted that
d226-9-129.home.cgocable.net [24.226.9.129] is the last spot his friend can trace to, and is only one hop away from him. The one router between them is what's causing problems. Whoever owns that (probably an ISP) will have to change that. Not to mention that his router most likely has ping response shut off.

gman
Aug 11th, 2007, 10:15 PM
Nah man I know what I'm talking about
.....
That should be the Windows IP address.

LOL.

gman
Aug 11th, 2007, 10:21 PM
OP's friend tried to tracert to 24.226.9.129 and the last stop was 24.226.8.198.

However, OP's own tracert to his friend indicates his external IP address may be something else. Note that his tracert did not go through either 24.226.9.129 or 24.226.8.198.

Of course, OP might doctored the IP addresses of the tracert output for privacy issue.

pandaharo
Aug 12th, 2007, 12:45 AM
have you tried turning off your windows firewall or the router's firewall?

siriuskao
Aug 12th, 2007, 01:15 AM
Nah man I know what I'm talking about



You are somewhat correct their. Everyone does have a IP address, which you are correct. However where you are wrong is where you say if the have a ISP. You have a IP address. Windows comes with its own IP address which is the 192.162 IP address that the user is connected to. There 2 types of IP address. 1 for the computer itself = e.g. 192.168.1.0, and the other for the internet = e.g. 220.xxx.xxx.x.
The 192.x.x.x is your private local address. The 220.x.x.x is your public address. The basic function of a router is to connect two networks; in this case the internet and your private network. When you check your IP address within your network, you see your actual computer's private address. When you check it online, you see your WAN address, as that's what everyone else sees outside your network.
Your Wan address is the one that your ISP issues you so that you can use the internet and this address is given to your router. each computer inside your network then has its won address.



That should be the Windows IP address.

wait, on my linux box I have 192.168.x.x IP address assigned......does that mean I am infected with Windoze virus!? nooo... ;)

Dethredic
Aug 12th, 2007, 11:48 AM
wait, on my linux box I have 192.168.x.x IP address assigned......does that mean I am infected with Windoze virus!? nooo...

He he he.... Yaaaaaaaaaa

I think it is something to do with the modem. I have turned off all firewalls and pulged my comp directly into the modem (didn't use the router) with no success.

ullyeus
Sep 2nd, 2007, 09:02 PM
He he he.... Yaaaaaaaaaa

I think it is something to do with the modem. I have turned off all firewalls and pulged my comp directly into the modem (didn't use the router) with no success.

It`s much more likely you still have a firewall on, did you turn off the Windows default firewall in addition to any other one`s you installed?

Are you sure it's a modem and not a modem/router (combined).


Nah man I know what I'm talking about




you have no idea what you are talking about.

Gee
Sep 2nd, 2007, 09:18 PM
Well, your first problem is NAT, it appears you have two routers.

Why are there two gatways? 192.168.2.1 and 192.168.1.1

This is from your tracert dump.

The second problem, you have to define your IP in the router and forward the port for VNC.

Once you do that, your friend will be able to connect to you.

But since there are two routers. You have to go to the edge router and define the other gateway in the DMZ. Then go to the second router and set the port for VNC to forward to your computer IP.

As for IoannI, he is clueless.

ullyeus
Sep 2nd, 2007, 09:35 PM
Why are there two gatways? 192.168.2.1 and 192.168.1.1



I asked the question but I bet he had a modem/router provided by his ISP.

Gee
Sep 2nd, 2007, 09:51 PM
If that is the case, he is better off plugging his DSL modem into port 4 of his router instead of the WAN port and use the router as a switch.

It has to be DSL, because cable modems do not have routers built in (Not with Rogers). But he mentioned Cogeco. So it is hard to tell.