January 28, 2004 at 2:18 pm
Hello all,
We are contemplating changing the default listener port of 1433 on SQL Server 2000 to a higher range number. I have received advice from another developer that a port value in the 10,000 range would be more secure. Can anyone provide advice on the implications of changing the listener port number and an acceptable number or range of numbers for the new port number.
Thanks in advance,
Sonya
January 28, 2004 at 2:41 pm
The main implication, of course, is that all the clients have to know where to find the server (assuming you have UDP 1434 blocked, anyway ... which you should).
The only reason I can think of for saying that a 5-digit port number would be "more secure" is that certainly some port scanners only scan the well-known service ports. If your port is a highly-numbered one, there's less chance of being scanned, I suppose. But you'll still get scanned fairly regularly, no matter what you do, so I don't know how much stock I'd put into that line of thought.
Chris
January 28, 2004 at 6:01 pm
Chris is right in that those looking for a quick "hit" will scan only well-known ports, but the serious person will scan 'em all. We do. Also, just because SQL Server doesn't sit on 1433 doesn't mean anything any more. Scanners are becoming more and more intelligent. Recent example is nmap. It tries to ID what's listening on the port by certain fingerprinting techniques. What switching from 1433 will do is prevent a generic worm designed to target 1433 from being very effective.
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply