Article ID: 17699
Date:22 March 2006

Updated: 08 August 2006

Title: How to run the Good Link Server (GLS) Connect Tool in GoodTools

Fact:

Good Tools is an easy way of running some of the Command Line utilities outlined in Chapter 8 of the Goodlink Administrators Guide. Here we will discuss the GLS Connect tab in GoodTools: If you want to see how to use any of the other GoodTools on this top picture, click the tab that you wish to see information about.

*Note: We usually launch GoodTools.exe from the default path of "C:\Program Files\Good Technology\GoodLink Server\util" (it might not be a bad idea to have the Admin create a shortcut on the GLS' desktop for this).

GLSConnect is a way to test network connectivity between a GoodLink Server and the Good DataCenter (GDC). This is useful in troubleshooting disconnects, sync latency, or other Server side coverage issues. As displayed above, when you open the tab the fields are already filled out with the server's information. By default the number of requests is set to 1 and the timeout (seconds between requests) is set to 30. Tracing is also disabled by default. Tune the Request and timeout fields to an appropriate setting depending on what type of issue you wish to test, then click the Test button:

Depending on the number of requests and the interval, it will take time for the popup window to appear. The dialog window will display the test results. This test succeeded. Failures will appear in the results and can indicate communication problems and help you in your troubleshooting. To send the results to csteam, click Send. These results can then be viewed by you, forwarded to other techs, Escalations, etc.

Additional Information: There is an issue running this tool in 4.5. There have beem instances where running GLS Connect will cause problems with the server connecting or disconnecting the server altogether. You can download a repaired copy here:

ftp://goodcust:g00d4Me!@ftp.good.com/gdglsconnectJan06.zip

Inside the ZIP file is a ReadMe file with instructions on running it. This issue is fixed in (4.8)