Top 5 Windows Command Line Network Troubleshooting Tools

preview_player
Показать описание
My top 5 windows command line troubleshooting tools are:
1. ping
2. tracert
3. ipconfig
4. netstat
5. nslookup

Watch the video to see examples of how to use these tools!

Affiliate Links (I earn a small percentage of the sale if you use these links):

00:00 - Welcome
00:55 - ping
02:49 - tracert
04:08 - ipconfig
05:33 - netstat
06:30 - nslookup

Contact us for network consulting and best practices deployment today! We support all Grandstream, Synology, DrayTek, Obihai, Poly, Ubiquiti, MikroTik, Extreme, Palo Alto, and more!

Come back for the next video!
Twitter - @WillieHowe
TikTok - @whowe82

SUBSCRIBE! THUMBS-UP! Comment and Share!
Рекомендации по теме
Комментарии
Автор

if you install the sysinternals suite from the Microsoft store it adds whois to your path and I find that very useful, I also think that everyone should have iperf3 as well

mathesonstep
Автор

i am sure this list never end, i assum you know about mtr on linux or winmtr on windows

petmic
Автор

I willie question I’m using unifi network all my networks are isolated works fine I use 192.168 subnets from 10 to 60 third octet I have 2 wan connections straight to my UDM getting a public ip from both isp but I want to use static iPs for both isp connections can I do that and what pi range you recommend. Thanks much

Black-
Автор

An FQDN with UniFi networks would be handy

flatfoot
Автор

getmac /v (maybe combined with | clip). I work in ISP side (including managed network services) and sometimes we need to dig into customer side routers and/or firewalls to investigate connection issues. Easier way to get workstation's MAC address from end user :D

lordpake