February 8, 2012 at 9:31 am
We have 2008 installed as default instance, at a later date we installed 2008R2 on same box and disabled default instance.
From outside, we access R2 always as ip\MSSQLR2
And it worked all these days.
Now hosting guys moved the server to a different zone on the network etc, it got a new ip etc,
2008 default instance is still disabled.
Now From outside, if we try newip\MSSQLR2, we get 'unable to find the instance' error.
We tried just newip and it works fine (and is connecting to the MSSQLR2 instance).
Why is this happening? What are the rules???? Does it just go by what is listening on port and ignore the instance name? Should it still not respond fine when we give the instance name too in connection parameters??
Locally on the db server machine, when we use SSMS, it connects fine for newip and newip/MSSQLR2
Just not for out side connections.. so where do we control this behavior?????
February 8, 2012 at 11:11 am
Named instances listen on a non standard port, either dynamic or static.
The SQL Server Browser service tells the clients on which port the named instance is listening. If you cannot contact the UDP port 1434, you can't connect to the browser service and you don't know which port to attach to. First thing I would check is firewall rules.
If you can connect to the named instance without specifying the instance name, two things could have happened:
1) There's an alias in your native client configuration
2) Somebody changed the port of the named instance to TCP 1433.
Hope this helps
Gianluca
-- Gianluca Sartori
February 8, 2012 at 2:21 pm
Got It. Thank you! That's what the firewall guys did probably (fix 1433 as the port for R2), when we complained that sql server is not accessible on that port.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply