Adam D
asked on
SBS 2011 - Network card random issues
I have an old SBS 2011 that has been working for a while without issue. I restart the machine on a monthly basis.
Over the past few months, with no apparent reason, both network cards will partially stop working. The card itself does NOT indicate any problem, the static IP address is still assigned but it will refuse to communicate, ping or send any packets anywhere.
The status changes to "Connect, no internet access" and that is the only error found.
If I change it to DHCP, it grabs a new address and then about 15-30 seconds later it says the same error. Even during that 30 seconds it won't ping.
The only way to fix the problem is to remove the network card from Device Manager and reinstall it with the same drivers. A reboot does not solve the problem and even adding a USB-to-RJ45 jack wouldn't work - same problem.
Very odd error.
This machine has NOT been updated in a long time, no changes on the system except standard use, files being added/removed, etc., but NO operating system changes.
It is not infected.
The wire, switch and router are good.
Not consistent, happens "out of the blue" at random intervals but usually takes at least 30-60 days, sometimes shorter, sometimes longer.
My question: What might cause random partial network problems?
Thanks.
Over the past few months, with no apparent reason, both network cards will partially stop working. The card itself does NOT indicate any problem, the static IP address is still assigned but it will refuse to communicate, ping or send any packets anywhere.
The status changes to "Connect, no internet access" and that is the only error found.
If I change it to DHCP, it grabs a new address and then about 15-30 seconds later it says the same error. Even during that 30 seconds it won't ping.
The only way to fix the problem is to remove the network card from Device Manager and reinstall it with the same drivers. A reboot does not solve the problem and even adding a USB-to-RJ45 jack wouldn't work - same problem.
Very odd error.
This machine has NOT been updated in a long time, no changes on the system except standard use, files being added/removed, etc., but NO operating system changes.
It is not infected.
The wire, switch and router are good.
Not consistent, happens "out of the blue" at random intervals but usually takes at least 30-60 days, sometimes shorter, sometimes longer.
My question: What might cause random partial network problems?
Thanks.
Any further information in the event logs that might be relevant?
We can rule out the network card, since you are saying a different network card has the same problem.
Is the server still able to communicate on the network when this happens? In other words, is the "no internet access" error accurate? By this, I'm just wondering if the problem is with the gateway IP and not the server.
We can rule out the network card, since you are saying a different network card has the same problem.
Is the server still able to communicate on the network when this happens? In other words, is the "no internet access" error accurate? By this, I'm just wondering if the problem is with the gateway IP and not the server.
ASKER
No, the server cannot communicate in anyway over the network, including locally. I cannot ping it from any other machine or ping the router/gateway from the server itself.
The only thing of possible interest is some SChannel errors presumeably about the time the network connection started to fail. Last email from Exchange was about 9 a.m. and the SChannel failures started happening about 7:30 a.m., then Exchange started complaining about DNS issues, then Windows started complaining about DNS issues, which of course comes down to the fact it couldn't talk to anything. :)
Thanks.
The only thing of possible interest is some SChannel errors presumeably about the time the network connection started to fail. Last email from Exchange was about 9 a.m. and the SChannel failures started happening about 7:30 a.m., then Exchange started complaining about DNS issues, then Windows started complaining about DNS issues, which of course comes down to the fact it couldn't talk to anything. :)
Thanks.
ASKER
Also, I understand about ruling out the network card as the source of the problem, or the problem itself (potentially) but why would deleting the network adapter in Device Manager (leaving the drivers "installed") and then "Scanning for new hardware" and allowing Windows to "reinstall" the drivers fix the problem?
A reboot will NOT fix the problem. But, semi-deleting the cards from Device Manager and scanning for new hardware will fix it.
A reboot will NOT fix the problem. But, semi-deleting the cards from Device Manager and scanning for new hardware will fix it.
Why is the server using 2 network cards? What if you only use 1?
ASKER
It isn't "using" two network cards, one is always disabled; but no network cards work when this problem occurs. Either internal or external.
After you reboot, does the network change to Public Network?
ASKER
I don't believe so, but after I remove the cards from Device Manager and put them back it did show it as public which I manually changed back to Private. It is possible it changed to public, but I cannot be sure.
However; depending on where you are going with that, even if it was changing to public I should still be able to ping the router, which I cannot.
Thanks. :)
However; depending on where you are going with that, even if it was changing to public I should still be able to ping the router, which I cannot.
Thanks. :)
I would compare the output of ipconfig /all while this is happening and after you fix it.
Can you also provide more details about the event in Event Viewer?
Can you also provide more details about the event in Event Viewer?
ASKER
Hello. It has been 11 days since my last server reboot and NIC problem. "Out of the blue" this morning (about 30 minutes ago) I lost connection to my server. I manually logged onto the server and found my NIC card said no internet connection. In fact it had no connection at all.
The event log was continuously showing the same SChannel error:
Windows SChannel
Fatal error 40
Error state is 1205
Event ID 36888
In theory, this means:
EventID 36888 Description: Schannel, 40 1205
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.
Apparently SChannel deals with TLS connections.
This server really doesn't do much. It runs Exchange 2010 on a SBS 2011 box and shares files. It has "AD" but I don't use it for that, except for file permissions. No domain facilities are in use. That is all it does. And until recently, say the past 6 months to a year, this "problem" has never been a problem. This is a recent occurrence with no changes on the server (and no updates).
The fix:
Delete the devices (without uninstalling the drivers) from Device Manager then scan for new devices. Sometimes it requires a reboot after that, but not always.
No real difference in the ipconfig /all - different IPv6 addresses/info, but that's it.
Thoughts? Thanks.
The event log was continuously showing the same SChannel error:
Windows SChannel
Fatal error 40
Error state is 1205
Event ID 36888
In theory, this means:
EventID 36888 Description: Schannel, 40 1205
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.
Apparently SChannel deals with TLS connections.
This server really doesn't do much. It runs Exchange 2010 on a SBS 2011 box and shares files. It has "AD" but I don't use it for that, except for file permissions. No domain facilities are in use. That is all it does. And until recently, say the past 6 months to a year, this "problem" has never been a problem. This is a recent occurrence with no changes on the server (and no updates).
The fix:
Delete the devices (without uninstalling the drivers) from Device Manager then scan for new devices. Sometimes it requires a reboot after that, but not always.
No real difference in the ipconfig /all - different IPv6 addresses/info, but that's it.
Thoughts? Thanks.
Do you get a red X, or a warning triangle?
Is it possible to physically reattach the network card?
Is it possible to physically reattach the network card?
Over the past few months, with no apparent reason, both network cards will partially stop working.Same model? Same drivers? Do they stop working at the same time?
the static IP address is still assigned but it will refuse to communicate, ping or send any packets anywhere.Can you ping local IP adress of the server? Can you ping the gateway?
A reboot does not solve the problem and even adding a USB-to-RJ45 jack wouldn't work - same problem.So it happens to all network cards or network adapters. Correct?
ASKER
1. Triangle
2. No, cannot "attach/detach" they are part of the motherboard
3. The two NIC cards are the same, same drivers, one is always disabled when not in use. Yes, they both stop working at the same time (if I re-enable the other one it does not work either).
4. No, as stated, cannot ping anything anywhere. Request timed out, not general hardware failure. It is as if it thinks it is connected but doesn't know the path. Or it is just sending its' ping into cyberspace (to nowhere) and when it doesn't hear back it fails.
5. Happens to all cards/adapters and even when connecting a USB-to-RJ45 adapter that doesn't even work.
Unlikely to be the motherboard or chipset itself because removing and re-installing (at least partially) the drivers in Windows fixes the problem and it is happy again for "X" amount of time.
Thanks.
2. No, cannot "attach/detach" they are part of the motherboard
3. The two NIC cards are the same, same drivers, one is always disabled when not in use. Yes, they both stop working at the same time (if I re-enable the other one it does not work either).
4. No, as stated, cannot ping anything anywhere. Request timed out, not general hardware failure. It is as if it thinks it is connected but doesn't know the path. Or it is just sending its' ping into cyberspace (to nowhere) and when it doesn't hear back it fails.
5. Happens to all cards/adapters and even when connecting a USB-to-RJ45 adapter that doesn't even work.
Unlikely to be the motherboard or chipset itself because removing and re-installing (at least partially) the drivers in Windows fixes the problem and it is happy again for "X" amount of time.
Thanks.
Have you tested your antivirus? Are there any rules that might cause it?
If you run the network troubleshooter (Fix my network), does it give you a clue what's happening?
If you run the network troubleshooter (Fix my network), does it give you a clue what's happening?
ASKER
Thank you for your responses, sorry for the great delay in getting back to everyone.
1. No, no problems with antivirus
2. Network troubleshooter is clueless - as usual
3. This problem just recently started, very little change on the server since inception, no updates to it in at least the past year or more. This system just sits there doing its' job and gets restarted roughly every 30 days or so.
4. No apparent rhyme or reason to the failure, just one day it says I have had enough and stops talking. Reboot will not fix it.
I have to delete the card from Device Manager (but I do NOT uninstall the drivers), then scan for new hardware. It finds it, puts it back and all is well with the world (or at least the server) until the next time.
Time frame is not consistent between failures.
If you have any other thoughts, let me know.
Thanks. :)
1. No, no problems with antivirus
2. Network troubleshooter is clueless - as usual
3. This problem just recently started, very little change on the server since inception, no updates to it in at least the past year or more. This system just sits there doing its' job and gets restarted roughly every 30 days or so.
4. No apparent rhyme or reason to the failure, just one day it says I have had enough and stops talking. Reboot will not fix it.
I have to delete the card from Device Manager (but I do NOT uninstall the drivers), then scan for new hardware. It finds it, puts it back and all is well with the world (or at least the server) until the next time.
Time frame is not consistent between failures.
If you have any other thoughts, let me know.
Thanks. :)
I would get the latest NIC driver from your OEM. The Microsoft drivers that ship with the OS for a very common NIC chipset are seriously broken. After you install the latest NIC driver, get and install the latest NIC firmware.
ASKER
Thanks Kevinhsieh, and I understand your reasoning behind this thought; but, why after years of working with no updates, changes or modifications to the server would you think I would need new NIC drivers and firmware?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also might want to think about what other elements are the same through all these issues. Network cable? Switch, or at least switch port?
By no problems with antivirus, I assume you mean you have turned it off and the problem still happened?
I think I said before that since you tried a different network card (which I assume installed different drivers?) we can rule out the NIC itself as the problem.
By no problems with antivirus, I assume you mean you have turned it off and the problem still happened?
I think I said before that since you tried a different network card (which I assume installed different drivers?) we can rule out the NIC itself as the problem.
ASKER
Thanks kevinhsieh, interesting information. :)
Brian - nothing new on the network, although recently after the last incident (not for that reason) I did upgrade the network switch; that was about 2 months ago now, I think, I would have to check my records on the exact date. No failure, yet, since the last time.
Yes, I had tried an external USB-to-RJ45 NIC when the other NIC(s) were down and that new NIC would not work either which may lend itself to either the motherboard itself or Windows. But, again, all is happy and well again after I delete the drivers ONLY from Device Manager and I am not even really deleting the drivers, just the "setup" in Device Manager.
Very odd problem.
I would like to know why besides they just die....
But we may have to just chalk this up to unsolveable or at least not worth our time to figure out. :)
It is an old system but it works and does what it is supposed to do 99.9999% of the time...so I am good with it. Just because it is old doesn't mean it is worthless. :)
Thanks.
Brian - nothing new on the network, although recently after the last incident (not for that reason) I did upgrade the network switch; that was about 2 months ago now, I think, I would have to check my records on the exact date. No failure, yet, since the last time.
Yes, I had tried an external USB-to-RJ45 NIC when the other NIC(s) were down and that new NIC would not work either which may lend itself to either the motherboard itself or Windows. But, again, all is happy and well again after I delete the drivers ONLY from Device Manager and I am not even really deleting the drivers, just the "setup" in Device Manager.
Very odd problem.
I would like to know why besides they just die....
But we may have to just chalk this up to unsolveable or at least not worth our time to figure out. :)
It is an old system but it works and does what it is supposed to do 99.9999% of the time...so I am good with it. Just because it is old doesn't mean it is worthless. :)
Thanks.
Yes, sometimes it basically comes down to cost of troubleshooting versus cost of the downtime. All the best.
also you may need to reset there network on your computer. which clears all cache for networks