Activating DHCP Scope Error

[columbiavol]

Sorry for all the questions. I got thrown into this fire this week with very little AD knowledge. I got a good book that I will spend the entire weekend studying. In the meantime, I appreciate your help and patience with me.

I created DHCP scopes. I tried to activate them but I get "DHCP-Acces Denied". I am logged in as the Administrator. The Administrator is in the Domain Admins, DHCP Admins, Admins group. Any suggestions?

 

[Jpoandl]

Not sure...look in the Event Viewer logs for more detail on the error.

Things to check:

1) Make sure that your DHCP is authorized in the domain. After you install DHCP, you must authorize the server service. Right click the DHCP server in DHCP manager and authorize.

2) Also make sure that no other DHCP services are turned on in remote devices (routers or other DHCP servers). If a conflict is detected, your DHCP service may turn off. You can temporarily islolate the Windows 2003 network to test this.

-hope this helps...

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[mlichstein]

The administrator should also be in the Enterprise Admins group, which is required to authorize a DHCP server in the domain.

 

[columbiavol]

I meant to say authorize the DHCP scopes instead of activate them. When I look for groups to join, I do not see Enterprise Admins. I'm still getting the Access is denied error when tryinmg to authorize the scopes.

 

[mlichstein]

Enterprise Admins is in the users container in AD users and computers. Double-click on the group, go to the members tab, and add your account.

 

[columbiavol]

There is no Enterprise Admin group listed anywhere in AD. We are a child domain. I'm wondering if the parent domain has to do somethng so we can authorize the DHCP scopes.

 

[mlichstein]

Yes. The enterprise admins group is located in the parent domain. Someone who is a member of that group will need to authorize your DHCP server.

 

[columbiavol]

Turns out the problem was the parent domain needed to open some ports on their router and edit an access list to allow open communication from the child to the parent. Good info to know for the future.