G
Guest
I'm having a problem with Win XP Pro and I'm not sure where to start. Any help would be appreciated. Here are the details
I have a network with a Win2k3 server acting as the domain controller. I have a few Win2k clients and a few WinXP Pro clients. The XP machines and the Win2k machines are the exact same machines from the same manufacturer. All the machines are located in the same building as the domain controller and are all part of the same domain and are part of the same subnet
The WinXP machines take 'forever' to log in to the system. The Win2k machines log in in what I would consider to be a normal amount of time (The WinXP machines take approximately 2 minutes to log in. The Win2k machines take about 20 seconds.) Furthermore, the XP machines seem to drag doing normal tasks such as using Windows Explorer and Office applications.
I have tried connecting one of the Win2k machines to one of the XP machine's network connection to determine if it was specific to that network location and the Win2k machine continues to function normally
I suspect it may be something related to security policies but that's just a shot in the dark
Thanks for your help
I have a network with a Win2k3 server acting as the domain controller. I have a few Win2k clients and a few WinXP Pro clients. The XP machines and the Win2k machines are the exact same machines from the same manufacturer. All the machines are located in the same building as the domain controller and are all part of the same domain and are part of the same subnet
The WinXP machines take 'forever' to log in to the system. The Win2k machines log in in what I would consider to be a normal amount of time (The WinXP machines take approximately 2 minutes to log in. The Win2k machines take about 20 seconds.) Furthermore, the XP machines seem to drag doing normal tasks such as using Windows Explorer and Office applications.
I have tried connecting one of the Win2k machines to one of the XP machine's network connection to determine if it was specific to that network location and the Win2k machine continues to function normally
I suspect it may be something related to security policies but that's just a shot in the dark
Thanks for your help