Comments on: Can this be a hardware problem?

By: tcor99

tcor99 — Fri, 07 Apr 2006 08:44:55 +0000

This could be several problems. It sounds like you may have a bad wall jack. Often times you will not get a ‘disconnect’ when one pair of the two conn for ethernet makes contact. Check the wall jack. Next, if the system was cloned,renamed, or removed from the network/readded, problems can arise in AD similar to what you have mentioned. Also do the usual such as check for client event logs, XP firewall, etc. If all else fails, replace the NIC.

By: mstry9

mstry9 — Wed, 05 Apr 2006 22:17:00 +0000

We have seen similar situations on our network. Our solution was found on Microsoft’s site, http://support.microsoft.com/kb/q239924/,
The problem relates to gigabit network cards only. If they lose connection for only a moment the Media Sense feature releases bindings to the network card and restors them when the connection is restored. Read the article for more info but this seems like it may just be you fix.

By: lhgrubbs

lhgrubbs — Wed, 05 Apr 2006 19:12:36 +0000

Try to keep the user way from the cables. (Just kidding – replace the connections/cables/computer) Since other computers in the same area, on the same hub, with the same network configuration are not having the problem, it is localized to this computer. Focus!

LeRoy

By: snapper70

snapper70 — Wed, 05 Apr 2006 17:28:02 +0000

Are you positive the computer name is unique? If not, then the computer probably can’t join the domain; or access resources while it’s “twin” is out there. If happening, that should be in the event log of the computer in question; or take it offline and see if you can ping it’s name from elsewhere. If so, you have a conflict which will give bizarre results; yet may work some of the time (when the OTHER one is down or having problems…).

Do you have a WINS server, or strictly DNS for name resolution?
Do you have (have you checked) the HOSTS and LMHOSTS file, or are they unused/default? (windowssystem32etchosts).

By: snapper70

snapper70 — Wed, 05 Apr 2006 17:28:02 +0000

Do you have a WINS server, or strictly DNS for name resolution?
Do you have (have you checked) the HOSTS and LMHOSTS file, or are they unused/default? (windowssystem32etchosts).

By: lirria

lirria — Wed, 05 Apr 2006 12:19:32 +0000

OK – one more thing to try – give it a static ip, dns etc and see if the same problem exsists – if it does it’s either the computer or the network card (best guess if it does it’s most likely the OS). There could be an issue with the IP address in the DNS server – so trying a different one should give you more information.

Lirria

By: tngeorge

tngeorge — Wed, 05 Apr 2006 10:40:03 +0000

The description reads like a combination of minor configuration errors. To get to the inter net without LAN functionality suggests that the Internet connection settings are using a defined PROXY. That and a bad connector will put the PC into automatic IP assignment, i.e. 192.168.x.x intermittent connections can then account for the strange behavior.

By: plynch

plynch — Wed, 05 Apr 2006 09:58:08 +0000

We have a similar situation, although it can happen on any PC in the network. The PC’s are running XP. When this happens it can be fixed by going to the Netwoork Connections in the Cotrol Panel. Right-click on Local Area Connection and then select Repair. Try that next time instead of moving the wires. Not sure what it does but it seems to reestablish access to the DNS.

By: ninjaburn

ninjaburn — Wed, 05 Apr 2006 09:49:42 +0000

I had a similar problem with a Dell Precision about a year or two back. After replacing the network card (and the motherboard it was soldered to, thankyouDell…) I found the problem still existed. After a LOT of research I found the DNS service in the machine was actually corrupted. I could not find a clean way of repairing the DNS so I completely reinstalled the OS. I found after that it worked beautifully.

Chances are it is either the DNS or WINS set up on the machine. Since the domain is designed not to allow access to unauthorized computers by default, your interal router may be set up to still feed IP’s through DHCP regardless of if the machine is in the domain or not. Hense why you can hit the net: there is no name resolution via DNS or WINS occuring there.

The cable wiggling may simply be causing Windows to reset its network connections, but that is a stretch of a guess at best.

By: shawn187

shawn187 — Wed, 05 Apr 2006 09:13:58 +0000

Is this a new computer to the network or did it once connect to the network and now it doesn’t?