In this video I take you through a troubleshooting scenario I encountered recently.
This is a great example where you don’t upgrade because you can, but you should upgrade when you have a specific issue that the upgrade will address. But even when you have to don’t just upgrade and walk away, you should monitor the upgraded device to ensure nothing else goes wrong.
You don’t want to fall into the “fix one, break two” scenario that can spiral out of control.
Enjoy
...
https://www.youtube.com/watch?v=pOkGXL_5buc
Disabling SNMP Packets from your Computer
I was onsite with a customer doing some customized training when they noted that ever since they installed a new Firewall, there are tons of log entries regarding SNMP. They explained that they knew what SNMP was used for; network monitoring and management. They went on to mention that the IP's in the logs are basically everyone in the company they are at a loss as to what could be causing this.
In this video I show you what we did to get to the bottom of this using a protocol analyzer (Wireshark). The important part of this methodology is that I followed my steps of; identifying the problem, making one change, and re-measuring for its impact. This is so critical since some of the online suggestions did not help me.
Regards,
...
https://www.youtube.com/watch?v=6LCqO5CdkAY
thought i would see if can really block RF signals, so i used my NetAlly Aircheck to monitor my cell phone's wifi and it actually worked.
the only criticsim i would have is that i wished the bag had a loop or carbiner.
...
https://www.youtube.com/watch?v=NBK04TIbS_o
I got a few emails from people checking up on me to be sure that all is well.
I'm doing just fine, just busy working on the coreitpros.com material.
Here's a quick one showing you how to create a display filter, mark, and then save those marked packets.
Enjoy
...
https://www.youtube.com/watch?v=fI4-MsW6Sqw
Before I get into the tshark command syntax and other details, I want to chat about why you want to use tshark or any command lint tool. Simply put, working from the command line allows a tremendous amount of consistency and flexibility.
Consistency
When you try to have someone perform your capture using the Wireshark GUI, there are many opportunities for errors as well as just being very time consuming. When you have the command line syntax figured out you can put it in an email, batch file or document ensuring the client is doing exactly what you wanted. The added bonus is that working from, the command line is usually more responsive that remotely controlling a GUI over possibly slow links.
Flexibility
As I mentioned earlier, using the command line allows you to put the command in a batch file or document. This is incredibly useful if you wanted to schedule a capture, or if you wanted to configure a computer to automatically start capturing when it’s turned on. Other examples would be setting a desktop shortcut for the client to start
...
https://www.youtube.com/watch?v=lkiG231lDHQ
So what do you do if you turn on a switch and don't remember the password..
Watch this
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=akBt6LhZTRM
www,thetechfirm.com
Troubleshooting At The Physical Level
Thought it would be a good idea to start a series using the NetworkDataPedia’s theme of ‘knowing your network. Let’s start at layer 1 or the hardware layer.
Unfortunately there is so much that can go wrong at this layer but you will still have a network connection and life will seem fine. I say unfortunately because if the problems would cause an complete outage, you would be forced to address it.
I find that many physical level issues are grouped into a few categories:
Installation and Support
I have many issues caused by installation, support shortcuts. Heres a quick list of what I’ve seen; CAT5 cable wrapped around a welder, RJ45 couplers to combine 2 short cables, unsupported bundle of cables pulling the RJ45 connectors out from the switch, overheating modem in a plastic bag, dirty fibre optic cables and ports.
read the free full article at the following link when its published
Youtube Channel: https://www.youtube.com/user/thetechfirm
https://www.thetechfirm.com
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=W4-A2BcxkmI
this is one of a 5 part series.. this is an actual class that i put together and thought i would put it out there.
Pleased DO NOT BOTHER WITH ANY OF THE LABS OR EXERCISES as I will not be providing any of the associated files.
...
https://www.youtube.com/watch?v=7CGGEOFwqw8
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