Windows Server 2003 and slow login

I have set up a Windows 2003, 2.6, 1 Gig RAM, Mirrored
SCSI drives. I also have a cable modem, Linksys 4 port
router used as the gateway and a Linksys 10/100 switch for
my computers to plug in to. Problem is, when I join one
of the computers to the 2003 domain and then reboot and
login to the domain, it takes a long time for it to
authenticate and bring up my desktop. This process should
fly seeing the environment it is in. I have the server's
DNS pointing to outside DNS servers, could that be the
problem??? I am stuck. Help.

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.

OK, I will try that, thanks.
>-----Original Message-----
>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.
>
>
>.
>

I have exactly the same problem. Would be interested in
how to resolve it.

>-----Original Message-----
>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.
>
>
>.
>