Critical bug in ICF configurability

This is a critical bug.

ICF (Internet Connection Firewall) cannot be disabled if it was previously
enabled and the associated network hardware is removed. Routing and Remote
Access configuration becomes inaccessible as a result.

Example:

1. Install Network Card A.
2. Install Routing and Remote Access.
3. Add Firewall to Network Card A. (Fails, of course, until Routhing and
Remote Access is disabled.)
4. Remove Network Card A.
5. Install Network Card B.
6. Attempt to enable and configure Routing and Remote Access. This fails,
because ICF is "enabled", but there is no way to access the ICF mapping to
the old network hardware because the Network Connections icon for the old
network hardware is gone.

Ultimately, one must either seek out and reinstall the old hardware to
disable the ICF (of course, if the hardware is damaged then this isn't an
option), or else one must uninstall and reinstall Windows Server 2003
altogether, if Routing and Remote Access is to be enabled.

Sorry, wrong error. The error I'm getting is regarding "Incoming
Connections". Anyone know how to fix?

Jon

"Jon Davis" <(E-Mail Removed)> wrote in message
news:#UrPyr$(E-Mail Removed)...
> This is a critical bug.
>
> ICF (Internet Connection Firewall) cannot be disabled if it was previously
> enabled and the associated network hardware is removed. Routing and Remote
> Access configuration becomes inaccessible as a result.
>
> Example:
>
> 1. Install Network Card A.
> 2. Install Routing and Remote Access.
> 3. Add Firewall to Network Card A. (Fails, of course, until Routhing and
> Remote Access is disabled.)
> 4. Remove Network Card A.
> 5. Install Network Card B.
> 6. Attempt to enable and configure Routing and Remote Access. This fails,
> because ICF is "enabled", but there is no way to access the ICF mapping to
> the old network hardware because the Network Connections icon for the old
> network hardware is gone.
>
> Ultimately, one must either seek out and reinstall the old hardware to
> disable the ICF (of course, if the hardware is damaged then this isn't an
> option), or else one must uninstall and reinstall Windows Server 2003
> altogether, if Routing and Remote Access is to be enabled.
>
>

Nevermind, it DID say ICF, but I restored the old network card and now it's
IC.

Jon


"Jon Davis" <(E-Mail Removed)> wrote in message
news:e4emW4$(E-Mail Removed)...
> Sorry, wrong error. The error I'm getting is regarding "Incoming
> Connections". Anyone know how to fix?
>
> Jon
>
> "Jon Davis" <(E-Mail Removed)> wrote in message
> news:#UrPyr$(E-Mail Removed)...
> > This is a critical bug.
> >
> > ICF (Internet Connection Firewall) cannot be disabled if it was
previously
> > enabled and the associated network hardware is removed. Routing and
Remote
> > Access configuration becomes inaccessible as a result.
> >
> > Example:
> >
> > 1. Install Network Card A.
> > 2. Install Routing and Remote Access.
> > 3. Add Firewall to Network Card A. (Fails, of course, until Routhing and
> > Remote Access is disabled.)
> > 4. Remove Network Card A.
> > 5. Install Network Card B.
> > 6. Attempt to enable and configure Routing and Remote Access. This
fails,
> > because ICF is "enabled", but there is no way to access the ICF mapping
to
> > the old network hardware because the Network Connections icon for the
old
> > network hardware is gone.
> >
> > Ultimately, one must either seek out and reinstall the old hardware to
> > disable the ICF (of course, if the hardware is damaged then this isn't
an
> > option), or else one must uninstall and reinstall Windows Server 2003
> > altogether, if Routing and Remote Access is to be enabled.
> >
> >
>
>