September 9, 2003 at 12:36 pm
To enhance security on a new sql server we want to change the default listener port from 1433.
But I'm worried: all our internal EM\QA setups took the defaults (i.e. probably 1433 is used). And what about our programmatic access to databases via OLEDB? I'd bet that few programmers have any "port"-related
fields in their connection strings.
The question: will changing the "port" opening a world of headaches for the admin?
TIA,
Bill
September 9, 2003 at 12:48 pm
It can. Clients will have to be set to use the new port.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
September 10, 2003 at 12:44 pm
Bill --
I usually configure my servers so that they listen on a port other than 1433 -- usually to an unassigned port number (in the 65000 range).
This does require modifying settings to clients/applications accessing the server, but I think it adds another level of security.
In other words, it's worth the grief and aggravation.
-- Tim
September 10, 2003 at 3:11 pm
Don't forget to "hide server" too. Or, block UDP 1434 at your firewall.
Cheers,
- Mark
Cheers,
- Mark
September 10, 2003 at 3:29 pm
Hide server will shift the port to TCP/2433. This is hard-coded. Also, if you watch the UDP traffic on 1434 for a "hidden" server, it's not so hidden.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
January 17, 2006 at 10:52 pm
hi
I modified port 1433 to 1037. But after my application not connect to SQL Server 2000.
Help, how to config connectiionstring or orther way to connect SQL server.
Thanks
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply