Slow workstations logon to Win 2003 - DNS Problem?

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi!


I am having a longstanding problem with XP Pro clients trying to logon
to windows 2003 domain controller. It is EXTREMELY slow. I watched the
postings here, and all the following is configured:
1. All clients point to and only to the DC as a DNS
2. The DC has DNS pointing to itself and DNS forwarding is to the ISP
3. Forced Kerberos to use TCP


---------------------------------------------
I have tried NSLookup without parameters:


C:\>nslookup
Default Server: crowder.tau.ac.il
Address: 132.66.156.44
----------------------------------------------


Which seems correct (this is the name and IP of the DC)


-----------------------------------------------
I tried NSLookup for the domain ("Goshen")


C:\>nslookup goshen
Server: crowder.tau.ac.il
Address: 132.66.156.44


Name: goshen.tau.ac.il
Address: 132.66.156.44
----------------------------------------------------


Here I get two responses - might this be the problem?


I get three DNS error messages on every restart of the server (in this
order):


The DNS server has encountered a critical error from the Active
Directory. Check that the Active Directory is functioning properly. The



extended error debug information (which may be empty) is "". The event
data contains the error.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


51 00 00 00
-----------------------------------------------------------
The DNS server was unable to complete directory service enumeration of
zone .. This DNS server is configured to use information obtained from



Active Directory for this zone and is unable to load the zone without
it. Check that the Active Directory is functioning properly and repeat



enumeration of the zone. The extended error debug information (which
may be empty) is "". The event data contains the error.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


0000: 2a 23 00 00 *#..
------------------------------------------------------------­­--
The DNS server was unable to complete directory service enumeration of
zone goshen.tau.ac.il. This DNS server is configured to use
information obtained from Active Directory for this zone and is unable
to load the zone without it. Check that the Active Directory is
functioning properly and repeat enumeration of the zone. The extended
error debug information (which may be empty) is "". The event data
contains the error.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


0000: 2a 23 00 00 *#..
------------------------------------------------------------­­-----


Can't figure out what to do. Any ideas?


Thanks a lot!
Amit

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:1109246855.285030.5220@l41g2000cwc.googlegroups.com,
amitstei@gmail.com <amitstei@gmail.com> made a post then I commented below
> Hi!
>
>
> I am having a longstanding problem with XP Pro clients trying to logon
> to windows 2003 domain controller. It is EXTREMELY slow. I watched the
> postings here, and all the following is configured:
> 1. All clients point to and only to the DC as a DNS
> 2. The DC has DNS pointing to itself and DNS forwarding is to the ISP
> 3. Forced Kerberos to use TCP
>
>
> ---------------------------------------------
> I have tried NSLookup without parameters:
>
>
> C:\>nslookup
> Default Server: crowder.tau.ac.il
> Address: 132.66.156.44
> ----------------------------------------------
>
>
> Which seems correct (this is the name and IP of the DC)
>
>
> -----------------------------------------------
> I tried NSLookup for the domain ("Goshen")
>
>
> C:\>nslookup goshen
> Server: crowder.tau.ac.il
> Address: 132.66.156.44
>
>
> Name: goshen.tau.ac.il
> Address: 132.66.156.44

The name "Goshen" is a single label DNS name. Is this your configuration?
Single label domain names are problematic and can cause long logon times.
Why did you force Kerberos to use TCP? If there is a domain or DNS
misconfig, that won't help, unless you did that to force it to use TCP
across a firewall where UDP is blocked.

If you can post an unedited ipconfig /all of the DC, and the actual Event ID
# of that error you posted, it will help to provide a mnore accurate
diagnosis.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================