Ping to other PCs but not the router

[hguhon]

I have a small home network with a wirless router, two wired PC's and two wireless notebooks. Two wireless notebooks and one wired PC are working fine and one PC has connection problem.

On that PC, I can successfully ping all other computers but not the router. I do "pin 192.168.2.1" and got "timed out". I can transfer files among the "bad" and "good" computers, but the bad computer can not access the internet. It seems like a local configuration problems, but I don't know how to solve it.

Any help are greatly appreciated.

 

[DelJo63]

most routers have a setting for responding to ping -- usually it is applied ONLY
to the WAN side (ie: public).

in addition, firewalls also have a setting for ping (or ICMP).

If Print/File sharing is working, you can forget the ping issue.
Not responding to pings is thought to enhance your security (albeit, only very slightly)

 

[Nodsu]

What is the IP configuration of the problematic computer? Maybe post the "ipconfig /all" output of one of the "good" machines and the problematic one.

 

[hguhon]

More details about the configuration

All the computers are connected to one route either wired or wirelessly.

Three "good" machines all can access to each other to the internet and ping to the route, and the "bad" PC.

The "bad" PC can exchange files and ping to other machines. But it fails to access to internet and ping to the route. This machine has no anti-virus program running and firewall is disabled.

=============
Here are from "good" PC.

Good:>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Belkin
IP Address. . . . . . . . . . . . : 192.168.2.121
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Good:>ping 192.168.2.2 ("bad" PC)

Pinging 192.168.2.2 with 32 bytes of data:

Reply from 192.168.2.2: bytes=32 time<10ms TTL=128
Reply from 192.168.2.2: bytes=32 time<10ms TTL=128
Reply from 192.168.2.2: bytes=32 time<10ms TTL=128
Reply from 192.168.2.2: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Good:>ping 192.168.2.1 (route)

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=2ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

==================
Here are from "bad" PC.

Bad:>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Belkin
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Bad:>ping 192.168.2.121 ("good" PC)

Pinging 192.168.2.121 with 32 bytes of data:

Reply from 192.168.2.121: bytes=32 time=1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128
Reply from 192.168.2.121: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Bad:>ping 192.168.2.1 (route)

Pinging 192.168.2.1 with 32 bytes of data:

Request timed out
Request timed out
Request timed out
Request timed out

 

[vintwala]

Hey,

Does applying a static ip address work?

 

[DelJo63]

ALL the IP addresses are fine -- static does not change the outcome!!!

Each IP is in the subnet 192.168.2.* so there is no routing issue.
The subnet mask is 255.255.255.0, but it's not shown for the bad pc.
run ipconfig /all on the 'bad pc' and make sure the subnet mask is the same.

your issue is the firewall on the 'bad pc'. It is blocking the ICMP protocol.

 

[Nodsu]

This is odd indeed.. Maybe look over all the security and firewall settings on the router and make sure that there are no MAC address filters or fake MAC addresses or anything similar.

 

[DelJo63]

let's talk concept; pinging your own router will not help solve anything so why fuss over it?

Pinging your ISP's gateway or DNS address will ensure that you can at least get to the ISP.
If your PCs can share files and printers, I suggest you forget the 'ping router' as it is a non-issue.

 

[hguhon]

The problem is "I can not access internet"

Thanks for all the suggestions and help.

The problem for me is that the "bad" PC can not access to internet. It can share files and printers with all the machines connected to the same route. Fire wall is turned off and no anti-virus program is running on this PC.

How can I know/ping my ISP's gateway or DNS address? I am using optimum on line as my ISP.

Thanks.

 

[DelJo63]

AH! this is a very different symptom.

From a good PC, access the router address in your browser just as if it were
a URL, login.

Look for a link or tab that will report WAN side or Status.
You will find your public IP address (ie not like 192.168.x.x)
and the Default Gateway -- this is what you want to ping.

Now you can use this address to test your access to the Internet via your ISP connection anytime you wish (it will remain reasonably constant).

logoff the router and repeat this on the BAD pc -- if you can access the router
config page but not the Internet, then the DNS settings on the bad pc are in question.

 

[hguhon]

The "bad" PC can not access internet

I got the Wan IP and the default gateway IP from my route config. From a "good" PC, I can ping both Wan IP and default gateway with no problem. But I got requested time out when I tried on "bad" PC.
I switched the cable. The good is still good and the bad is still bad. So I am prety sure the problem is local on the "bad" PC.
Because I can exchange files between "good" and "bad" PC, I think the TCP/IP level is ok.

Also, I can not accesss to the route (through 192.168.2.1)

 

[DelJo63]

As you have access from sysA-sysB regardless of the symptom,
I assert your firewall is blocking ICMP and ping does not matter.

 

[hguhon]

How can I check my firewall setting?

How can I check my firewall setting?

I disabled my firewall through
control panel -> network connection -> local area network (properties) -> Internet protocol -> properties
and unchecked firewal check box.

Anywhere else should I check?

 

[DelJo63]

which FW are you using?
cp->Windows Firewall is the preferred means to disable the default FW.

Comodo is disabled directly via the System Tray right-click->exit

 

[Samstoned]

change the bad ip address of 192.168.1.2
to 192 168.1.200
check your dhcp setup in router it really should not interfer but it may show address range above 100
then if you can connect its something about the 192.168.1.2 thats not working in router NAT