Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

Windows Server 2003 as DC suddenly stopped working on network

$
0
0

Hi all,

I have windows server 2003 setup as a domain controller for a few workstations in an office. The server roles used are AD, DNS & TS. I had it up and running fine, not problems. Few little things with folder permissions for roaming profiles, but nothing major. All of a sudden, the server stopped communicating on the network. It was as if I had unplugged the ethernet cables. I cannot access it from any workstation, neither with its name, nor ip. I cannot get onto it through RDP nor logon to the domain properly (the workstations keep using offline versions of the profiles). Oddly though, i CAN access the workstations from the server. everything seems to be working only one way.  After much hunting through the server logs, I found a few errors relating to DNS, however that appears to no longer be an issue, even though the problem points to a DNS error. And the service: Windows Firewall/ICS refuses to start.

I don't pretend to be an expert with all of this, and i don't know whether it matters if Firewall/ICS service is running or not....but I am at a complete loss. Especially considering that I wasn't changing any settings at the time it stopped functioning.

I know its not a lot of info, but any ideas or suggestions??????

The only thing I can do next is to reinstall DNS and reconfig all the entries for the AD.

Thanks!


Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>