
Active Directory Web Services, commonly known as ADWS, is a Windows Server service that provides a web service interface to Active Directory domains and Active Directory Lightweight Directory Services instances. It is essential for tools such as the Active Directory module for Windows PowerShell and the Active Directory Administrative Center. When ADWS stops working, administrators see errors like "Unable to find a default server with Active Directory Web Services running." This guide explains how to check if Active Directory Web Services is running, test its connectivity, and troubleshoot common issues.
Integrate Enterprise Systems with AAMAX.CO
Many businesses need web applications that connect securely with directory services for authentication and user management. AAMAX.CO is a full-service digital marketing company offering web development, digital marketing, and SEO services worldwide. Their web application development team builds internal portals and business tools that integrate with enterprise identity systems, including Active Directory and modern identity providers. They help organizations create secure, user-friendly applications built on reliable infrastructure.
What Active Directory Web Services Does
ADWS was introduced with Windows Server 2008 R2 and is installed automatically when you promote a server to a domain controller. It listens on TCP port 9389 and allows management tools to communicate with Active Directory over a web services protocol. Without it, PowerShell cmdlets like Get-ADUser and Get-ADComputer fail, and the Active Directory Administrative Center cannot connect. Traditional tools like Active Directory Users and Computers use LDAP directly, so they may continue working even if ADWS is down, which can make the problem confusing to diagnose.
Method 1: Check Using the Services Console
On the domain controller, press Windows + R, type services.msc, and press Enter. Scroll to Active Directory Web Services. Check the Status column; it should say Running. The Startup Type should be set to Automatic. If the service is stopped, right-click it and choose Start. If it starts and then stops again, check the Event Viewer for the underlying cause.
Method 2: Check Using PowerShell
PowerShell offers a quick way to check the service locally or remotely. On the domain controller, run:
Get-Service ADWSThe output shows the status and display name. To check a remote domain controller, use:
Get-Service -Name ADWS -ComputerName DC01To check every domain controller in the domain at once, combine commands:
Get-ADDomainController -Filter * | ForEach-Object { Get-Service ADWS -ComputerName $_.HostName }Note that this command itself requires at least one working ADWS instance. If it fails, check each domain controller individually. To start the service, run Start-Service ADWS, and to restart it, run Restart-Service ADWS.
Method 3: Use the Command Prompt
From a command prompt, run:
sc query ADWSA state of RUNNING confirms the service is active. For a remote server, use sc \\DC01 query ADWS. You can start the service using net start ADWS.
Method 4: Test Port 9389 Connectivity
Even if ADWS is running, clients may not be able to reach it because of firewall rules. From a client machine, test the port with PowerShell:
Test-NetConnection DC01 -Port 9389If TcpTestSucceeded returns True, the port is reachable. If it returns False, check Windows Defender Firewall on the domain controller, network firewalls between the client and server, and any security software that may block the port. On the domain controller itself, netstat -ano | findstr 9389 confirms that the service is listening.
Method 5: Review the Event Viewer
ADWS writes events to its own log. Open Event Viewer, expand Applications and Services Logs, and select Active Directory Web Services. Look for Event ID 1000, which indicates the service started successfully, and Event ID 1100 or 1200, which relate to listening and certificate status. Errors here often point directly to the problem, such as certificate issues or configuration errors.
Common Problems and Fixes
Unable to Find a Default Server
This error appears when PowerShell cannot locate a domain controller running ADWS. Confirm the service is running, verify port 9389 is open, and check that the client's DNS settings point to your domain's DNS servers. You can specify a server explicitly using the -Server parameter in Active Directory cmdlets.
Service Fails to Start
Check dependencies, as ADWS relies on other services such as NetTcpPortSharing. Run sc qc ADWS to view its configuration and dependencies. Corrupted .NET Framework components can also prevent startup; running system file checks or repairing .NET may help.
Certificate Warnings
ADWS may log warnings if no suitable certificate is available for secure connections. While this does not prevent basic operation, installing a valid domain controller certificate through your certificate authority resolves these warnings and supports secure communication.
Time Synchronization Issues
Kerberos authentication requires accurate time. If clocks between clients and domain controllers drift, authentication can fail. Use w32tm /query /status to check time synchronization.
Best Practices for Monitoring ADWS
- Include ADWS in your server monitoring system with alerts if it stops.
- Keep the startup type set to Automatic on all domain controllers.
- Document firewall rules allowing TCP 9389 from management workstations.
- Regularly review the ADWS event log as part of routine domain controller health checks.
- Run
dcdiagperiodically to evaluate overall domain controller health.
Conclusion
Checking whether Active Directory Web Services is running is straightforward using the Services console, PowerShell, or the command prompt. If the service is running but tools still fail, test port 9389 connectivity, verify DNS settings, and review the ADWS event log. With consistent monitoring and proper firewall configuration, you can keep ADWS healthy and ensure administrative tools and integrated applications continue working smoothly.