Windows 2k Server with XP Pro Clients

[Darksamie]

I have a setup where I have a Windows 2000 Server (running AD) and about 16 XP Pro Clients. These computers are not the fastest things around, but they are quite decent anyway.

The problem I seem to be having is during client logon to the server. When the XP client goes through the logon sequence, it takes about 5 minutes to actually log on. I am thinking of re-installing XP on the machines in the network environment to see whether that helps, but otherwise these are freshly installed machines (they were done before the server was available).

Any ideas?

Are there any templates for group policies available for XP under windows 2000 server?

Thanks

 

[AndyHui]

Dunno, Brad...😛

Go ask in Networking.

 

[NogginBoink]

Try checking the system event logs for errors, then looking up those error messages in the KB for resolutions.

 

[Darksamie]

I just thought I would answer my own question with something only recently put on the Microsoft web site.

The following is a link that tells system administrators exactly how to control (via group policy) Windows XP Pro CLients.

http://www.microsoft.com/windowsxp/pro/techinfo/administration/policy/managing.asp

If only I could work out how to make the logon speed up 🙂

 

[millsy]

I have read this problem before but can't seem to remember where???

I am sure there is a fix, have you checked through MS knowledge base??

what about emailing MS

 

[Darksamie]

I have had a look through the Knowledge Base. Can't really find anything that is applicable or that will solve the problem.....

 

[AndyHui]

w0iii...still having problems with this huh?

I'll see what I can dig up. 🙂

 

[NogginBoink]

Have you checked the system event logs on the client machines?

It's likely these machines are trying to tell you what's wrong and you're not listening.

 

[watts3000]

Check the name of the domain contoller make sure you used a fully qualified domain name. Hopefully you did not use a www. prefix when nameing the domain .I have seen where systems have a dns resolution problem where domains that are not properly named will actually go out to the internet and try to resolve there names instead of reslving on the lan locally