DHCP Fiasco - 02/17/06 12:51 AM
Well today was a fun day at work. Today my boss comes running up to me telling me that the network is down. I go and check out the DSL Modem and see that everything seems to be fine. I get another call from someone else making the same claim. So I decide to go check it out.
Turns out overnight a group of computers decided to go from this:
IP: 192.168.1.x
Subnet: 255.255.255.0
Gateway: 192.168.1.1
To
IP: 10.0.1.x
Subnet: 255.255.255.0
Gateway: 10.0.1.1
After manually setting a few computers I was able to get everything back online. I then checked the DHCP settings of our lovely Westell 2200 Modem. Ofcourse all the settings were correct and everything seemed to be inorder. Two Service calls to Verizon brought forth no results, though I kinda realized I was screwed when one of the fixes was to turn off the PPPoE connection, and that they wanted to know the IP address of the Hub... This was after many attempts to get the computers to actually get an IP addy from the DHCP server. They all keep going back to the 10.0.1.x addresses.
I know I probably missed something and spent awhile combing the 'net. So like what's the deal?
Turns out overnight a group of computers decided to go from this:
IP: 192.168.1.x
Subnet: 255.255.255.0
Gateway: 192.168.1.1
To
IP: 10.0.1.x
Subnet: 255.255.255.0
Gateway: 10.0.1.1
After manually setting a few computers I was able to get everything back online. I then checked the DHCP settings of our lovely Westell 2200 Modem. Ofcourse all the settings were correct and everything seemed to be inorder. Two Service calls to Verizon brought forth no results, though I kinda realized I was screwed when one of the fixes was to turn off the PPPoE connection, and that they wanted to know the IP address of the Hub... This was after many attempts to get the computers to actually get an IP addy from the DHCP server. They all keep going back to the 10.0.1.x addresses.
I know I probably missed something and spent awhile combing the 'net. So like what's the deal?