Firewall Strange Behaviour

August 13, 2010 at 22:36:09
Specs: Windows 2003 Standard
I totally am baffled over this problem. Nothing like this has ever happened to me and I doubt that I would like to see something like that happening again.

My problem is that every time I turn ON Windows Firewall, my server will after about 1 or 2 minute shut all ports out except RDP. You could try the IIS and it would timeout, ping will not give you a reply, ftp would not connect and everything else will fail. Then when you turn off the Firewall, it will be back to normal again.

I know some of you guys would most probably tell me that I would need to Add Exceptions but I have already done that. I have these ports open : 80, 21, 110, 587, 25, 53.

The strangest thing is that if you turn on Windows Firewall, it does not stop traffic immediately but rather wait for a minute or 2 before it will stop the traffic. Why is this happening? Does anyone know what's going on? Any suggestions on what to check on?

"There are two ways to live your life. One is as though nothing is a miracle. The other is as though everything is a miracle." -- Albert Einstein


See More: Firewall Strange Behaviour

Report •

#1
August 14, 2010 at 02:36:26
Is the "dont allow exceptions" box ticked on the firewall? Additionally why are you wasting time with the Windows firewall? Do you not already have a firewall on your gateway upstream?

Report •

#2
August 14, 2010 at 02:44:41
1. Don't allow exceptions is not checked.

2. I don't know which upstream providers are providing free firewall protections but I know I wouldn't be wanting to be with them coz if lets say my program runs on a very strange port, then I guess I won't be able to use it coz they have already blocked it.

"There are two ways to live your life. One is as though nothing is a miracle. The other is as though everything is a miracle." -- Albert Einstein


Report •

#3
August 14, 2010 at 07:11:43
If your server is connected to the internet then presumably your router is an integrated device that has firewall capabilitys no? And additionally ISP's block very few ports other than maybe 25. Traffic should no be shaped per se other than to ensure QoS.

Report •


#4
August 14, 2010 at 09:00:22
It's a Web Server. All ports are OPEN on my side. Server provider does not care about the other ports being open.

Can we stay on topic perhaps? It has nothing to do with my Server Provider or etc.

"There are two ways to live your life. One is as though nothing is a miracle. The other is as though everything is a miracle." -- Albert Einstein


Report •

Ask Question