Close This Window

Connectivity: Windows XP Service Pack 2 Firewall Configuration.

SYMPTOMS

After installing Windows XP Service Pack 2

Connection Failed:
SQLState:'01000'
SQL Server Error: 53
[Micosoft][ODBC SQL Server Driver][DBNETLIB] ConnectionOpen (Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error:17
[Micosoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied

OR

SQLState: S1T00 Native Error: 0 - Info. Message: [Microsoft][ODBC SQL Server Driver]Timeout expired

PROBLEM

After installing the Windows XP Service Pack 2 the Firewall stops the SQL Servers traffic across the SQL Ports. The server is running and working properly in most accounts, but communication to the server is being stopped by the Firewall.

Additional Source Information
http://support.microsoft.com/default.aspx?kbid=841251
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2chngs.mspx
 

SOLUTION PART 1:  

First be on the computer acting as the server – that is the one that has MS SQL or MSDE installed. We need to add your MSDE or SQL Installation as an allowed program to the Windows Firewall. To do this click “Start, Run” and type in “Firewall.cpl”. You should now have the Windows Firewall window open. At the top click “Exceptions”. Mid-way down the page click “Add Program..”

Now click “Browse..” and click the arrow point down beside “Look In:”. You will want to navigate yourself to the C:\Program Files\Microsoft SQL Server\MSSQL$SWDATA\Binn\ folder and click on “sqlservr.exe”.
Note: SQL Standard users may have the “sqlservr.exe” in a different location.

Now press “OK” on the 2 following screens.

SOLUTION PART 2:  

We will need to be on the computer acting as the server - that is the one that has MS SQL or MSDE installed. First we will need to find out on what TCP Port your server is running. Click on Start, and Run. In the "Open:" field type “svrnetcn.exe” and click OK. In the Enabled Protocols you should see "TCP/IP" - choose it and then click the "Properties..." button. Here you can find what port SQL is using to supply the data. Most SQL servers use TCP port 1433 for data transfer and UDP port for server acknowledgment, but this is not always the case for the TCP port. Many times the TCP port will be assigned to another number.

SOLUTION PART 3:

You will need to be logged on to an Administrator account to change these settings The solution for this problem is very simple. Navigate Windows into the control panel (Start, Control Panel) and double-click on the Windows Firewall (as seen below).

*NOTE if you receive this error "Due to an unidentified problem, Windows cannot display Windows Firewall Settings" See this link.

Once you have this open click on the “Exceptions” tab

After you select the Exceptions tab; we will now need to add the two SOAPware ports. The First port that you will need to add is the UDP Port, which is UDP 1434; then followed by the TCP Port 1433.

IMPORTANT:  The UDP will always be 1434, but your TCP port may not be 1433.  To check this, on the Server - click Start > Run > type svrnetcn.exe, click OK > Pick the Server from "Instance on this Server" > Select TCP\IP from the Enabled Protocols Box, click Properties > the Default Port will appear.  If the port is not 1433, substitute that number for 1433 in the rest of this process.

To do these simply click “Add Port”. In the Port Number field type in 1434, select “UDP”, and name it “SOAPwareUDP”. Click OK.

The next step will be to add the TCP Port to the connections. To do these simply follow the same directions as before. Click “Add Port”; in the Port number field type 1433, Choose TCP, and type in “SOAPwareTCP” in the name field and press OK.

Both of these items now should be listed in the “Exceptions Tab”. The last step that needs to be completed is to place Check Marks in the 2 items that you added as seen below.

Reboot your PC.

When your OS returns you should be able to connect to your databases once again.

Additional Source Information
http://support.microsoft.com/default.aspx?kbid=841251
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2chngs.mspx

STATUS
 

SOAPware, Inc. has confirmed that this is not a problem in the SOAPware, Inc. products listed. We are researching this problem and will post new information here in the SOAPware, Inc. Knowledge Base as it becomes available.

Close This Window

The information provided in the SOAPware, Inc. Knowledge Base is provided "as is" without warranty of any kind. SOAPware, Inc. disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall SOAPware, Inc. or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if SOAPware, Inc. or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
 

You need to register 2 DLLs. To do this you click ‘Start, Run, and type the commands below and press enter they must be done one at a time.

First:
regsvr32 c:\windows\system32\atl.dll

Second:
regsvr32 c:\windows\system32\hnetcfg.dll 
This should solve your problem of not being able to open up Windows Firewall.