D
DigitalMess
I have a problem and it seems like it started occurring
around the time I created a domain separate from our NT
4.0 domain on the same subnet, and deployed a Windows
2000 Server running Active Directory. But this problem
occurs to Windows XP Clients that have never been joined
to the Windows 2000 Domain.
On an XP Professional client if I use a valid domain user
login account it takes somewhere between 2 - 5 minutes
sometimes even longer than that to establish a network
connection or domain connection and load the users
desktop. We don't do roaming profiles on the NT Machines
and the only work around I've found is to yank out the
network cable until the desktop is loaded and then plug
it back in. Everything is fine afterwards except for one
client now needs to have the network adapter disabled
then enabled before you can do anything on the domain,
but you can surf the Internet.
Any ideas??????????????? This is getting really
frustrating
Thanks in advance!
DigitalMess
around the time I created a domain separate from our NT
4.0 domain on the same subnet, and deployed a Windows
2000 Server running Active Directory. But this problem
occurs to Windows XP Clients that have never been joined
to the Windows 2000 Domain.
On an XP Professional client if I use a valid domain user
login account it takes somewhere between 2 - 5 minutes
sometimes even longer than that to establish a network
connection or domain connection and load the users
desktop. We don't do roaming profiles on the NT Machines
and the only work around I've found is to yank out the
network cable until the desktop is loaded and then plug
it back in. Everything is fine afterwards except for one
client now needs to have the network adapter disabled
then enabled before you can do anything on the domain,
but you can surf the Internet.
Any ideas??????????????? This is getting really
frustrating
Thanks in advance!
DigitalMess