Saturday, January 15, 2011

I can't find firewall on Windows Server 2003 Enterprise Edition

I Just want to open the 1433 port for SQL Server locally, please I dont know who config this server so when I try netsh firewall , prompt saids "the command not exits" by the way routing and nat are disabled

I cannot find Windows Firewall Option on this Server, thats the most rarely!

Server Version : Windows Server 2003 Enterprise Edition (5.2, Build 3790) without any Service Pack

Thanks!

alt text

  • Go to the Control Panel and double-click on Windows Firewall. It will ask you if you want to start ICS, say yes, then you should be able to add the exception there. Don't forget to add exceptions for RDP and www if you use it.

    Angel Escobedo : I cant find Windows Firewall on Control Panel thanks
    mrdenny : Not sure how, but it sounds like the Windows Firewall has been removed. Does the Windows Firewall service exist in the service list?
    Angel Escobedo : omg not exists!
    Adam Brand : Hm that is no good. Do you have an Anti-Virus program installed? If not, install AVG or something and give it a scan. The firewall is not something that can be easily installed/uninstalled.
    Angel Escobedo : When I begin with this since 2 months ago... MacAffe was installed nowadays the AV is NOD32
    Angel Escobedo : by the way, the main IP is protected by Perimetal Firewall and a Unix Enrouting, so in short terms "is a little secure for us" but I want to try open ports manually how can I achieve this?
    : If you can't seem to find the firewall on the server then what leads you to believe the box has firewall rules? Could it be that SQL server is either not listening on port 1433 or not using TCP/IP as a transport? Have you tried using localhost:1433?
    Adam Brand : Sounds really bad to me...I would consider nuking the server if the firewall is gone.
    From Adam Brand
  • Try opening the Windows Firewall UI from the Start Menu's Run command:

    • Start-> Run
    • firewall.cpl

    You should have the Windows Firewall now.

    If the Windows Firewall isn't able to run on your system, consider updating your system to Windows 2003 Service Pack 2 or better.

    Angel Escobedo : please check the image above
    pcampbell : Thanks to Albic, it appears there IS no Windows Firewall pre-SP1. Of course, it's always recommended to keep up with security fixes. Are you able to apply those service packs?
    From pcampbell
  • According to the Wikipedia article the Windows Firewall for Windows Server 2003 was introduced with Service Pack 1. Therefore it is not included in the RTM build which you are running.

    After the installation of Service Pack 1 (or better Service Pack 2) you should be able to access the feature.

    This Technet page describes the changes to the firewall in Service Pack 1 in more detail.

    From Albic
  • Looks like you may not have the Windows Firewall afterall... :)

    But your main goal seems to be to enable connectivity to your SQL Server instance. Since I don't know what version/edition of SQL Server you have but I am guessing that you have SQL 2005 as 2008 would not install on Win2003 RTM. So here is a useful link: http://support.microsoft.com/kb/914277/en-us

    From

0 comments:

Post a Comment