I have a Windows 2003 server located at a remote hosting facility.   No
hardware firewall is available, so I am looking for an affordable,
straightforward Zone-Alarm type software firewall for Windows 2003 Server.
(maybe ZA *is* the solution?)  I am running IIS, FTP, and Remote Desktop
services (port 3389).    ZA is great on my desktops, but on the server I'd
like to avoid ZA's "learning curve" where you have to answer pop ups
allowing this service or that as various services access TCP ports.

Ideally at the time of installation, I would like to be able to explicitly
specify the RDP port remain open so when the system reboots, I'm not locked
out of my server and forced to call the remote hosting company tech support
to manually configure the firewall for me.

From other posts I've read the built in ICF won't work with a server with
multiple static IP's, and TCP filtering isn't selective about which
interface can be filtered (plus in my testing it seemed to have trouble with
port 80 IIS)

Anybody have experience with ZoneAlarm or other software firewalls in a
Windows 2003 Server environment?

Thanks.

-- Paul

[ Post a follow-up to this message ]

Windows 2003 has a firewall built that you can use.  Internet Connection Sha
ring, Internet Connection Firewall, and Network Bridge are included only wit
h Windows Server 2003, Standard Edition, and the 32-bit version of Windows S
erver 2003, Enterprise Edit
ion.  I find that works just well has zone alarm.  You clould also look into
 IP filtering, but Firewall would make more sense.

"Paul" wrote:

> I have a Windows 2003 server located at a remote hosting facility.   No
> hardware firewall is available, so I am looking for an affordable,
> straightforward Zone-Alarm type software firewall for Windows 2003 Server.
> (maybe ZA *is* the solution?)  I am running IIS, FTP, and Remote Desktop
> services (port 3389).    ZA is great on my desktops, but on the server I'd
> like to avoid ZA's "learning curve" where you have to answer pop ups
> allowing this service or that as various services access TCP ports.
>
> Ideally at the time of installation, I would like to be able to explicitly
> specify the RDP port remain open so when the system reboots, I'm not locke
d
> out of my server and forced to call the remote hosting company tech suppor
t
> to manually configure the firewall for me.
>
> From other posts I've read the built in ICF won't work with a server with
> multiple static IP's, and TCP filtering isn't selective about which
> interface can be filtered (plus in my testing it seemed to have trouble wi
th
> port 80 IIS)
>
> Anybody have experience with ZoneAlarm or other software firewalls in a
> Windows 2003 Server environment?
>
> Thanks.
>
> -- Paul
>
>
>

[ Post a follow-up to this message ]

also... Google has some articles on gettinf ICF to use multiple IP's.  I cur
rently have one box with one static for IIS, RDP and FTP.  Are you using a S
tatic for all these services?

"Paul" wrote:

> I have a Windows 2003 server located at a remote hosting facility.   No
> hardware firewall is available, so I am looking for an affordable,
> straightforward Zone-Alarm type software firewall for Windows 2003 Server.
> (maybe ZA *is* the solution?)  I am running IIS, FTP, and Remote Desktop
> services (port 3389).    ZA is great on my desktops, but on the server I'd
> like to avoid ZA's "learning curve" where you have to answer pop ups
> allowing this service or that as various services access TCP ports.
>
> Ideally at the time of installation, I would like to be able to explicitly
> specify the RDP port remain open so when the system reboots, I'm not locke
d
> out of my server and forced to call the remote hosting company tech suppor
t
> to manually configure the firewall for me.
>
> From other posts I've read the built in ICF won't work with a server with
> multiple static IP's, and TCP filtering isn't selective about which
> interface can be filtered (plus in my testing it seemed to have trouble wi
th
> port 80 IIS)
>
> Anybody have experience with ZoneAlarm or other software firewalls in a
> Windows 2003 Server environment?
>
> Thanks.
>
> -- Paul
>
>
>

[ Post a follow-up to this message ]

Yes, I am currently using one static IP for IIS, RDP and FTP currently, but
I want the option open to have future IIS and FTP sites on their own static
IPs if necessary.  I will check out Google on ICF configuration.  Thanks.

-- Paul


"Jason" <Jason@discussions.microsoft.com> wrote in message
news:771EA96C-A037-4046-AD86-0100D78DD22B@microsoft.com...
> also... Google has some articles on gettinf ICF to use multiple IP's.  I
currently have one box with one static for IIS, RDP and FTP.  Are you using
a Static for all these services?[vbcol=seagreen]
>
> "Paul" wrote:
> 
Server.[vbcol=seagreen] 
I'd[vbcol=seagreen] 
explicitly[vbcol=seagreen] 
locked[vbcol=seagreen] 
support[vbcol=seagreen] 
with[vbcol=seagreen] 
with[vbcol=seagreen] 

[ Post a follow-up to this message ]

On Thu, 15 Jul 2004 17:37:01 -0700, Paul wrote:
>=A0I have a Windows 2003 server located at a remote hosting facility.
>=A0 No hardware firewall is available, so I am looking for an
>=A0affordable, straightforward Zone-Alarm type software firewall for
>=A0Windows 2003 Server. (maybe ZA *is* the solution?) =A0I am running
>=A0IIS, FTP, and Remote Desktop services (port 3389). =A0 =A0ZA is great
>=A0on my desktops, but on the server I'd like to avoid ZA's "learning
>=A0curve" where you have to answer pop ups allowing this service or
>=A0that as various services access TCP ports.

Zone alarm doesn't run on a server. I use Black Ice Server works perfect.=
I've used it on my 2000 web server for years. I tried Visnetic Firewall but=
it has a nasty bug in the driver that will crash your 2003 server hard!

I don't use the application protection module in BI however.


John Cesta

---------------------------------
The CPU Checker - Maximize Server Uptime
LogFileManager - The only IIS Logfile Management Tool
DomainReportIt PRO - Helps Convert IIS Installs
http://www.serverautomationtools.com



>
>=A0Ideally at the time of installation, I would like to be able to
>=A0explicitly specify the RDP port remain open so when the system
>=A0reboots, I'm not locked out of my server and forced to call the
>=A0remote hosting company tech support to manually configure the
>=A0firewall for me.
>
>=A0From other posts I've read the built in ICF won't work with a
>=A0server with multiple static IP's, and TCP filtering isn't selective
>=A0about which interface can be filtered (plus in my testing it seemed
>=A0to have trouble with port 80 IIS)
>
>=A0Anybody have experience with ZoneAlarm or other software firewalls
>=A0in a Windows 2003 Server environment?
>
>=A0Thanks.
>
>
>=A0-- Paul

[ Post a follow-up to this message ]