Guest Column | May 29, 2013

Effectively Diagnosing Wireless Connectivity Problems

By Jim Christofferson,VP, Business Development, Connect, Inc.

Dropped sessions, slow response times and erratic performance can be difficult to definitively diagnose. And because of that, companies often find themselves living with these issues for long periods of time. Unfortunately, the costs of choosing to live with connectivity problems compound rapidly, even for symptoms that are seemingly minor.   

In a recent Field Technologies article, Andrew McFarlane, CEO of Mobile Pulse, put his finger on the crux of the challenge: “It is difficult to diagnose mobile network issues and very difficult to differentiate device, application and network problems.” Therefore a tool that can identify a device, application or network problem is precisely what is needed. He continues: “The effort involved in troubleshooting is expensive and time consuming without the right tools.” As such, the diagnostic tool must remove any ambiguity about the source of the problem(s) so that all efforts can focus on a solution.

Interested readers will know that there is a wide selection of diagnostic tools related to mobility. Yet it can be very difficult to ascertain whether or not a solution will effectively distinguish between device, application and network problems. Here’s what to consider when evaluating a diagnostic tool.

Please log in or register below to view the full article.

access the Guest Column!

Get unlimited access to:

Trend and Thought Leadership Articles
Case Studies & White Papers
Extensive Product Database
Members-Only Premium Content
Welcome Back! Please Log In to Continue. X

Enter your credentials below to log in. Not yet a member of Field Technologies Online? Subscribe today.

Subscribe to Field Technologies Online X

Please enter your email address and create a password to access the full content, Or log in to your account to continue.

or

Subscribe to Field Technologies Online