Re: Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- From: v-stezhu@xxxxxxxxxxxxxxxxxxxx (Steven Zhu [MSFT])
- Date: Mon, 26 Jun 2006 08:48:23 GMT
Hi Derek,
Thanks for your new information.
Sure, you are right; there isn't ISA in Windows SBS 2003 Standard version.
Usually, for such kind of service cannot be started issue, we need to use
some tools to collect memory dumps and debugging to see what the root cause
is. However, because debugging memory dump in out of support boundaries of
our newsgroup, I would suggest you contact our Customer Support Service
(CSS) via phone to get the problem fixed in a more efficient manner. For
the CSS contact info, please visit:
http://www.microsoft.com/services/microsoftservices/srv_support.mspx
However, based on my research, Please check:
Network Connections
Windows Management Instrumentation
Remote Procedure Call (RPC)
were started. To do this, please refer to following steps:
1. Run "Services.msc"
2. Find Remote Procedure Call (RPC) service and check if it was started.
3. Make sure the three services were all started and try to start Firewall
service again.
If all three services are started but Firewall still cannot be started, I'd
like to suggest you reset Winsock. Please Type "netsh winsock reset"
(without quotation mark) at the command prompt, and then press ENTER.
Note: Restart the computer after you run this command. Additionally, for
computers that are running Windows XP SP2, there is a new netsh command
that can rebuild the Winsock key. For more information, visit the following
Web site:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx
Warning Programs that access or monitors the Internet such as antivirus,
firewall. Or proxy clients may be negatively affected when you run the
"netsh winsock reset" command. If you have a program that no longer
functions correctly after you use this resolution, reinstall the program to
restore functionality.
For more detailed information, please refer to the following article:
How to determine and recover from Winsock2 corruption
http://support.microsoft.com/kb/811259/
If you still want to dig into this issue here, please provide me the system
and application event log on your Exchange server so that I can try to help
you check if there are any obvious evidence to this issue. 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 select Save Log file as¡
3.) Select path and type the name.
4.) Click Save.
Application log:
--------------------
1.) Open Computer Management; click Event Viewer under System Tools.
2.) Right click Application Log and select Save Log file as¡
3.) Select path and type the name.
4.) Click Save.
Please send the system log file and application log file to my work
address: v-stezhu@xxxxxxxxxxxxxx
Thank you for you patience and understanding and have a great day.
Best Regards,
Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- References:
- Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- From: Derek
- RE: Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- From: Steven Zhu [MSFT]
- Re: Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- From: Steven Zhu [MSFT]
- Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- 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 not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- Next by thread: Re: Error 170 - Could not start the Windows Firewall/Internet Connection Sharing (ICS) service on Local Computer.
- Index(es):
Relevant Pages
|