Can remote into just one instance on server

Question

Can remote into just one instance on server

adams.squared

SSCrazy

Points: 2675
More actions
August 6, 2010 at 10:55 am

#222279

I have a server with 2 instances. One is the default and one is named. I can remote into the default instance, but not the named. Both have the Allow Remote Connections checked off. I can log into both when local.

Viewing 14 posts - 1 through 13 (of 13 total)

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

Carl Federl One Orange Chip Points: 25384 More actions · Answer 1

If SQL Server is running on a Cluster and certain other conditions apply, such as VPN, then this is a known bug.

http://blogs.msdn.com/b/sql_protocols/archive/2006/02/27/unable-to-connect-to-a-sql-server-named-instance-on-a-cluster.aspx

SQL = Scarcely Qualifies as a Language

adams.squared SSCrazy Points: 2675 More actions · Answer 2

adams.squared

SSCrazy

Points: 2675

August 6, 2010 at 11:01 am

#1203681

I'm not running this one on a cluster.

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 3

By "remote in", do you mean RDP in? There's only one node to RDP into if so and therefore you are done. If you mean "connect", you've confused the issue. I suspect you meant that you only can connect when you are logged on locally, and cannot connect from a different machine. Please confirm before we go further, otherwise we may troubleshoot the wrong problem.

Varghese Pathisseril SSC Rookie Points: 25 More actions · Answer 4

There are some confusion with this question. With the exception of default instance all instance are called named instance in standalone system. You can RDP only to the Default instance name or physical host name.

Hostname: Server1

Default Instance Name: Server1

All additional instance name as follow: Server1\VS1, Server\VS2, Server\VS3 .....

Good luck

adams.squared SSCrazy Points: 2675 More actions · Answer 5

sorry about that. i am trying to connect using Management Studio from my client. I can connect to the default instance, but not to the named instance. If I RDP into the server, I can connect to both instances locally.

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 6

OK, so we ARE trying to connect here. My guess is that default is on 1433 and that you don't have the SQL Browser running. Can you confirm the status of the SQL Browser?

adams.squared SSCrazy Points: 2675 More actions · Answer 7

The browser was running on the server. it's not on the client, but I'm assuming that is not necessary since i am not trying to connect to the client.

TITLE: Connect to Server
------------------------------
Cannot connect to gpdev-01\test1.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. 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, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

A specified SQL Server instance name is not valid. name is correct

The TCP, or named pipes protocols are not enabled. enabled

The firewall on the server has refused the connection. <shrug> I can connect to default instance, wouldn't that mean I should be able to connect to the named instance?

The SQL Server Browser service (sqlbrowser) is not started. started

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 8

If the named instance has been moved to a static port, then no, the firewall could still be an issue. The firewall opens up both addresses and ports, and while the Browser can route dynamic ports, it won't do static ports. Try to telnet to the port in question remotely and see if anything is listening on that port/if it makes it past the firewall.

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 9

This looks like a VERY helpful article about your exact issue:

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

adams.squared SSCrazy Points: 2675 More actions · Answer 10

that should give me something to mess with for a while. i'll let you know how it turns out.

thanks

adams.squared SSCrazy Points: 2675 More actions · Answer 11

It was the firewall. I shut it down on the server and it works fine. Now I'll work on the firewall on Server 2008 to get it to work right.

Thanks

sunil kak SSC-Addicted Points: 470 More actions · Answer 12

Try connecting by specifying the port no of the named instance

e.g. gpdev-01\test1,<port no>

Steve Jones - SSC Editor SSC Guru Points: 736063 More actions · Answer 13

Use configuration manager to set a specific port for the named instances, then enable the firewall, allow traffic through for those ports. Specify as listed above.

server, port