February 19, 2015 at 6:13 am
HI,
version: SQL SERVER 2012 enterprise edition and SP2.
Due to one of the security reason, I have changed default port 1433 to another port number in configuration manger tools->protocols for MSSQLSERVER->TCP/IP --> IP ALL section mention another port number.
After restarted service, SQL SSMS able to connect server itself and new port number also LISTENING.
But SQL client SSMS not connected to one of the PC side after changing default port, what action need to take care for resolve this issues? Pl. suggest.
Thanks
February 19, 2015 at 6:16 am
in order to connect to an alternate port, you either need the sql browser service running, or explicitly state the port.
the browser service runs on port 1434, and when running, would tell a connection to connect to the "right" port;
otherwise, simply add the specific port as server,portnumber
Lowell
February 19, 2015 at 6:27 am
Thanks Lowell, It is working now..
management also not recommend to start the browser service. so in this case need to mention new port number in ODBC connection or web.config file to server name and followup port number also for application connectivity. am I correct?
February 19, 2015 at 6:35 am
SQL Galaxy (2/19/2015)
Thanks Lowell, It is working now..management also not recommend to start the browser service. so in this case need to mention new port number in ODBC connection or web.config file to server name and followup port number also for application connectivity. am I correct?
that is absolutely correct. an application will need it's connection string modified to explicitly use the port as well,if you ar enot using the browser service.
Lowell
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply