Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How do i make MSSQL2000 listen to 1433/TCP only on

Server Network Utility only gives me the option to change listening port, nothing about address binding.

share|improve this question
No such thing in MSSQL2k i'm afraid. Http:// – evilSnobu Dec 23 '13 at 12:36

I didn't use sql server 2000 for 10 years now, but seems it, by default, binds to all the IP's and that there isn't a way to natively restrict this.

What Microsoft seems to suggest in this case is to close sql server port via IPSec using Local Security Policy Editor for all ip address. And add a rule to allow only on sql server port. I guess this could be achieved with Windows Firewall also.

Here is my source : (follow the thread using "Next in thread" link)

share|improve this answer
Nevermind, the 'legacy' application i was trying to secure is doing this (from a client computer): TCP 10.xx.xx.57:20922 10.xx.xx.6:1433 TIME_WAIT Have to get rid of all this stuff, quick. This spells TROUBLE. – evilSnobu Dec 23 '13 at 23:57

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.