Troubleshooting
Server
Server Not Accepting Connections
When the server component is running clients do not connect up to it saying that the connection is refused or something similar.
This could be because the server is listening on the wrong IP address. For instance there could be 2 network cards installed in your computer connected to 2 different networks. Don't set the server to listen on 127.0.0.1 or localhost as it will not work. Instead set it to the IP address of network card you are expecting the clients to connect up to.
In addition, certain OS/Java combinations will instruct the Java VM to use the IPv6 stack. You want to use the IPv4 stack, which can be forced by the VM parameter -Djava.net.preferIPv4Stack=true.
No Virtual Machines are Started when Requested
When the server is instructed to start all virtual machines on a VMware server, none start.
This is caused because the user that is logged into the VMware server does not have suitable permissions to execute/read/execute the virtual machine files. When the server component logs into the vmware server, it authenticates with the host computer that is running the VMware server. So that for example in Linux if the user logging into the VMware server does not have read/write permission for the virtual machine directory it will not be allowed access.
To fix this problem allow the user read/write access. One way is if the vmware server is on a UNIX based O/S then there should be a user group called vmware. Give the group read/write access to the virtual machine directory:
chgrp vmware <virtual machine directory>
chmod ---rw---- <virtual machine directory>
Cannot Login to a VMware Server when Requested
When trying to start a virtual machine in a VMware server a connection cannot be establised.
Firstly make sure that the port, username and password are correct. If they are and the VMware server is on a UNIX based O/S then it could be a problem with the xinetd service running. This service authenticates users logging into the VMware server into the host system. It could be setup in a way that only allows local users to login. This needs to be changed to allow remote users.
To allow remote users, the most secure way appears to only allow single IP address rather then let everyone authenticate. Open the file (On Gentoo and Fedora) /etc/xinetd.conf and ...
The guest OS doesnt seem to be able to keep a network connection.
We found this to be the case with dynamic network connections. A work around is to supply a static IP on the subnet.
Client
Fatal Error C1902 compiling the client
Compiling the client modules using nmake, I get the error: Fatal Error C1902 (C++).
We encountered this problem and solved it by removing the mspdb80.dll in the VC\bin directory.
