There are a ton of port numbers and applications on the exams so what I'm going to do in this episode
is just do a really quick rundown in particular a quick overview of the protocols that you're going
to be seen on the exam.
Port numbers and basic functionality this is going to be really really quick and we're going to be running
through all kinds of them so watch fast.
First is Hypertext Transfer Protocol or Google HTP using TZP port 80.
This is for unsecure Web sites.
Now we always say port 80 for each TTP but you could also see a lot of systems that use default ports
like for example 1880 or something like that.
But the actual default is always 80.
Next is secure a TTP or HTP as this is going to be using TZP port 1:43.
OK now let's talk about remote shells so the first one is going to be ancient old telnet telnet has
been around forever and it uses TCAP port 23 it is completely insecure if you're going to be using a
remote shell today you're going to be using secure shell or S-sh and that's on port 22 in fact.
We're going to see a lot more of S-sh because not only does it make a good shell it can also do tunneling
and other programs can run inside.
So what I want to talk about now is file transfer if we want to move a file from one computer to the
next we've got a lot of protocols in here.
The granddaddy of all is file transfer protocol or FTB.
It uses ports 20 and 21 although in some cases it will only use port 21.
The problem with FGP is it's completely insecure.
So there's a bunch of alternatives to regular FTB.
The first one is FGP over S-sh.
So basically we set up an S-sh connection instead of just using it as a remote shell.
We fire up an FPP program and run it through it.
So if we were doing FCP over S-sh we're using port 22.
Another option is FGP.
Yes.
Basically what they did is they took old FGP and they added the same SSL T.L. security that we have
with HTP.
Yes.
So it runs on FCP ports 20 and 21 just like regular FTB However it's completely secure.
Next is s FGP.
This is called S-sh file transfer protocol or secure firewall transfer protocol.
This sounds the same but it's a totally different protocol that FCP and has really great security and
it runs on port 22.
Next is called secure copy or SEP.
This is a very primitive file transfer over S-sh.
It's just a command line now with these other FGP.
You could actually make folders on the remote system and stuff like that.
This thing only moves files it's very primitive but it still works.
Next is trivial FTB TFT P is exactly as it sounds a very trivial form of FGP it only allows you to copy
files and it runs on UDP it's one of the very few protocols that runs on UDP and that's UDP port 69.
Now Windows systems also move a lot of files sharing folders and that type of stuff.
It doesn't use any of these FGP it's got its own Microsoft NET biased protocol.
So net bias originally ran on Portes 1:37 1:38 1:39.
However the more modern versions use something called SMB server message block and that runs on port
445.
Next let's talk about mail.
If you're sending mail you're going to be using the simple mail transfer protocol S-M T.P. it runs on
TCAP port 25.
And remember that sends our mail to the other folks.
Now to get your mail back you have a choice you can either use IMAP or you can use POP IMAP stands for
Internet message Access Protocol it uses port 1:43.
Pop is an older protocol but still quite popular and it uses port 110.
OK let's move into the world of what I'm just going to call eccentric.
These these are all over the place.
Number one the famous DNS domain name system.
This is what allows us to use names like W WW that total CENTCOM and things like that.
It runs on TCAP port 53 next is DHC C.P. or Dynamic Host Configuration Protocol.
DHC is all it allows us to have dynamic IP addresses instead of having to type in IP addresses and all
our computers.
It's going to use UDP port 67 and 68 next is simple network management protocol and overall protocol
we use for organizing our networks we can have as an MP have our routers talk to us and stuff like that.
It uses UDP ports 161 and 162 Elda app or lightweight directory access protocol uses port 389 last for
remote desktops.
This is used heavily by Windows for example is RTP RTP protocol which is the underpinning which allows
us to log into remote desktops uses TCAP port 33 89.
Now folks you're going to be seeing more of all of these protocols in different episodes so what I'm
only trying to do here is give you a nice organized pile so that you make sure you're comfortable with
a whole bunch of port numbers and a whole bunch of functionalities with a whole bunch of protocols.