How to disable Tunnel/ISATAP Adapter?

There was an issue that whenever I ping a windows server, I was getting the response I was getting the response with IPV6 address. When checked on the source and destination, IPV6 was disabled. On detailed analysis found that the IPV6 was actually active on Tunnel adapter of the destination server.

Issue was fixed after disabling IPV6 from the Tunnel adapter on destination server by using the below command:

netsh int ipv6 isatap set state disabled
netsh int ipv6 6to4 set state disabled

You can also disable Teredo/isatap(Tunnel) adapter using the below command:

netsh interface teredo set state disable
netsh interface isatap state disable


Windows Server 2012 GUI went missing

Very recently, I came across an issue with Windows Server 2012 R2. When I accessed the server using RDP, only thing I can see was the command prompt and the mouse cursor. GUI was corrupt/missing. I was then able to recover the GUI using the below command:

Dism /online /enable-feature /all /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer

After a restart my machine came back online again.

You can also install using the powershell command:
Install-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra


Windows 2003 Stops ping after Cntl+Alt+Del screen.

Very recently, I came across an issue where the server was not responding to ping command. When checked within the server name resolution was not working. Tried various options like disable/enable NIC, update drivers, change vlan etc and nothing worked. During troubleshoot I once rebooted the server and found that the server was responding to the ping command after the reboot, unfortunately its stop responding after the Windows login screen.

When checked the event logs found the issue was somehow related to the IPSec service. When checked, the serive was not running. Was then able to start the service after registering the DLL file named “polstore.dll” by executing the command.

regsvr32 polstore.dll

Manually starting the service IPSec and a reboot fixed the issue.