Crack the network management puzzle under Windows Server 2008

While fully enjoying the powerful capabilities of the Windows Server 2008 system, it sometimes brings some annoyance to our day-to-day management operations. This is not, when we try to manage a network on a computer that has a Windows Server 2008 system installed, it is often possible to encounter some seemingly simple puzzles that can not be solved in a conventional way, and the frequent occurrence of these puzzles obviously lowers our efficiency in managing the network; in fact, as long as the Windows Server 2008 System Related settings to carry out some ingenious "tuning", we often can easily crack a variety of network management Puzzle Bureau!

1, crack local connection properties do not open the Puzzle Bureau

Recently, I do not know why, the author is ready to open the Windows Server 2008 system environment in the local Connection property Settings window, to modify the corresponding system of the network parameters, the result found that the local Connection property Settings window can not open anyway. Initially, the author thought it was the improper setting of the Group Policy parameters of the Windows Server 2008 system, but after a careful examination of the relevant system Group Policy parameters, the author did not find anything suspicious. Later suspected that the network virus at work, so I installed the use of 360 security guards and Kaspersky antivirus software to the Windows Server 2008 System for a comprehensive and thorough scanning, after a long time after the anti-virus wait, also did not find any network virus "figure." In the face of local connection properties can not open the puzzle, we should take what measures to crack it?

After excluding network virus and System Group Policy parameter setting improper factor, we can try to the Kaspersky antivirus software and 360 security guard shut down, then open the Local Connection Properties Setting dialog box, the results found still not. In the case of no clue, the author had to surf the internet "for help", and later learned that this fault phenomenon is indeed caused by Kaspersky antivirus software, The original Kaspersky anti-virus software in the case of the system will be enabled to automatically block file Netman.dll, and Netman.dll file is exactly the local Connection Properties Settings dialog box related to a network management file, when Netman.dll file was blocked by Kaspersky Antivirus software, then the local Connection Properties Settings dialog box from Then it doesn't show up properly. Find the cause of this trouble, then the author also quickly found the answer: to open Kaspersky Anti-Virus software, the main program interface, from the Settings page to set the Netman.dll file to allow the pass, and then restart the Windows Server 2008 system. Sure enough, after the above setup operation, the author found that the Local Connection Property Settings dialog box has been able to open the normal, so the local connection properties can not open the Mystery Bureau was successfully cracked.

2, cracked ping command test unsuccessful puzzle Bureau

Friends with a Windows Server 2008 system installed on the computer network parameters of a series of settings, found that the computer can not only normal surfing the internet, but also the ability to use a variety of tool software for online communication chat, However, in the corresponding computer system to perform a ping command to check the connectivity of another computer in the local area network, he found the ping command test operation is always unsuccessful, and then he tried to the other computer system connectivity ping Command test operation, the result is still unsuccessful, Prompt information such as "General failure" also appears automatically on the system screen. Later, when the friend Ping the same computer on the local area network on the computer where the Windows XP system was installed, he found that the ping command was executed successfully.

What is the reason for this, the Windows Server 2008 System network access is clearly in the normal state, why not ping the other computers on the LAN? The reason for this failure is most likely the Windows server 2008 system with the improper setting of the firewall parameters, in order to successfully solve this fault puzzle, we need to open the corresponding system firewall configuration interface, according to the following operation of the corresponding ICMP incoming, outgoing policy all enabled: