Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.
Course Of The Month
6 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
DHCP server on Windows network
Posted on 2013-05-29
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
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
3 Comments
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.
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.
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.
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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten.
The USB drive must be s…
This Micro Tutorial hows how you can integrate Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease.
The following video show how to bind OSX Mavericks to …
Suggested Courses
Course of the Month6 days, 1 hour left to enroll
Earn Certification
MCSA Configuring Windows 7 Exam 70-680
$49.00$44.10
707 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.