Installation manual

MONGOOSE
Installation Manual
41
Troubleshooting the Mongoose Connection
Before troubleshooting a connection issue, it may help if you understand the basics of how Mongoose
Tracker discovers and then establishes communications with a Mongoose. Mongoose devices send
occasional UDP messages. RaneLink (a Windows Service installed with Mongoose Tracker that helps
establish communication with Mongoose devices) listens constantly for these messages and, once it
receives one, does the following two things, if necessary: It sets up a temporary link-local IP address (in
other words, it is cleared when the computer reboots) on the appropriate network interface card (NIC). It
also adds an entry to the computer's network route table. is entry tells Windows and Mongoose Tracker
which NIC to use for communicating with the Mongoose. e same UDP (Zeroconf) messages also
indicate to Mongoose Tracker that a Mongoose device is available on the network, so it can be displayed
in the Device Discovery window.
Mongoose Tracker displays in its Device Discovery dialog box all Mongoose devices it detects, whether
or not it is able to connect to the device. If Mongoose Tracker detects a device but is unable to establish
communications, a button appears labeled Troubleshoot Connectivity.
Click this button to display a list of suggestions for resolving your connectivity issue. For your convenience,
the same list of suggestions is presented below (in order of priority):
1. Give Mongoose Tracker more time to establish the connection.
It can sometimes take up to two minutes for Mongoose Tracker to establish the network settings and
communications it needs (within Windows) to connect to the Mongoose. During this time, Mongoose
Tracker may be waiting for DHCP server detection, Windows’ networking timeouts, or simply trying
to complete its negotiation with the Mongoose device. When you first power up a Mongoose, it’s
internal power-up routine can take a long time to complete. So the first troubleshooting tip? Patience!
2. Add Mongoose Tracker and the RaneLink service to your firewall exceptions list
If you’ve practiced patience and it hasn’t paid off, it’s time to try something else. e most common
culprit at this point is your firewall (either the Windows firewall or a third-party firewall). It may be
preventing communications. To avoid this problem, add the Mongoose Tracker and the RaneLink
service (a service needed by Mongoose Tracker to establish a connection) to the firewall’s exceptions
list. e file names are Mongoose Tracker.exe and RaneLink.exe and they are both located in the
Mongoose Tracker installation folder. e default location is listed below:
C:\Program Files\Rane Corporation\Mongoose Tracker\Mongoose Tracker.exe
C:\Program Files\Rane Corporation\RaneLink\RaneLink.exe
Note: You may need to reboot your computer after adding these files to the exceptions list.
3. Ask your IT department for some assistance.
If your computer is administered by an ITdepartment, you may need their help. Refer them to the
following two topics in the Mongoose Tracker Help system: Administrative Rights Requirements
and Ethernet Communications Between Mongoose Tracker and Mongoose. Perhaps you are the IT
department. In that case, these IT topics are meant for you!