• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 195
  • Last Modified:

Logging on to Server from XP Pro

I have got a feeling I am doing something really stupid here.

I have today set up a new server with Domain Conroller

I have set all 8 PC's to it

The only thing is that when you log on it takes ages, up to 5 mins.

When I was leaving I realised that I had set the DNS server address wrong on my server.

Was this the problem? I didn't get chance to test it?

I had set it to x.x.x.1 instead of x.x.x.2

Would this be causing the long hold on logging on?
  • 2
1 Solution
all computers on your network (including the server) should be pointed to your domain's DNS server (usually the domain controller)  Are all computers on your network pointed to the correct DNS server? your ISPs dns server shouldnt be listed anywhere.
Definitely; DNS is vital for a proper functioning of your AD.
Use only your internal DNS server (never your ISP's, except in the Forwarders configuration).
Here's the correct setup and some links that might be useful.

*** TCP/IP-Settings ***
* On your DC/DNS, make sure the only DNS listed in the TCP/IP properties is itself.
* On your domain members, enter only your DC as primary DNS.
* Do NOT enter your ISP's DNS server in the TCP/IP settings on any domain member. All DNS resolution needs to be done by your internal DNS server *only*.

*** DNS Server Settings ***
* Delete the root zone (if present) in your DNS servers' forward lookup zones (the single dot, "."), to enable external lookups.
* Right-click your forward and reverse lookup zones, go to Properties, and make sure that Dynamic Updates are enabled.
* In the properties page of your DNS servers, configure forwarders to point to your ISP's DNS. The forwarders section is the *only* entry in your network where your ISP's DNS should be listed.
* It's recommended (but not necessary) to set your zones to Active Directory integrated (this can be done in the properties of the zones as well).

Once you've checked this, open a command prompt and enter "ipconfig /registerdns", then stop and re-start the netlogon service. Check if the SRV records have been created (see link below).

10 DNS Errors That Will Kill Your Network

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

How to Verify the Creation of SRV Records for a Domain Controller

How Domain Controllers Are Located in Windows

How Domain Controllers Are Located in Windows XP

SRV Resource Records May Not Be Created on Domain Controller

HOW TO: Set Up the Domain Name System for Active Directory in Windows Server 2003

HOW TO: Configure DNS for Internet Access in Windows Server 2003

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows Server 2003
alanheatonAuthor Commented:
I think I must of sorted it now.

It was bugging me all afternonn why it was taking so long to log on, then I realised at the end.

All my workstations are set to Obtain Automatically, this should be OK?
As long as the DNS server settings DHCP server hands out are correct, it doesn't matter if you use static or dynamic addresses.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now