Changing the firewall with Windows XP/Vista

Tutorials showing methods of fixing connection failures

Changing the firewall with Windows XP/Vista

Postby Ablyss » Fri Jul 26, 2013 11:13 am

These steps apply to the version of Windows Firewall that is included in Windows XP Service Pack 2 (SP2) and in Windows Server 2003.
If you are running a firewall on the computer that is running SQL Server 2005, external connections to SQL Server 2005 will be blocked unless
SQL Server 2005 and the SQL Server Browser service can communicate through the firewall. You must create an exception for each instance of
SQL Server 2005 that you want to accept remote connections and an exception for the SQL Server Browser service.

SQL Server 2005 uses an instance ID as part of the path when you install its program files. To create an exception
for each instance of SQL Server, you must identify the correct instance ID. To obtain an instance ID, follow these steps:

  1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, click the SQL Server Browser service in the right pane, right-click the instance name in the main window, and then click Properties.

On the SQL Server Browser Properties page, click the Advanced tab, locate the instance ID in the property list, and then click OK.


To open Windows Firewall, click Start, click Run, type firewall.cpl, and then click OK.Alternatively open Windows Firewall through the control panel.
If the machine where SQL Server has been installed is a 64 bit one, the files mentioned in the following points can be found at C:\Program Files (x86)\Microsoft SQL Server\.

Creating exceptions for SQL Server 2005 in Windows Firewall
    To create an exception for SQL Server 2005 in Windows Firewall, follow these steps:
  1. For XP and Vista, open Windows Firewall and click the Exceptions tab, and then click Add Program.

  2. Browse for the file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe. Click Open, and then click OK.
    MSSQL.1 is a placeholder for the instance ID that you obtained in step 3 of the previous procedure.
  3. Repeat the process and add the programme C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe

Note: the path may be different depending on where SQL Server 2005 is installed (For 64bit machines the default location is C:\Program Files (x86)\Microsoft SQL Server\).
[*] You must also ensure that file and print sharing is enabled on the server.

3rd Party Firewalls

If you have 3rd party firewall software you will need to make sure that these settings are also applied.

If the client is unable to connect to the server with the server firewall enabled but it can connect when the server firewall has been disabled and you use 3rd party firewall software further considerations need to be made.

On a peer-to-peer network (a network of linked computers that are not domain authenticated) the NETBIOS protocol needs to be enabled.
The NETBIOS protocol translates the IP address of a computer into a name. For example typing HOSTNAME at the command prompt provides us with the user
friendly NETBIOS name. By default this protocol is blocked with many 3rd party firewalls, so access will need to be given.

You could find up to 3 variations of the NETBIOS protocol which will all need to be unblocked.

NETBIOS Name Service
NETBIOS Datagram
NETBIOS Session.

Computers on a network with a dedicated server running Windows Server Technology use DNS protocols and do not require the NETBIOS protocol to function.
Site Admin
Posts: 23
Joined: Thu Jul 25, 2013 3:53 pm

Return to Connection Failure

Who is online

Users browsing this forum: No registered users and 0 guests