One solution for the "Error 170: The requested resource is in use" error when starting the Windows Firewall.

[Guest Kevin Cotreau]

One solution for the "Error 170: The requested resource is in use" error when starting the Windows Firewall.

 

Hi All,

 

 

 

I recently got this error on a Windows 2003 server while trying to start the

Windows Firewall/Internet Connection Service (ICS): "Error 170: The

requested resource is in use". This also seems to affect Small Business

Server (SBS) too if the previous posts are any indication. After researching

it, there seemed to be very little that is concrete out there regarding a

solution, but based on what I did right before I got the error, I was

quickly led right to the solution.

 

 

 

A little background: Right before this error popped up, I had just run the

Routing and Remote Access Wizard (RRAS) to set up routing between a local

network card and a VPN. The firewall was then turned off as an unrelated

test, and around this time, I was totally cut off from the server, which was

remotely located. Once at the remote location, it was clear one symptom was

that the server had connectivity out but nothing could get back in, even

though the firewall was technically off. Trying to turn on the firewall gave

the 170 error.

 

 

 

I just went back into RRAS and deleted the server and the firewall started

after a reboot (It might start immediately, but I don't think I even

bothered to test that). Of course, if you are actively using RRAS, you

should copy all settings before deleting the server and re-creating it. This

is also probably why the solution of running the Configure E-mail and

Internet Connection Wizard given for SBS sometimes also works.

 

 

 

Also I want to mention the solution I found recommended by Steven Zhu, MCSE

from Microsoft Online Partner Support, since it deserves a try either before

or after my solution as you decide based on your specific configuration. If

you have a complex RRAS configuration, it may solve the problem without

having to delete the server, but it may introduce some problem that I can't

anticipate here. I was about to try this solution, but I ultimately didn't

need to. His solution is to make sure that the Network Connections, Windows

Management Instrumentation, and Remote Procedure Call (RPC) services are

running, and if they are, reset Winsock by running the following command

from a command prompt: "netsh winsock reset" (without quotation mark). The

following article about recovering from Winsock2 corruption might be

helpful: http://support.microsoft.com/kb/811259/.

 

 

 

I hope this helps someone.

 

Kevin Cotreau

MCSE+I, MCNE, et al.

[Guest Robert L [MVP - Networking]]

Re: One solution for the "Error 170: The requested resource is in use" error when starting the Windows Firewall.

 

Re: One solution for the "Error 170: The requested resource is in use" error when starting the Windows Firewall.

 

Kevin,

 

We have seen many people had this errors without resolution. Thank you for the post.

 

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

"Kevin Cotreau" <u4ic61@hotmail.com> wrote in message news:Wc6dnWVem8trdDLbnZ2dnUVZ_vyinZ2d@comcast.com...

Hi All,

 

 

 

I recently got this error on a Windows 2003 server while trying to start the

Windows Firewall/Internet Connection Service (ICS): "Error 170: The

requested resource is in use". This also seems to affect Small Business

Server (SBS) too if the previous posts are any indication. After researching

it, there seemed to be very little that is concrete out there regarding a

solution, but based on what I did right before I got the error, I was

quickly led right to the solution.

 

 

 

A little background: Right before this error popped up, I had just run the

Routing and Remote Access Wizard (RRAS) to set up routing between a local

network card and a VPN. The firewall was then turned off as an unrelated

test, and around this time, I was totally cut off from the server, which was

remotely located. Once at the remote location, it was clear one symptom was

that the server had connectivity out but nothing could get back in, even

though the firewall was technically off. Trying to turn on the firewall gave

the 170 error.

 

 

 

I just went back into RRAS and deleted the server and the firewall started

after a reboot (It might start immediately, but I don't think I even

bothered to test that). Of course, if you are actively using RRAS, you

should copy all settings before deleting the server and re-creating it. This

is also probably why the solution of running the Configure E-mail and

Internet Connection Wizard given for SBS sometimes also works.

 

 

 

Also I want to mention the solution I found recommended by Steven Zhu, MCSE

from Microsoft Online Partner Support, since it deserves a try either before

or after my solution as you decide based on your specific configuration. If

you have a complex RRAS configuration, it may solve the problem without

having to delete the server, but it may introduce some problem that I can't

anticipate here. I was about to try this solution, but I ultimately didn't

need to. His solution is to make sure that the Network Connections, Windows

Management Instrumentation, and Remote Procedure Call (RPC) services are

running, and if they are, reset Winsock by running the following command

from a command prompt: "netsh winsock reset" (without quotation mark). The

following article about recovering from Winsock2 corruption might be

helpful: http://support.microsoft.com/kb/811259/.

 

 

 

I hope this helps someone.

 

Kevin Cotreau

MCSE+I, MCNE, et al.