asked on

Allowing Remote Connections to SQL Server 2005 through Windows Firewall

Hi all,

I am trying to allow sql remote connections to SQL Express 2005.

Now if I turn off the windows firewall I can connect successfully, However when I turn on the public profile settings it stops any connection being made.

I've added UDP port 1434 and TCP port 1433 to be allowed as both incomgin and outgoing ruls on the fire wall.

However when I try to connect through VS im getting the 40 error, saying the server doesnt exist?

Any ideas?

VB ITS

Have you tried all the steps in this article? http://support.microsoft.com/kb/914277

Take note of the text in bold blue text as they collapse to reveal instructions when clicked.

ASKER CERTIFIED SOLUTION

Vitor Montalvão

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

flynny

ASKER

Thanks for the replies guys,

Vitor,

Yes there is an instance of SQL Server 2008 running on the server as well. How do I identify theport thats being used on the instance?

(As far as I was aware 1434 UDP redirected to the correct instance? am I wrong?)

Vitor Montalvão

The 1433 and 1434 are used by default for the first installed instance but you can confirm it in SQL Server Configuration Manager by checking in the TCP/IP properties of the instance.

flynny

ASKER

Many thanks Vitor, there insrance was running on a different port.

http://sqlandme.com/2013/05/01/sql-server-finding-tcp-port-number-sql-instance-is-listening-on/

helped me identify and solve.

Thanks for pointing me in the right direction.

Vitor Montalvão

Just a warning. If the server is behind a firewall you won't want to set a dynamic port for that instance because after each reboot it may use a different port so it's better you chose a static port.