RE: slow login to new windows server 2003 domain

From: Constantin Chionas (constantinchionas_at_hotmail.com)
Date: 10/13/04 

Date: Wed, 13 Oct 2004 07:23:12 -0700

This is caused because the clients cannot find the DNS server, try to enable
the DNS role in the server and enter the server IP address in the Preferred
DNS Server in the adapter's Internet Protocol (TCP/IP) properties of the
clients.

This should fix it, and if not do the following:

- Open the DNS MMC from the Administrator Tools and go to your domain name
under the Forward Lookup Zones.

- Select the line Name Server (NS) and click properties, you should find
your server listed under the Name servers list, note that the IP Address
field next to your server name should show the server IP address, if not,
than your server name cannot be resolved, to check it more try to press Edit
under the list, and press Resolve next to the field that contain your server
full address. The IP address of your server should be added in the IP address
list when you press resolve, otherwise means it cannot be resolved. If this
happened follow the next step.

- Try adding (A) host for your server in your domain Forward Lookup Zones,
and try the previous step again and check if it will resolve. If it did
resolve and the server IP address appears then your clients should logon fast.

I had the same problem until I figured out that this was one of the ways to
solve it. Every time I used to enable the DNS role and let the wizard create
the DNS zones I had to add (A) host with the same server name to work
properly.

"barfidav" wrote:

> I'm experiencing very slow response times when logging into my new Windows
> Server 2003 domain from a client XP workstation. Both the server and the
> workstation are new machines with the latest processors and plenty of memory.
> When I initially join the new domain by changing from the old domain to the
> new one in "My Computer" properties (and re-boot as required), it takes
> around 10 minutes to login for the first time. After the first login, I
> would expext it to be much faster, but it still takes around four minutes to
> login each time I logout. Does anyone have any ideas on why this is so slow?

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)