Introduction

A cluster connection problem generally means that either the server or a client window is frozen.

Master can’t connect to slave’s VRDaemon

In the master’s log, you see:

[X] ConnectToDaemon:Failed to connect to '192.168.1.2'.Is the VRDaemon running?
[X] RemoteStart: Failed to connect to daemon.

- Make sure you have the VRDaemon running on all the clients.

- Try disabling the firewall from both the server and the client.

- On the master, use Putty to try a connection to the client’s port 9998:
(You can find the machine Host Name and IP address in the VRDaemon start message)

If Putty can’t connect to the daemon, you will get the following error:

In this case, if you used the machine Host Name, try using the IP Address instead.
If Putty still can’t connect, contact your system administrator.

If Putty can connect to the Daemon, you will get the following message:

Client can’t connect to server

If the client can’t connect to the server, you will see this in the client’s log:

[ ] Trying to connect to '192.168.1.1':9999
[X] Attempt 1: Can't connect to '192.168.1.1':9999
[X] Attempt 2: Can't connect to '192.168.1.1':9999

This is probably a network issue.

- Try disabling the firewall from both the server and the client

- With Putty, try a connection from the client to the master on port 9999 (in Raw mode) :

If Putty can’t connect to the server, you will get the following error:

This means that your network has probably a problem. Ask your system administrator for help.

If the connection occurs normally, you should see a window like: