|
RebelRemote |
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.
Most reasons for not being able to connect to RebelRemote Server's VSGate involve not specifying the correct address or port number. When attempting to connect, verify that:
The IP address of RebelRemote Server's VSGate is correct.
The port number of RebelRemote Server's VSGate is correct. Port 11160 is the default, but this may have been reconfigured by your system administrator.
RebelRemote Server's VSGate service has been installed correctly.
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 was invalid. Other than password or user typos, this may occur if:
The user does not have an account on the NetWinder OfficeServer, or the user doesn't have proper encryption key.
The authentication server settings are improperly configured on RebelRemote
Server's VSGate or at the authentication server itself.
|
|
[TOP] |
|
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.
Make sure that the log-in session has been started or has not been terminated.
The left side of the main window should show a message like "TUNNELING".
If the client is not logged in, applications will not be able to access
the secure network.
Launch the application after RebelRemote Client
has started. For certain applications, it may also be necessary to launch
the application during a log-in session.
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. There are actually several ways to configure DNS services on VSGate. More information is available on the Administrator's Guide.
|
|
[TOP] |
|
The application may be listening on a fixed port number that is already in use on the gateway. This may occur for several reasons:
If the gateway is not running UNIX, the gateway may be treating the required port number as a privileged port (<1024) In this case, the gateway should be restarted with the -o option.
Another application may be running on the gateway that's using the same port number. Don't run this application on the gateway.
Another user may be running the same application on their remote system. If this is the case, using assigned IP addresses on the gateway is recommended.
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] |