XP Pro and W2K Server.

[WhiteShadow6]

I recently upgraded my Domain Controller Server (hardware and software) from NT4 Server to a clean installed W2K Server.

Since this upgrade I am having connectivity problems from all my Workstations (all XP Pro) to the Server. First of all, they take alot longer to login compared to when the server was NT4 plus the time they take to login varies (anyware from 1 to 5 mins). Secondly, intermitantly unaccessable mapped network drives.

The strange part is the server always responds to ping requests (even left going overnight with "ping 192.168.0.1 -t") in less than 1ms time and I never have problems with the Internet Connection Sharing, it always works even when the network drives are unaccesable (which indicates that it's not hardware).

It appears that network requests that are purley TCP/IP (like network games) and TCP via the ICS Service work fine, there is only a problem with services related to "Microsoft Networks" (logging in, mapped network drives, remote Computer Management, etc.).

My question is; are there any known problems with XP Pro to 2K Srv connectivity or where should I begin to try and fix these probs.

All systems are running latest service packs.

Thanks in advance,
WS6

[10ECsoon]

With a clean install of the server, you'll want to re-map network drives (disconnect and then re-map), even if you used the same name for the server. Ping requests just means that TCP/IP is working correctly.

You'll also want to make sure that all workstations are pointed to the server as one of their DNS servers, and that they are registering correctly in the servers DNS. That should get you started, anyway.

[WhiteShadow6]

All workstations were clean installed XP pro after the server was upgraded, thus the network drives were re-mapped and all workstations are pointed to the server as first DNS.

10ECsoon, what exactly do you mean "and that they are registering correctly in the servers DNS."?

WS6

[10ECsoon]

If you have a W2K Domain Controller, than it's going to be running DNS. Check the Forward Lookup Zone for your domain and make sure that all the workstations have host (A) records. Although from your second post I'm willing to bet that they're going to be there. Hmm. :confused:

Are you using any kind of roaming profiles or offline files? Folder redirection?

[WhiteShadow6]

I've just fixed it!:D

Actually my server wasn't running the DNS server service, so I installed W2K's DNS Server and I was able to fix my network drive and login problems! but I lost the shared internet access.
Seems the W2K DNS Server was blocking the ICS's DNS Server from translating requests.
So, I uninstalled the W2K DNS Server, then disabled then re-enabled the ICS service and everything seems to be working fine, but I fear after next logon I will have the old slow logon and no access to mapped drives. If that is the case I will try making a C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS file and locally translating.

Thanks 10ECsoon, your mention of the DNS server in your first posts got me on the right track.

WS6