Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
Sql server 2012 connection
Sql server 2012 connection
Rate Topic
Display Mode
Topic Options
Author
Message
IgorMi
IgorMi
Posted Monday, November 12, 2012 3:39 AM
SSCommitted
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
anthony.green
anthony.green
Posted Monday, November 12, 2012 3:41 AM
SSCertifiable
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
IgorMi
IgorMi
Posted Monday, November 12, 2012 3:49 AM
SSCommitted
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
anthony.green
anthony.green
Posted Monday, November 12, 2012 3:50 AM
SSCertifiable
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
IgorMi
IgorMi
Posted Monday, November 12, 2012 4:20 AM
SSCommitted
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
Dennis Post
Dennis Post
Posted Monday, November 12, 2012 4:37 AM
SSC-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
Lowell
Lowell
Posted Monday, November 12, 2012 6:07 AM
SSChampion
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.