Stopping DHCP CLIENT on DC's and Exchange servers
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Stopping DHCP CLIENT on DC's and Exchange servers

 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS
Author Message
Joe_SMS
Guest





Posted: Tue Oct 25, 2005 8:50 pm    Post subject: Stopping DHCP CLIENT on DC's and Exchange servers Reply with quote

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.
Back to top
Kevin D. Goodknecht Sr. [
Guest





Posted: Wed Oct 26, 2005 12:50 am    Post subject: Re: Stopping DHCP CLIENT on DC's and Exchange servers Reply with quote

Joe_SMS <jw_nagy@hotmail.com> wrote:
Quote:
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.

The DHCP Client service is a required service, must be set to Automatic and
running.
The DHCP client service is responsible for registering dynamic DNS updates,
which is how DCs and clients register their records in DNS.

Dynamic DNS Updates Do Not Work if the DHCP Client Service Stops:
http://support.microsoft.com/default.aspx?scid=kb;en-us;264539

No DNS Name Resolution If DHCP Client Service Is Not Running:
http://support.microsoft.com/default.aspx?scid=kb;en-us;268674


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Back to top
Joe_SMS
Guest





Posted: Wed Oct 26, 2005 4:51 pm    Post subject: Re: Stopping DHCP CLIENT on DC's and Exchange servers Reply with quote

Question: KB268674 which was last revised June 28, 2005 indicates that
it ONLY applies to Windows 2000. All other information I can find are
from folks who had been previously burned by this. Being said, why
wouldn't it apply to Windows 2003 ? I still think that perhaps there's
a longer version of this story being that there is so little evidence
of how critical this service is documented in Microsoft Dynamic DNS
whitepapers, training material, etc... One of the strange things that
happened when the DHCP client service was stopped was that it actually
went out and removed the record from DNS. Any further information on
this would be appreciated......like if the behavior has been the same
since Windows 2000 and since the KB article doesn't include Windows
2003 in the 'applies to', does it apply exactly the same way ?

Thanks much in advance.
Back to top
Kevin D. Goodknecht Sr. [
Guest





Posted: Wed Oct 26, 2005 8:50 pm    Post subject: Re: Stopping DHCP CLIENT on DC's and Exchange servers Reply with quote

Joe_SMS <jw_nagy@hotmail.com> wrote:
Quote:
Question: KB268674 which was last revised June 28, 2005 indicates
that it ONLY applies to Windows 2000. All other information I can
find are from folks who had been previously burned by this. Being
said, why wouldn't it apply to Windows 2003 ? I still think that
perhaps there's a longer version of this story being that there is so
little evidence of how critical this service is documented in
Microsoft Dynamic DNS whitepapers, training material, etc... One of
the strange things that happened when the DHCP client service was
stopped was that it actually went out and removed the record from
DNS. Any further information on this would be appreciated......like
if the behavior has been the same since Windows 2000 and since the KB
article doesn't include Windows 2003 in the 'applies to', does it
apply exactly the same way ?

You posted this in both Win2000 and Windows.server.dns groups, if you are
working with Win2k3 read this section of this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816592#XSLTH3134121122120121120120
The article clearly states this:
"When one of these events triggers a DNS update, the DHCP Client service,
not the DNS Client service, sends updates. If a change to the IP address
information occurs because of DHCP, corresponding updates in DNS are
performed to synchronize name-to-address mappings for the computer. The DHCP
Client service performs this function for all network connections on the
system. This includes connections that are not configured to use DHCP."
This backs up the previous article I posted. It is the DHCP client service
that registers DNS records.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> DNS All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB