first, what is a port number and what does it mean?

a ``port'' or protocol number is how the internet protocol multiplexes and de-multiplexes transport protocols. or in more everyday words, its how a computer interface through one internet protocol address, like your network interface card or your modulator/demodulator, can have and keep track of multiple ``conversations'' in various different ``languages'' with one or more computers.

so when you conduct a ``port scan'' of an ip address that is attached to an interface on a computer, what you are doing is asking that computer if it wants to talk to you in a specific language. if the remote computer wants to have a chat in ``language'' 80 or 21 or 23 it waits for someone to start the conversation in that language. or on that port.

now i must make a distinction. a computer can be set up to speak ``language 80'', or http, on any port number. so this is where my analogy breaks down, and i stop.

you can close a port by telling your computer to stop ``wanting to chat in that language', shutting down the program or service/daemon that is listening on that port. or, you could stick a big gigantic wall infront of the listening port. a wall made out of fire, with gun turrets. or not the turrets. but the point is that your computer is still listening on this port, but doesn;t know that nobody is talking to it because there is a firewall between it and everybody else.


and keep reading here, 'cause there is plenty of hardcore technical information that is as straight forward as this post is vague and confusing.

if your port starts running, you better run right out there after it to see where its going.

use the good ol'e netstat protocol to check for open ports, from the command prompt of course. or use third party programs like tcpview or active ports to see what is listening on a port - with the option to close it.

now i must go paralyse my body and allow my subconscious to digest all the wonderful events that have transpired over the last thirthy two hours