Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

One of our computers has started to constantly acquire a new lease from our DHCP server (a Trendnet router.) I get these 3 messages every couple of minutes, and the messages are logged at the same time:

Your computer was successfully assigned an address from the network, and it can now connect to other computers.

The system detected that network adapter Local Area Connection 3 was connected to the network, and has initiated normal operation.

The system detected that network adapter Local Area Connection 3 was connected to the network, and has initiated normal operation.

(Yes, the last message is repeated twice.)

Because of this, the computer is having constant problems with communicating with other computers on the network. It's used as a CruiseControl .net server, so it intermittently fails to copy files to network locations, and it fails to connect to our subversion server.

The lease expiration time on the router is 1 week, so I don't think it's an early expiration issue and I'm not having this problem with any other computers on the LAN. I've updated the drivers for the network interface and that didn't seem to have any effect. I've power cycled the router, and I've rebooted the computer. I installed a PCI network card and it's still having the same problems, though the time between the message sets is longer (about 1/2 hour instead of a couple of minutes.) The last thing to be updated at the time this problem started was a Windows Defender definition, so I don't think it's any recently installed software.

My question is: are there other things I can do to debug this problem, or does anyone have any idea what is going on?

EDIT: I've also changed ethernet cables and ports on the switch and I still get the same problem.

EDIT: I tried reinstalling and restarting TCP/IP (http://www.mydigitallife.info/2007/06/19/reinstall-and-reset-tcpip-internet-protocol-in-windows-vista-2003-and-xp/), but that didn't seem to help.

share|improve this question
    
What happens if you set a static IP address to the computer? –  emtunc Jul 29 '10 at 19:43
    
Setting it to a static IP address doesn't seem to solve the problem (I get the detected error messages and the network hiccups.) –  Michael Kelley Jul 29 '10 at 22:05
add comment

3 Answers 3

Well, this sounds to me like some issue on the motherboard. I don't have anything else to go by other than my experience of running several hundred computers as a day job, it's just a gut feel. I think you should start looking at getting yourself a new server. How old is that box?

share|improve this answer
add comment

You might try to "hard code" the line settings (speed & duplex) of the problematic NIC (versus its default of "auto-detect").

share|improve this answer
    
I tried that, but I still get the "The system detected that network adapter Local Area Connection 3 was connected to the network, and has initiated normal operation." message about every 15 minutes. –  Michael Kelley Jul 30 '10 at 18:20
    
"I installed a PCI network card and it's still having the same problems, though the time between the message sets is longer (about 1/2 hour instead of a couple of minutes.)" Was a different IP used? –  user48838 Jul 30 '10 at 21:09
add comment
up vote 0 down vote accepted

This appears to be a hardware problem with our Netgear GS108 switch. I thought I had tested without the switch, but apparently not!

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.