Sql server 2012 connection

Question

Post reply

Sql server 2012 connection

Igor Micev

SSC-Dedicated

Points: 33109
More actions
November 12, 2012 at 3:39 am

#270139

Hi All,
I've got installed two sql server instances on a server: slq2008 r2 and sql2012.
sql2008 r2 listens on default port 1433, and sql2012 is set to listen on 1434 port.
When configured with ports 1433 and 1434 respectively, I can connect remotely to sql2012, but an issue is the following:
When I try to connect at fist hand it fails with message
"
Cannot connect to server_name\SQL2012.
------------------------------
ADDITIONAL INFORMATION:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
"
After that trying to connect again it successes. The services are running.
When I try to connect directly when working on the machine i don't have these issues
Have anyone had issues like this one?
Please share experiences
Regards
IgorMi
Igor Micev,My blog: www.igormicev.com

Viewing 7 posts - 1 through 6 (of 6 total)

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

Ant-Green SSC Guru Points: 113507 More actions · Answer 1

Is there a reason you have set the 2012 instance to listen on the SQL browser port?

Igor Micev SSC-Dedicated Points: 33109 More actions · Answer 2

If i leave both instances to listen on the default port 1433, then the second's services don't start.

Regards

IgorMi

Igor Micev,My blog: www.igormicev.com

Ant-Green SSC Guru Points: 113507 More actions · Answer 3

Change the 2012 instance to listen on a different port, but not 1434 as that port is used for the SQL Browser service

Igor Micev SSC-Dedicated Points: 33109 More actions · Answer 4

Hi,

I've changed it to 1435 (i would have changed it to another one later) but it is not that.

I was trying to connect from ssms 2008 and 2012 and the same issue, at first it fails, and then it successes...

However, meanwhile I fortunately surpassed this issue, adding port 1435 to the Firewall advanced settings for TCP port for SQL Server in the Local ports listing (It was only 1433). And because for Remote ports the listing is "All ports" I'm realizing why it fails at first and then successes.

Thank you for your replies!

IgorMi

Igor Micev,My blog: www.igormicev.com

Dennis Post SSCarpal Tunnel Points: 4473 More actions · Answer 5

Hi,

You can also add sqlserver.exe to your firewall exception (Without any ports). That'll allow you to use dynamic ports.

For better, quicker answers on T-SQL questions, read Jeff Moden's suggestions.[/url]

"Million-to-one chances crop up nine times out of ten." ― Terry Pratchett, Mort

Lowell SSC Guru Points: 323518 More actions · Answer 6

on my dev machine I have the last 4 versions of SQL installed.,and i have a port layout scheme to make it obvious to myself,

my default instance is 2005 listening on the default port of 1433.

For my other instances, I gave them static ports kind of matching their versions:

SQL2008 on port 10000

SQL2008R2 on port 10500

SQL2012 on port 11000

my day to day development is on R2 now, but i need all versions in order to test various client databases.(or to be ready...no customers with 2012 yet)

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!