Netwoek issue-ping failure

[edfair]

Server (PRO SP2) --switch-- Worker (Home SP2)
Worker crashed beyond repair and reloaded. Intermittently fails to access the server database.
Original link was a linksys wireless router operating as a switch and DHCP. Replaced when it corrupted on a parameter change. Replacement worked but then went to switch and fixed IPs on both machines at 192.168.1.2 & 3 (server)
Server can ping 127.0.0.1, local host, serverIP, server name. worker IP, worker name, and the router when it was installed.
Worker can ping 127.0.0.1, local host, workerIP, worker name, and the router when it was installed. It fails on the server IP and server name. Server firewall is disabled.
Worker would lock up with IP failure (ping to server failed) after some period of time. Rebooting or logging off the server would fix it temporarily. Has now become a solid failure.
Microsoft troubleshooting suggests card failure based on the solid failure but also suggested IP reset, which was no help. I don't think card failure because pinging outbound from the server is OK. It feels like a firewall issue but with it disabled I question that.

Any suggestions?


Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[lhuegele]

Just because you can ping out from the NIC doesn't mean there's not a problem with it. The only way to know for sure would be to replace the NIC and try again.

You can also try taking the NIC card out, then reinstalling it. That has helped us before.

Good luck.

 

[CorruptedLogic]

Do you have another machine you can throw into the netowork to rule out the "worker" pc? Also, if you're using fixed IP's, is your default gateway info correct on both machines? (i think that worker PC gateway should = Server IP and vice versa). I'm assuming here that all required protocols are installed (ip, F&P sharing etc).
Also, are any of the event logs complaining about forced master browser elections or master browser issues? I've had issue in the past where both PC's continuously advertised that they were the master browser. That caused intermittent connectivity issues.

CCNA, CCDP, Net+, A+
Work Smarter, Not Harder....
This was supposed to be the future.....Where is my JetPack?!

 

[edfair]

Between IPreset and disable of the firewall the server became visible again. Once firewall was enabled with exceptions the system was back to original with no problems showing up in the elapsed 2 weeks.

Thanks.

Ed Fair
Give the wrong symptoms, get the wrong solutions.