March 8, 2012 at 3:05 am
I have a server that have a default instance and several named instance.
Below are the Instances:
SERVER -- <DEFAULT_INSTANCE> -- PORT 1434
SERVER -- INSTANCE1 -- PORT 1433
SERVER -- INSTANCE2 -- PORT 1435
SERVER -- INSTANCE3 -- PORT 1436
When I am connecting remotely to <DEFAULT_INSTANCE>, it instead connect to INSTANCE1. Its either using OSQL or SSMS.
To be able to connect to the default instance, its either I create an alias or specify the port after the server(SERVER,1434).
What is the rationale behind this? Is there a way to connect without specifying the port or creating an alias?
Any explanation would be greatly appreciated
March 8, 2012 at 3:19 am
Make sure the SQL Server Browser service is running and that the UDP port 1434 is open on the firewall (both sides: server and client).
Aliases aside, without querying the SQL Browser, default instance means port 1433 and named instance means unknown port (unable to connect).
-- Gianluca Sartori
March 8, 2012 at 4:33 am
Possibly because INSTANCE01 is on the port that would normally be used for a default instance.
Maybe when you make a request to a default instance (i.e. no instance name), a call to the SQL browser service is not made to identify the correct port, and 1434 is just assumed ?
[font="Courier New"]sqlmunkee[/font]
[font="Courier New"]Bringing joy and happiness via SQL Server since 1998[/font]
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply