Windows 2003 disabling/blocking public IP?

Hi All,

I have set up a Windows 2003 Standard Edition server with the following
network configuration:

- NIC 1: private interface (LAN), no NAT, no basic firewall
- NIC 2: public interface (connected to the Internet through a Cable
Modem), NAT, basic firewall

I've assigned NIC 2 a pool of 3 static IP addresses, provided by my ISP
(let's call them public-IP1, public-IP2 and public-IP3)

On NIC 2 I've defined some services and ports that enable public access
to some of our internal servers:

public-IP1:80 --> private-IP-1:80
public-IP2:80 --> private-IP-2:80
etc.

It all seems to work fine most of the time, but today I had the
following problem:

I was able to access web site at public-IP2:80 from OUTSIDE (the
Internet), but NOT the website at public-IP1:80.

Note that while this happened the website at private-IP-1:80 WAS
accessible for LAN users.

I also tried to open a different port on that interface
(public-IP1:8080 -> private-IP:80), with no luck!

So it seems to me that public-IP1 was, some how, blocked to all
incoming traffic.

After some research I did not find any useful information, so I decided
to DISABLE/ENABLE the Network connection on NIC 2 and this seemed to
solve the problem.

I would like to know if W2003 can block or disable an IP address in
response to an attack, or any reasons for this unexpected behavior.
Could this be caused by my ISP?

Please note that I'm quite new to these kinds of network settings, and
if you need further information, please let me know.

Thanks for any ideas!!

Juan

Anyone? Please?

(E-Mail Removed) ha escrito:

> Hi All,
>
> I have set up a Windows 2003 Standard Edition server with the following
> network configuration:
>
> - NIC 1: private interface (LAN), no NAT, no basic firewall
> - NIC 2: public interface (connected to the Internet through a Cable
> Modem), NAT, basic firewall
>
> I've assigned NIC 2 a pool of 3 static IP addresses, provided by my ISP
> (let's call them public-IP1, public-IP2 and public-IP3)
>
> On NIC 2 I've defined some services and ports that enable public access
> to some of our internal servers:
>
> public-IP1:80 --> private-IP-1:80
> public-IP2:80 --> private-IP-2:80
> etc.
>
> It all seems to work fine most of the time, but today I had the
> following problem:
>
> I was able to access web site at public-IP2:80 from OUTSIDE (the
> Internet), but NOT the website at public-IP1:80.
>
> Note that while this happened the website at private-IP-1:80 WAS
> accessible for LAN users.
>
> I also tried to open a different port on that interface
> (public-IP1:8080 -> private-IP:80), with no luck!
>
> So it seems to me that public-IP1 was, some how, blocked to all
> incoming traffic.
>
> After some research I did not find any useful information, so I decided
> to DISABLE/ENABLE the Network connection on NIC 2 and this seemed to
> solve the problem.
>
> I would like to know if W2003 can block or disable an IP address in
> response to an attack, or any reasons for this unexpected behavior.
> Could this be caused by my ISP?
>
> Please note that I'm quite new to these kinds of network settings, and
> if you need further information, please let me know.
>
> Thanks for any ideas!!
>
> Juan