Ok, I am having exactly the same problem described by Chintan Mehta
Were there any solutions?? Is this an error that Microsoft Should address?
"jemezhobbit" <(E-Mail Removed)> wrote in message news:<4BDFA254-EE11-48DA-AE16-(E-Mail Removed)>...
> .. sounds exactly like the problem that I'm having .. it's not only web service, but DNS is being blocked even when I open port 53 ..
>
> .. worse yet, I cannot run a third-party firewall as Win2k3 won't allow it ..
>
>
>
> ----- Chintan Mehta wrote: -----
>
> I have the same problem. My configuration is as follows
> * Windows Server 2003 standard
> * 5 Static IP addresses on a single NIC (one listed as
> the main IP on the TCP/IP properties page for the
> connection and other 4 added as additional IP addresses
> in the advanced TCP/IP settings property page)
> * IIS Web sites each assigned to an individual IP address
> on port 80
> * ICF turned on to allow Remote Desktop Administration
> (server name and port 3389) and Web Server (servername
> and port 80) and others.
>
> With these desired settings the server only responds to
> the last IP address on the IP adresses list on the
> advanced TCP/IP settings page (not the one listed as the
> main IP). Also none of my http web sites are accessible.
> Also Remote Desktop is only possible on the last IP
> address.
> * If I turn off ICF then all my http web sites work fine.
> * If I remove the additional IP addresses then the main
> IP begins to work fine again.
>
> Please help! Should I drop ICF altogether and use IPSec
> instead as a firewall?
>
> Chintan
>
> >-----Original Message-----
> >Hi!
> >I have a problem with my Windows 2003 Standard Edition
> Server and the
> >Windows integrated Firewall.
> >The machine has 4 ip-adresses which work perfectly when
> the firewall is
> >turned off.
> >1. But when I turn on the firewall and enable the port
> 80 (webserver) only
> >(port 80-) traffic for the last ip-adress of the server
> is coming through
> >the Windows-Internet-Connection-Firewall, traffic for
> the other adresses is
> >dropped. Protocol ftp is working perfectly on all IP-
> adresses even with
> >firewall enabled. It seems a Microsoft-BUG, is it?
> >2. All settings in the ip-adress -tab of the protocol-
> definition in the
> >firewall are ignored, means if you enter a specific ip-
> adress for ftp e.g.
> >the protocol still works on the other, excluded ips.
> >What can I do, patch?
> >Thanks for all Answers
> >Tom
> >>>.
> >
|