August 19, 2012 at 8:20 pm
A strange problem has cropped up in our enviornment that I'm kind of scratching my head about. Why all of a sudden would users who connect via Management Studio or Query tools have to enter the port to connect to SQL Server? Ideas of what to look at?
August 19, 2012 at 11:19 pm
I think SQL Server Browser service has stopped.
August 20, 2012 at 2:06 am
i go with suresh.
Regards
Durai Nagarajan
August 20, 2012 at 5:13 am
If SQL Server Browser Services is stopped then you have to specify the port number when connecting to that SQL Server instance.
August 20, 2012 at 5:18 am
No, checked for that. The Browser services is running on all systems where this is occurring.
August 20, 2012 at 5:58 am
is "named pipes" enabled in sql configuration manager
Regards
Durai Nagarajan
August 21, 2012 at 12:26 am
If you specifically set the Network Protocol in the 'Connection Properties' of SSMS to be 'TCP/IP', do you still need the port?
If you connect via sqlcmd, do you need the port?
Do you have any aliases set up in Configuration Manager?
August 28, 2012 at 12:55 pm
check for UDP port 1434 not being blocked by a firewall.
August 28, 2012 at 1:37 pm
Thanks for the responses. I will pass it along. It appears to be a security issue only happening to laptop users coming in via the VPN.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply