RE: Windows Server 2003 and slow login

From: Matthew [MSFT] (mfresoli_at_online.microsoft.com)
Date: 04/28/04 

Date: Wed, 28 Apr 2004 15:10:37 GMT

Hi Joe,

Yes, the Domain Controller should point to itself only, and then use
forwarders to resolve externally (or root hints). Then the clients should
point to the DC for name resolution. Also make sure the register this
connection in dns is checked in the TCP/IP advanced settings.

Check the DNS on the server and make sure your zone for the domain is
present, and the properties allow for dynamic updates.

Then at a command prompt type:
ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon

A good resource for DNS information is www.microsoft.com/dns

Thank you,
Matthew Fresoli
Microsoft Network Support 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm 
Note:  For the benefit of the community-at-large, all responses to this 
message are best directed to the newsgroup/thread from which they 
originated.

Relevant Pages

  • Re: cannot join WinXP to Windows 2000 domain
    ... unedited ipconfig /all from both servers and the client machine. ... another server W2003 DC for it's DNS and the LAN's DHCP ... I would even be willing to move the W2000 DNS services to reside on ... Host records that map the name of the domain controller to its ...
    (microsoft.public.win2000.active_directory)
  • RE: [Help] How to change the IPaddress for production ADC
    ... change the Primary DNS ipaddress 172.10.10.1 to 172.10.200.1) ... My point is i have Additional domain controller in my location ... run ipconfig /registerdns and ipconfig /flushdns ... on workstations: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event 5782 from NETLOGON on server boot
    ... > I'm getting a 5782 from NETLOGON, but only at boot on the ... > DNS records failed with the following error: ... > machine as the domain controller. ... A new server, the one ...
    (microsoft.public.win2000.dns)
  • Re: Confusing A.D. problems...
    ... Running ipconfig /flushdns followed by ipconfig /registerdns absolutely ... You would normally first stop the netlogon ... > doesn't work on a domain controller. ... > the server to flush the dns. ...
    (microsoft.public.win2000.active_directory)
  • Re: problems demoting a win 2k DC (SRV records missing?)
    ... net stop netlogon & net start netlogon and open up the ... records that need to be registered in DNS ... I have to hand configure the SRV ... >>more then one domain controller you ...
    (microsoft.public.win2000.active_directory)