The Jokers
Thema drucken
01.12.2017 14:49
|
This isn't my strong suit but today I attempted to change the subnet mask on our dhcp servers from a /23 to a /22. A week ago, I did some internal testing using static IPs with the new netmask set on them on different machines and tested their ability to communicate and everything looked good. About a week ago, I set the lease time to an hour to get ready for the netmask change. When I made the change today, I purposefully did not hand out the new subnet in the scope since the new IPs are just going to be set statically for internal testing with new equipment for now. I thought everything went well since I was able to release/renew my settings on my computer, was getting the new /22 mask, and was able to communicate with all equipment. The guy next to me lost the ability to go out to the internet and could not reach our local exchange server or any other server resources. He was being handed the new /22 mask just like me. Another co-worker next to me had no issues, but various people in the building kept calling saying they could not access server resources. I'm wondering what I did wrong here, why it was working for some users but not others. Again, this isn't my strong suit but I thought this was a relatively straight forward procedure. Any help would be appreciated, thanks. I reverted the changes until I can figure out why this happened. |
|
Antworten
