Garth
Guest
|
 Posted:
Mon Jan 24, 2005 3:31 am Post subject:
Windows 2003 Internet Connection Firewall (ICF) |
|
|
Hello,
I have Internet Connection Firewall enabled on the active
NIC on my Windows Server 2003 box. Remote Desktop is
enabled in the inbound rules, and is pointed at the
primary IP of the server.
When I add a second IP to the TCP/IP config for the NIC,
it completely kills the network connection-- no traffic
can get through whatsoever (although my active Remote
Desktop session stays alive). If I disable the firewall,
traffic works fine. If I re-enable, it doesn't. It
seems ICF cannot handle more than one IP address being
bound to the NIC. Has anyone run into this before?
Thanks,
Garth |
|
Steven L Umbach
Guest
|
| Posted:
Mon Jan 24, 2005 6:46 am Post subject:
Re: Windows 2003 Internet Connection Firewall (ICF) |
|
|
I have not tried that personally but have seem multiple users post the same
problem with no solutions indicated other than using a third party software
firewall or ipsec filtering policy [which is not stateful and should not be
an only internet facing firewall] . Maybe SP1 will change the behavior. ---
Steve
"Garth" <anonymous@discussions.microsoft.com> wrote in message
news:1f5201c50192$ebec6bc0$a601280a@phx.gbl...
| Quote: | Hello,
I have Internet Connection Firewall enabled on the active
NIC on my Windows Server 2003 box. Remote Desktop is
enabled in the inbound rules, and is pointed at the
primary IP of the server.
When I add a second IP to the TCP/IP config for the NIC,
it completely kills the network connection-- no traffic
can get through whatsoever (although my active Remote
Desktop session stays alive). If I disable the firewall,
traffic works fine. If I re-enable, it doesn't. It
seems ICF cannot handle more than one IP address being
bound to the NIC. Has anyone run into this before?
Thanks,
Garth |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in