Wheatland

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

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.

Wheatland

Well, I got the new computer to work today by doing a static IP address. I'll try that tomorrow on the other one... it's too late to do it today.

Anyone have an idea of how I might have caused this?

NeoPlosive

Are you using DHCP?

On Server - Start > Run > 'cmd'

net stop dhcpserver
net start dhcpserver

Naming of unique stations shouldn't affect network connectivity.

Wheatland

I got them both working using static IP's.

The Win2K Server is apparently the DHCP. I checked the router, and DHCP in not enabled there.

On the server : Computer Management>Services & Applications>Services>DHCP Server... the status is "Stopping".

I'm guessing that may be an indicator of the problem?

So, from a cmd on the server I typed "net stop dhcpserver" and got the following reply:
"The service could not be controlled in its present state" and referred to "net helpmsg 2189"

I'm guessing from what the help msg said, the service is hung up and if I can't stop/start it like you recommended, then maybe a server reboot might be in order.

Does that sound like the correct course of action?

NeoPlosive

Sounds like DHCP has hung for some reason. A restart should kick DHCP back into action again.

Check the status after a restart and if it's running remove the static ip configuration from the clients and let us know if you're back on track again, or not.

Wheatland

First off, let me say thanks to you who have responded so far. The tips have been helpful.

Status: I rebooted the server, and the status is now "Started", and it seems to be working. I also was just notified about a third computer with LONC problems, and after the reboot, it works fine with no other work done.

So, it looks like the DHCP server being "hung" was the symptom, and rebooting the server has cleared it up. The question now is what caused the DCHP server hangup?

I've checked the event viewer, and don't really know what I'm looking at, so I didn't find anything helpful there. I was told by someone on another forum to check the DHCP log, but I don't know where that is.

Maybe some of you more experienced people can tell me if it is worth spending time trying to figure this out, or do I just keep my eyes and ears open for this symptom again, and only research it further if it happens again?

Thanks again for the help.

EDITED TO ADD: NeoPlosive, Yes the station I'm working at is one of the problem ones, and I've now reset it to dynamic IP and DNS... and it is working fine.

NeoPlosive

DHCP logs are stored server side:c:\(windows or winnt)\system32\dhcp in the format of DhcpSrvLog-DAY.log

This will only provide information on leases etc, event viewer would be more appropriate for logs in relation to the DHCP service.

It could just be the case that something kicked the service out... see how it goes and if things go funny again maybe you could export you event logs for around the time of the issue beginning.

dearsam2009

Wheatland

I just wanted to post a note to let everyone know I have had no further problems.

Thanks for the help.