cgunix
asked on
Sudden loss of ping
We have a mature network, and fairly plain vanilla. 200 Pcs, 15 servers.
I'm the sys admin.
I've found 5 static IPs I cannot ping from my PC; everything else I can ping. I don't recall this problem before. (My PC has a dynamically assigned IP)
I rdp into a server; that server can ping these 5 IPs (and anything else I try)
Where do I start looking to solve such an odd problem?
I have Win 7, we have Win 2003 and Win 2008 servers.
All machines mentioned are on 192.168.150.nnn
Static IPs are 150.55 and down. DHCP scope is 150.56 and up (into 151.200)
(Possibly red herring; we have a current problem with a switch, causing BAD_ADDRESS lines to fill up the DHCP scope. Sometimes we delete them if a user can't get on, and they then get on. Doesn't seem to affect loged-on users. We're working on it. I'm confident my non-ping problem pre-dates this.)
Thanks
Larry
I'm the sys admin.
I've found 5 static IPs I cannot ping from my PC; everything else I can ping. I don't recall this problem before. (My PC has a dynamically assigned IP)
I rdp into a server; that server can ping these 5 IPs (and anything else I try)
Where do I start looking to solve such an odd problem?
I have Win 7, we have Win 2003 and Win 2008 servers.
All machines mentioned are on 192.168.150.nnn
Static IPs are 150.55 and down. DHCP scope is 150.56 and up (into 151.200)
(Possibly red herring; we have a current problem with a switch, causing BAD_ADDRESS lines to fill up the DHCP scope. Sometimes we delete them if a user can't get on, and they then get on. Doesn't seem to affect loged-on users. We're working on it. I'm confident my non-ping problem pre-dates this.)
Thanks
Larry
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@cgunix - Thanks for the update and I was happy to help.
ASKER
A while ago we were running close on IPs for DHCP to hand out. We'd been using ...150.nnn and we added ...151.nnn. To accomplish this we changed the subnet mask from 255 in the third octet to 254. DHCP passed this new subnet out.
Most often my PC would happen to get an IP in the 150.nnn range - things worked fine.
My ping problem occurred when the DHCP flooding caused me to get an IP in the 151.nnn - range. I was still generally OK as far as general work went.
The ping problem occurred when I tried to connect to machines that were statically assigned an IP __** AND **__ whose subnet mask I had neglected to change. Those machines didn't know how to get back to me with the ping results.
As soon as I went into a machine and corrected the subnet mask, ping worked.
Thanks for you help. I appreciate this forum.