In this presentation I take a few minutes to review some of the more common physical layer issues I run into. Please note that these same topics apply to support, installation and design. The key indirect point that I try to highlight is that some of these issues are not easily found sitting behind a keyboard and requires the analyst to get up and physically perform an inspection. Iknow, I know, what if that’s not practical and the network isn’t geographically close to you? No problem, simply have someone on site take some photos or a video and send it to you. Heck, now a video call with Skype or Google is practical. As I mention at the end of the video, I hope this helps you with your day to day job. Regards ... https://www.youtube.com/watch?v=1FBOalYXOUg
I always stress the importance of getting familiar with your tools. There is nothing more frustrating than trying to figure out a tool while troubleshooting. I usually follow up this point with my popular “tool calibration” points where I go over the simple point of understanding how your tool behaves.
I will cover a popular Wireshark configuration question that I cover in my training sessions, “interface configuration”. As you get more familiar with Wireshark, you might notice that there are interfaces displayed that you don’t need. In certain scenarios you might want to display only a specific interface.
Read the full article at
http://www.networkcomputing.com/author-bio.asp?author_id=2332
when its posted
...
https://www.youtube.com/watch?v=1wB3ku4TSLY
no software to install, download or buy!!
go to the network computing for the full article
Recovering A WIFI Key From Windows
Just want to start by echoing what I mentioned in the video. This video will not show you how to ‘crack’ or figure out a wireless password of unknown network. Instead this article will show you how to ‘retrieve’ a wireless password that is already configured in your Windows computer.
In past articles, I routinely mention that Network Technicians should be open to many things that may transcend the traditional networking space. I think every technician has been in a situation where they need to recover the password from their laptop or desktop during the worst scenarios.
I remember several occasions when I was working with someone and they were using a new laptop but didn’t remember the WPA2 password on their previous laptop. Then I show them this nifty trick or I guess the kids are calling it a ‘hack’ to retrieve their password from the other computer.
To recap the commands I used in the video:
................
...
https://www.youtube.com/watch?v=l5kpHY2W0Kc
Many of my clients tell me they appreciate my breadth of IT experience. For example, if they are complaining that an application is slow, it's helpful to understand the packets, network equipment configuration, cabling, computer operating systems, components, and applications/programming.
When I teach people how to use Wireshark, I include as much of the other I.T. disciplines as possible to ensure the attendees understand the FULL picture.
In this video, i echo those sentiments for a different kind of post.
...
https://www.youtube.com/watch?v=7bHYIXbEqsA
As a follow up from my first video someone asked me to show the Cable Test facility within the Netgear Switch, so here it is.
...
https://www.youtube.com/watch?v=FXXIplZkbS8
What could possibly go wrong? I plug the cable in, get a link light, ping something and if see no issues, I’m done, right? We’ve all done it 1,000,000 times right? I replaced two older switches with newer switches that support when gigabit speeds. As I said before, the lights are green and tested fine with a couple of pings.
The other day I decided to do the Speedtest between two computers that traversed both switches. To my surprise the speeds were less than 100 Mbps. So I thought, why not document the troubleshooting steps so I could help others might encounter the same issue.
I’ve said many times that you should baseline your network, your computer so you have some sort of reference for future testing. This was one example of that exact point. I knew that the computers could generate well over 100 megabits of traffic so when I saw sub 100 Mb speeds, I knew something was up.
The first step was to check the laptops network speed status and confirmed that they were both connected at 1 Gbps. Then I checked my switch/switch port status and noticed the connection between them was 100 Mbps.
This is where the fun starts, I went over to physically inspect the cabling and realized the cables were quite old. The jacket was deteriorating and was probably there for over 20 years. I simply pulled a new run between the switches, tested with my NetAlly LinkRunner G2 and quickly confirmed that the new cable did in fact support one gigabit speeds. I then tested the existing cable with my LinkRunner and confirmed that it was indeed running at 100 Mbps.
Some people skip this last step which drives me crazy. I’ve seen analysts replace a cable, check the speeds and say “Everything should be fine“ and then walk away. Please, take the extra few minutes to test and confirm that it “actually works as expected”. In some cases something else maybe ‘broke’ and cabling was simply one part of the performance problem.
Iperf - https://iperf.fr/
NetAlly LinkRunner G2 - https://www.netally.com/products/linkrunnerg2/
The Technology Firm – https://www.thetechfirm.com
...
https://www.youtube.com/watch?v=B5y5Uhr5ZE8
How To Convert A Wireshark Trace To Open Office Graph
The hardest technique to master with protocol analysis is spotting a pattern, or to be more precise a change in pattern. A break in pattern may explain a performance issue, disconnection or application anomaly.
Example it can be extremely difficult to look at a trace file and determine when throughput dropped or latency jumped up. Wireshark has a graphing facility but many times I want to do something specific or change the chart format.
I have shown analysts how to import a Wireshark trace file to Excel but get many request asking how to do this with an open source spreadsheet. In this article I chose Open Office’s Calc and walk you through how to import a trace file and create a
read the full article for free when its posted on Network Computing Blog: https://www.networkcomputing.com/author/tony-fortunato
...
https://www.youtube.com/watch?v=hbTg26Ruy0s
Here I am in all too familiar predicament; I have access to the configs of my AP, but I can't find any documentation as to what the wep or wpa key is.
I don't want to change the key since there are currently some webcams and printers on the wireless network.
So I took the config and googled Cisco Type 7 password decrypter and found quite a few places to go paste my key into, and viola, I got my key
Enjoy
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=jdGqGs_jxRc
When I first starting getting back into Pilot, I noticed that my Wireless and other adapters are labeled 'Microsoft'.
In this video I show how I went back to Wireshark to determine which adapter was my WiFi adapter.
...
https://www.youtube.com/watch?v=ez20DUs-9Xc
One technique that protocol analysts like to use is some sort of ring buffer or a way to capture many smaller files instead of one gigantic trace file. The scenario can range from long term captures to capturing from a busy network/device. Ether way you end up with a lot of data. For those of you who haven’t experienced opening a 1 GB trace file in a protocol analyzer, I recommend you have a lot of processing power, RAM, time and patience.
Let say you have twenty, 500 MB trace files and you want to put them together. Here’s a few things to keep in mind.
- You need to realize that technically there is a ‘gap in time’ of time where the analyzer had to stop, save and start again, resulting in potential lost packets. Depending on your specific circumstances this may not be an issue, but if you’re not sure, you should note the last packet time in each trace file, or add a comment in the last packet to easily identify any false positives that Wireshark may flag from missing packets. I cover this topic in a bit more detail in this article (http://tinyurl.com/y9lzbkow).
read the full article at
https://netbeez.net/blog/author/tony/
...
https://www.youtube.com/watch?v=Ae9cfa-EI04