The System Never Confirms that a Scenario is to Start on a Port

Usually this means the the remote execution deamons are not working correctly on your machine. First, you need to see how you're starting the simulation execution. To do so, open a new terminal window and type:


This should either return a value of ssh, rsh or undefined. Undefined defaults to rsh. First, assuming that you're using ssh, verify ssh is available by typing:
ssh (machine name) ls

The machine name is the name in the JFORCES scenario startup widget except in the case where this is defined as localhost. In this case type "hostname" and replace machine name in the above command with the result. If ssh is working you should see a list of all directories and files in the specified machine. If it's not, one of three things generally happen:

  1. The command hangs for a long time

  2. The system responds with a "connection refused" error

  3. The system requests a password.

In any of these cases you'll need to install and configure ssh. Click here for some help.

Alternately, if you're using rsh test it by typing:

rsh (machine name) ls

The results should be the same as for ssh. The fix might be trickier. Rsh was the UNIX remote shell of preference for years before hackers became a real nuisance and is still an option when your system is not exposed to the internet. Depending on your situation you might want to change to ssh (change the setting for REMOTE_EXEC in ~/.cshrc, add it if necessary) and install and configure ssh. Or, if you're not so worried about hackers, verify the inetd deamon is running and configure as required.