like, share and subscribe to support my channel.. Troubleshooting WiFi can be challenging enough without adding a remote variable to it. There are times when I wish I could perform a remote Wifi survey. Some access points allow that feature, but rarely do I have access to the client’s access points, nor do I want access. You know, just in case something happens, I don’t want people thinking I was mucking around. A simple solution is to physically go over with a wireless test tool like netAlly’s Aircheck G3 (https://www.netally.com/products/aircheckg3/) , our smartphone, or your laptop. Things start to get tricky when the location is remote. That’s when you can rely on your access point, but be careful since some vendors will cut off all wireless clients while performing a wireless scan. Another option is to purchase wireless sensors that you can connect and perform a scan. And lastly, is to remote into someone’s laptop and check to see which wireless networks they hear. One trick I like to use, when possible, is to determine if they have a wifi printer at the remote site, web into it (they rarely have passwords) and run the printer test/diagnostic feature. Most Wifi printers will also provide wireless information including all the SSID’s it hears. ... https://www.youtube.com/watch?v=0oZ430nV0uc

So what do you do when you want to get an idea of your wireless performance and have no wireless tools around? In this example, I use ping to get an idea of wireless performance. In the ideal sceanrio, I would check the RF spectrum for interferers and proper channel planning, check the channel for utilization with some wireless tools. Unfortunately some times I do not have all my tools available or with me. Or even more realistically, I might want to walk a customer through some testing over email or the phone. What can cause the ping times to go all wonky and even result in dropped packets? Well here's a few: station and AP have issues hearing one another station can hear the AP fine, but the AP doesn't hear the station well wireless interferer channel utilization is high Hope this little tutorial helps. Linkedin Profile http://ca.linkedin.com/in/fortunat Lovemytool Blog: http://www.lovemytool.com/blog/tony-fortunato/ Youtube Channel: http://www.youtube.com/user/thetechfirm ... https://www.youtube.com/watch?v=jxjMuRLalOA

As a network analyst, you probably ping everyday as part of your job. We ping to: • check if a device is up, or reachable • resolve a host name • determine if there is a latency issue • identify packet loss • test IP Time To Live values • validate if certain packet sizes are able to traverse your network Over the past few years the protocol used by ping (ICMP) is being dropped, rerouted, spoofed and all sorts of other creative things in the name of security. read the rest when its posted at network computing http://tinyurl.com/h8orh26 ... https://www.youtube.com/watch?v=pNvBHe3U6YQ

tons of info at www.thetechfirm.com I am surprised that this exercise we do in class still proves to be helpful as well as quite popular. Are there are many utilities out there to help find rogue servers, but why bother when you already have Wireshark installed. When you get comfortable with this exercise you can save some steps by creating a capture filter for just DHCP packets, or better yet, just DHCP server packets. As always with protocol analysis, there are many ways to do this exercise and this is just my preference since it forces me and the attendees to review the DHCP process as they go through the packets. Rogue DHCP servers are becoming more common these days since a DHCP server can simply be a part of an application loaded on your computer. The introduction of tablets and smart phones that can provide hotspot support, are also DHCP servers. I even see more applications out there that turns your laptop into a WiFi hotspot so you can tether it to your tablet or smart phone. Don't worry, I haven't forgotten the classic example of an employee who wants wireless access in a nearby conference room and simply connects the LAN port of his wireless router at his desk and starts dishing out IP addresses. I like the added twist where I ask people to identify the legitimate DHCP based on paying attention to the story, not the packets. I can't tell you how many times I figure out a problem by going back to the user and having a conversation rather than going over the trace a million times. I think people forget that Wireshark and protocol analysis is an exercise in forensics and you need a story for context and to make sense of the packets. I have said many times that many times the answer comes from the story, not the packets. Getting things to work better - bit by bit- Linkedin Profile https://ca.linkedin.com/in/fortunat Youtube Channel: https://www.youtube.com/user/thetechfirm NetworkDataPedia Blog: https://www.networkdatapedia.com/blog/author/Tony-Fortunato Network Computing Blog: https://www.networkcomputing.com/author/tony-fortunato Linkedin Company URL: https://www.linkedin.com/company/the-tech-firm/ ... https://www.youtube.com/watch?v=uyvEa7Nh80A