Discover how servers utilize sockets to facilitate TCP and UDP connections. Observe how netstat is utilized on windows and linux servers to determine the state of sockets along with applications utilizing them. Explore some common ways port conflicts manifest, and learn how to detect and mitigate them.
- View Offline
- [Narrator] Server troubleshooting can be a quagmire.…The sheer amount of possible problems can seem endless.…Thankfully there are some solid tools…that allow for quick resolution.…When connecting to a service…on a server like HTTP or Telnet,…I'm connecting via a specific port and protocol…dedicated for that application.…This bidirectional connection is often referred to…as a socket.…When a server wants to accept HTTP connections,…it will listen on TCP port 80.…
Only a single application can listen on a given protocol…and port number at a single time.…When multiple applications want to use the same socket,…it is called a port conflict.…Some applications will check for an open port,…and these will generally warn me of the port conflict.…Some other applications will simply fail…with a generic error.…The best tool to determine if a port is in use…is Netstat.…Luckily, this command is available for both Windows…and Linux, though the syntax is slightly different for each.…
On Windows, my go to command line parameters…
Even if you're rusty on your OSI model knowledge, this course is invaluable if you're having trouble with your network. It offers a clear, practical troubleshooting guide to narrowing down and solving most problems related to network connectivity.
- Troubleshooting the physical layer: POTS, Ethernet, and more
- Troubleshooting the data link layer
- Troubleshooting the network layer
- Troubleshooting the transport layer
- Troubleshooting Wi-Fi
- Troubleshooting proactively