Suggestions for a tool to monitor dropped connections (particularly wifi)

usasma

Retired Admin
Joined
Feb 20, 2012
Posts
2,126
I'm looking for a tool to monitor a wifi connection for a given period of time (2, 4, 8, maybe more hours)
It has to detect and log dropped connections (maybe weakening connections also).

What we have is (at work) people coming in saying they occasionally lose connectivity.
Testing for this is nearly impossible - so what we need is a tool that monitors the connectivity and logs any changes over the given time period.

If I can find the right tool, my work will buy it for our use - but it'd also be a good tool for users who have problems with network dropoffs. They could run it and then post the log for a networking expert to look at.

Any ideas/suggestions?
 
I think you need to survey your clients and ask them to record the times of the dropouts, their physical location, and perhaps what they were doing at the time and try to discern a pattern. Maybe it happens when Fred zaps his daily bag of popcorn, or it started when the new FedEx Kinko's laser printing shop across the street opened. Is it happening to everyone or just a few? What is different with those affected? Different channel? 802.11g vs 11n?

WiFi Inspector is nice, has a grafting feature, and best of all, is free. BUT, it only charts the last 8 minutes (this is where the survey may come in handy).

How much is company will to put into this? There are network monitoring programs that cost many $100s or more. Other than that, I agree to check your router logs.
 
Maybe it happens when Fred zaps his daily bag of popcorn

I resemble that remark! :lol:

I use Event Viewer too and tell employees to jot down the date and time of an issue, then look for WLAN start & stops in EV. If they're connected to a server, you'll also see the time stamp for a successful logon to a domain. I don't think Xirrus or InSSIDEr keep a log, but both will show you the last several minutes of signal history if someone calls you right away after a disconnect. I like InSSIDer and think it's a better program - you're able to visually see a disconnect when it happens. Also, there are spectrum analyzers available for use with InSSIDer. They're not cheap, but still not as expensive as overpriced Fluke tools.

You could also try Wireshark and run a full day's capture in the background, but it's not going to tell you anything about the wireless signal itself. Another program that comes to mind is Spiceworks, which can monitor & log your network and all assets. I've got it running in one office but haven''t used it a lot. It can be useful but the web interface is poorly laid out and riddled with ads.
 
Thanks for the input Digerati, but I understand how to troubleshoot dropped connections - and the myriad things that may cause them.
What I need is a tool that will document the network activity on a customer's computer at my shop - and will show that (hopefully) there are no drops at my shop. It'd also be nice if it had a display/logfile simple enough to easily explain to a customer.

The company will put a decent amount of money into it - they've purchased rights to a lot of software that we use.

The best thing that I've found is FreeMeter - but development stopped on it in 2010. Haven't tried it on Win8 as I doubt the company will want to purchase something that old (and without decent support).
I'm also looking at NetWorx, but haven't really done anything with it yet.
 
Oh wow - sorry Fred, or is Dan? :) I forgot I've bumped into a "Fred" here recently. "Fred" was some name I just picked instead of Joe or Sally. Good to "meet" you, BTW.

I like InSSIDer and think it's a better program - you're able to visually see a disconnect when it happens.
Hmmm, Funny. I was going to say I like Wifi Inspector because I think it is better, and you can visually see a disconnect when it happens, but also see when it reconnects. On my notebook, after a disconnect InSSIDer locks up. Have to exit and restart the program - it would not even let me change networks. But WFI starts charting again when wifi reconnects. I guess you get what you pay for.

But really, those programs go on the individual clients and not what you need, John, (unless you are trading notebooks with these users). Install them on your machine and you can tell if you lose connection, but not if your clients do - unless everyone lost it at once. You need to be looking at it from the network side - the router logs or a router/network monitoring program. At this point, you don't know if your network is tossing clients, or the clients are falling off from their side for some unknown reason. The client software can only tell if WiFi is present, or not. If present, it can tell you about it, but if not there, it's not there.

And you need to be able to monitor the WAP (wireless access point) side separately from the router side (even if a "wireless router"). If the WAP is tossing wireless connections or if the devices are dropping from their ends, the WAP may default to informing the router the devices "logged off", as opposed to "loss connection".

The problem needs to be verified and clarified. Many times I've had clients (and I see this in the tech forums all the time,) say they've "lost connectivity" but the reality was they didn't. They were still connected to the network - but lost "Internet" access. What does "occasionally" really mean. Twice in the last month? Or twice in the last hour? What kind of network are we talking about? A small office using a standard home-type, ISP provided wireless router? Or separate WAP and router? Or is it large network with dozens of very busy users and a big chunk-of-change in the network equipment? If the network/wireless equipment is more than found in most homes, it likely came with monitoring software admin (you?) can use remotely from their computer or terminal. How many affected users/wireless devices are we talking about? Two or three and not sure if a coincidence? Or scary (all eyes on you - get it fixed now) numbers?

The router logs will tell when they signed in and logged off, but if we knew specifics about the router (and/or WAP) there might be specific software out there for it.
 
Thanks to everyone for their input! I've submitted this list and hope to see some results soon!

This email is in reference to my suggestion for a network connection logger.

My favorite tool for this would be FreeMeter ( FreeMeter )- but it's not been worked on since 2010 and the author seems to have some problems with his software being pirated. I've used the version from SourceForge in the past: FreeMeter Bandwidth Monitor For Windows | Free Communications software downloads at SourceForge.net

Beyond that, I'm looking for something that has a graph - to make spotting the connection drops easy.

I've used:
ping -t Geek Squad ? Computers, Home Theaters, Appliances, Online Support & More > %userprofile%\Desktop\log.txt
...but it's difficult to scan through 4 hours of the log.txt files

Scripting, especially through the Resource Monitor/Performance Monitor interface is probably the best - but is beyond my abilities. More info here: How to pull the information that Resource Monitor (ResMon.exe) provides? - The troubleshooters and problem solvers... - Site Home - TechNet Blogs

Finally, here's a list of some programs that have possibilities (I prefer the first one personally). My concern here is that they may be too advanced for some to interpret:

Bandwidth monitor, bandwidth speed test, bandwidth and traffic monitoring tool for Windows
Download Microsoft Network Monitor 3.4 from Official Microsoft Download Center (Microsoft
Network Monitor)
internetconnectivitymonitor - Internet Connectivity Monitor periodically checks for a working internet connection, and generates a log. - Google Project Hosting
Net Uptime Monitor - the simple Internet Connection Monitor
AkinsTech » Blog Archive » Script to Monitor Your Internet Connection
Ping Tester - Visual Ping Test Tool
Connection Monitor - Monitor your internet connection
Ping Monitor - Free Network Ping Monitoring Tool
 
Ahhh! I see now, there's a bit of confusion here.
This is not an issue with my network - rather it's an issue of customers coming to us saying "I lose my internet connection at home after an hour or two".

Rather than charging them for a house call, we first diagnose problems at the shop.
We always preface it with "This won't diagnose any problem that you may be having at your home - but it should let us know if there's a problem that's not related to your home network setup"

If we have a logged test showing no drops at the shop - then the problem has to be at their end.
It's nicer than saying "Well, we watched the log files for this, that, and the other thing - and weren't able to see any problems in the shop".
This is more of a "convince the customer" than it is a technical troubleshooting procedure.
 
Yeah, you would need to install monitoring software on the clients machines that you, at a later date, then review. Not likely to happen.

This is a common complaint. I tell them to move closer to the wireless router. Minimize the number of floors, ceilings, and walls in between router and notebook. Change wireless channels. Move out of their crowded apartment complex! Move the router higher. Move the router lower. Turn the router 90°. Turn the notebook 90°. Get 11n. Change the notebook adapter to one with external antenna.

Or my best advice - go Ethernet! It's inherently more secure anyway.
 
Digerati, I was only kidding on the Fred popcorn thing. :lol:

Just my frank opinion, but I stick to the KISS rule, keep it simple and don't over analyze the basics. 90% of wireless connection problems are related to signal or interference. Considering it's UsaSma asking the Q, I assume he knows how to tell if the laptop has lost a Wan or wireless Lan connection. I would disagree with taking a laptop in and monitoring it Off the problematic network since you're eliminating a large portion of the customer's variables - their wireless network. Unless you really think they have a failing network card. Or do a quick remote session and install Xirrus or Inssider. Saves you the time of monitoring laptops at no charge.

UsaSma, I thought you were talking about an office environment. I say do the housecall. You can analyze their neighboring networks, channel selection, signal and router settings all at once, plus see what the physical variables are like brick walls or location of their router. There's no better way to convince a customer than to show them you've fixed the problem.

One example that comes to mind: One woman had a slow internet connection with lots of disconnects. She was accidentally connecting to a neighbors open network instead of her own.
 
We have a guy who does housecalls - he's booked at least 2 weeks out constantly.
Most people don't want to wait. Nor do they want to pay for the housecall - which is much more expensive than the shop work.

We offer what we can in the shop (we even do some simple diagnostics for free).

For example, it was the simple diagnostics that discovered a local problem with the DHCP Broadcast Flag in Vista ( Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers ) shortly after Vista was released to the public. We did the free fix for a number of customers until we found they were all coming from the same ISP. Then I got in touch with the ISP - and placed them in touch with Microsoft when I attended Summit the next week. They (the ISP) had to upgrade their hardware to become Vista compatible!

We get the "using the neighbor's wifi" problem a couple of times a month. Usually when we ask them how close they are to their router - and they give us that blank stare! :0)

I don't do housecalls (I don't have the patience) - but I did go to a friend's house last week. She said her connection would drop out every afternoon and then would come back around 7 pm. Found her tiny little AT&T ADSL modem sitting on the rug - no airflow to the bottom (and no connection to the internet). I blew on the bottom of the modem for a bit - and viola! Connectivity! Turns out that the sun would start shining in that window in the afternoon and would raise the temperature just enough to cause the modem to overheat.
 
What about using remote sessions, like Teamviewer? I know I'm more generous with my time on a remote session than a service call. IMO, the Vista/DHCP Broadcast flag issue is another example of why network troubleshooting needs to be done on the network. Connect that same Vista laptop to a newer router and it won't be an issue.

She said her connection would drop out every afternoon and then would come back around 7 pm. Found her tiny little AT&T ADSL modem sitting on the rug - no airflow to the bottom (and no connection to the internet). I blew on the bottom of the modem for a bit - and viola! Connectivity! Turns out that the sun would start shining in that window in the afternoon and would raise the temperature just enough to cause the modem to overheat.

Now that's a first!! :lol:
 
Digerati, I was only kidding on the Fred popcorn thing.
I thought so, but you never really know how folks are going to take something - for example, some get offended when you say something they already know as if everyone is already supposed to know their areas and levels of expertise. Oh well. Anyway, thanks for your understanding.

Found her tiny little AT&T ADSL modem sitting on the rug
lol That's why I insist on calling notebooks notebooks instead of laptops. Notebooks have no business sitting on people's laps.

That "housecall" reminds me of a company I supported that for 2 weeks had a total network shutdown every workday morning somewhere between 7:15 and 7:25. Suddenly, the server would go offline for no apparent reason, knocking everyone off, and then just as suddenly, the connection was restored and everything worked perfectly again until the next morning.

We ended up visiting the office every morning to watch the employees and morning routines to see if we could figure it out, and finally did - via a distraction by a, ummm... ...pretty young intern in a short skirt.

She, like many office workers where dress codes dictate nicer attire, would wear comfortable shoes to work, then change into "presentable" shoes once she got to work. While ogling... err, I mean while "troubleshooting through technical observation" one morning, she arrived at work (which started at 7:30 each day) sat down at her desk, then proceeded to pry off the heal of her walking shoes by hooking them behind her computer case, when suddenly, the network went down again. It seems her shoe exchange resulted in snagging or pressing on a tattered Ethernet cable which shorted out the connection and put the server into a fit. After a good laugh, totally embarrassed intern, new RJ-45 and repositioning of computer, no more network outages.
 
Digerati, I was only kidding on the Fred popcorn thing.
I thought so, but you never really know how folks are going to take something - for example, some get offended when you say something they already know as if everyone is already supposed to know their areas and levels of expertise. Oh well. Anyway, thanks for your understanding.

Oh, hell no! I don't take offense easily. My humor and sarcasm get missed sometimes :lol:. I have a habit of being direct with whatever my train of thought is and just cut to the chase. The "I resemble that remark" is a Garfield the cat reference.

Who'd have thought high heels were the cause of a network problem! :lolg:
 
Digerati:
...some get offended when you say something they already know as if everyone is already supposed to know their areas and levels of expertise...
Yep, I do that! Sorry! :(
 
@ John - No offense taken. I think it a bit "human nature" when already frustrated over something not working correctly and someone suggests something totally obvious. I've burned holes through people's heads with my eyes for doing that! But of course, facial expressions and body language are hard to express via the written word.

As I mentioned before, I believe forums are places for "open discussions" for all to participate, share and learn, and not one-on-one discussions between OP and helper. So I try to speak to all (reading now, and those seeking answers in the future) so those of all skill-sets can follow. But often that is seen as condescending. But I assure you and all, I don't mean to sound that way, and certainly don't mean to be offensive. So my apologies to my peers and colleagues if I appear that way.

FTR - I come to these forums to share what I know before that sieve of brain of mine forgets it all. And while I have supported IT hardware professionally for nearly 45 years and one thing I have learned is there is ALWAYS much more to learn - especially in rapidly advancing and evolving technologies. No one is, or can be an expert in all so the biggest advantage to these forums is they bring expertise from all areas of IT together. So the icing on the cake for me sharing what I know helping others (besides the occasional thanks) is I get the opportunity to learn from my fellow experts too.

I have a habit of being direct with whatever my train of thought is and just cut to the chase. The "I resemble that remark" is a Garfield the cat reference.
I hear you. I am the same way, perhaps due to being a grumpy ol' retired USAF Master Sergeant, or from being a long time electronics technician working in and training others in and around deadly voltages where there's no time or place for misunderstanding - or personal feelings getting in the way of safety, security, or mission.

And sadly, too many people forget computers are electronics - bound by the Laws of Physics and Electronic Principles - and that ANYTHING that plugs into the wall can kill.

********

As for TeamViewer and other remote programs, they are great, but their big gotcha is the remote computer must be working well enough to boot, establish a network connection, and then allow remote access. Not to mention, someone needs to setup remote access on the client end to begin with. Often not an easy task when the user is still hunting for that elusive "any" key.

We get the "using the neighbor's wifi" problem a couple of times a month.
I get those here too - and when that happens, they get a lecture from me about "fraud", "theft of services", felonies, jail and large fines for them and their neighbor who conspired to allow it.

And while I think ISPs charge outlandish prices for the services they provide, stealing is still stealing and outlandish prices don't justify stealing.
 
Thanks Fred! It looks like the best one I've seen! I'll forward it on to the powers that be!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top