February 16, 2012 at 8:43 am
I can remotely connect to the Default instance of a new SQL Server 2008 R2 machine that I configured but when I attempt to connect to Named instance remotely it fails.
I can connect to the named instance when I log onto the Server.
I right clicked on the Named instance in SSMS and Selected properties>> Connections.
Allow remote connections is checked.
Any help would be greatly appreciated.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 16, 2012 at 8:48 am
Couple of things to check
Is SQL Browser started so that port numbers can be translated?
Can you connect using the port number for the named instance? SERVER\Instance,1433
Server firewall blocking the named instance port?
Corporate firewall blocking the named instance port?
February 16, 2012 at 8:58 am
I goggled it before reading you post and it was the browser.
Thank for the good suggestions.:-)
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 16, 2012 at 9:19 am
Gianluca Sartori (2/16/2012)
Use PortQry to test the sqlbrowser service from the client machine.If you can't connect to it, you can't connect to named instances (you wouldn't know which port to connect to).
You can set up an alias for the instance using the SQLServer configuration manager -> native client config on whatever clients need to connect to it. In that case you will not need the browser but you'll have to assign a port to the instance.
The probability of survival is inversely proportional to the angle of arrival.
February 16, 2012 at 9:22 am
Gianluca Sartori (2/16/2012)
Use PortQry to test the sqlbrowser service from the client machine.If you can't connect to it, you can't connect to named instances (you wouldn't know which port to connect to).
Make sure you override the protocol to UDP if using this as the default is TCP. E.g. the command line would look like:
PortQry -n servername -e 1434 -p UDP
And the response would show the instances listed on that machine.
I tend to favour disabling SQL Browser these days and use fixed ports/aliases as it's just more secure...
February 16, 2012 at 9:28 am
HowardW (2/16/2012)
Gianluca Sartori (2/16/2012)
Use PortQry to test the sqlbrowser service from the client machine.If you can't connect to it, you can't connect to named instances (you wouldn't know which port to connect to).
Make sure you override the protocol to UDP if using this as the default is TCP. E.g. the command line would look like:
PortQry -n servername -e 1434 -p UDPAnd the response would show the instances listed on that machine.
I tend to favour disabling SQL Browser these days and use fixed ports/aliases as it's just more secure...
... and less complicated!
-- Gianluca Sartori
February 16, 2012 at 12:41 pm
Thanks for you feedback.
I have already resolved the issue.
PortQry is cool but I ran the statement and it only returned to default instance not the named instance that I had an issue with before I resolved the problem.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 16, 2012 at 1:37 pm
Inquiring minds want to know... What was the issue and how did you solve it?
Jared
CE - Microsoft
February 16, 2012 at 2:28 pm
SQLKnowItAll (2/16/2012)
Inquiring minds want to know... What was the issue and how did you solve it?
+1
-- Gianluca Sartori
February 17, 2012 at 5:36 am
Welsh Corgi (2/16/2012)
I goggled it before reading you post and it was the browser.Thank for the good suggestions.:-)
I previously stated that the problem was with the browser.
I had to start that service and that resolved the problem.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 18, 2012 at 12:27 pm
Gianluca Sartori (2/16/2012)
SQLKnowItAll (2/16/2012)
Inquiring minds want to know... What was the issue and how did you solve it?+1
-2
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 19, 2012 at 11:27 am
Welsh Corgi (2/18/2012)
Gianluca Sartori (2/16/2012)
SQLKnowItAll (2/16/2012)
Inquiring minds want to know... What was the issue and how did you solve it?+1
-2
🙂
-- Gianluca Sartori
February 1, 2016 at 11:02 pm
I have a similar issue and it is rather odd.
SQL Browser is running (check)
TCP/IP is enabled (check)
Port is statically configured to 1433 (check)
This is SQL 2012 Express that I'm trying to connect to. We do have Firewall rules in place, but port 1433 is allowed. In fact if I use Telnet to that Server by name or IP and pass port 1433 I get a connection.
If I put in only the HOSTNAME (no \SQLEXPRESS) in SSMS I get a connection (this is very odd to me :w00t: ). If I put in the HOSTNAME\SQLEXPRESS no connection. If I put in HOSTNAME\SQLEXPRESS,1433 I get a connection.
Perhaps SQL Browser is not getting through?
Regards, Irish
February 2, 2016 at 1:14 am
Jeffrey Irish (2/1/2016)
Perhaps SQL Browser is not getting through?
That's the most likely answer. Test SQL Browser connectivity with PortQry on UDP 1434.
-- Gianluca Sartori
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply