Workstations do not appear in LAN Ranger

Question

My network seems all configured correctly, but wokstations are not appearing in my LAN Ranger network view.

Symptoms

N/A

N/A

Cause

N/A

Resolution

N/A

Instructions

This indicates a problem with the client / server communications.

Ranger communications works across pure TCP/IP. On each Ranger server, three services run to communicate with the client workstations. If these three Ranger services could not start or bind successfully to the TCP/IP port then there will be messages in the server's event log.
   

Tip:    When the Ranger client is installed on NT4, 2000, 2003, XP clients, you should always be able to log in as the local machine adminsitrator. Ranger will bypass and disable all securty and monitoring functions and you will have complete access to the local machine as an adminsitrator level user.     



It is recommended you check the following:

Ensure the Ranger services are correctly running on your Ranger server. Look for the two Ranger icons in the tooltray. Check the services dialog via control panel.

Check the state of any physical socket connections by maximising the two services dialogs in the server's tooltray. You should see a socket active for each active workstation Ranger is installed on.

Check that the IP address in RangerAdmin Edit Settings matches that of your server. Verify by pinging from another machine.

From a workstation, log in as the RangerSetup user. Select the "check installation" option and watch for the message confirming the response time when pinging the server. If TCP/IP comms is not working then this will not work.

To test comms on the actual port used by Ranger, use telnet from DOS on a workstation to telnet to the Ranger server on port 8888.


Eg. Telnet 10.0.0.1 8888


If the Ranger service is running and visible on that port, then you should receive a few lines of garbage back (this is the encrypted service handshake).

If you have a multi-layer / multi-subnet network it may be that either your network switches/routers are not passing traffic on port 8888 or some other server program is using the same port.

Stop LAN Ranger and the Ranger services (via the start menu). Locate and delete the RgrShDbConnections.tab and RgrShDbStatusLog.tab files from the Ranger directory. Restart the services and then start LAN Ranger again. If this solves the problem then ensure your are running the latest Ranger 4.4SR1 and it is fully patched.

Try running the "Ranger Repair/Setup" option from Ranger Account Manager. This will ensure the system user has sufficient permissions to access the Ranger directory (required to enable the services to start)

On workstations, ensure that TCP/IP is installed as a network protocol and configured correctly.

If Windows 95 workstations are being used, ensure the W95ws2setup.exe Windows 95 sockets patch is applied.

Note: After removing Ranger you will most likely be able to log in, since the workstations probably have mulpiple network protocols defined.

If TCP/IP comms is found not to be functioning, then it may be necessary to reinstall TCP/IP from Window's Add/Remove Programs.

Ensure your system is running ranger relaease 4.4SR1 or later.

Testing

N/A