Network Adapter Stops Allowing External Connections After Around 30 Hours
Here's an odd issue for you guys. I've got a server here that has an internal connection to our network through one interface, and the second interface is connected to a real world IP address as it's hosting a website there and FTP service through IIS. I'm just using a software firewall to protect it.
Here's the deal. The system works great and hosts the website really well...for about 30 hours. Then you can't access it. I can access it if I'm inside the school. But if I disable the external network card on the server, I can't access it inside the school anymore, so I know my computer in my office isn't just cheating and connecting locally. So I've found a fix, but no idea why it fixes the problem. You'd think so far that it would have to be a switch up stream or a router or something if my computer inside could access the internet services on the server by going out our gateway, and back in through the external port on the server through an outside perimeter switch, but it turns out, that the fix is to disable the network adapter, and then re-enable it. Voila, everythings running again. I really don't want the fix to be a batch script that kills the network adapter and re-enables it every 30 hours, any ideas of what this could be? Brand new Dell PowerEdge 2900 running Server 2003. Everything else works great.