Running a Traceroute
If you are seeing issues with connecting to Workamajig, then please run a traceroute (tracert) from your computer to see if the issue can be located.
Then if the routers IP address in question is within your control, have your IT folks investigate if the issue can be resolved.
If the IP Address is an external address, then there may not be much that can be done, as these report back IP's from across the nation and also datacenters.
Please email support@workamajig.com if you experience long periods of outages or want to inquire further.
Windows
1. Click Start.
2. Click Run. From here a box will open.
3. Type "cmd" without quotes in the box to open the command prompt.
4. Type in "tracert app##.workamajig.com" without quotes, replacing it with your server URL or IP Address.
You will see each transfer through other computers on a network, or HOPs the IP packet takes along the path to the site/server. On each line, there will be three durations (in milliseconds) to each hop along with the domain name of that device and its IP address.
The more HOPs there are, the more routers the packet traveled through. You will see something like: 28 ms 41 ms 33 ms www.firstdevicedomain.com [192.168.0.1] 2 48 ms 41 ms 49 ms www.seconddevicedomain.com [16.70.15.99]] 3 92 ms 99 ms 98 ms www.thirddevicedomain.com [53.11.75.99] 4 122 ms 141 ms 137 ms www.domain.com [46.44.5.122]
Typically, a router configuration problem or bad IP address will read something like this on the first HOP line: "157.54.48.1 reports: Destination net unreachable."
Mac OS X
1. Open Utilities. This can be found on the desktop header, under the "Go" drop menu.
You can also access it by using the keyboard shortcut Up, Command and U.
2. Open up the Terminal (also known as the command line.)
3. Type "traceroute app##.workamajig.com" without quotes, replacing it with your server URL or IP Address.
4. Read the results of the traceroute.
If the IP packet did not complete its path, you will see a notation as to why such as "Host is down" or "Source Route Failed." The former indicates the server is down, the latter that your router may be configured to block source-routed packets.