Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Sql server 2012 connection Expand / Collapse
Author
Message
Posted Monday, November 12, 2012 3:39 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 8:28 PM
Points: 1,905, Visits: 1,522
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



Post #1383588
Posted Monday, November 12, 2012 3:41 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833
Is there a reason you have set the 2012 instance to listen on the SQL browser port?



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1383589
Posted Monday, November 12, 2012 3:49 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 8:28 PM
Points: 1,905, Visits: 1,522
If i leave both instances to listen on the default port 1433, then the second's services don't start.
Regards
IgorMi
Post #1383593
Posted Monday, November 12, 2012 3:50 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833
Change the 2012 instance to listen on a different port, but not 1434 as that port is used for the SQL Browser service



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1383597
Posted Monday, November 12, 2012 4:20 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 8:28 PM
Points: 1,905, Visits: 1,522
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


Post #1383601
Posted Monday, November 12, 2012 4:37 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 6:48 AM
Points: 109, Visits: 305
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.
http://www.sqlservercentral.com/articles/Best+Practices/61537/

"Million-to-one chances crop up nine times out of ten." ― Terry Pratchett, Mort
Post #1383608
Posted Monday, November 12, 2012 6:07 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:59 PM
Points: 11,792, Visits: 28,078
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

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1383649
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse