Network connection problems in Win2000

[loosingit]

I have one workstation that when the server is rebooted it will not connect back to it, the server is running win2000 server and it shows the computer in the domain even when it is unable to log on, like it still thinks it is connected. It will take hours to log back on if I do not go into network settings and remove tcp/ip, reboot and then reinstall tcp/ip on this workstation. After that it is just fine but this gets old, any advice? Other workstations do not have this problem, all workstations are set up identical.

 

[vbrocks]

What kind of OS is on the workstation?

 

[loosingit]

Windows 2000 is running on the workstation. Other workstations do not have this problem although they did in the beginning after installing 2000, seemed to work itself out. I have even changed the network card, no help.

 

[vbrocks]

Have you tried logging off on the client, then rebooting the server? What happens then when you try to connect?

 

[loosingit]

Yes, I have tried that, I have shut done the workstation, rebooted the server and looked in network neighborhood and it still shows the workstation even though it is not even powered on. When I turn on the workstation and log in, I don't get a log in error it goes ahead and my first clue that I am not connected to the server is the errors I get when server based software fails to load. When I go to network neighborhood and try to connect to the server drive it tells me that there is no domain server to log me on.

 

[TechMerlin]

Can you resolve the server name from the client (e.g. Ping <servername>)

 

[karmic]

with the server on, open a cmd prompt and try

nslookup

If your domain name isn't returned, the problem is narrowed down...

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[vbrocks]

Please run ipconfig /all on the client and on the server to see if anything is not correct .... (when you have the problem)