cannot connect to named instance thru SSMS on developers desktop

Question

cannot connect to named instance thru SSMS on developers desktop

SQListic

SSCertifiable

Points: 6904
More actions
August 28, 2012 at 4:53 pm

#260711

Hi Experts,
I got a scenario where one of the developer cannot connect to named instance, but able to connect to default instance thru desktop. He got RDP access to sql server and able to login into both instances but not thru SSMS on the desktop ?
Please Help
Thanks!

Viewing 15 posts - 1 through 15 (of 22 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Could you explain 'cannot connect' a little more? What happens? What errors? What investigation has been done?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 2

Agreed, need the error to help here. There's a few dozen things it could be.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

My complete guess would be that the SQL browser service isn't running or he's got a firewall blocking the higher ports.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQListic SSCertifiable Points: 6904 More actions · Answer 4

Thanks for the reply.

Here is the error message

-----------------------------------------

Cannot connect to servername\instancename

Additional information

A netowrk-related or instance-specific error occure while establising a connection to SQL Sevrer.

The server was not found or was not accesible.verify that the instance name is correct and that SQL Server is configured to allow remote connections(provider:SQL network Interfaces,error 26-

Error Locating Server/instance Specified)(Microsoft SQL Server)

------------------------------

How to upload images into Sqlservercentral.com forums?

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 5

Verify that remote connections for the instance are set to on, and double check the listener on the server that the instance is listed. I think Gail's wild guess is accurate here, and is definately the place to start with the error you transposed.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

SQListic SSCertifiable Points: 6904 More actions · Answer 6

checked remote connections for the instance set on. It is enabled.

Does each SQL Server listens on different port numbers?

for example: default on 1433 and named on something else ?

if we have two instances installed on a box , do we see two sql server browsers in sql server configuration manager ?

because i am seeing only one SQL Server Browser service here

Thanks all. This is the best place to learn SQL Server.

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 7

Sqlism (8/28/2012)
checked remote connections for the instance set on. It is enabled.

One down... 🙂

Does each SQL Server listens on different port numbers?
for example: default on 1433 and named on something else ?

Yuppers, each instance gets its own port. First is 1433 everything else is random between 1024 and 5000, depending on what's open, runs under Winsock (or at least used to). 1434 is the browser (listener). couple of others are dedicated as well, like SQL Broker.

if we have two instances installed on a box , do we see two sql server browsers in sql server configuration manager ?
because i see only one SQL Server Browser service

Yeah, you're supposed to. You should see something like this:

If you do, make sure TCP/IP is ON for the instance.

If you don't, RDP to the server and get into the services. Make sure a service called: "SQL Server Browser" is started. If it isn't, fire it up or correct whatever issues it's having.

Generally, an overview and some help using the Browser:

http://www.mssqltips.com/sqlservertip/1946/overview-of-the-sql-server-browser-service/

Let us know what you find from there, if anything.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

SQListic SSCertifiable Points: 6904 More actions · Answer 8

I can see two instances under SQL Server Network Services in SQL Server config manager

In default instance:

Right clicked TCP/IP--> Properties---> Ip adresses .... I can see port number as 1433

In named Instance:

Right clicked TCP/IP--> Properties---> Ip adresses .... I can NOT see port number as 1433, it is just left blank

Strangely if this is the cause ?

How can i connect to this named instane from one of the production servers management studio 😮

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 9

Sqlism (8/28/2012)
In named Instance:
Right clicked TCP/IP--> Properties---> Ip adresses .... I can NOT see port number as 1433, it is just left blank

Yeah, check the last value, it should be dynamic. It will function, just doesn't hard-port it if you don't set it that way.

How can i connect to this named instane from one of the production servers management studio 😮

It does make it more difficult to directly connect to a non-dedicated port value. I'm getting a bit deep for my experience (and available research time). I'm going to call in some backup since it's not the easy fixes, it's been a while since I argued with this particular issue.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 10

As long as the SQL Browser service is running on the server, there should be no issues connecting to a named instance. The client contacts the SQL Browser service, asks for the port the named instance is running on and then connects on that port.

Hence checking whether SQL Browser is running should be the first step.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQListic SSCertifiable Points: 6904 More actions · Answer 11

i can see one sql server browser running in configuration manager

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 12

Sqlism (8/28/2012)
i can see one sql server browser running in configuration manager

You would need to check if it's running in services. RDP to the box, Rt-Click on "My Computer", select manage. Near the bottom of the list you'll see 'Services'. Click that, and in the list that pops on the right scroll down until you find SQL Server Browser. Make sure it has the word 'Started' in its line. If it doesn't, rt-click and try to start it.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

JMD7 Valued Member Points: 73 More actions · Answer 13

SQL Browser uses UDP port 1434 for all it's communication. If Firewall is enabled on your database server, please ensure you have setup the inbound rule in "Inbound Rules" in the Windows Firewall on the database server.

The In bound Rule needs to be setup for Profile="Domain", Enabled="Yes", Action="Allow", Override="No",Program="Any",Local Address="Any", Remote Address="Any", Protocol="UDP", Local Port= "1434",Remote Port="Any",Allowed Users="Any" and Allowed Computers= "Any".

If it still does not work, there is a possibility that you have a network level Access Control List (ACL) blocking access to UDP port 1434 on the database server from client machines.

Your network team may need to allow access to UDP port 1434 on yourdatabaseserver (ip address) from all of your companies client machine subnets.

Hope this helps.

spaghettidba SSC Guru Points: 105732 More actions · Answer 14

I would:

1) check if the named instance is reachable from the client machine. You can do that specifying the port number in the "server name" box using a comma: SERVER,port

2) if 1) works and you cannot connect using SERVER\INSTANCE, the sqlbrowser service may be unreachable. You could use PortQry on the client machine and check if the browser service is reachable.

3) if the browser service is unreachable, could be a firewall issue. The firewall should be configured to allow connections on port UDP 1434 from ANY address and to ANY address. If this is a clustered instance, be aware that the browser service is not cluster-aware and could respond to datagrams incoming on the virtual IP address with datagrams originating from the physical IP address. This causes most firewalls to drop the datagram, unless ANY address is specified in the rule for incoming and outgoing IPs.

Hope this helps

Gianluca

-- Gianluca Sartori