Server 2003 Firewall Server Error 170

Home > Server 2003 > Server 2003 Firewall Server Error 170

Server 2003 Firewall Server Error 170

This can occur when Routing and Remote Access is enabled. Please complete a re-registration process by entering the secure code mmpng06 when prompted. To collect system log and application log, please refer the following steps: System log: ------------------ 1.) Open Computer Management; click Event Viewer under System Tools. 2.) Right click System Log and Or proxy clients may be negatively affected when you run the "netsh winsock reset" command.

I have narrowed it down to the Windows Firewall/Internet Connection Service (ICS), which won't start; the startup type is set to automatic. All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server Any ideas there? from: Anwar Friday, January 28, 2011 5:11 AM Reply | Quote 0 Sign in to vote Do you mean its a fresh installation ?

Kevin Cotreau Windows Server 2003 2 28-08-2007 04:41 AM Error "Cluster File Share resource '...' has failed a status check." during defrag Christian Fssler Windows Server 2003 8 28-08-2007 02:52 AM 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 Share this post Link to post Share on other sites Upgrade to a WGS Supporter Account to remove this ad. Of course, if you are actively using RRAS, you should copy all settings before deleting the server and re-creating it.

Hi Drashna; Sorry about posting in the wrong forum; it's been a crazy week and a long time since I have been on WGS. For more information, see Help and Support Center at Microsoft Customer Support Microsoft Community Forums Jump to content Networking Existing user? I fried my router recently. ;( Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in Can I buy 2016 WSE yet? Solved Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer Posted on 2012-05-01 SBS Windows Server 2003 MS Legacy OS 1 Verified Solution 5 Thanks for dropping by Imagination is the Key! I am new to Plex and have that setup but I'm still much more comfortable with the Streaming Services provided by Microsoft.

I did the usual troubleshooting as explaine by Meinolf Weber, but it didn't take effect till i restarted the server. The Report states: Date: 6/9/2006 Source: ipnathlp Time: 1:24:38PM Category: None Type: Error EventID: 32009 User: N/A Computer: OGMA Description: The Windows Firewall/Internet Connection Sharing (ICS) service could not start because Find Remote Procedure Call (RPC) service and check if it was started. 3. I cannot connect from any of my client computers.

Please assist - it's a production env. All rights reserved. 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 Share this post Link to post Share on other sites Drashna Jaelre (WGS) 314 Tinkerer Lead Moderator 314 11640 posts Gender:Male Location:San Diego, CA, USA Interests:Computers, Home Server (obviously), math,

Or "set up" Routing and Remote Access? check over here Please help this is VERY important that I get this back up ASAP! Sure, you are right; there isn't ISA in Windows SBS 2003 Standard version. Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d… MS Legacy OS Storage Software Windows OS Storage Hardware Storage Move the Taskbar to Create Additional

Index(es): Date Thread Flag as inappropriate (AWS) Windows Science Usenet ArchiveAboutPrivacyImprint >Archive >Windows > >2006-06 Home About RSS Imagination is the Key DIY Hey there! Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your account. (LogOut/Change) You are 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 his comment is here From: Derek RE: Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.

If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Uncategorized My Solution of ‘Error 170: The Requested Resource is in Use' when Starting WindowsFirewall Filed under: Uncategorized — Leave a comment September 20, 2011 I recently got up a creek Posts RWA Leads to IIS Page By ChuckVader · Posted 5 hours ago I have that update installed and it works ok no denied 403 message, try the direct link to

Thank you, Erik .

Suggested Solutions Title # Comments Views Activity Exchange Management Console Error - Initialization falied 18 88 76d disable Win7 network security 2 47 27d Ms Filer Server Migration toolkit issues 2 And not a problem. See you around! Also, have you tried just disabling the Windows Firewall service?

For more detailed information, please refer to the following article: How to determine and recover from Winsock2 corruption If you still want to dig into this issue here, please provide From: Steven Zhu [MSFT] Prev by Date: RE: certificate server for infopath Next by Date: Re: Migration from 2K server to SBS2003 server Previous by thread: Re: Error 170 - Could Error 170: the requested resource is in use." I can ping the clients from the server, but the clients can't ping the server and get a reply. weblink Comments RSS feed Leave a Reply Cancel reply Enter your comment here...