Adjusting services to solve Windows Server 2008 troubles

I believe many people are trying to use the system for the "famousness" of the Windows Server 2008 system; after a period of trial, we may find that the Windows Server 2008 system is not as easy to use as before. This is mainly because in addition to the Windows Server 2008 system to protect the system security to strengthen a number of restrictions, there is also when we frequently install and uninstall the application, inadvertently changed some of the local system settings parameters, resulting in our trial Windows In the process of the Server 2008 system, various usage problems and troubles were encountered. In fact, many of the problems and troubles are caused by the faulty state of the system service. We can ensure that the Windows Server 2008 system is smoother by simply moving the settings of the Windows Server 2008 system service!

1. Solve the problem that the firewall cannot be set up

When a colleague wants to access the network printer connected to the Windows Server 2008 system, the target network printer cannot be found. I try to ping the Windows Server where the network printer is located from the client system. When the system host was found in 2008, the ping command could not be executed successfully. However, when pinging the client system from the Windows Server 2008 system host, the ping command can be executed successfully. Therefore, the author estimates that the colleague cannot find the network printer, which is probably the Windows Server 2008 system. The built-in firewall feature in the host limits shared print access and ping commands. To do this, the author immediately clicks the "Start" /"Settings" /"Control Panel" command in the Windows Server 2008 system, in the pop-up system control panel window, double-click the "Windows Firewall" icon to enter the basic firewall of the corresponding system Parameter configuration interface, click the "Settings" button, ready to modify the relevant parameters, the system has appeared Windows Firewall /Internet Connection Sharing (ICS) service does not start normally prompt information, follow this prompt, the author clicks Start the "/" run command, enter the string command "services.msc" in the pop-up system run dialog box, click the Enter key, enter the service list window of the corresponding system, find the target system service from it, and double-click with the mouse When this service option was found, it was found that the Windows Firewall/Internet Connection Sharing (ICS) service could not be enabled to run normally. So, we can't parameterize the built-in firewall in Windows Server 2008 system. I thought it would System Service has a dependent Remote Procedure Call (RPC) The service and Network Connections service are not working properly, causing the Windows Firewall/Internet Connection Sharing (ICS) service to fail to start properly. However, after careful inspection, the two dependent services are already in the normal startup state, which indicates that they are connected to the system firewall. The service fails to start the failure and has nothing to do with it.

Figure 1 LanmanServer service

Later, I accidentally saw that the "Server" service in the Windows Server 2008 system is turned off, without the support of this system service, Windows Server 2008 system is definitely unable to support network share printing operations; therefore, the author also opens the property setting window of the "Server" service (as shown in Figure 1), click on the "General" tab page of the corresponding window. Start the "Start" button, restart the "Server" service, and then set the startup type parameter of the system service to "Automatic", and finally click the "OK" button to save the above good settings, and restart Windows Server. 2008 system; wait until the system restarts successfully, I try to enter the basic firewall parameter configuration interface again, click on the setting button, I found that the parameters of the firewall can be modified now, which means that the "Server" service is closed unexpectedly, which is exactly our Unable to set the root cause of the firewall.
Previous 12 3 4 5 Next Read more