Re: SQL Server Specific Windows Firewall Exception
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Sun, 05 Aug 2007 21:43:21 -0600
You generally don't want something that installs and
automatically opens up ports - that's been a huge problem in
the past. So things are intentionally designed to be secure
by default now with the newer Microsoft services. There are
applications that use only local, nonremote connections to
SQL Server so automatically opening up ports in such cases
would unnecessarily increase the surface area of exposure to
threats, hacks.
-Sue
On Sun, 29 Jul 2007 18:30:01 -0700, Andrew Hayes
<AndrewHayes@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
If you edit File and Print Sharing in Windows Firewall, you'll see that it
lists 2 UDP ports and 2 TCP ports.
This is something that cannot be done normally but is offered through the
XPSP2 resource DLL. You can see this by looking at the registry entry for
GloballyOpenPorts under HKLM.
"137:UDP"="137:UDP:LocalSubNet:Enabled:@xpsp2res.dll,-22001"
"138:UDP"="138:UDP:LocalSubNet:Enabled:@xpsp2res.dll,-22002"
"139:TCP"="139:TCP:LocalSubNet:Enabled:@xpsp2res.dll,-22004"
"445:TCP"="445:TCP:LocalSubNet:Enabled:@xpsp2res.dll,-22005"
My question is - when will such a DLL or other method become available for
SQL Server 2005 so that we don't have to add a number of different program
and port exceptions to get remote connections and administration to work
through Windows Firewall?
Or possibly have it install the exceptions for us, such as Office 2007 does
for Groove, OneNote and Outlook? The SQL Server Surface Area Configuration
tool is the best place for such firewall changes to be chosen.
.
- Follow-Ups:
- Re: SQL Server Specific Windows Firewall Exception
- From: Andrew Hayes
- Re: SQL Server Specific Windows Firewall Exception
- Prev by Date: RE: Create view "disconnected" (correct group this time)
- Next by Date: Re: Intermittent Login failure at boot
- Previous by thread: Re: AAArgh! sp_addlinkedserver giving me fits
- Next by thread: Re: SQL Server Specific Windows Firewall Exception
- Index(es):
Relevant Pages
|
Loading