Solved one computer on subnet will not ping through router

May 30, 2018 at 09:34:38
Specs: windows 7 pro
One comp (windows 7) will not ping through router from address192.168.1.66 to 192.168.4.62. Subnets are connected with netgear VPN routers. When I run tracert, the first leg sends the message to router 192.168.2.1 instead of the correct gateway of 192.168.1.1. All other computers on all subnets work fine except this one. I have been looking for a bad setting but can find nothing. Help

message edited by billbrower


See More: one computer on subnet will not ping through router

Report •

#1
May 30, 2018 at 09:40:43
The default router on the computer must be set wrong.

Report •

#2
May 30, 2018 at 09:48:22
you would think so. I have checked the IPV4 settings multiple times and it is 192.168.1.1. for the default gateway. I don't know anywhere else to look hat would cause it to point to a different subnets router. Also all internet services work normally. PING just times out, and tracert times out trying to rebroadcast from 192.168.2.1. Additionally, if I ping all my routers from this computer, 192.168.2.1 is successful. 192.168.3.1, 192.168.4.1, and 192.168.5.1 all fail with time out. If I ping 192.168.1.66 from 192.168.4.3 it is successful. All windows firewalls are turned off.

message edited by billbrower


Report •

#3
May 30, 2018 at 11:12:13
✔ Best Answer
1) Did this PC work properly at one time?
2) If yes, was anything changed on it before it stopped working?
3) Is this the only PC having problems communicating across routers?
4) Are you using DHCP on each subnet, or static assignments?

I'm forced to assume a couple of things. One, that all subnets are /24 and two, that there's a router at 192.168.1.1 and the traffic from 1.66 passes through it. Correct?

Assuming the above is right...............

Additionally, if I ping all my routers from this computer, 192.168.2.1 is successful. 192.168.3.1, 192.168.4.1, and 192.168.5.1 all fail with time out. If I ping 192.168.1.66 from 192.168.4.3 it is successful.

Do you get a response from any clients on the 192.168.2.0/24 subnet located behind that firewall? Since you are getting a response from 2.1 but not the other routers, it seems like it should be an issue with the router at 1.1 (ie: bad routes to the other subnets that aren't responding) But if it were, I would have to think it would affect all clients on the 1.1 subnet, not just the one. Have you checked all other clients on 192.168.1.0/24?

Has anybody changed anything on the router at 1.1?

If all other clients are working properly then I think you should try wiping the present config from the problem PC's network interface. I'd do that and then reboot and redo the configuration.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

message edited by Curt R


Report •

Related Solutions

#4
May 30, 2018 at 12:32:23
thank you. That's what I thought the next step might be. Yes, all other clients on the 1.0 subnet (14 of them) all communicate fine to any other subnet. This only showed up when I was configuring a printer on the 4.0 subnet to print from 1.66 and it couldn't find the printer. I just went back and remotely logged on to 1.66 from a computer on the 4.0 subnet(I am physically at that site) that I had configured to print on the 4.62 printer months ago. That print path still works to print a test page (it is 192.168.4.62 redirected from 1.66) After printing the test page to 4.62 I did a tracert from 1.66 to 4.62 and it went off chasing 2.1 and timed out without successfully pinging it. I will reconfigure the network adapter and see if it works. I will wait till morning when I am at that site, as I do not want to reconfigure my adapter remotely.

message edited by billbrower


Report •

#5
May 31, 2018 at 06:35:33
it's fixed but I'm not sure why. Reconfigured the adapter, same problem. I then reconfigured to a dynamic IP and everything worked. Could not get it to work with a static IP. After messing with it for an hour, I found that if I listed the default gateway as the 1st DNS server (DNS is disabled on this router, as server 192.168.1.2 is my DNS server) and listed the actual DNS server as the 2nd DNS server, everything works. All other clients in my network are configured with the actual DNS server as the 1st DNS server and they work fine. I will probably never know why this one is different but I am going to work on other problems. Thanks for the idea that headed me in the right direction Curt R..

Report •

#6
May 31, 2018 at 06:48:18
Always a pleasure to help and I'm glad you got it working. Also, thanks for posting what did work.......with luck it may help somebody else in the future!

If you'd like, I could possibly help troubleshoot this further. It would require either a good diagram of your network with the config's for each routers, or just a text document detailing this info. Router config's should include DHCP server settings, DNS/Default Gateway settings and any/all static routes. If you're going to send a flat text document, include how each router interconnects. (ie: 1 is connected to internet and all others connect to 1, etc)

This still sounds like it has to be a configuration issue on the problem PC as all other clients in that same subnet are working properly.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question