Warning
WARNING: The TrackAbout MetaWiki has been deprecated and is no longer being updated.

Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.

Difference between revisions of "Troubleshooting Connectivity"

From TrackAbout MetaWiki
Jump to navigation Jump to search
(Major edits)
Line 1: Line 1:
 
==No Internet Connectivity==
 
==No Internet Connectivity==
*Check if this is only affecting you or your whole office. If only you reboot your computer. You can also check if other devices using the same network have issues too.
+
* The best connectivity test is going to be the one performed on the same or similar device or computer as the one having problems, and on the exact same network subnet or wifi access point.
*Contact your IT or network department or IT contractor. For small operations, reboot you cable modem and routers, wait 5 minutes and try again. If problem persist, contact you internet service provider.
+
* Check if the issue is only affecting one device or many. Check if other devices using the same network have issues too.
 +
* Contact your IT or network department or IT contractor.
 +
** For small operations, you might reboot your Internet modem and/or routers if you can do so without disturbing operations, wait 5 minutes and try again. If problems persist, contact your internet service provider.
 
*See also [[#Advanced troubleshooting|Advanced troubleshooting]] below
 
*See also [[#Advanced troubleshooting|Advanced troubleshooting]] below
  
==Slow access==
+
==Slow Access==
 +
Are you getting the speed you're paying for?
 
===Internet speed test sites===
 
===Internet speed test sites===
*OOKLA http://www.speedtest.net/
+
* DSL Reports http://speedtest.dslreports.com/
*Speakeasy http://www.speakeasy.net/speedtest/
+
* OOKLA http://www.speedtest.net/
*Comcast http://speedtest.comcast.net/
+
* Speakeasy http://www.speakeasy.net/speedtest/
*Verizon http://my.verizon.com/services/speedtest
+
* Comcast http://speedtest.comcast.net/
 +
* Verizon http://my.verizon.com/services/speedtest
  
===Only TrackAbout access is slow===
+
===If only TrackAbout access is slow===
*All pages or specific page is slow?
+
Try to pinpoint the scope of the issue by answering these questions:
*Affects all computers?
+
*Are all pages or mobile actions slow, or only specific ones?
*Affects all locations?
+
*Does the issue affect all computers or mobile devices or only some or one?
 +
*Are all your locations affected or only one?
  
 
===Internet access but no TrackAbout Access===
 
===Internet access but no TrackAbout Access===
*Check the [http://status.trackabout.com TrackAbout System Status] url: http://status.trackabout.com. While at this site, please subscribe to notifications and updates on exactly when our system is being updated. If a system is doing, our engineers are likely already working on restoring the service. Feel free to contact the [[Contact Us|Support team]].
+
Check the TrackAbout Status Page at http://status.trackabout.com
*Use this web site to check if the issue might be just your location or geographical region, or affecting everyone http://downforeveryoneorjustme.com/app.trackabout.com
+
* While at this site, please subscribe to notifications and updates on exactly when our system is being updated.  
**Check other web sites: http://downforeveryoneorjustme.com/
+
* If TrackAbout is experiencing an outage, our engineers are likely already working on restoring the service. Feel free to contact the [[Contact Us|Support team]].
 +
* Our status page indicates whether the application web site and the mobile sync services are basically UP or DOWN. It does NOT guarantee performance of all subsystems is optimal. It only monitors and measures basic tests.
 +
* The System Metrics section shows independent, third-party external tests (Pingdom and New Relic) against two specific health check endpoints:
 +
** Application Web Site - Hits an API which proves the web site engine is up and the database is serving responses.
 +
** TAMobile 6 Sync Services - Hits an API which proves the service is operational, the queuing system is functional and the database is serving responses. There are still many different queues spread across many different customers, so this doesn’t prove that all queues are perfectly healthy or responding quickly. It’s just an up/down check.
 +
* The Status Page also shows when we are doing maintenance or if we’re having an incident or outage.
  
*Check Internet access using TrackAbout TAMobile
+
Use "Down for Everyone or Just Me" to check if the issue might be just your location or geographical region, or affecting everyone: http://downforeveryoneorjustme.com/app.trackabout.com
**Launch TAMobile 6 (TrackAbout on the handheld)
 
**Select '''Utilities''' then select '''CONFIG'''
 
**From the drop-down list, select '''Save Mode''' and select '''Wireless Mode'''
 
  
*Ping test: Open a command prompt and type: <console>>ping ping.trackabout.com</console>
+
Check Internet access using TrackAbout TAMobile
*Trace Route: Open a command prompt and type: <console>>tracert ping.trackabout.com</console>
+
*Launch TAMobile 6 (TrackAbout on the handheld)
 +
*Select '''Utilities''' then select '''CONFIG'''
 +
*From the drop-down list, select '''Save Mode''' and select '''Wireless Mode'''
 +
 
 +
Ping test: Open a command prompt and type: <console>>ping ping.trackabout.com</console>
 +
 
 +
Trace Route: Open a command prompt and type: <console>>tracert ping.trackabout.com</console>
  
 
==Mobile device==
 
==Mobile device==
  
===No Connectivity===
+
===No Connectivity on Mobile Device===
*Using the mobile browser, open the Google search page www.google.com
+
*Using the mobile browser, open the Google search page www.google.com. If Google's search page loads, the general Internet is likely OK.
*Still no access? If device has Wifi and Cellular turned on, turn off the Wifi and try again. (Sometime Wifi are not reliable)
+
*If device has both WiFi and Cellular turned on, your device will favor the WiFi. Try turning off Wifi to fall back to Cellular and try TrackAbout again.
*In the TAMobile 6 app, use the '''wireless Lookup''' feature , entering '111' for serial number or barcode, you should be able to confirm Internet access as well as reacing the TrackAbout servers.
+
*In the TAMobile 6 app, use the '''wireless Lookup''' feature , entering '111' for serial number or barcode, you should be able to confirm Internet access as well as reaching the TrackAbout servers.
  
 
===Connecting a Rugged Handheld to a Wireless Network===
 
===Connecting a Rugged Handheld to a Wireless Network===
Line 47: Line 60:
  
 
==Advanced troubleshooting==
 
==Advanced troubleshooting==
===Miscelaneous Tools===
+
===Miscellaneous Tools===
*Link to page [[Troubleshooting with Ping and Trace Route]]
+
*See [[Troubleshooting with Ping and Trace Route]]
  
===Unable to connect to WIFI network from Rugged Handheld===
+
===Unable to connect to WiFi network from Rugged Handheld===
If you are unable to get Internet access but you connect to the Wifi networks, follow the steps below. This is related to the IEEE 802.11d, a specification that adds support for "additional regulatory domains" such as country information element to beacons, probe requests, and probe responses.
+
====Check and Disable 802.11d====
 +
If you are unable to get Internet access but you are connected to Wifi, follow the steps below. This is related to the IEEE 802.11d, a specification that enables support for "additional regulatory domains" such as country information element to beacons, probe requests, and probe responses.
  
 
'''Config Editor'''
 
'''Config Editor'''
 
# Make sure the Wifi Radio is turned on.
 
# Make sure the Wifi Radio is turned on.
# Make sure to uncradle your device. Depending on your PC settings, the WIFI will not connect if the handheld is in the cradle.
+
# Make sure to uncradle your device. Depending on your PC settings, the WiFi will not connect if the handheld is in the cradle.
#Select the config Editor in the '''Wireless companion''' (can be different based on you OS). Choose Options:
+
#Select the config Editor in the '''Wireless companion''' (can be different based on your OS). Choose Options:
 
##From the drop-down list, select '''Regulatory'''
 
##From the drop-down list, select '''Regulatory'''
##Settings = '''USA'''
+
##Settings = '''USA''' (if you're in the USA, might be different otherwise)
##Enable 802.11d = '''UN-check this box!'''
+
##Enable 802.11d = '''UN-check this box'''
 
##Save and Click the 'X' in the upper right to close the app
 
##Save and Click the 'X' in the upper right to close the app
 
##Back in the Config Editor, click the X in the upper right
 
##Back in the Config Editor, click the X in the upper right
Line 66: Line 80:
  
 
===Questions To Ask To Identify Mobile Connectivity Issues===
 
===Questions To Ask To Identify Mobile Connectivity Issues===
 
+
* Is mobile device traffic VPNed through another connection? Can it traffic be routed directly over the Internet to TrackAbout instead of over the VPN?
* Is mobile device traffic VPNed through another connection? Can it be sent directly as a test?
 
 
   
 
   
* Has any significant performance testing been performed using the Desktop Simulator? Does it perform same/better/worse than handheld? If the desktop performs well, then it might be an issue with the speed or age of the handheld devices.
+
* Has any significant performance testing been performed using TAMobile 6 Desktop? Does it perform same/better/worse than handheld? If TAMobile 6 Desktop performs well, then it might be an issue with the speed or age of the handheld devices.
 
   
 
   
* Can you test with any other brand of device? Could it be something specific to handheld? (perhaps bad interaction with the wireless APs chosen).
+
* Can you test with any other make or model of device? Could it be something specific to handheld? (perhaps bad interaction with the wireless APs chosen).
 
* How old are the handheld devices? What year were they manufactured, what is the model #?
 
 
   
 
   
 
* Do ALL transactions from handheld take a long time or only some. Are there ever fast, sub-1-second transactions? Does TrackAbout ever perform well or is it always bad?
 
* Do ALL transactions from handheld take a long time or only some. Are there ever fast, sub-1-second transactions? Does TrackAbout ever perform well or is it always bad?
Line 87: Line 98:
 
* Is your network configured to blacklist sites that are known to consume a lot of bandwidth (video streaming in particular)?
 
* Is your network configured to blacklist sites that are known to consume a lot of bandwidth (video streaming in particular)?
 
   
 
   
* Is it possible to dedicate a VLAN with QoS to TrackAbout to ensure adequate bandwidth is maintained? Does the local network support QoS features?
+
* Is it possible to dedicate a VLAN with Quality of Service (QoS) features enabled to ensure adequate bandwidth is provided to TrackAbout? Does the local network even support QoS features?
 
   
 
   
 
* Do all devices have problems at the same time? Or is it only some devices that suffer performance problems?
 
* Do all devices have problems at the same time? Or is it only some devices that suffer performance problems?
 
   
 
   
* Is there a redundant internet service provider or only a single provider? How reliable is the internet in general?
+
* Is there a redundant Internet service provider or only a single provider? How reliable is the Internet in general?
 
   
 
   
 
* Are there local tools available to monitor the health of the local network and connectivity to the Internet?
 
* Are there local tools available to monitor the health of the local network and connectivity to the Internet?
 
* Can TrackAbout get remote access to a laptop on the same wifi network that the handhelds are using to run remote troubleshooting steps? Can we get a handheld cradled on the laptop using something like PocketController Pro so we can remote control the handheld as well?
 
**If TrackAbout had a device it could control on the network, what would we do?
 
***We would run all-day ping tests to a variety of sites.
 
***We would run periodic small download tests against a small image file on TrackAbout to see if bandwidth slows at some point during the day.
 
***We would test throughout the day using the Desktop Simulator to gauge performance over time.
 
***We would choose a handful of API endpoints and script repeated transactions against TrackAbout to prove end-to-end connectivity and performance. Gather statistics and analyze at end of day.
 
***We would correlate our local SA tests with transaction performance as seen in our web logs. We can tell when downloads are slow by looking at the total time taken per transaction from time the server sees the first byte of the request from the client until the last byte is sent to the client.
 

Revision as of 19:49, 24 November 2015

No Internet Connectivity

  • The best connectivity test is going to be the one performed on the same or similar device or computer as the one having problems, and on the exact same network subnet or wifi access point.
  • Check if the issue is only affecting one device or many. Check if other devices using the same network have issues too.
  • Contact your IT or network department or IT contractor.
    • For small operations, you might reboot your Internet modem and/or routers if you can do so without disturbing operations, wait 5 minutes and try again. If problems persist, contact your internet service provider.
  • See also Advanced troubleshooting below

Slow Access

Are you getting the speed you're paying for?

Internet speed test sites

If only TrackAbout access is slow

Try to pinpoint the scope of the issue by answering these questions:

  • Are all pages or mobile actions slow, or only specific ones?
  • Does the issue affect all computers or mobile devices or only some or one?
  • Are all your locations affected or only one?

Internet access but no TrackAbout Access

Check the TrackAbout Status Page at http://status.trackabout.com

  • While at this site, please subscribe to notifications and updates on exactly when our system is being updated.
  • If TrackAbout is experiencing an outage, our engineers are likely already working on restoring the service. Feel free to contact the Support team.
  • Our status page indicates whether the application web site and the mobile sync services are basically UP or DOWN. It does NOT guarantee performance of all subsystems is optimal. It only monitors and measures basic tests.
  • The System Metrics section shows independent, third-party external tests (Pingdom and New Relic) against two specific health check endpoints:
    • Application Web Site - Hits an API which proves the web site engine is up and the database is serving responses.
    • TAMobile 6 Sync Services - Hits an API which proves the service is operational, the queuing system is functional and the database is serving responses. There are still many different queues spread across many different customers, so this doesn’t prove that all queues are perfectly healthy or responding quickly. It’s just an up/down check.
  • The Status Page also shows when we are doing maintenance or if we’re having an incident or outage.

Use "Down for Everyone or Just Me" to check if the issue might be just your location or geographical region, or affecting everyone: http://downforeveryoneorjustme.com/app.trackabout.com

Check Internet access using TrackAbout TAMobile

  • Launch TAMobile 6 (TrackAbout on the handheld)
  • Select Utilities then select CONFIG
  • From the drop-down list, select Save Mode and select Wireless Mode

Ping test: Open a command prompt and type:

>ping ping.trackabout.com

Trace Route: Open a command prompt and type:

>tracert ping.trackabout.com

Mobile device

No Connectivity on Mobile Device

  • Using the mobile browser, open the Google search page www.google.com. If Google's search page loads, the general Internet is likely OK.
  • If device has both WiFi and Cellular turned on, your device will favor the WiFi. Try turning off Wifi to fall back to Cellular and try TrackAbout again.
  • In the TAMobile 6 app, use the wireless Lookup feature , entering '111' for serial number or barcode, you should be able to confirm Internet access as well as reaching the TrackAbout servers.

Connecting a Rugged Handheld to a Wireless Network

If you are having problem connecting to your wireless network, contact your IT or network department or IT contractor. See also Advanced troubleshooting below

Testing WIFI

Using a smartphone, several Apps exist to test Wifi signal strength and coverage

Android Free Apps

iOS Free Apps

Advanced troubleshooting

Miscellaneous Tools

Unable to connect to WiFi network from Rugged Handheld

Check and Disable 802.11d

If you are unable to get Internet access but you are connected to Wifi, follow the steps below. This is related to the IEEE 802.11d, a specification that enables support for "additional regulatory domains" such as country information element to beacons, probe requests, and probe responses.

Config Editor

  1. Make sure the Wifi Radio is turned on.
  2. Make sure to uncradle your device. Depending on your PC settings, the WiFi will not connect if the handheld is in the cradle.
  3. Select the config Editor in the Wireless companion (can be different based on your OS). Choose Options:
    1. From the drop-down list, select Regulatory
    2. Settings = USA (if you're in the USA, might be different otherwise)
    3. Enable 802.11d = UN-check this box
    4. Save and Click the 'X' in the upper right to close the app
    5. Back in the Config Editor, click the X in the upper right
  4. Enable Internet
    1. Access the Settings - Connections - WIFI. There select Connect to Internet

Questions To Ask To Identify Mobile Connectivity Issues

  • Is mobile device traffic VPNed through another connection? Can it traffic be routed directly over the Internet to TrackAbout instead of over the VPN?
  • Has any significant performance testing been performed using TAMobile 6 Desktop? Does it perform same/better/worse than handheld? If TAMobile 6 Desktop performs well, then it might be an issue with the speed or age of the handheld devices.
  • Can you test with any other make or model of device? Could it be something specific to handheld? (perhaps bad interaction with the wireless APs chosen).
  • Do ALL transactions from handheld take a long time or only some. Are there ever fast, sub-1-second transactions? Does TrackAbout ever perform well or is it always bad?
  • Have long-duration (all day) ping tests been performed to ping.trackabout.com? Can long-duration tests be run to see if there is any correlation between failure to ping and long handheld transaction times? It would be worth doing parallel all-day performance tests to a number of locations on the Internet to see if all slow down or fail at the same time that users are experiencing problems.
  • If there is a time when ping begins returning slowly, have traceroutes been run to determine the node that is failing?
  • Is performance variable based on time of day? Could it be congestion on the local network?
  • Are there any known “bad actors” or abusers of the local network? Can you detect them?
  • Is your network configured to blacklist sites that are known to consume a lot of bandwidth (video streaming in particular)?
  • Is it possible to dedicate a VLAN with Quality of Service (QoS) features enabled to ensure adequate bandwidth is provided to TrackAbout? Does the local network even support QoS features?
  • Do all devices have problems at the same time? Or is it only some devices that suffer performance problems?
  • Is there a redundant Internet service provider or only a single provider? How reliable is the Internet in general?
  • Are there local tools available to monitor the health of the local network and connectivity to the Internet?