Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On a Windows Server 2003 there is a strange issue. Every 6 hours the server don't accept outbound TCP/IP traffic while inbound traffic working fine.

If the problem occurs I can connect with RDP to the server and ping around the world. If I try to connect to let's say an SMTP server using telnet on the same network switch, I can't get a connection. If I try to go to a Website (using Firefox or IE) I can't get an answer. But if I try to connect from another LAN Client to the server it works, I can use all TCP/IP Services on the Server but only inbound. The server doesn't use DHCP, it has a static IP and uses as DNS Server.

If I restart the Server everything works fine for exact 6 Hours and then the error occurs again. Netstat shows me about 200 Connections and I try to set the MaxUserPort to 20000, if I restart the Network with nets int ip reset c:\resetlog.txt the issue is still the same. Only a restart will help.

What could cause such an error and where should I look for evidence on that outbound TCP/IP problem?

share|improve this question
During the times where outbound traffic does not work, launch netmon/wireshark on a client machine and capture traffic as you try to attempt to go to a webpage or portqry out. This should help you follow the packets and determine where the blockage is occurring. – KPS Dec 24 '14 at 18:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.