I have a SBS2000 server running ISA Firewall with 2 nics (lan and wan). How
do I configure SQL and ISA to allow the SQL database to be accessible on the
WAN side (i.e. to be accessible via the internet) of my dual nic SBS2000
server? How do I minimize the security risks? I have already installed the
SP3 patch for SQL.

Any advise would be appreciated.

Re: Remote access SQL database on SBS2000 server by Steve

Steve
Mon Oct 18 18:36:08 CDT 2004

Dirk wrote:

> I have a SBS2000 server running ISA Firewall with 2 nics (lan and
> wan). How do I configure SQL and ISA to allow the SQL database to be
> accessible on the WAN side (i.e. to be accessible via the internet)
> of my dual nic SBS2000 server? How do I minimize the security risks?
> I have already installed the SP3 patch for SQL.
>
> Any advise would be appreciated.

You would need to either Server Publish SQL Server or create an IP
Packet Filter to allow access.

Either will let you control where the connection originates from, and I
would strongly recommend you limit access to specific IP addresses.

On top of that, any Windows account or SQL login account should have
strong passphrases, and if it's a Windows account, restrict it as much
as possible.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Re: Remote access SQL database on SBS2000 server by SuperGumby

SuperGumby
Tue Oct 19 06:44:20 CDT 2004

that's a lot more informative than my 'fer francis' sake, DON'T EVEN THINK
ABOUT IT'.

"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0doops32pf1uw005@msnews.microsoft.com...
> Dirk wrote:
>
>> I have a SBS2000 server running ISA Firewall with 2 nics (lan and
>> wan). How do I configure SQL and ISA to allow the SQL database to be
>> accessible on the WAN side (i.e. to be accessible via the internet)
>> of my dual nic SBS2000 server? How do I minimize the security risks?
>> I have already installed the SP3 patch for SQL.
>>
>> Any advise would be appreciated.
>
> You would need to either Server Publish SQL Server or create an IP
> Packet Filter to allow access.
>
> Either will let you control where the connection originates from, and I
> would strongly recommend you limit access to specific IP addresses.
>
> On top of that, any Windows account or SQL login account should have
> strong passphrases, and if it's a Windows account, restrict it as much
> as possible.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.