Discussion Locked

Local Area Network Connection issue

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

In brief:

The DNS server is setup on a Windows 2000 Server machine. The network card went bad a couple weeks ago, so I had it replaced with a Netgear PCI 10/100 card. I've been noticing that after x amount of time (around 5-8 hours) the server stops responding to incoming and outgoing connection requests. All pings to the server are timed out, and the activity monitor for the network connection shows no activity (even though it is still enabled). When I disabled and reenabled the connection, everything started working again, web browsing, etc. Any ideas on what the problem could be?

18 replies

by bfilmfan

Make sure that the LAN card is not set to autopower down after a certain amount of time.

by oz_media

To agree with BFILMFAN, DAMN I HATE IT WHEN THAT HAPPENS!!! :)

It usually seems to happen in shorter time intervals though. 30 minutes.

by trek05

Double checked the power save features. Everything is configured correctly. Thanks. Any other suggestions.

by sgt_shultz

anything in the event logs
can you try locking new nic media type either up or down i suggest down to 10mb half duplex
what else changed.
wonder why how did the other nic fail
can you try another nic
what is the netgear model number

by tomsal

Suggestions and a comment....

ALWAYS check the stupid stuff first. That's a rule I try to live by (because when I don't and the answer is simply *I FEEL* stupid..lol)....

So then...check the health of the cable itself and the switch ports it plugs too (or patch panel, whatever your system is..actually check both the patch and the switch).

You are looking for obvious damage to anything, you are also looking for loose connections..lord knows some RJ-45 connectors in my time have not "connected" all that tight and they tend to come loose VERY easily.

Of course disabling and re-enabling the connection and that causes it to work again would limit the chance of a loose connection issue a bit. I'd still check it. Stranger things have happened.

Also how open is this system? By that I mean in two regards -- straight out security wise and are you the sole person who has rights/works on this machine?

Theories on this are -- possibly some virus infection causing instability, someone who is going into the system unbeknownst to you and fussing with things (we had a user here who swore up and down his lan conneciton would work some times and other times it wouldn't...after some talking with him and looking things over -- he was disabling the connection manually..he thought you had to turn it off as part of the computer).

Next move on to drivers (if you think its stupid well that's what I call it "Checking the Stupid things"). Perhaps nuking the current drivers, and then shutting down, re-boot and download and install the latest version ones fresh again.

The reason I'm saying this stuff is because we all know that DNS is a service, it shouldn't just shut down unless its configured to do so.

I'm making all assumptions that you have checked the service settings already, that you tried stopping--restarting it, and that DNS is properly configured.

The last stupid thing is did you install any new software recently or make any system changes within the sam

by tomsal

It cut me off...last suggestion was think about new software installed or changes made within the same time frame that these problems occurred.

And finally...the comment part...

I'd never use a cheapo Netgear nic in an important company server like a DNS box. I'd go with a server grade managed nic instead and they have built in diagnotics on them as well as teaming functionality.

by trek05

Not exactly sure why the other NIC went. I've checked the event log, and the only out of ordinary entry I found was this:

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 3000
Date: 7/27/2005
Time: 8:49:01 AM
User: N/A
Computer: xxxxxxx
Description:
The DNS server is logging numerous run-time events. For information about these events, see previous DNS Server event log entries. To prevent the DNS Server from clogging server logs, further logging of this event and other events with higher Event IDs will now be suppressed.

The NIC is a Netgear FA311. I haven't tried to swap it out with another card. I did change the patch cables, the one going from server to jack, and the one from patch panel to switch. Swich lights do not indicate any abnormalities, and no strange messages when I looked into the HP switch log.

I've forced the connection to 100 full duplex. If it continues I'll use the suggestion and throttle it back to 10 half.

All your suggestions are appreciated.

by trek05

You are right about the Netgear NIC. I'll try the other suggestions too. Thanks

by jguasch

Does your Server have dual nic or just one nic?

when this happends again, check for routes on the server while it is down. (route print) maybe the server looses its routing table. I have seen this before and it was a routing issue. Upgrade the drive..

Try

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create a DWORD value with the name "EnablePMTUDiscovery", and the value of "1".

Also, you can do a keep alive

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters]

REG_DWORD
KeepAliveTime 300000 (5 min)

KeepAliveInterval 1000 (1 min)

But I agree, use server grade nic cards for servers.

by trek05

Got an Intel PRO/1000 MT PCI Gigabit Server Adapter, and problem seems to be solved. Once again... you need to pay to play. Thanks for all your help.

This discussion is closed to new replies.