DHCP Client

[kevin_lane]

weird one trying to start the DHCP Client Service and getting access denied however my first domain controller has the service started and in SCOM everything is ok, however my second DC has an issue with the DHCP Client Service I’m getting access denied

 

I have gone through the registry on the first domain controller and replicated the exact same permission on the dhcp reg folder and the tcpip reg folder and still I get the same access denied error I have checked the local security policy > user rights assignments and everything is exactly the same and i still get the same message when i try to start the dhcp client service.

 

all of my 3 domain controllers have static ip address and all are DNS servers the only server that is handling dhcp request is my first domain controller

 

any ideas would be grateful

[Michael]

You don't need the DHCP Client running on your server, only DHCP Server on the one server (in this case). You could disable DHCP Server on the other two servers.

 

DHCP Client receives IPs, DHCP Server dishes out IPs.

[kevin_lane]

are you sure becasue it is acting as a dns server does it not have to update dhcp request for dns

[Michael]

Yes I am certain you don't need it. What the description's saying is if you had an IP from DHCP Server (via DHCP Client on a workstation), it also registers this in DNS. Seeing as you have static IPs you don't need it.

 

Each workstation also has the DHCP Client service to receive IPs from DHCP Server and register in DNS.

[SHimmer45]

DHCP client on the server performs the DDNS updates

[kevin_lane]

thats what i thought so am i right?

[SHimmer45]

i wouldnt disable it

[Michael]

I was under the impression the DHCP Client on the workstation did the DDNS updates by talking directly to the DNS Server.

 

If you used a dynamic IP on a server, then its own DHCP Client would do DDNS updates but just for itself.

[Geoff]

Either the DHCP client on the client updates the DNS records on the DNS server or the DHCP server updates the DNS records on the DNS server on the clients behalf. The DHCP client running on the server has nothing to do with this at all.

[Michael]

Either the DHCP client on the client updates the DNS records on the DNS server or the DHCP server updates the DNS records on the DNS server on the clients behalf. The DHCP client running on the server has nothing to do with this at all.

 

Exactly what Geoff said, just explained better than me!