April 8, 2016 at 2:34 am
Hello everyone
Hope someone can confirm my thinking...
I have an environment where I can connect to named instances in 1 port of the network without specifying the port number.
However for SQL servers in a different part of the network I need to specify the port number in order to connect.
I am right in thinking that this could be due to UDP 1434 has not been allowed thru the firewalls ?
SQL browser is running on all instances.
Any thing I could check before going back to network people ?
thanks in advance.
April 8, 2016 at 2:52 am
SQL Browser runs per server, not per instance, and it only works for named instances. Therefore, if you have any default instances that don't run on the default port, you need to supply the port number when connecting. You can set up aliases in SQL Server Configuration Manager to get round that, if I remember correctly.
John
April 9, 2016 at 12:46 pm
MickyD (4/8/2016)
I am right in thinking that this could be due to UDP 1434 has not been allowed thru the firewalls ?
This would sound the most likely, check to ensure this port is allowed
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 11, 2016 at 1:49 pm
I think the PORT 1434 is reserved only for the dedicated Admin connection so you cannot use that for general use. Only one Admin at a time can use this.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply