Brian;
You are on the right track. It is in fact a DNS issue. You should
configure your Windows 2000 Server to be a DNS server, and point all
of your clients at it for DNS resolution, and it alone. If your
Windows XP client is pointed to another DNS server in addition to this
on eit can cause this issue as well. It should be pointed at the
Windows 2000 server only. The reason this delay occurs is because
Windows XP is querying DNS for information about the domain
controller. Id it is pointed at a DNS server other than the domain
contreoller it will simply time out, and try over and over again. If
you have trouble with external name lookups after pointing it soley at
the domain controller add your external ISP provided DNS server addess
to the forwarders list on the DNS configuations settings. This should
address the issue.
Best regards,
Harley Henderson MCSE 2000
Microsoft Enterprise Platform Support
Windows Server Setup Support Team
Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-039? If not, Microsoft strongly
advises you to review the information at the following link regarding
Microsoft Security Bulletin MS03-039
http://www.microsoft.com/technet/sec...n/ms03-039.asp and/or
to visit Windows Update at
http://windowsupdate.microsoft.com to
install the patch. Running the Windows Update scan will help to
insure you are current with all security patches, not just MS03-039.
Microsoft also highly recommends to all customers that you visit the
http://www.microsoft.com/protect site and perform the three
straightforward steps listed to improve your computer’s security.
On Wed, 29 Oct 2003 15:41:37 -0800, "Brian" <(E-Mail Removed)> wrote:
>XP Pro sp1, Brand new Dell Optiplex, All Dell
>pre-installed. Attempting to log in to a Win2k server
>domain. It will log in but only after about 60
>seconds...maybe 3 minute even, haven't timed it but it's
>definately way long. The 2k server is the domain
>controller and dhcp server. Other boxes on the network are
>WinNT, ME, and an XPPro laptop. Every other box on the lan
>will log in in seconds. There is a 3 line startup script
>that 2K feeds users logging in to map a couple network
>drives. It works, but again the "loading your preferences"
>screen just sits there for entirely too long. I have 10
>more identical boxes to hook to this server and would like
>to get this resolved before hooking up the rest! It feels
>like a DNS timeout but DNS seems to be working fine. I
>added the computer to the Active Directory users and
>computers. Should I not have done that? I did not set
>this network up and do not own it. I am helping out a
>client setting up his new workstations and have full access
>to the 2k server...any suggestions on where to look? Seems
>it should be something simple that's causing some kind of
>timeout before completing the logon. Windows is not quite
>my forte so I'm in unfamiliar territory when it comes to
>troubleshooting Avtive Directory Domain Controler
>issues....or is this an XP issue? Any help, ideas, or
>pointers would be appreciated. Thanks!
Similar Threads
