SQL Server with Mr. Denny

May 6 2010   11:00AM GMT

If you change the default instances port number, you may not be able to connect

Denny Cherry Denny Cherry Profile: Denny Cherry

Something that some companies like to do is to change the port number that the default instance is listening under as a security precaution.  However this has a habit of stopping anyone from connecting to the default instance without knowing the port number.

This is because the default instance doesn’t register itself with the SQL Browser when it starts, so you can no longer simply just connect to the default instance when named instances will work just fine.  The fix from CSS is to simply change the port back to TCP 1433.  The reason for this is that changing the port number doesn’t do a lot to secure your SQL Server as a quick port scan will show an attacker which port the SQL Server is listening on.  That or they’ll simply check out the web.config and get the port number from there.

Denny

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: