DHCP server on Windows network
What is the point in authorising a Windows DHCP server. If I have client machines joined to a domain, they will obviously retrieve DHCP addresses from the authorised DHCP server. If someone puts a rogue DHCP server on the network will my client machines get an IP from the rogue machine or how should I stop this. thanks
Asked:
Who is Participating?
These pages explain DHCP server authorisation pretty well.
http://technet.microsoft.com/en-us/library/dd296633%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/cc737140%28v=ws.10%29.aspx
It basically prevents unwanted Windows DHCP servers from running on your network. Unfortunately this doesn't apply to non-windows DHCP servers so it's usefulness is somewhat limited.
http://technet.microsoft.com/en-us/library/dd296633%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/cc737140%28v=ws.10%29.aspx
It basically prevents unwanted Windows DHCP servers from running on your network. Unfortunately this doesn't apply to non-windows DHCP servers so it's usefulness is somewhat limited.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
The way it works is that when a Windows DHCP server starts up, it checks if it's authorised. If its not authrorised then it won't serve any clients. This way, in theory, the only DHCP servers that are active will be ones you've authorised in AD.
As i mentioned above though, non-windows DHCP servers don't check for authorisation, so this is only effective at preventing rogue Windows DHCP servers.