Tools

No PDC Error in Dameware

This article describes the No PDC error and its relation to Microsoft Windows Network Browser.

First published date

10/16/2018 12:55 AM

Last published date

3/20/2025 4:36 AM

Overview

This article describes the No PDC error and its relation to Microsoft Windows Network Browser.

Product section

Dameware Remote Support & Mini Remote Control

Cause

The No PDC message is displayed because of any of the following:

  • The local machine was configured to be part of a workgroup instead of a domain.
  • The Domain Controller is running an Active Directory.
  • The NetBIOS is disabled on the operating system (for example, NetBIOS over IP (NetBT/WINS), NetBIOS over IPX,) or was not configured properly during network implementation.
  • The remote domain is currently unavailable within Microsoft's Network Browser list, or not reachable via NetBios.

Resolution

You may perform the steps below: 

1. Launch DRS as administrator
2. Click on View
3. Go to Properties
4. Click Network Browser tab
5. Place a check on “User Alternate Machines for PDC lookup failure”

     
    SolarWinds does not have control over this browser enumeration. Microsoft’s Windows Network Browser is part of the operating system, which is retrieved from the master browser defined on the network via a NetBIOS lookup. Our software will ask your operating system for the browser list and then displays the information. The machines are classified and defined in the master browser depending on the operating system and network.
     
    There are known issues with Vista/Server 2008/Windows 7 and Microsoft’s Windows Network Browser (NT Browser). The NetBIOS browsing across subnets may fail after upgrading to Windows Server 2008 article may with the Microsoft Windows Network browser behavior on your 2012 AD environment.
     
    For a detailed discussion of how Microsoft's Windows Network Browser is displayed (enumerated) within our software, please refer to the Dameware Remote Support Network Browser article.
     
    Depending on your Network configuration and implementation, Microsoft Windows Network Browser may or may not work in an Active Directory environment. Active Directory is different and is running on top of the operating system itself, so it is entirely up to the operating system if these APIs can communicate with any features within the Active Directory.   
     
    However, this is why SolarWinds created the Active Directory Browser. This portion of the browser pane communicates directly with Active Directory via LDAP and ADSI.  Add your AD domain, either via its IP address or via the FQDN (if hostname resolution is properly set up on your machine). Or if you have a distributed Domain environment with multiple Domain Controllers, then just add the DC that is closest to your physical location (most likely by its IP address) and manage your AD Domain that way.   

     

    Please check as well if the computer browser service is enabled on your primary domain controller and the host machine.