Slow initial connection from Win2k machine

[dullard]

At work, I've got several machines which I frequently transmit files between. They are a large mixture of old and new hardware, and old and new operating systems. The only computer with Win2k takes about 3 minutes to finally ask for the name/password when I first click on a machine to transfer files. In fact it is so slow, that I usually can leave the room, find the computer that I want to access, click to the Win2k computer, sign in, transfer the file, and walk back to my office well before the name/password appears on the Win2k machine. After the initial sign-in the network time is fast as well as any future attempts to connect to that computer. But everytime I need to reboot the Win2k machine, I have to go through this waiting game again. What could be the cause of this trouble?

 

[DaiShan]

what kind of chipset is the motherboard running?

 

[dullard]

Thanks for the reply: i860.

 

[boran]

I have same problem with win2k when trying to access win9x based clients, the initial connect is REALLY slow (like 1 or 2 minutes)

after that it goes normal speed, it's like they both are communicating to identify themselves to eachother....

I can connect to win2k computers at the normal speed (meaning lightning fast)

chipset :
AMD 761 NB + Via 686b SB

 

[dullard]

<< I have same problem with win2k when trying to access win9x based clients, the initial connect is REALLY slow (like 1 or 2 minutes) >>



So does this occur to everyone?

 

[Tannah]

I'd have to say yes. The only work around I've found is to type in the path to what you want to access. Example "\\server\D" would access a computer that is named server and access the shair called D on it
If you connect like this, I find you don't have to wait for the computer to find the other one..