XP Can be Pinged, But XP can't Ping

My Unix machine can ping my XP no problem, But when I try to ping my Unix box from XP. . . Nothing. Any Idea where to start looking? It's a Simple network setup Unix 199. 199. 199. 5 XP 199. 199. 199.

Windows Networking 2246 This topic was started by ,


data/avatar/default/avatar17.webp

1 Posts
Location -
Joined 2003-03-04
My Unix machine can ping my XP no problem,
But when I try to ping my Unix box from XP... Nothing.
Any Idea where to start looking?
It's a Simple network setup
Unix 199.199.199.5
XP 199.199.199.6
The XP, under connection status has no default gateway, and is connected
The xp also has an other network card, so i disabled that connection incase it was causing the problem.
Any direction would be great. Thank you

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar19.webp

690 Posts
Location -
Joined 2000-05-21
Some obvious things to check:
 
Subnet mask set correctly on the XP machine? (eg. 255.255.255.0)
Some kind of firewall running on the Unix machine? (might be deliberately set to block pings)

data/avatar/default/avatar07.webp

1 Posts
Location -
Joined 2003-03-04
I got a Question. 199.199.199.* on and internal network? I've never seen that range used before. You learn something new all the time.
 
try one of these instead.
10.0.0.0 — 10.255.255.255
169.254.0.0 — 169.254.255.255
172.16.0.0 — 172.31.255.255
192.168.0.0 — 192.168.255.255

data/avatar/default/avatar28.webp

530 Posts
Location -
Joined 2001-10-09
Quote:I got a Question. 199.199.199.* on and internal network? I've never seen that range used before. You learn something new all the time.

try one of these instead.
10.0.0.0 — 10.255.255.255
169.254.0.0 — 169.254.255.255
172.16.0.0 — 172.31.255.255
192.168.0.0 — 192.168.255.255

I use 100.100.100.100 and 100.100.100.200 for my w98 / XP,Linux machine. I know 192.*.*.* is what is recomended to use but my network runs with no problems. What can go wrong if you use other internal network addresses. Does it harm anyone or can it interfere with the internet. For example what if I use 216.239.35.100 (Google) will it interfere?

data/avatar/default/avatar19.webp

690 Posts
Location -
Joined 2000-05-21
Quote:Quote:I got a Question. 199.199.199.* on and internal network? I've never seen that range used before. You learn something new all the time.

try one of these instead.
10.0.0.0 — 10.255.255.255
169.254.0.0 — 169.254.255.255
172.16.0.0 — 172.31.255.255
192.168.0.0 — 192.168.255.255

I use 100.100.100.100 and 100.100.100.200 for my w98 / XP,Linux machine. I know 192.*.*.* is what is recomended to use but my network runs with no problems. What can go wrong if you use other internal network addresses. Does it harm anyone or can it interfere with the internet. For example what if I use 216.239.35.100 (Google) will it interfere?
This is exactly the reason. If your IP address happens to be the same on your LAN as a site on the Internet and your LAN is connected to the Internet (NAT, ICS etc) then you (and anyone else on the same LAN) will be unable to reach the Internet site.

In fact, due to the way subnetting works, you'd be unable to access any computer on the Internet with an IP in the range 100.100.100.0 - 100.100.100.255 ("best case scenario" assuming a subnet mask of 255.255.255.0).

The IP ranges Captwista mentioned are reserved for Local Area Networks and so will be guaranteed never to cause such a conflict.