One NIC in HP Proliant half-way fails after a day
Hello,
Dual network cards on a HP Proliant ML350 G6, not setup in a team. Server 2003 OS.
The primary NIC has a public IP (a Cisco router in transparent bridge mode is in front of it, firewalling all traffic except port 80).
The secondary NIC has a private IP and connected to a private network.
The server runs IIS web server only.
After installing a third NIC (USB Trendnet NIC) a few weeks back (wish I never had) - primary NIC now kind of goes offline after about 24 hours or less.
When I say "kind of" - the NIC is up, appears normal, and I can ping the gateway from the inside. But you cannot access the web server from the outside. Also - we had port 20000 tunneled in for RDP which would also stop working when the NIC seemed to go down. Removed the port forwarding and set the server back to the default 3389 but no change.
Running a repair on the NIC or rebooting fixes it, short term.
Uninstalled the Trendnet drivers software, no change. Updated the drivers from what it was using before to the HP drivers from HP's site, no change.
Any ideas?
Dual network cards on a HP Proliant ML350 G6, not setup in a team. Server 2003 OS.
The primary NIC has a public IP (a Cisco router in transparent bridge mode is in front of it, firewalling all traffic except port 80).
The secondary NIC has a private IP and connected to a private network.
The server runs IIS web server only.
After installing a third NIC (USB Trendnet NIC) a few weeks back (wish I never had) - primary NIC now kind of goes offline after about 24 hours or less.
When I say "kind of" - the NIC is up, appears normal, and I can ping the gateway from the inside. But you cannot access the web server from the outside. Also - we had port 20000 tunneled in for RDP which would also stop working when the NIC seemed to go down. Removed the port forwarding and set the server back to the default 3389 but no change.
Running a repair on the NIC or rebooting fixes it, short term.
Uninstalled the Trendnet drivers software, no change. Updated the drivers from what it was using before to the HP drivers from HP's site, no change.
Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As you have fixed your own problem, you seem to be someone who is very capable. Perhaps your input to the site on a regular basis could be helpful to the rest of us? I'm here today because I have a similar issue and I'm looking for answers. There are many of the questions on this forum that either you or I could probably answer quite easily. But do we? This site is a community, not a tech support service (even though we pay for the privilege of membership), so we can't really blame the site itself when we don't get the answers we want. If the community members who have seen these issues before are there and watching, they can probably be very helpful. But many of them, like you and I, are probably only looking when they have a problem, and not contributing when all is well. It's hard to point the finger at others for what we ourselves are guilty of. I invite you, and I will try as well, to watch for questions that you can answer and be on the other side of the issue for a while. We can be part of the solution instead of part of the problem.
ASKER