Rules for Determining Good vs. Bad Communications
Here is the general list of rules follow for determining good versus bad communications (As far as networking goes, at least!):
- Memorize a bunch of known ports for common TCP/IP applications. The next section in this tutorial will get you started.
- Learn how to use NETSTAT to see what's happening on your computer. Learn to use switches such as -a, -n, and -o to help you define what you're looking for.
- Take the time to learn the ports that normally run on your operating system. When you see a connection using ports you don't recognize, figure out the process running the connection using a utility such as Linux's ps or Process Explorer for Windows.
- Take the time to learn the processes that normally run on your operating system. Most operating systems have their own internal programs (such as Windows SVCHOST.EXE) that are normal and important processes.
- When you see a process you don't recognize, just enter the filename of the process in a Web search. There are hundreds of Web sites dedicated to researching mystery processes that will tell you what the process does.
- Get rid of bad processes.
In this tutorial:
- TCP/IP Applications
- Transport Layer Protocols
- TCP
- UDP
- ICMP
- IGMP
- The Power of Port Numbers
- Registered Ports
- Connection Status
- Rules for Determining Good vs. Bad Communications
- Common TCP/IP Applications
- HTTP
- Publishing Web Pages
- Web Servers and Web Clients
- Secure Sockets Layer and HTTPS
- Telnet
- Telnet Servers and Clients
- Configuring a Telnet Client
- Rlogin, RSH, and RCP
- SSH and the Death of Telnet
- SMTP, POP3, and IMAP4
- Alternatives to SMTP, POP3, and IMAP4
- E-mail Servers
- FTP
- Passive vs. Active FTP