Wired Network issues Intel Pro/1000 MT

[pcordes1979]

Hi, I am new to the forums here but not new to Thinkpads. I have a Thinkpad T42 w/ the Intel Pro/1000MT network chip. I have the hardest time connecting to any wired network at times. When it does work it works beautifully. I already ruled out software as I recently upgraded the hard drive and loaded XP Pro SP3 fresh onto it along with the latest drivers from Intel. What happens is sometimes I can't even do an ipconfig /all (gives message saying there is a problem with the network devices or something like that) until i disable the wired network in device manager and then re-enable it. Then it doesn't detect the network connection right away. Sometimes it may take a few minutes, other times hours, but as I mentioned once it connects it is rock solid. I have seen on other computers that the wired network port pins will become weakened and not connect as well but I don't think that is the case here, as once things are connected the only way to break it is to unplug the cable. Has anybody else run into a similar problem and figured out how to stop both issues that I have(both the ipconfig issue and the not connecting issue. I also ruled out the cable and my router as it will work fine on any other computer I plug the cable into. - Peter

[RealBlackStuff]

Welcome to the Forum.
If you use Access Connections, delete the existing profile and create a new one.
Or disable AC and let Windows manage your connections.
Check in the Properties that Windows can NOT switch it off to save power.
Also that you obtain an IP address and DNS automatically.

[pcordes1979]

I have done all of those. Actually I never installed Access Connections after I reinstalled XP onto the system, mainly as I wanted as little "unneccessary" software on the computer as I could get. I did uncheck the shut off for power savings box and it does get the IP automatically. The problem is it doesn't detect the network cable is plugged in right away, the link lights don't even come on right away like they should. It eventually will work just not right away like it should, and when it is working it works great with no drop outs no matter how much I wiggle the cable around. If there is some component issue I would have no problem repairing it, as I have done SMT and BGA rework before professionally. I have just never seen this particular problem, and the usual suspects that I have seen before in this issue the LAN connector itself and the filter module on the bottom of the board seem to be checking out fine(if the LAN connector was an issue I would be able to wiggle the network cable and the connection would go in and out and the solder joints on both the connector and the filter module are both good). - Peter

[RealBlackStuff]

Maybe bend the socket pins up a bit, and scratch them with a pen knife to remove any oxidation?
Have you tried another CAT5 cable?

[kiwipad]

Peter, the ipconfig problem may be an irrelevant distraction - I've seen that on quite a few XP machines (including both my TPs on XP SP3) where >1 network interface is enabled (not active, just not specifically disabled) and whichever i/f is active has worked fine - you just can't see that it is by using ipconfig ! Aside from disabling the inactive i/f I don't know of any fix.

As for the link not coming up on cable connect, does this occur if the cable is plugged on boot or just if the cable is plugged with the machine running? Could be a Windows service failing to start (for any number of Windows reasons) - check the Event Viewer when the "failure" occurs.

IG

[pcordes1979]

Sorry for the delay in responding to your last post. I was just able to test things out a bit. You were right the ipconfig issue may be a distraction, but still may somehow be related, as I've had that issue on NO other computers I own including 3 T20 and 1 R31 series systems(granted they are only 10/100 not 1000 network chips). The problem happens right from powering the system on, even with the network cable plugged in, and even if turning the system off and then turning it right back on, it will not show the network lights for 3 to 5 minutes or so. Its almost like the intel LAN chip is delaying something, since it does it even when sitting in BIOS. As I said before, once it connects, its rock solid, and nothing short of actually unplugging the LAN cable will make the connection drop.

Basically speaking I plug in the network cable, turn the system on, go into BIOS and in 3 to 5 minutes or so it will finally show the network lights. Same thing happens in Windows and even in network connections it shows the cable is unplugged even though the cable is plugged in, until the network lights come on then Windows will show the cable is connected. Personally speaking I think this rules out the LAN port itself. I was more wanting to know with my first posting is if anybody had a simliar issue and if so how was it fixed, short of replacing the whole motherboard. If I need to replace some components that is no problem as I have a scrap T42 board with a bad video chip(reflowed it once for intermittent video issue worked for about 6-7 months after that and then just a distorted display right from bootup(but runs fine despite not being able to see whats going on)). - Peter