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.
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 A 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,