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
LVL 6
Sid_FAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
ChrisConnect With a Mentor Commented:
The client doesn't know which to use, it just sends out a broadcast request and waits for a reply from whichever DHCP server replies first.

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.
0
 
ChrisCommented:
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.
0
 
Sid_FAuthor Commented:
ok but if I have a client joined to a domain which has an authorised dhcp server how will the client know to only use that dhcp server.
0
All Courses

From novice to tech pro — start learning today.