Stopping DHCP CLIENT on DC's and Exchange servers

  • Thread starter Thread starter Joe_SMS
  • Start date Start date
J

Joe_SMS

Where's the WARNINGS and flashing red lights about this ? Had someone
troubleshooting a problem on a DC notice that the dhcp client service
was running and thought he read somewhere that it could be a problem.
He then proceded to manually stop the service on multiple DC's and
Exchange servers.


When he did so, the DNS records disappeared for these boxes and the
entire network was basically down. What is the caveat with this ? Does
stopping the DHCP client service actually UNREGISTER DNS records ?
What am I missing ? Even called Microsoft and they couldn't even tell
us for sure that stopping that service on DC's would have this drastic
of an effect. Starting the DHCP service on all of the boxes got us
back up again but......


......I want the LONG VERSION of this story please....


Thanks much.
 
In
Joe_SMS said:
Where's the WARNINGS and flashing red lights about this ? Had someone
troubleshooting a problem on a DC notice that the dhcp client service
was running and thought he read somewhere that it could be a problem.
He then proceded to manually stop the service on multiple DC's and
Exchange servers.


When he did so, the DNS records disappeared for these boxes and the
entire network was basically down. What is the caveat with this ?
Does stopping the DHCP client service actually UNREGISTER DNS records
? What am I missing ? Even called Microsoft and they couldn't even
tell us for sure that stopping that service on DC's would have this
drastic of an effect. Starting the DHCP service on all of the boxes
got us back up again but......


.....I want the LONG VERSION of this story please....


Thanks much.
Click to expand...

There's no long version, just the short. This service is an ABSOLUTE
requirement whether the machine is a DHCP client or has a static IP. It's
THE resolver service and provides DNS dynamic registeration. Period.

Q268674 - No DNS Name Resolution or Registration Occurs If DHCP Client
Service Is Not Running:
http://support.microsoft.com/?id=268674

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
Where's the WARNINGS and flashing red lights about this ? Had
someone
troubleshooting a problem on a DC notice that the dhcp client
service
was running and thought he read somewhere that it could be a
problem.
He then proceded to manually stop the service on multiple DC's
and
Exchange servers.


When he did so, the DNS records disappeared for these boxes
and the
entire network was basically down. What is the caveat with
this ? Does
stopping the DHCP client service actually UNREGISTER DNS
records ?
What am I missing ? Even called Microsoft and they couldn't
even tell
us for sure that stopping that service on DC's would have this
drastic
of an effect. Starting the DHCP service on all of the boxes
got us
back up again but......


......I want the LONG VERSION of this story please....


Thanks much.
Click to expand...

the netlogon service registers SRV RRs

I assume you are talking about the A and PTR records of DCs?

Read more at:
http://www.microsoft.com/technet/pr...elp/cb7a2363-0ed6-4c7c-87ba-7cc9592a8028.mspx
 
In
Jorge_de_Almeida_Pinto said:
the netlogon service registers SRV RRs

I assume you are talking about the A and PTR records of DCs?

Read more at:
http://www.microsoft.com/technet/pr...elp/cb7a2363-0ed6-4c7c-87ba-7cc9592a8028.mspx
Click to expand...

Jorge, actually that's correct about the Netlogon service performing the
registration, but the poster was referring to why stopping the DHCP Client
Service disabled registration, and that's because the Netlogon service,
along with simple registration and hostname resolution absolutley relies on
the DHCP Client service started in order to work.

I hope that helps.

Cheers!

Ace
 
Back
Top