Link to home
Start Free TrialLog in
Avatar of KMDComp
KMDCompFlag for United States of America

asked on

DHCP server not responding on 2008 sbs

Over the weekend I copied our 2008 sbs VM's VHD from one hyper-v server to another with more memory.  Everything seemed to be working fine when I left on Saturday and most things are still working fine.  However, any machines  that were turned off over the weekend or that I hook up to the network today can't get an address assigned through DHCP.  

I've confirmed that the service is running and if I assign the machine a static IP, it can ping and access the server normally.

I’ve restarted the service several times.  

I've also used wire shark to confirm that the DHCP discover requests are being received from a machine with the correct hardware address.

I've also fired up the resource and performance monitor so I could see what the DHCP server is doing while a machine is requesting an address, it does not show any activity at all.  

Nothing relevant is showing up in the event logs either.

Suggestions?
SOLUTION
Avatar of marine7275
marine7275
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of KMDComp

ASKER

I just tried to unauthorize it and got a popup that said "the parameter is incorrect"
Avatar of KMDComp

ASKER

More info:  

After doing a search on that error, it indicated that it might be caused by a problem with the bindings to the network interface.  I tried to check the bindings, but the list is blank and the server does have a static IP address.  I think we can call that the cause of the nonresponsive DHCP server, but how do we fix it?  
ASKER CERTIFIED SOLUTION
Avatar of Krzysztof Pytko
Krzysztof Pytko
Flag of Poland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of KMDComp

ASKER

Thanks.  Can't reboot the server until tomorrow morning, I'll try it then.  
Avatar of KMDComp

ASKER

It's fixed.  I tried to run the "connect to internet" wizard again which failed because of a dhcp problem.  When I checked dhcp again, it was bound to the virtual network adaptor with the correct IP.  Clients are now able to get dhcp issued IP's again.  

 
Avatar of KMDComp

ASKER

marine7275 got me started down the right path and iSiek gave me the idea to try and run the wizard again.  I think restarting would have worked too.