Windows Server Firewalls (2008 and SBS 2008) - Definitive stance on disabling firewalls

Hi Folks,

I'm looking for some definitive facts/stance on the Windows Server 2008 firewall/SBS 2008 firewalls. Or some recommendations from an authority.

When we have had a situation where we had to turn the Windows firewall off (I realize we can set exclusions but they don't always work), we have taken a few different approaches:

1. Turn it off in the GUI (http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx) - we've done this and on occasion (several), it will indicate it is off in the GUI but will still block ports (intermittantly)

2. Set the firewall service to manual - we've tried this but same as #1, it will actually start to block certain traffic on occasion after a period of time

3. This is the tact we've come to taking - we DISABLE the firewall service.  I have no doubt that this is officially unsupported by Microsoft for the security impact (these are small business networks however, not NASA or Fort Knox).  This seems to work definitively at keeping these ports open ... however, I've run into two occasions where Exchange 2007 stops allowing connections after a period of time (and in fact, Exchange 2007 won't allow you to install unless the firewall service is running).

*sigh* - what is a girl/boy to do?  What key step/information are we missing here to ensure our connections work ALL OF THE TIME?  

Of course it is a good idea to have the firewall on - but if starts closing ports that are excluded, the disruption to a customer is not a good thing, particularly if the ports being closed are RDP such that we can't support them remotely either to fix the situation.

Comments welcome but I'm really looking for someone to point out or say something new here - something we are missing...  Thanks!
LVL 13
itgrooveAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Christopher BarnesCommented:
I have installed about 15 SBS 2008. I never ever turn the firewall off and never need to. You need to look at the situation more carefully. You talk about having trouble with RDP. RDP is a a essential component of SBS 2008 and all MS Servers. I don't believe the server/firewall/OS is closing the ports. More likely to be a router or other software running on the server. What anti virus are you running? What router does the client use?

Hardware based firewalls (maybe on the router) and sofware based firewalls (typically MS server firewall) are essential. It does not matter if you are a big or small business. The Internet is a bad place and hackers love to take over Small Business Servers and use then as SMTP relays and proxies.
0
itgrooveAuthor Commented:
LOL.  Yes, I get that and I wouldn't have posted this without considering the 'situation more carefully'. All of our customers have a Gateway/Firewall, we would never consider not having a firewall, however the local one is the one that is causing trouble.
And I'm happy for your luck in this situation (or maybe you hit the nail on the head, what AV are you using?  We use Trend) but I can say with utmost confidence that we have tested RDP connections inside the network - the local SBS box was blocking the port from connectivity (note, we use a different port, to obsure the port but the firewall should be honouring our exception rule, just like it would for TCP3389).  In these cases (and it is not just RDP), after a period of time, it will just close.  We can ping the server, we can get to it using a file share - thus the server is up but inside the network and out, RDP will be off (or in some cases, OWA/https or SMTP will be denying connectivity).
This looks to be a directly related problem that we've stumbled upon - that may be exactly the problem we are running into.  http://support.microsoft.com/default.aspx?scid=kb;EN-US;961775
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
itgrooveAuthor Commented:
Didn't get much commentary but I do appreciate barnescr attempt.  I believe, at least for 2 most recent occurrences, that the support article I have posted is relevant and will recur.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.