From: Roberto Meneghini on
Hello,

Latley I've been experiencing the following issue when re-starting our
SBS2003:

Windows Firewall Servvice fails to start (See event log entry below). At
this point, none of the client computers can see the server. However, I can
ping any client from the server. To solve the problem I need to do the
following:

1- Disable Routing and Remote Acceess Service.
2- Re-boot the server
3- Enable RRAS.

Is this a side effect of one of the system updates? Any ideas on how to
resolve this issue?


Sincerely,

Roberto Meneghini


Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 32009
Date: 9/16/2006
Time: 10:43:11 AM
User: N/A
Computer: SEPSYS-SBS1
Description:
The Windows Firewall/Internet Connection Sharing (ICS) service could not
start because another program or service is running that might use the
network address translation component (Ipnat.sys). This can occur when
Routing and Remote Access is enabled. If this is the case, you must disable
Routing and Remote Access before the Windows Firewall/Internet Connection
Sharing (ICS) service can start.


From: Robert L [MVP - Networking] on
Do you have two NICs on the server?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Roberto Meneghini" <RobertoMeneghini(a)discussions.microsoft.com> wrote in message news:DAD67FD6-BA17-4AE7-8443-35128E924A2E(a)microsoft.com...
Hello,

Latley I've been experiencing the following issue when re-starting our
SBS2003:

Windows Firewall Servvice fails to start (See event log entry below). At
this point, none of the client computers can see the server. However, I can
ping any client from the server. To solve the problem I need to do the
following:

1- Disable Routing and Remote Acceess Service.
2- Re-boot the server
3- Enable RRAS.

Is this a side effect of one of the system updates? Any ideas on how to
resolve this issue?


Sincerely,

Roberto Meneghini


Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 32009
Date: 9/16/2006
Time: 10:43:11 AM
User: N/A
Computer: SEPSYS-SBS1
Description:
The Windows Firewall/Internet Connection Sharing (ICS) service could not
start because another program or service is running that might use the
network address translation component (Ipnat.sys). This can occur when
Routing and Remote Access is enabled. If this is the case, you must disable
Routing and Remote Access before the Windows Firewall/Internet Connection
Sharing (ICS) service can start.

From: Roberto Meneghini on
Hello Robert,

Yes, but one is disabled. Our SBS2003 machine is connected to a Firewall box
and this box is attached to the T1/Phone switch.

Roberto

"Robert L [MVP - Networking]" wrote:

> Do you have two NICs on the server?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Roberto Meneghini" <RobertoMeneghini(a)discussions.microsoft.com> wrote in message news:DAD67FD6-BA17-4AE7-8443-35128E924A2E(a)microsoft.com...
> Hello,
>
> Latley I've been experiencing the following issue when re-starting our
> SBS2003:
>
> Windows Firewall Servvice fails to start (See event log entry below). At
> this point, none of the client computers can see the server. However, I can
> ping any client from the server. To solve the problem I need to do the
> following:
>
> 1- Disable Routing and Remote Acceess Service.
> 2- Re-boot the server
> 3- Enable RRAS.
>
> Is this a side effect of one of the system updates? Any ideas on how to
> resolve this issue?
>
>
> Sincerely,
>
> Roberto Meneghini
>
>
> Event Type: Error
> Event Source: ipnathlp
> Event Category: None
> Event ID: 32009
> Date: 9/16/2006
> Time: 10:43:11 AM
> User: N/A
> Computer: SEPSYS-SBS1
> Description:
> The Windows Firewall/Internet Connection Sharing (ICS) service could not
> start because another program or service is running that might use the
> network address translation component (Ipnat.sys). This can occur when
> Routing and Remote Access is enabled. If this is the case, you must disable
> Routing and Remote Access before the Windows Firewall/Internet Connection
> Sharing (ICS) service can start
From: Roberto Meneghini on
Hello Robert,
Any ideas on how to solve this issue? The server always had two network
cards, but just one enabled. As I mentioned before, the system was working
fine upto a month ago. Noting has been installed except for Microsoft's
updates and patches.

Thanks,

Roberto


"Robert L [MVP - Networking]" wrote:

> Do you have two NICs on the server?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "Roberto Meneghini" <RobertoMeneghini(a)discussions.microsoft.com> wrote in message news:DAD67FD6-BA17-4AE7-8443-35128E924A2E(a)microsoft.com...
> Hello,
>
> Latley I've been experiencing the following issue when re-starting our
> SBS2003:
>
> Windows Firewall Servvice fails to start (See event log entry below). At
> this point, none of the client computers can see the server. However, I can
> ping any client from the server. To solve the problem I need to do the
> following:
>
> 1- Disable Routing and Remote Acceess Service.
> 2- Re-boot the server
> 3- Enable RRAS.
>
> Is this a side effect of one of the system updates? Any ideas on how to
> resolve this issue?
>
>
> Sincerely,
>
> Roberto Meneghini
>
>
> Event Type: Error
> Event Source: ipnathlp
> Event Category: None
> Event ID: 32009
> Date: 9/16/2006
> Time: 10:43:11 AM
> User: N/A
> Computer: SEPSYS-SBS1
> Description:
> The Windows Firewall/Internet Connection Sharing (ICS) service could not
> start because another program or service is running that might use the
> network address translation component (Ipnat.sys). This can occur when
> Routing and Remote Access is enabled. If this is the case, you must disable
> Routing and Remote Access before the Windows Firewall/Internet Connection
> Sharing (ICS) service can start