FIX: Windows Server is not operational
Windows Server provides for quite a reliable platform that does a good job of hosting programs or sites. But that does not mean there are no errors to be encountered with Windows Server, with the one that has been reported by many is the Server not operational message.
Of course, that’s not a pretty sight to be faced by any server operator. Nevertheless, it is also quite easy setting things right here, and with the least of effort too. So, dig right in for the solution to the server not operational issue.
How to fix the Server is Not Operational error
1. Setting the right IP configuration
- Check the IP configuration to ensure the gateway is configured to serve as the DNS server on the Domain Controller.
- You are also recommended to change the IP configuration to either 168.1.33 or 127.0.0.1.
- Check if this solves the problem.
2. Turn off guest account in the trusted domain
- Click on Start > Programs > Administrative Tools > Active Directory Users and Computers.
- Locate the domain in the console tree where you wish to introduce the change.
- Click on the Users
- Right click on Guest in the details pane.
- Select Disable Account.
3. Create similar trusting domain user account in the trusted domain
- Click on Start > Programs > Administrative Tools > Active Directory Users and Computers.
- In the console tree, right click on the Users
- Point to New and select User.
- Type details of the user already present in the trusting domain and then select Next.
- Type in the existing user account password and then select Next.
- Click on Finish.
- Check if this solves the issue.
4. Resolving configuration error
- Join the server to the domain followed by configuring the server to be a domain controller.
- This makes the Active Directory Domain Services (AD DS) Wizard in Server Manager to use Kerberos authentication and not NTLM authentication for browse the AD DS forest.
The above steps should be all you need to do to get rid of the Server Not Operational error.
Further reading.