| Connection Cases | Terminal Services w/o Terminal Bridge | Terminal Services with Terminal Bridge |
| Host and client within corporation network | Easy | Easy but not really need Terminal Bridge |
| Host and client within home network | Easy | Easy but not really need Terminal Bridge |
| Home/Internet connect to office (office PC has global IP) | Possible, need to open firewall on corporation network. | Easy, no need to open firewall |
| Home/Internet connect to office (office PC has private IP) | Almost impossible | Easy, no need to open firewall |
| Office connect to home/Internet PC (home/Internet PC directly connect To the Internet) | Possible, trouble with dynamic IP issues, also need to open firewall on corporation network. | Easy, no special setup, no need to open firewall |
| Office connect to home/Internet PC (home/Internet PC connect to the Internet through router) | Very difficult, involves router setup, dynamic IP issues, also need to open firewall on corporation network. | Easy, no special setup, no need to open firewall |
| Connect two machines on the Internet | Possible, may involve router setup and dynamic IP issues | Easy, no special setup |
| Problem | Solution |
| On host, I got "Terminal Bridge Service is not properly started. You may need to run the program as Administrator." |
Run pstbridgehost.exe as administrator. If you are using vista, right click the program and click "Run as Administrator" on the popup menu. If you are using earlier version, logon the computer using an administrator account and run the program. This need to be done only for one time. |
| On client, I got "Terminal Bridge Service is not properly started. You may need to run the program as Administrator, otherwise some functions of the program might not work." | The program should work, some functions including logging will not work. To resolve the problem, run pstbridgeclient.exe as Administrator. Read the solution for the item above. This need to be done only for one time. |
| I am not be able to connect to the host computer when using Remote Desktop. |
Make sure Terminal Bridge client display Ready status. Also make sure in the computer field of the "Remote Desktop Connection" dialog, type in the string which is displaying on the right side of "Remote Desktop Connect String" on the client GUI.
|
|
In the host message list, I got "Warning: The Terminal Server on this host might have not been started. Please make sure the Terminal Server is started." |
Make sure your host computer meet requirements. Also open "System Properties" dialog, go to remote tab and check "Allow users to connect remotely to this computer"
|
|
I receive "The remote connection has timed out. Please try connecting to the remote computer again." when using Remote Desktop. |
One possibility is that the Terminal Services on the host is not up. Make sure it is up. The other problems could be network connection issues.
|
|
On the host message list, I got "Failed to connect to terminal server." |
Make sure terminal Services on the host is up.
|
|
I got "The system could not log you on ..." when using Remote Desktop to connect to my host machine. |
Make sure you are using the user account of the host machine rather than the bridge user account. Also make sure the user name is correct on the Remote Desktop login dialog. If you are connecting to several machines, Remote Desktop will prepopulate the user name as the last user name you used. This is the behavior of the Remote Desktop.
|
|
I got "Failed to connect to bridge server. Please make sure the Internet connection is okay." |
There is a small chance that the bridge server is not up or is having a network problem. If you are sure the Internet connection is okay, you might want retry later.
|
Note: In the installation directory, you should be able to find some log files (activity.log and activity_prev.log). activity.log contains logging information for today's activities and activity_prev.log contains last day's activities. The logged messages can be more than those shown in the message list box. Quite often, you can look into the log files to find the reason of any problems.