LAN Overview
    Server Hardware
    Server Roles
Windows Event IDs



Windows Server Domain

Miscellaneous Server Problems

I have experienced various Windows Server problems that have sometimes taken a bit of effort to understand and resolve. Most of the time, a quick "Google" will point to a relevant Microsoft Knowledgebase article, at other times, there may be a number of solutions proposed. I have documented a number here and the fix that worked for me - your issue and resolution may be different, but hopefully, this page can provide a useful starting point.


Errors Warnings   Other
Role OS Version Description / Resolution Microsoft KB Ref. etc.



2008 / R2

Frequent occasions when DNS could not resolve queries for host names in some TLDs , including

A dnscmd /ClearCache or a DNS service restart would clear the problem - but it would soon reoccur.

Microsoft Knowledge Base


Technet References

Understanding Forwarders


DNS Forwarders vs Root Hints


Configure a DNS Server to Use Forwarders


OpenDNS IP Addresses

Resolution This is a known issue in Server 2008 & 2008R2 when the DNS server is using root hints to provide the IP addresses of root name servers.

This problem does not occur if the DNS server is set to use forwarders, rather than root hints, for internet name resolution.

I configured my DNS servers to use forwarders and pointed to the Open DNS servers.




2008 / R2

Could not ping my servers from inside the domain Various Google hits, including :-
Why can't I ping my server?
Resolution By default, the Windows firewall blocks ping requests, the easiest way to enable it is from the Windows Firewall applet in the Control Panel.

Select the Inbound Rules tree option, scroll down to
File and Printer Sharing (Echo Request  . . ) and enable the appropriate rule(s). There are separate rules for IPv4 and IPv6 and for Private and Domain networks.
RDP Windows Server 2003 Could not RDP to Windows Server after reboot
Various Google hits, including :-

Remote Desktop does not connect after a restart
Resolution In summary, I had to
1.) Stop the IPSec service on the remote machine, and set its startup mode to "Manual"
2.) Restart the remote machine
3.) Restart the IPSec service and set its startup mode back to "Automatic".
This can ALL be done remotely, even without RDP
I was able to stop the service remotely, but could not restart the server using the instructions

Instead, is used Shutdown.exe as described in How to Shut Down and Reboot Remote PCs via the Command Prompt or Restart or Shut Down a Windows Remote Computer and Document the Event






mailto: Webmaster

 Terms & Conditions