Networks

Ask something
Question Locked

Intermittant network disconnectivity

0 helpful
9 replies

by lmayeda

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our network suffered some sort of power incident over the weekend that damaged our DSL modem and router (which has been replaced). One computer which hosts a business application does not appear on the network neighborhood even though it is active. This host is an XP Pro, with a static IP address,is plugged into an UPS, is wired and on the active directory. It's power option is to NEVER shut down. Sometimes I just need to log in to "wake it up". Other times, I have to reboot it before I can find the computer via a SEARCH for COMPUTER. It then remains visible on the network neighborhood until a day or 2 passes and I can no longer see or ping it until I go thru the same process. This problem just started happening after the DSL modem and router were "fried". Any ideas to help me pin point the problem?

9 replies

by chris cook

I have had people with this problem fairly frequently. Usually the problem lies in the Power Options in the Control Panel. If you look there you should find a setting for the network card. A lot of times this is set to turn off the network card to conserve power. If this is enabled, try disabling it and see if that helps.

by lmayeda

The POWER settings was on HOME/HOME OFFICE and I thought I had changed the Turn off Hard Disks and System Standby to NEVER but when I viewed it later, I selected the ALWAYS ON option and that system has stayed connected for a week, so I think this was the solution. I'm not sure why an office power outage should have started the disconnectivity issue but this works so I'm happy. Thanks a lot.

by chris cook

Glad to hear that worked for ya! Sometimes the simple things cause the most problems.

by shasca

Try swapping out the Network Card. It may have taken a slight hit too.

by lmayeda

NIC is built into the motherboard. Will double check that the station is still plugged into an UPS (as it "should" be).
May try going through the hardware test process. Could be the problem...system stayed up over the weekend. Thanks.

by rob miners

Click Start, Run and type cmd and press Enter.

at the command prompt type netsh winsock reset and then press ENTER.

Click Start, click Control Panel

Click Network Connections.

Right-click "Local Area Connection", and then click "Properties".

Click on (highlight) "Internet Protocol (TCP/IP)", and then click "Properties" button

Click the General tab, and then click "Advanced" button , bottom right.

Click the WINS tab.

Under "NetBIOS setting" section, click Enable NetBIOS over TCP/IP, and then click OK two times, then "close".

( ) Default

(*) Enable NetBios

( ) Disable NetBios

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jserrago

Off the top of my head this sounds like a DNS issue to me. Also was the IP address reserved in the router before it got fried? I would try that in the new one.

It could also mean that the NIC on board might be failing. From the station do you have any problems accessing the internet?

I would check the router settings, and the DNS on the station and the server.

by lmayeda

The workstation has a static IP address outside of the range set on the router. I also specified the static IP of the workstation in the HOST table on the server. Not sure how to test a failing NIC.
I "think" I was able to ping an outside website when the station was not able to ping the server ... but I could be wrong. Will check for sure the next time.

This discussion is closed to new replies.