Re: Is there any reason to use port 1433?
- From: Henrik <henrik@xxxxxxxxxxxxxx>
- Date: Fri, 29 Dec 2006 15:55:16 -0500
Han,
1433 is the default port that SQL Server uses for TCP/IP client communication. You can configure that to be another port, but hackers will find them and attempt hacking there too.
I wrote a utility to do a bit of self defense for these hacking attempts.
http://www.creeksolutions.com/Products/BlockSSHacking/tabid/92/Default.aspx
BlockSSHacking runs as a Windows service protecting your SQL Server from brute force hacking attempts coming from the Internet.
The service checks your system every 5 minutes (configurable setting) for evidence of ongoing hacking. If such attempts are in progress then those source addresses are blocked from future access to your server (quickly leading to you recovering your bandwidth).
BlockSSHacking notifies you via email when it has blocked someone from hacking your system.
Henrik
Han wrote:
Hello.
I am new to SQL security.
Some days ago I happened to open my event log and found lots of attacks have been going on to my SQL server 2005. Maybe for some months. I have been using firewall and Windows integrated authentication. The attacks might be not quite successful. Anyway, I changed the SQL server port from 1433 to something another. Strikingly all the attacks have gone. Now I am curious why they use port number 1433. Is there any reason to use the port, benefit or something? Or is there any danger or caution to use something other than 1433?
- References:
- Is there any reason to use port 1433?
- From: Han
- Is there any reason to use port 1433?
- Prev by Date: Re: Is there any reason to use port 1433?
- Next by Date: Re: How can I block attempts to hack into my SQL server?
- Previous by thread: Re: Is there any reason to use port 1433?
- Next by thread: Re: How can I block attempts to hack into my SQL server?
- Index(es):
Relevant Pages
|
|