Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare - Knowledgebase Articles > Dameware Remote Support Network Browser

Dameware Remote Support Network Browser

Table of contents

Updated June 20, 2018

Overview

Often when a machine is not displayed in the browser of Dameware Remote Support (DRS), it is due to System Error: 6118 (list of servers unavailable), which can be observed in the Information pane at the bottom of DRS's display. This common operating system error message is displayed in DRS if any of the following conditions exist:

  • NetBios is disabled in the operating system (for example, NetBios over IP (NetBT/WINS) or NetBios over IPX) or is simply not configured properly.
  • The remote domain is not currently available within Microsoft® Windows Network Browser list or is not reachable via NetBios.
  • The local machine is configured to be part of a WorkGroup instead of a domain.
  • The domain controller is running Active Directory (in which case, use the AD portion of the DRS browser).

Environment

Dameware Remote Support

Dameware NT Utilities

Detail

Microsoft Windows Network Browser: 

Dameware software is not directly in control of how certain portions of the Network Browser enumeration is accomplished. This is because the Dameware Remote Support (DRS) program does not directly classify machines into domains, workstations, computers, and servers. This information is dynamically obtained directly from the operating system and network environment - from Microsoft Windows Network Browser (as displayed in My Network Places or Network Neighborhood). DRS retrieves the Microsoft Windows Network Browser list from the OS on the local machine and displays this information without altering it in any way. 

 

The list of computers is obtained directly from the Security Account Manager (SAM) Database on the domain controller and provides a list of all domain members. This list may contain machines that are not currently online and potentially machines that no longer exist if these computer accounts were not maintained or purged. All Windows NT/2000/XP/2003/Vista machines must have a computer account in the domain before they are allowed to log in to the domain. However, if a machine is disjoined from the domain, renamed, moved to another domain, or retired, its account is not automatically deleted, and this old information must be manually removed from the domain. 

 

The list of workstations, servers, and domain controllers is retrieved directly from Microsoft Windows Network Browser, which the primary machine retrieves from the master browser. The list is also displayed in My Network Places or Network Neighborhood. The way these machines are classified is determined by the OS, the network, and how the machines announce themselves to the master browser. Machines may also be hidden (via a registry key) within Microsoft Windows Network Browser (read ahead for more information on hidden machines). You may also experience issues with the OS if there is more than one master browser. Machines may also not be listed in Microsoft Windows Network Browser if NetBios over TCP was not enabled within the O/S configuration.

 

Microsoft Windows Network Browser can be maintained in many different ways (including DNS and WINS). Encountering a corrupted WINS database is a common issue. The Microsoft Windows Network Browser sometimes reflects the real list of computers that are online, so it is normal to have some variation. Bogus domains may be listed as workgroups that have been setup within a user's enterprise. Computers come online and go offline, get promoted and demoted to and from domain master browser, the master browser, and the backup browser. The default browser update interval can be as long as 12-15 minutes or longer if the primary machine was configured as a master browser. As a result, machines may be listed incorrectly in the browser (especially if the primary machine has just rebooted) until the next update occurs.  However, performing a refresh in DRS (right-click Microsoft Windows Network and select Refresh) updates the list as well.

 

Servers and workstations may be hidden. When this option is enabled, the machine does not show in Microsoft Windows Network Browser. In this case, add the machine to the Favorite Machines list. You may need to use the IP address instead of the host name. You can also change the hidden property or check to see whether it is enabled. To do this, open DRS's Properties View and add the machines to the Batch Processing pane at the bottom. Select the desired machines using the CTRL and SHIFT keys. Right-click and select Batch Processing. The option to modify hidden values is now available.   

For additional information, see the following Microsoft Knowledge Base articles:


Common Questions About Browsing with Windows
Description of the Microsoft Computer Browser Service
MS Windows NT Browser 

 

You can get the information displayed when under Members View directly from the SAM database domain controller. It provides a list of computer accounts (domain members) for the domain. When each machine is retrieved from the SAM database, its type is unknown. DRS automatically performs a search for the machine in Microsoft Windows Network Browser to retrieve the machine type and all pertinent information such as OS and version. If the information is not present in Microsoft Windows Network Browser, DRS cannot determine the type of machine and does not update the machine icon. For these machines, DRS will displays the Windows NT Workstation or Server designation in the same way it is displayed in Microsoft Server Manager.

 

There are browsing considerations when multiple sites are joined by ISDN routers (on a pay per use basis):

Browsing & Other Traffic Incur High Costs over ISDN Routers

Last modified

Tags

Classifications

Public