Error 170 Windows Firewall Internet Connection Sharing Ics
Contents |
United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My could not start the windows firewall internet connection sharing ics service on local computer stuff Preferences Send a message Log Out TechRepublic Search GO Topics: windows cannot start the windows firewall internet connection sharing ics service CXO Cloud Big Data Security Innovation Software Data Centers Networking Startups Tech & Work All Topics Sections: how to fix windows firewall internet connection sharing Photos Videos All Writers Newsletters Forums Resource Library Tech Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My
Error 170 The Requested Resource Is In Use
stuff Preferences Send a message Log Out TechRepublic | Forums | Networks Networks Register Now or Log In to post Welcome back, My Profile Log Out Recent Activity FAQs Guidelines Question 0 Votes Locked Windows Firewall/Internet Connection Sharing (ICS) By bikosm · 8 years ago I am trying to connect my Windows 2003 server to the internet using a wireless connection. I am able to get connect to the access point but no page will open.The Windows Firewall/Internet Connection Sharing (ICS) service is not running and when i try to I get the following error: Could not start the windows firewall/internet connection sharing (ICS) service on local computer. Error 170: the requested resource is in use.Any Ideas.Rgds,Steve Share Flag This conversation is currently closed to new comments. 2 total posts (Page 1 of 1) + Follow this Discussion · | Thread display: Collapse - | Expand + All Answers Collapse - Try this by dilumd · 8 years ago In reply to Windows Firewall/Internet ... I think answer your looking for can be found from this linkhttp://www.techtalkz.com/windows-server-2003/40214-one-solution-error-170-requested-resource-use-error-when-starting-windows-firewall.html 0Votes Share Flag Back to Networks Forum 2 total posts (Page 1 of 1) Search Start New Discussion Start New Discussion Create a new discussion If you're asking for technical help, please be sure to include all your system
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time https://www.experts-exchange.com/questions/27699372/Error-170-Could-not-start-the-Windows-Firewall-Internet-Connection-Sharing-ICS-service-on-Local-Computer.html Job Ways to Get Help Expand Search Submit Close Search Login Join Today http://www.techtalkz.com/windows-server-2003/40226-one-solution-error-170-requested-resource-use-error-when-starting-windows-firewall.html Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer Want to Advertise Here? Solved Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer windows firewall Posted on 2012-05-01 SBS Windows Server 2003 MS Legacy OS 1 Verified Solution 5 Comments 2,145 Views Last Modified: 2012-05-06 Hi, We're getting this error on an SBS 2003 after P2V. Please assist - it's a production env. Thx 0 Question by:IT_Group1 Facebook Twitter LinkedIn Google Best Solution byIT_Group1 Thanks - it was solved by running: SC STOP IPNAT Go to Solution 5 Comments LVL 21 windows firewall internet Overall: Level 21 MS Legacy OS 8 Windows Server 2003 7 SBS 3 Message Expert Comment by:motnahp002012-05-01 What is your hypervisor - VMware or Hyper-V? 0 Message Author Comment by:IT_Group12012-05-01 Sorry - it's already back to physical - after the p2v, a v2p was done. Thx 0 Message Accepted Solution by:IT_Group12012-05-01 Thanks - it was solved by running: SC STOP IPNAT 0 LVL 77 Overall: Level 77 SBS 47 Windows Server 2003 29 MS Legacy OS 13 Message Active 2 days ago Expert Comment by:Rob Williams2012-05-01 When do you get it? If RRAS is enabled you will get that message but it is unrelated to the Control panel / Windows firewall 0 Message Author Closing Comment by:IT_Group12012-05-06 Great solution - works every time :) 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Featured Post What Security Threats Are You Missing? Promoted by Recorded Future Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP
Remember Me? Password Home Articles Register Forum RulesUser Blogs Gallery Community Community Links Social Groups Pictures & Albums Members List Go to Page... One solution for the "Error 170: The requested resource is in use" error when starting the Windows Firewall. Windows Server 2003 View First Unread Thread Tools Display Modes 28-08-2007, 04:40 AM #1 Kevin Cotreau Guest Posts: n/a 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. A