-: Ports and protocols. 2 2
Now I'm going to apologize in advance for two reasons. 3 3
First, this is a really long lecture. 4 4
And second, you're probably going to need to go through it 5 5
two or three times because the information in this lesson 6 6
is going to be so important to you 7 7
because it makes up a good percentage of your test. 8 8
In fact, I'd probably say five to 10% of your test questions 9 9
could come from this lesson alone. 10 10
And that's why it's really important for you 11 11
to learn it thoroughly. 12 12
If there is any of these lessons or videos 13 13
that you're going to to start memorizing 14 14
this is going to be the one for you. 15 15
Now I'm going to go through each of the different 16 16
ports and protocols that you need to be aware of. 17 17
And for each one of those, 18 18
I'm going to give you a specified port number 19 19
that's used for that port and protocol. 20 20
Now for the exam, you may get an easy question like 21 21
what port is used for HTTP, 22 22
and you need to select the right port number, 23 23
in this case 80 from the list of choices. 24 24
But there are many other questions 25 25
that are going to rely upon the information from this video 26 26
that aren't going to be as nearly as cleanly 27 27
or easily or directly as that. 28 28
I have seen a lot of questions on the exam 29 29
that actually ask things that rely on your knowledge 30 30
from this lesson. 31 31
And they're not going to be direct port numbers like that. 32 32
For example, the exam might ask you a question like 33 33
one of your users is complaining that they can't connect 34 34
to the share drive inside your Windows-based office network. 35 35
You believe that their host based firewall 36 36
might be blocking this service. 37 37
What port should you verify as open inside the firewall? 38 38
Now, to answer this question, 39 39
you need to figure out a few things. 40 40
First, what service is being used to allow file transfer 41 41
and file sharing inside of a Windows based network? 42 42
The answer to that is SMB the Server Message Block Protocol. 43 43
Now, once you figured that out, 44 44
you then have to answer the question of what port 45 45
is used by SMB. 46 46
And in this case, it's port 445. 47 47
So as we get started going through this lesson, 48 48
I'm going to tell you the protocol, 49 49
the port number and what it's going to be used for. 50 50
These are the three key pieces of information 51 51
that you need to memorize in order to be successful 52 52
on the network plus exam. 53 53
And honestly, for any other future CompTIA exams 54 54
you might take like the Security+, CySA+, 55 55
PenTest+ or CASP+. 56 56
All right, so let's get started covering 57 57
all 28 protocols and ports that you have to know. 58 58
First, we have the File Transfer Protocol or FTP. 59 59
FTP is going to operate on ports 20 and 21. 60 60
FTP is used to transfer files between a client and a server 61 61
on a computer network. 62 62
This is an unsecured method though, 63 63
and the data's going to be transmitted in the clear, 64 64
which means there is no encryption. 65 65
So it's really not safe for us anymore to use FTP, 66 66
especially for doing so over the internet 67 67
if we want to be transferring any sensitive files. 68 68
Remember with FTP, there is no encryption. 69 69
So the files can be read by anyone on the network 70 70
who may be eavesdropping into your conversation 71 71
as you send it over port 20 and 21. 72 72
In summary File Transfer Protocol or FTP 73 73
runs over ports 20 and 21 74 74
and it provides insecure file transfers. 75 75
The next one we have is Secure Shell or SSH. 76 76
This is going to operate on port 22. 77 77
So what does SSH do? 78 78
Well, it allows you to remotely take control 79 79
of another computer using a command shell. 80 80
It's best known for its use as remote logging capability 81 81
and it is a cryptographic network protocol. 82 82
This means that it uses encryption 83 83
and it's safe to use even over an unsecured network 84 84
like the internet and it's safe from prying eyes. 85 85
For example, 86 86
if I wanted to change the configuration of my web server, 87 87
I can actually log in through SSH 88 88
from my house in Puerto Rico, all the way to my file server, 89 89
sitting in California, all the way over the internet 90 90
using SSH. 91 91
And I can be certain that nobody's going to be able to see 92 92
what I'm doing because it's secure with encryption 93 93
on both ends of that connection if I'm using Secure Shell. 94 94
So in summary, Secure Shell or SSH runs over port 22 95 95
and it provides secure remote control 96 96
of another machine using a text-based environment. 97 97
The next one we have is 98 98
Secure File Transfer Protocol or SFTP. 99 99
And this is another way to do file transfer 100 100
but this time we're going to do it securely 101 101
by using encryption. 102 102
SFTP operates on port 22, 103 103
the exact same port that we use for SSH or Secure Shell, 104 104
because in all honesty, all we're doing here 105 105
is tunneling the FTP protocol through SSH 106 106
to give us a secure method of doing that file transfer. 107 107
In summary, the Secure File Transfer Protocol or SFTP 108 108
is going to run over port 22 109 109
and provide us with secure file transfer. 110 110
Next, we have Telnet 111 111
and it works a lot like the way that SSH does. 112 112
In fact, Telnet came out many years before SSH. 113 113
The problem with Telnet though, is that it's insecure. 114 114
Telnet is used to provide bi-directional interactive 115 115
text oriented communication 116 116
using virtual terminal connections. 117 117
Now that is a whole lot of words to simply say 118 118
that Telnet provides us with remote access 119 119
via the Command Prompt. 120 120
The problem is that we're sending everything in the clear 121 121
with no encryption, 122 122
which means that we're going to be sending all this data 123 123
and somebody can see what we're doing, 124 124
including if we send our usernames and passwords. 125 125
Just like FTP, Telnet is considered insecure 126 126
and you should never use Telnet over an insecure network 127 127
like the internet, 128 128
because people can read your username, your password, 129 129
and every other command that you type in. 130 130
Really do not do this 131 131
or you will become the victim of a data breach. 132 132
So in summary, Telnet is going to run over port 23 133 133
and it provides you with insecure remote control 134 134
of another machine using a text-based environment. 135 135
Next, we have the Simple Mail Transfer Protocol or SMTP. 136 136
This operates on port 25. 137 137
It is the internet standard for sending electronic messages 138 138
or email. 139 139
It was founded back with the RFC or Request For Comments 821 140 140
all the way back in 1982. 141 141
Then in 2008, the current version came out, 142 142
which uses RFC5321. 143 143
So do you need to know these RFCs? 144 144
No, no, you don't. 145 145
The only reason I'm including them here 146 146
is to give you an idea of just how long 147 147
we've been using SMTP to send our emails 148 148
all the way back from 1982 to 2008, 149 149
all the way now to the present. 150 150
In summary, when you hear about SMTP, 151 151
remember it runs over port 25 152 152
and provides the ability to send emails over your network. 153 153
Next, we have DNS or the Domain Name System, 154 154
which uses port 53. 155 155
Now DNS is what gives us a hierarchal decentralized 156 156
naming system for our computers, our services, 157 157
and other resources that are connected 158 158
to the private networks and the internet. 159 159
This is going to convert our domain names to IP addresses 160 160
and our IP addresses to domain names. 161 161
For example, if you go to diontraining.com, 162 162
that's going to be a lot easier for you to remember 163 163
than a long IP address, like 66.12.54.85. 164 164
This is because we, as humans 165 165
are better at thinking about names and words 166 166
than we are with numbers. 167 167
So it's easier for us to remember diontraining.com 168 168
or comptia.org or something like that, right? 169 169
So to make the computers and the internet 170 170
easier for people to use, 171 171
we're going to rely on domain names 172 172
instead of their IP addresses. 173 173
And DNS allows us to do that. 174 174
Now, DNS is really important in networking. 175 175
So we're going to do a separate lesson dedicated all to DNS 176 176
so you can understand how it really works in the real world. 177 177
For now, I just want you to remember 178 178
that DNS runs over port 53 179 179
and it converts domain names to IP addresses 180 180
and IP addresses back to domain names. 181 181
The next one we have is DHCP 182 182
or the Dynamic Host Configuration Protocol. 183 183
And this operates over port 67 and 68. 184 184
Now DHCP servers are used 185 185
to automatically assign IP addresses 186 186
and other network configuration parameters 187 187
to your network clients to help simplify the administration 188 188
of our networks. 189 189
This allows your computers to get IP addresses 190 190
and network perimeters automatically, 191 191
which is really, really awesome 192 192
and makes your life as a network administrator 193 193
much, much easier, especially in large networks. 194 194
Again, DHCP is a really important concept. 195 195
So we're going to spend an entire lesson 196 196
talking all about the methods that it uses 197 197
to go through the discover, the offer, 198 198
the requests and the acknowledgement process 199 199
to give you an address using DHCP. 200 200
For now, though, I just want you to remember that DHCP 201 201
runs over port 67 and 68, 202 202
and it automatically is going to give you 203 203
the network parameters to your clients, 204 204
such as their assigned IP address, their subnet mask, 205 205
the default gateway, and the DNS server 206 206
that they should be using. 207 207
Next, we have TFTP or Trivial File Transfer Protocol. 208 208
This is going to operate over port 69. 209 209
This is going to transmit files in both directions 210 210
of a client server application. 211 211
Now TFTP doesn't provide any authentication 212 212
or directory visibility though. 213 213
Basically TFTP is a stripped down version of FTP, 214 214
which is why we call it a Trivial File Transfer Protocol. 215 215
So where might we use this? 216 216
Well, usually TFTP is going to be used 217 217
by network administrators 218 218
when they send configuration files 219 219
or they request configuration files from a router or switch. 220 220
Also, it can be used for booting up an operating system 221 221
from a network file server 222 222
when you're using a PXE environment. 223 223
Now, in summary, I want you to remember 224 224
that Trivial File Transfer or TFTP is going to run over port 69 225 225
and it's used as a lightweight file transfer method 226 226
for sending configuration files 227 227
or network booting of an operating system. 228 228
Next, we have the Hypertext Transfer Protocol or HTTP, 229 229
which operates over port 80. 230 230
This is the foundation of data communication 231 231
for the worldwide web. 232 232
HTTP is designed for collaborative 233 233
and hypermedia presentations 234 234
across many different types of devices. 235 235
If you're watching this video, 236 236
you've already used either HTTP 237 237
or it's secure version HTTPS 238 238
to access this website.. 239 239
HTTP is the unsecure version, 240 240
whereas HTTPS is going to use encryption 241 241
and we'll talk later about that in this video. 242 242
In summary, when you hear HTTP, 243 243
I want you to remember that it operates over 80, 244 244
and it's used for insecure web browsing. 245 245
The next one we have is Post Office Protocol version three, 246 246
or POP3. 247 247
POP3 is going to use port 110, 248 248
and it's used by local email clients to retrieve email 249 249
from a remote server over a TCP IP connection. 250 250
POP3 is only used for inbound or incoming email. 251 251
POP3 also uses a store and forward method of communication. 252 252
So if somebody sends you an email, 253 253
it will go to your email server and it will wait there 254 254
until you're ready to receive it. 255 255
When you're ready to receive it, 256 256
your email client will connect to your server over POP3 257 257
using port 110 and download those emails. 258 258
Then your email client will either tell the server 259 259
to keep a copy of that on the server 260 260
or it'll tell it to delete the email from the server. 261 261
Either way POP3 is going to be able to handle this for you. 262 262
POP3 is this older method of receiving emails, 263 263
but it is still heavily used by many people today. 264 264
In summary, I want you to remember 265 265
that Post Office Protocol version three or POP3 266 266
runs over port 110, 267 267
and it's used for receiving incoming emails. 268 268
Next, we have Network Time Protocol or NTP. 269 269
NTP is going to operate on port 123. 270 270
Now I really like this port number 271 271
because it's pretty easy for me to remember. 272 272
I tend to think of it like this, 273 273
I'm counting up 123 274 274
almost like I'm counting the seconds of time 275 275
as it continues onward over and over again. 276 276
That's how I remember NTP. 277 277
Now the Network Time Protocol 278 278
is going to provide your system with a clock synchronization 279 279
between different computer systems 280 280
over packet switched variable latency data networks. 281 281
NTP is actually a really old protocol. 282 282
It was created all the way back in 1985. 283 283
And it's one of the older internet protocols 284 284
that we still use commonly today. 285 285
NTP is useful to be able to sync up our time and dates 286 286
across all of our network devices. 287 287
You may not realize it, 288 288
but your computer is using NTP all the time 289 289
to ensure that its internal clock is accurate. 290 290
So remember NTP or Network Time Protocol 291 291
is going to operate over port 123, 292 292
and it's used to keep accurate time for our clients 293 293
on our network. 294 294
Next, we have NetBIOS 295 295
or the Network Basic Input/Output System 296 296
which operates over port 139. 297 297
NetBIOS provides a service for allowing applications 298 298
on a separate computer 299 299
to communicate over a local area network 300 300
to share files and printers. 301 301
If you use file or printer sharing in a Windows network, 302 302
your port 139 is probably open 303 303
because you're using NetBIOS. 304 304
In summary, NetBIOS operates over port 139 305 305
and it's used for file or printer sharing 306 306
in a Windows network. 307 307
Next, we have the Internet Mail Application Protocol 308 308
or IMAP and it's going to operate over port 143. 309 309
Now IMAP provides email clients with the ability 310 310
to retrieve email messages from a mail server 311 311
over a TCP IP connection. 312 312
IMAP is a newer type of email retrieval protocol, 313 313
and it was designed to improve some things 314 314
over the older POP3 methods. 315 315
Basically, IMAP allows the end user 316 316
to view and manipulate the messages 317 317
as if they were stored locally on their machine 318 318
even though they're still sitting on the server. 319 319
This is important because with POP3 320 320
when I logged in from my laptop or my tablet, 321 321
I would show unread on one of those and read on the other 322 322
because the email server didn't keep track 323 323
of the state of each message as I read it or didn't read it. 324 324
But with IMAP the server 325 325
keeps all of these things synchronized 326 326
across all of my devices. 327 327
This makes IMAP much better for modern email communications, 328 328
because most of us have a laptop, a desktop, a smartphone, 329 329
and maybe even a tablet too. 330 330
In summary, remember that IMAP operates over port 143, 331 331
and it's a newer method of retrieving incoming emails, 332 332
which improves upon our older POP3 method. 333 333
Next, we have the Simple Network Management Protocol 334 334
or SNMP. 335 335
This is going to operate on ports 161 and 162. 336 336
SNMP is going to provide you with the ability 337 337
to collect and organize information 338 338
about all the managed devices on an IP network. 339 339
This includes things like routers, switches, VoIP phones 340 340
and other devices. 341 341
SNMP can modify the information 342 342
by changing the devices behavior 343 343
and it can provide you with the ability 344 344
to monitor the uptime, downtime 345 345
and other states of any given device. 346 346
We're going to talk more about SNMP in another video, 347 347
because again, it's really important 348 348
in conducting proper network management. 349 349
For now, I want you to remember that SNMP 350 350
operates over ports 161 and 162, 351 351
and SNMP is used to collect data about network devices 352 352
and monitor their status. 353 353
Next we have LDAP 354 354
or the Lightweight Directory Access Protocol. 355 355
LDAP or LDAP is going to operate on port 389 356 356
and it's an open vendor neutral industry standard 357 357
for accessing and maintaining 358 358
distributed directory information services. 359 359
Now, I want you to think about LDAP 360 360
like Active Directory in Windows 361 361
but it's not just limited to the Windows networks. 362 362
Instead, Active Directory is a proprietary version of LDAP 363 363
and for this reason LDAP and Active Directory 364 364
both use port 389 to communicate. 365 365
So what exactly does LDAP do? 366 366
Well, it's a directory service. 367 367
So if you're in your email client 368 368
like Microsoft Outlook at work, 369 369
and you try to look up somebody's name in the address book, 370 370
you're actually using LDAP to do that. 371 371
In addition to this LDAP can store information 372 372
about your users and their groups. 373 373
In summary, LDAP is going to operate over port 389, 374 374
and it's used to provide directory services to your network. 375 375
Next, we have secure web browsing, 376 376
which is Hypertext Transfer Protocol Secure or HTTPS. 377 377
HTTPS is going to operate over port 443. 378 378
And essentially it's going to do everything 379 379
that Hypertext Transfer Protocol, 380 380
the unsecure version HTTP did, 381 381
except it's also going to do this over an encrypted tunnel. 382 382
This tunnel can either use a Secure Sockets Layer, SSL 383 383
or Transport Layer Security TLS to operate. 384 384
Now, TLS is the newer and more secure method 385 385
whereas SSL is the older and less secure method. 386 386
By using a TLS or SSL tunnel with HTTP 387 387
you now have an end-to-end encrypted tunnel 388 388
between your client and the web server. 389 389
And this allows you to do things like e-commerce, 390 390
logging into your bank or going into any other website, 391 391
much more securely. 392 392
In summary, HTTPS is going to operate over port 443, 393 393
and it's used as a secure and encrypted version 394 394
of web browsing. 395 395
Next, we have SMB or the Server Message Block Protocol. 396 396
This is going to operate over port 445. 397 397
Now the Server Message Block Protocol 398 398
is going to provide your system with shared access 399 399
to files, printers, and other types of communication 400 400
between different devices on your network. 401 401
It operates a lot of times with NetBIOS as well. 402 402
NetBIOS is going to be used to do the authentication 403 403
over port 139, and then Server Message Block 404 404
will handle the actual passing out of those files 405 405
and printer services to you by handing over that data. 406 406
In summary, SMB is going to operate over port 445 407 407
and it's used for Windows file and printer sharing services 408 408
on a Windows network. 409 409
Next, we have Syslog or the System Logging Protocol. 410 410
This is going to operate a report 514. 411 411
Syslog is used to send system log or event messages 412 412
to a specified server on your network 413 413
known as a Syslog Server. 414 414
Basically, we're going to use a Syslog Server 415 415
to collect data from various device logs 416 416
across our network and consolidate them all 417 417
into a single machine for monitoring and review 418 418
by our network administrators and cybersecurity analysts. 419 419
In summary, remember that Syslog operates over port 514, 420 420
and it's used to send logging data 421 421
back to a centralized server. 422 422
Next, we have SMTP TLS or the Simple Mail Transfer Protocol 423 423
Transport Layer Security. 424 424
This is the encrypted version of SMTP 425 425
and then operates over port 587. 426 426
SMTP TLS is our secure version of our sending mail service. 427 427
And it's going to make sure that we can send emails 428 428
over the internet and we can do it by using encryption. 429 429
It's exactly the same service as SMTP. 430 430
The only difference is that 431 431
we take that normal SMTP traffic, 432 432
that operate over port 25 and we add an encryption. 433 433
And so now we can send it over port 587. 434 434
This will make sure that we have security 435 435
with this end-to-end encrypted TLS tunnel. 436 436
So remember, SMTP TLS is going to operate over port 587 437 437
and it's a secure and encrypted way 438 438
for us to send our emails. 439 439
Next, we have the secure version of LDAP 440 440
known as LDAPS which is LDAP Secure. 441 441
Just like most things 442 442
LDAP has both a secure and insecure version. 443 443
When we're using LDAP over 389 that's insecure. 444 444
But when we go ahead and do it securely, 445 445
we're going to run that with encryption over port 636. 446 446
Again, it's going to operate just like LDAP did 447 447
just like Active Directory and all of those things. 448 448
The only big difference here 449 449
is that we're now adding this encrypted tunnel 450 450
over SSL or TLS to make it more secure. 451 451
In summary, LDAPS is going to operate over port 636 452 452
and provide secure directory services. 453 453
Next, we have IMAP over SSL 454 454
or the Internet Message Access Protocol over SSL. 455 455
This is going to operate over port 993. 456 456
IMAP over SSL is our secure version of our IMAP service. 457 457
Earlier we talked about how IMAP was used to receive emails 458 458
and we can maintain their read or unread status. 459 459
And that's exactly what IMAP SSL is going to do. 460 460
It's exactly the same service 461 461
but again, the difference here is we took our normal IMAP 462 462
that operate over port 143 in plain text 463 463
and we now put it over an encrypted SSL tunnel, 464 464
which then added this into port 993. 465 465
Now in summary, IMAP over SSL is going to operate 466 466
over port 993, 467 467
and it's a secure and encrypted way 468 468
for us to receive emails. 469 469
Next, we have the secure version of POP3 470 470
known as Post Office Protocol version three over SSL 471 471
or PPOP3 over SSL. 472 472
This is going to operate over port 995. 473 473
Now when we have POP3 over SSL, 474 474
this is the secure version of our POP3 service. 475 475
Again, we talked about OP3 earlier as an older protocol 476 476
used to receive emails, 477 477
but we couldn't maintain their read or unread states. 478 478
Well with POP3 over SSL, it does the exact same thing. 479 479
Again, the only difference 480 480
is we are now adding this encrypted tunnel 481 481
so we have this text in a secure encrypted format 482 482
and we run it over that tunnel on port 995. 483 483
So remember POP3 over SSL operates over port 995, 484 484
and it's a secure and encrypted way to receive our emails. 485 485
Next, we have the SQL Server Protocol 486 486
or Structured Query Language Server Protocol. 487 487
This is also known as SQL. 488 488
It operates over port 1433. 489 489
Now SQL is a language that's used to communicate 490 490
with a database server. 491 491
Often in your networks you're going to find clients 492 492
that need to communicate with a database server. 493 493
If that server is a Microsoft SQL Server, 494 494
then your client is going to communicate to that server 495 495
over port 1433 to talk to the database engine. 496 496
In summary, remember the SQL server 497 497
will communicate over port 1433 498 498
and it's used for communication from a client 499 499
to a database engine. 500 500
Next, we have the SQLnet Protocol, 501 501
which operates over port 1521. 502 502
SQLnet is used by the Oracle version of an SQL server. 503 503
And it provides a lot of the same functions 504 504
as Microsoft SQL Server that we just discussed. 505 505
If you're running Oracle databases in your network, 506 506
you're going to be using port 1521 507 507
instead of port 1433. 508 508
In summary, remember that SQLnet is for Oracle 509 509
and it communicates over 1521 as its port 510 510
and it's used to go from a client to an Oracle database. 511 511
Next, we have another type of SQL protocol. 512 512
This one is known as MySQL 513 513
and it operates a report 3306. 514 514
MySQL is an open source version of SQL 515 515
that is heavily used by the world 516 516
because of all these different clients 517 517
can communicate with SQL servers 518 518
using this open source protocol. 519 519
If you're going to be using a MySQL server, 520 520
you're going to be using the MySQL protocol 521 521
to communicate to them. 522 522
So remember, the MySQL protocol 523 523
is going to communicate over port 3306 524 524
and it's used for communication from a client 525 525
to the MySQL database engine. 526 526
Next, we have the Remote Desktop Protocol or RDP. 527 527
Now RDP is going to operate over port 3389. 528 528
So be careful here, 529 529
notice 3389 it looks a whole lot like 389 530 530
that we covered with LDAP 531 531
and students will commonly mix up these two port numbers 532 532
on the exam because of this exam writers 533 533
absolutely love to include both 389 and 3389 534 534
as answer choices whenever you get a question about 535 535
RDP, LDAP or LDAPS, so be careful here. 536 536
Now the Remote Desktop Protocol is a proprietary protocol 537 537
that was developed by Microsoft, 538 538
and it allows users to control their computers remotely 539 539
using a graphical interface. 540 540
Now RDP is kind of similar to SSH and Telnet 541 541
in that it provides us with the ability 542 542
to remotely control another computer or server, 543 543
but it gives us this additional benefit 544 544
of being able to actually see what we're doing 545 545
by using a graphical user interface. 546 546
It gives us full control over it 547 547
with our mouse and our keyboard 548 548
as if we were sitting down 549 549
in front of that other machine locally. 550 550
So when we had SSH and Telnet, 551 551
we can only control computers using text-based commands 552 552
over a command line or a shell. 553 553
But with RDP, we have a full graphical user interface. 554 554
As you can see, I have an Android phone 555 555
that's actually using RDP through a web browser, 556 556
and it's able to see this Windows machine 557 557
and remotely control it. 558 558
This allows users with RDP software 559 559
to be able to access their computers from anywhere they are, 560 560
whether they're doing so over the internet 561 561
or inside your network, 562 562
as long as you're using port 3389. 563 563
So in summary, remember that RDP operates over port 3389 564 564
and it provides you with graphical remote control 565 565
of another client or a server. 566 566
Next, we have the Session Initiation Protocol or SIP. 567 567
SIP is going to operate over ports 5060 and 5061. 568 568
SIP is going to be used to provide signaling 569 569
and controlling media communication sessions 570 570
for different applications. 571 571
This is commonly used in VoIP, video calls, voice calls, 572 572
as well as an instant messaging. 573 573
When you're using something like VoIP or Skype or FaceTime 574 574
or something like that you're probably going to be using SIP 575 575
to initiate that communication. 576 576
So remember, SIP operates over reports 5060 and 5061 577 577
and it's used to initiate VoIP and video calls. 578 578
All right, that was a ton of information. 579 579
Like I said, this is a really important video 580 580
with a lot of dense material that you have to master. 581 581
You're going to need to remember the protocol, the port, 582 582
and what it's used for, 583 583
for each of the 28 things 584 584
that we just covered in this lesson. 585 585
I promise you watching this video once 586 586
is not going to be enough 587 587
for getting all that into your head and having it memorized. 588 588
So you need to go back and re watch this video 589 589
a few more times to ensure you've memorize 590 590
all 28 of these protocols and ports. 591 591
I also recommend that you create flashcards 592 592
and quiz yourself on these ports and protocols. 593 593
On the one side, you should write the port number 594 594
and on the other side of the card 595 595
I want you to write the protocol. 596 596
This way you can start testing yourself as you go. 597 597
There really is no easy way to memorize 598 598
a lot of these unfortunately, 599 599
it's just something you have to spend time with 600 600
and get it into your memory and then quiz yourself often 601 601
to ensure you don't forget them before test day. 602 602
If you can remember the port, the protocol 603 603
and what it's going to be used for, 604 604
for each of these 28 items, 605 605
you're going to do well on these questions come test day.