[sumudu33]

First off, I'm an ameteur network manager... so please go easy on me. I probably caused my own problem. :rolleyes:

I tried to add a new XPpro workstation to our Win2k Server environment, and now I've got 2 computers with "limited or no connectivity" problems (LONCP)... one is the new station, and another is a station that is related to this issue as I will explain below.

I was going to try to replace a desktop (call it station 1) with the new computer (call it 1b). I added 1b to the network, giving it an unused computer name, and it worked fine... could see the network, surf the net, access files on the server, use Outlook to connect to exchange, etc. Then a few days later it starts yelling about the LONCP, and has no access to the network. Can't see the internet or anything. I've tried all kinds of things to fix this, but to no avail.

The other computer (call it station 2) was not named correctly to match our network (just the computer name) so I tried to rename it. It accepted the new name, and worked fine for the moment (maybe a day or so?), but later on has the LONCP. It was a wireless connection, so I thought maybe the wireless network adapter was the problem, but even after moving it to connect with a cat5 cable, it had no access.

I suspect it has something to do with naming them since that is the only common thing to both systems. Maybe I just need a basic refresher on adding/renaming a computer to Win2k Server.

The short question is How do I solve the LONCP?
The long question is what did I do to cause it, and is there a short overview of how I should have done this?

Thx.