asked on dhcp not working
Our DHCP server on SBS 2011 is not performing properly, on few workstations its not assigning the IP address, we have tried to reset the network card on workstations but they are able to obtain any IP and the workstation is set to public network for some reason, all was good earlier but this morning this suddenly happened to 3 of our workstations.
also on the workstation network adapter I saw its able to send data but receive is 0
also on the workstation network adapter I saw its able to send data but receive is 0
SBSDHCPNetworking
Last Comment
John
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
How exactly is your network laid out? However, I'd be checking the number of DHCP addresses available for lease, along with the length of leases that's set as well. I'd also check to see if there any issues with your network equipment.
If you are having DHCP issues, one quick check to rule out a problem is to check DHCP is running.
It may sound silly at first, but sometimes people plug in another device doing DHCP such as a router from home. If this happens, Windows DHCP sees that another DHCP is running and stops. (with an event inthe event log that is easy to skip past)
Then wither the rogue dhcp is removed when the user realises they can't do what they wanted, leaving you clueless, or it gives out IP addresses possibly on a different subnet.
PC's that already have a lease may continue to use it, leading you to think DHCP is running when it isn't.
so just a quick check that DHCP is running is a good idea. Just open DHCP console and see if there is a red X
It may sound silly at first, but sometimes people plug in another device doing DHCP such as a router from home. If this happens, Windows DHCP sees that another DHCP is running and stops. (with an event inthe event log that is easy to skip past)
Then wither the rogue dhcp is removed when the user realises they can't do what they wanted, leaving you clueless, or it gives out IP addresses possibly on a different subnet.
PC's that already have a lease may continue to use it, leading you to think DHCP is running when it isn't.
so just a quick check that DHCP is running is a good idea. Just open DHCP console and see if there is a red X