mike epprecht sql mvp

Hi

You have to configure IPSec at NIC level to disallow connections on the
public IP. By default and design, SQL Server will always listen on all IP's
and SQL Server can not be configured not to listen on them.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

rick

Thanks Dan. The system is a typical (dual-homed) SBS2003. I thought that I
got a level of firewalling with SBS. I guess I was naive. So I'm not sure
of which way to go. Would you folks recommend:

1) New hardware firewall (any suggestions?)
2) TCP/IP (and UDP) filtering in Advanced TCP/IP Settings?
3) IPSec policies?
4) Move my SQL databases to an internal server?
5) Combination of above?