Troubleshooting Guide for Goverlan Agent Communication

Summary:


This article is a troubleshooting guide for communication between the Goverlan Console and the Goverlan Agent as well as the errors "Error 1232: The network location cannot be reached. For information about network troubleshooting, see Windows Help." and "Error 53: The network path was not found."

Information:

Refer to these links for information on Installing Goverlan Agents, and  for Understanding Goverlan Agents


The diagram below demonstrates how Goverlan Console communicates with the Goverlan Agent via the default Port 21158.



Check 1 - Ping Test:



Open a command prompt on A and ping machine B by:

1: IP address (Example. ping 192.168.1.214)
If this test fails, then the machine is either disconnected from the network or behind a firewall which doesn't allow pings.

If this test is successful you should get replies from the ping as shown below. Proceed to step 2. 




2. DNS(FQDN) name (Example. ping TechPC1.mydomain.com)

If this test fails, check your WINS and/or DNS Server Settings under your Network Connection TCP/IP Advanced properties. They should point to valid servers which are aware of the remote machine.

If this test is successful you should get replies from the ping as shown below. Proceed to step 3. 




3. NetBIOS/LLMNR name (Example. ping TechPC1)

For more information on LLMNR, see this Technet Blog.

If the test fails but your machine is pingable by IP address and FQDN, proceed to step 3a.

If this test is successful but you get a different IP address from step 2, flush your DNS cache (ipconfig /flushdns) or check your DNS server for outdated DNS entries.
Otherwise, you should get replies from the ping as shown below. Proceed to Check 2. 




Step 3a

If you are using GoverLAN to query information on a machine which belongs to another Active Directory domain than the domain your machine belongs to, GoverLAN may fail with the error 1232 or 53. For instance, if your machine belongs to the Active Directory domain: Division1.mycorp.com, and you open the computer container of the Active Directory domain: Division2.mycorp.com, the list of computers is displayed, however querying information on a machine may return error 1232 or 53. This is because GoverLAN uses the NetBIOS name format of the machine to query information and your local computer cannot find it under its own domain.

To remedy this particular problem:

Open the Network Connection Properties window of your primary network adapter.
Open the Properties window of the Internet Protocol (TCP/IP) item.
Click on the Advanced button.
Select the DNS tab.
Check the radio button named: 'Append these DNS suffixes (in order):' 
Underneath this option, click on the Add... button and enter the DNS suffix of your domain (for instance: division1.mycorp.com), click Add.
Repeat the previous step and add the DNS suffixes of the other Active Directory domains you will need to administer using GoverLAN.
Click on OK, OK, and OK.
Try to use GoverLAN again.

Check 2 - Telnet Test:

Note: You must enable Telnet Client via Windows Programs and Features or have an application with Telnet ability.

1. Open a command prompt and perform a telnet test from to B including the Goverlan Agent port. (Example telnet 192.168.1.214 21158)
If the test is successful you should get a blank screen with a CMD titled with the IP address and a cursor as shown below:



If the test fails you will get the below error message and must check the client machine for Windows Firewall blocking the port. See this KBA on Configuring Windows Firewall for the Goverlan Agent port.




keywords: goverlan agent, agent error, error 1232, error 53, cannot connect, agent communication, 


KBAs

  1. What are the minimum requirements for Goverlan?
  2. Uninstalling the Goverlan Agents using GoverLAN_Agents_Remove.exe
  3. Troubleshooting Access Is Denied
  4. Required Windows XP Local Policy Settings for Remote Administration
  5. Configuring WMI Security
  6. How to configure the Goverlan Central Data Repository (GCDR) for better logged-in workstation detection.
  7. How to install, update or uninstall the Goverlan Agents on one or more machines
  8. Using the Goverlan Client Agent Installer Resource kit for manual agent installation.
  9. I cannot remote control a Windows XP SP2 or Server 2003 machine once it has been logged into with Microsoft Remote Desktop
  10. Goverlan returns "The Scope Action cannot be saved to the Goverlan Folder" or "GoverLAN failed to save its credential database. Error XXX. No alternate credential will be remembered."
  11. Goverlan Remote Control Video Capture Error. "Couldn't Initialize the Quicktime Runtime"
  12. Configuring Remote Assistance
  13. Authorizing Non-Admins for Remote Control
  14. Goverlan Remote Control Command line arguments
  15. Start an RDP/Telnet/SSH/AMT KVM/VNC connection in Goverlan Admin & Diagnostics from the right click menu
  16. How to Enable User Acceptance "Prompt local user for approval" for Remote Control
  17. Goverlan Agent installer as MSI for Version 8
  18. Error "Object Already Exists" when installing Goverlan.
  19. Using Goverlan to connect to VPN clients
  20. Configuring SQL Server Express for SUREDATA
  21. Upgrading your Goverlan Central Server
  22. How to Migrate the Goverlan Central Server to a new machine
  23. How to migrate Goverlan v8 Console to a new machine
  24. How to Configure the No Visual Notification (Stealth Mode) flag for a Remote Control Session
  25. Troubleshooting Remote Assistance
  26. Goverlan shows yellow icon for machine after Server 2003 Update KB3033395
  27. Troubleshooting Guide for Goverlan Agent Communication
  28. Govtools.exe Command Line Arguments
  29. Changing the default TCP port for Goverlan Agents
  30. Remote Controlling Ubuntu 14 Error no security type suitable for rfb 3.3 supported
  31. Applying SureDATA database configurations with the Goverlan Central Server or Goverlan Admin GPO Template
  32. List of current feature restrictions in Goverlan
  33. Goverlan Migration - Step By Step
  34. Getting Started with the new Goverlan Licensing System
  35. Troubleshooting Goverlan Reach
  36. Goverlan Agent push to a custom admin root share (Non C$).
  37. Enabling Debug Dumps for Goverlan Processes

Feedback and Knowledge Base