Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare - Knowledgebase Articles > Error: No PDC

Error: No PDC

Table of contents

Updated May 23, 2017


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


All Dameware Remote Support versions


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.

Our software does not have control over this browser enumeration. Microsoft’s Windows Network Browser is part of the OS, which is retrieved from the master browser defined on the network via a NetBIOS lookup. Our software will ask your OS for the browser list and then displays the information. The machines are classified and defined in the master browser depending on the OS 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 (© 2017 Microsoft Corporation, available at, obtained on May 24, 2017.) 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 DNTU's Network Browser (Microsoft Windows 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 OS itself, so it is entirely up to the OS if these APIs can communicate with any features within the Active Directory.   
However, this is why we created the Active Directory Browser because this portion of the Browser pane communicates directly with Active Directory via LDAP & ADSI.  Add your AD domain, either via its IP-Address or possibly via the FQDN (if names resolution is properly setup 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.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified