Network Troubleshooting: Pt. 2 - Commands, logic, tools

This is a video that looks deeper into the understanding of networking and troubleshooting techniques.
Part 1 ( • Network Troubleshootin... ) - OSI and TCP/IP model and how networking works.
Part 2 (this video) - Commands, logic, tools
Part 3 ( • Network Troubleshootin... ) - Using Wireshark
Commands:
1) netstat -bona
2) nslookup [ip address/dns name]
3) ping [ip address/dns name]
4) tracert [ip address/dns name]
5) test-netconection -Computername [name] -port [port]
Music: www.bensound.com

[@Cevans3535]

Adding an additional command I've found immensely useful for quickly determining what process is running on a specific port (6161 in this example):
Get-Process -Id (Get-NetTCPConnection -LocalPort 6161).OwningProcess
Several times I've ran into situations where vPowerNFS service won't run because a program called SnareCore also has a default port of 6161 and that command is a real quick way to find out what's running on a specific port .

[@VirtualDenis]

That is a great comment, thank you. It definitely beats redirecting "netstat" output to a file and searching for it.

[@winfreak]

Thank you for this. I got stumped on a question before, and this answered it.

[@briwaff8620]

Thank you vrry much

[@Cevans3535]

Out of curiosity, what sketch pad do you use in your demonstrations for whiteboarding? I often find myself wanting to write quick notes on screenshots I take for cases, but writing with a mouse is horrible and slow. I picked up a cheap one from Amazon and while it's nice and proves that it's very useful for me, it's super basic and now I want to invest in a better one.

[@VirtualDenis]

@Chris Evans To be honest I didn't pick it. It was a present and it works well. It's a tabled called ONE by WACOM, and it fulfills its function. It's cheap as well :).