|
lordimpaq (m)
|
i know it might sound crazy, i know how to authorize a DHCP server, i've done it countless times,
but for some reason this particular server doesn't assign ip addresses to clients
when u authorize it says its authorized but when u still click on the DHCP page it says you have to authorize,
it baffles me, please help.
|
|
|
|
|
|
uspry1 (f)
|
Google it finding "Not Authorized DHCP server".
|
|
|
|
|
|
Maleeq (m)
|
@lordimpaq
From your statement, I feel the DHCP server you are trying to authorize is a stand-alone server. Is that right?
Well, if that is true, then you should know that Stand-Alone or Workgroup DHCP servers (running Windows 2000 or 2003 server) CANNOT become authorized in Active Directory network. They can still coexist with these networks as long as they are not deployed on a subnet with any authorized DHCP servers. This is not a good setup and should be avoided. Such servers are termed "Rogue Servers".
This is what is happening, when a rogue server detects an authorized server on the same subnet, it automatically stops its own DHCP service and stops leasing IP addresses to clients. As such, try all you may, it wont be authorized and wont lease IP in these scenarios.
Cheers!
|
|
|
|
|
|
yemibee (m)
|
@ uspry1 its like you just compounded the guys problem by sending him to doom  . Well, if i understand the problem, i guess you ought to first install Active Directory and if its a standalone server like Uspry1 rightly said, you should make it Domain Controller then you can reinstall DHCP and Authorize within the domain, also note that if you might need to install DNS and make it your primary DNS, else you would have some problems with Vista. Cheers, hope it works for you. |
|
|
|
|
|
yemibee (m)
|
 was actually refering to Maleeq
|
|
|
|
|
|
uspry1 (f)
|
@ uspry1 its like you just compounded the guys problem by sending him to doom . Well, if i understand the problem, i guess you ought to first install Active Directory and if its a standalone server like Uspry1 rightly said, you should make it Domain Controller then you can reinstall DHCP and Authorize within the domain, also note that if you might need to install DNS and make it your primary DNS, else you would have some problems with Vista. Cheers, hope it works for you. @yemibee At first i scratched my head what you talked about!  Oh you referred to Maleeq has said it all! was actually refering to Maleeq LOL! That's okay! Understandable!  |
|
|
|
|
|
Maleeq (m)
|
@ uspry1 its like you just compounded the guys problem by sending him to doom . Well, if i understand the problem, i guess you ought to first install Active Directory and if its a standalone server like Uspry1  Maleeq rightly said, you should make it Domain Controller Since he mentioned authorization, I believe he's working in an Active Directory environment already. No need to re-install active directory services. Now, its not a most that DHCP servers be Domain Controller or Back Up Domain Controllers. Any domain member server (File, Print, Mail, Application servers) can run DHCP services too. also note that if you might need to install DNS and make it your primary DNS, else you would have some problems with Vista.
By implication, do you suggest installing DNS services on all DHCP servers? I don't think that is necessary if he already has a DNS server correctly configured on the domain. |
|
|
|
|
|
|
|
lordimpaq (m)
|
why would i want to authorize with a "rogue server" in the first place,
the server i'm trying to authorize is a secondary domain controller, i've got 4 domain controllers, in three different locations,
and they all replicate to each other,
the DNS server is okay, and believe me, i've tried everything technet could offer, but they didn't work,
i'll just have to re install the server operating system,
|
|
|
|
|
|
Maleeq (m)
|
Well, something is wrong (With the system or your configuration). When DHCP services is installed on a Domain controller, it gets AUTOMATICALLY authorized once you have a scope defined.
|
|
|
|
|
|
lordimpaq (m)
|
what i'm saying is that it stopped working all of a sudden, it was working before,
then i checked the event viewer to see that it had something to do with the DNS
and apparently the server could communicate with the DNS server, and yet it could not authorize despite frequent rebooting of the server
|
|
|
|
|
|
![Nairaland [Nigerian Forum] Home](http://www.nairaland.com/Themes/default/images/english/home.gif)
Author
