RebelRemote

  1. RebelRemote Overview
  2. RebelRemote Client Links
  3. Making a Remote Connection
  4. Troubleshooting

Troubleshooting Tips

If you encounter difficulties running RebelRemote, you may find some of the suggestions below helpful for troubleshooting the problem. For most client problems, the first step will be to enable the traces, Display-Trace Log-in and Display-Trace Data. This will display the events on a trace list during the log-in and application session. The previous session's events can be displayed while RebelRemote Client is off-line by selecting Display-Show Trace. Although the number of events logged to the trace display is limited (older events are overwritten with newer ones), the trace display can be saved to disk and sent to your system administrator.

Unable to connect to VSGate

The most common reason for not being able to connect to RebelRemote Server's VSGate is that the address or port number specified is incorrect. When attempting to connect, verify that:

Unable to successfully log into VSGate

In most cases, an unsuccessful log-in to the server will display an error message explaining the reason for the failure. The most common error message is that the user or password is invalid. Other than password or user typos, this may occur if:


   [TOP]  


 

Unable to run some or all applications

If the trace display is enabled (see above) and RebelRemote Client does not show any activity when executing Windows TCP/IP applications, the data is not being tunneled.

Application reports DNS lookup failure

You will receive this error message when the Domain Name Service (DNS) has not been configured on the host that is running RebelRemote Server's VSGate. Before you attempt to connect, make sure you know the IP adrdess of the machine behind VSGate.


   [TOP]  


 

Application is unable to bind to a port

The application may be listening on a fixed port number that is already in use on the gateway. This may occur for several reasons:

Ping doesn't run

This is a known and expected behavior. The ICMP protocol that is used by ping is not tunneled. If the problem you are seeing is not resolved by one of the suggestions above, please contact your administrator regarding the problem. Your administrator will then contact Rebel.com if they determine that the problem is related to the RebelRemote software.

 


   [TOP]