XP in the NT Domain

[eayko]

Hi! Just want to ask your idea or opinion regarding this issue.

We experience slow response (usually more 3-5 mins) from the mapped network drives whenever we access it for the FIRST TIME (e.g. from starting or restarting the xp clients) using the windows explorer. Also, the login process takes longer than usual.

Background: We replaced some of our 98 boxes with xp pro. Our network is small-to-medium (about 65 clients) connected to the NT domain via 100Mbps link ethernet. IP address are static to all. The servers consists of the following: a PDC - acts as a print server, a BDC - acts as a file server, another BDC - acts as a NAV System center and WINS server. DNS server is not local to the LAN. XP boxes are above minimum specification. Login script uses "NET USE" command.

Thanks in advance!

 

[bcastner]

On a W2k domain these problems are almost always a combination of:

1. Autosensing failure between switch and workstation NIC; you can use this matrix for some hints as to how to force the workstation nic settings:
[tt]
Workstation Switch Result

Forced Half Forced Half Works
Forced Full Forced Full Works
Auto Auto Maybe
Forced Full Auto NO
Auto Forced Full NO
Forced Half Forced Full NO
Forced Full Forced Half NO

[/tt]
2. DNS resolution issues.

Slow logons from XP to a win2000 domain usually indicate a DNS misconfiguration issue. While the following is not a fix-all for all AD-domain problems, it is an absolute requirement that DNS is set up correctly before it will work properly. If your DNS is not set up like this, then you will experience problems like you describe. XP differs from previous versions of windows in that it uses DNS as it's primary name resolution method for finding domain controllers: How Domain Controllers Are Located in Windows XP <

http://support.microsoft.com/default.aspx?scid=kb;en-us;314861>

If DNS is misconfigured, XP will spend a lot of time waiting for it to timeout before it tries using legacy NT4 style NetBIOS. (Which may or may not work.)

1. Ensure that the XP clients are all configured to point to the local DNS server which hosts the AD domain. That will probably be the win2k server itself. They should NOT be pointing an an ISP's DNS server. An 'ipconfig /all' on the XP box should reveal ONLY the domain's DNS server. You should use the DHCP server to push out the local DNS server address.

2. Ensure DNS server on win2k is configured to permit dynamic updates. Ensure the win2k server points to itself as a DNS server.

3. For external (internet) name resolution, specify your ISP's DNS server not on the clients, but in the forwarders tab of the local win2k DNS server. On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints' tabs because they are greyed out, that is because there is a root zone (&quot;.&quot present on the DNS server. You MUST delete this root zone to permit the server to forward unresolved queries to yout ISP or the root servers. Accept any nags etc, and let it delete any corresponding reverse lookuop zones if it asks.

The following articles may assist you in setting up DNS correctly: Setting Up the Domain Name System for Active Directory <

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675>

HOW TO: Configure DNS for Internet Access in Windows 2000 <

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202>

 

[eayko]

Would be the second suggestion (No.2 DNS Resolution Issue) be applicable to NT Domain? Should DNS server be local to the network?

 

[FoxEgg]

GRRRRRRRRRRRRRRRRRRRRR !!!!

I have EXACTLY this same problem... I have a very small network (6 machines) which had 98 machines, W2000 Professional machines and it worked fine...

I put the database on the W2000 machine and mapped drives and all was fine...

Then I replaced one 98 machine and added one more node using 2 wiz bang XP Pro machines... and I immediately had this delay which is a real nuisance.

I thank you, bcastner, for that excellent essay in reasons (even though I am not using Win 2000 Server)...

I am an engineer and I followed your suggested link to Microsoft...

: How Domain Controllers Are Located in Windows XP <

http://support.microsoft.com/default.aspx?scid=kb;en-us;314861>;

and after 2 hours of reading and doing their Gobbledegook, I GAVE UP !!! ...



Comment:

It cannot be that hard.. IT JUST CANNOT BE THAT HARD .. surely there must be some simple way whereby a garden variety small network operator can run some routine or set some switch and not have to reconfigure the whole network just to make it work as fast as a W98 machine.

Any suggestions.... ???

************
I should add some extra information.... because it might be an 'issue' (altho it never has been in the past)..

(1) My IT guy has configured the DNS on all machines to look at our ADSL access point... this goes on all machines.. and so I am not going to be able to change the DNS without losing Internet access at all the machines (ie I don't want to).

(2) My small network shares a WORKGROUP and a SWITCH with my colleagues who have a Win 2000 Server hanging off it and several (8) Thin Clients... I don't access their Win 2000 Server for anything.... So really their network has a parallel existence... It never has been a problem in the past.


John Fox