Unable to ping server / IPSec problem
There are many reasons for unable to ping a server. The reason might be corrupted network drivers, server is down, network problems and a lot of reasons like these.
But if you are able to ping the server while booting the server and unable to ping after the server is fully booted, it may be an issue with IPSec driver. A System Error event with Event ID 4292 will be logged as shown below.
The immediate resolution would be boot the server in safe mode and disable IPSec service. After disabling the IPSec service, start the server in Normal Mode and check. The problem should be resolved.
If the problem is not resolved and you require IPSec driver, then do the following:
To resolve this issue, delete the following registry subkey and then rebuild the policy:
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following subkey:
- On the Edit menu, click Delete.
- Click Yes to confirm that you want to delete the subkey.
- Quit Registry Editor
- Rebuild a new local policy store. To do this, follow this step:
Click Start, click Run, type regsvr32 polstore.dll, and then click OK.
Please refer the KB article http://support.microsoft.com/kb/870910