LAN Ranger not seeing client machines

Question

LAN Ranger does not see some network machines when Ranger is installed on them.

Symptoms

N/A

Resolution

Instructions

For LAN Ranger to display and allow control of client machines, there has to be working TCP/IP connectivity between server and client. If Ranger has been installed on a client machine (using the RangerInstall user) and the machine has been rebooted, the machine's name should appear in the LAN Ranger's "Computer" list.

If it does not:

• Check that TCP/IP is installed and working correctly between client and machine. Remove Ranger, use Ping to test IP connectivity. If using multiple subnets, test routing of traffic on the appropriate port (usually 8888).

• Check the Ranger Server address and port is correctly configured in RangerAdmin. This address is copied to and used by client machines when Ranger is installed.

It is to this address that clients send the switch on and all subsequent Ranger messages. Internally, this IP address is stored in :

HKEY_LOCAL_MACHINESOFTWAREHyperion Security SoftwareRangerCurrent Settings
     "Ranger Server Address"

Check this address is correct after Ranger has been installed.

Additionally...

• Check the DHCP IP leasing configuration.
• Try pinging the local machine from the server - is there connectivity?
• If ping works, test the underlying socket communications by logging on as the local adminsitrator on a workstation and from a command prompt, telnet onto the port used by the Ranger service running on the server.

     telnet 192.168.0.1 8888

     (insert your server's IP address)

If socket communications exists, you will receive a few lines of "garbage" response. This is the service handshake. If a connection is unavailable, there is a problem with Windows' TCP/IP installation on either the workstation or server.

• Check the server's Ranger Server service dialog.

It should show one connections for every active Ranger machine on the LAN. If is shows none, then there are either no machines on with Ranger installed or something is wrong with TCP/IP. Try removing then reinstalling TCP/IP on the server

• Check the event log for Ranger Server errors such as not being able to create enough sockets.