Subtitles of the Movie

And welcome to chapter 2 of this VTC tutorial getting you ready for the 291 exam. In this chapter we discuss all things TCP/IP. We'll be implementing, managing and maintaining IP addressing on a Windows Server 2003, computer. What's this all about, well really it's, what it's all about is getting your computer to communicate on an IP network, probably 90 to 95, may be 99% of the networks you'll be working with today have to do with IP networks. In this first module we'll give you an overview of the TCP/IP protocol suite and the first thing we'll need to talk about in this overview, some of this background information is some of the benefits of TCP/IP. Why is it the default protocol on which Server 2003 as well as Windows 2000 runs. One it's scalable. Scalable is a kind of tech-ish term used in the computer industry but what it means is that simply it works in networks big and small. It can easily accommodate the network of 10 or 10 million. It's also routable. Routable means that it allows for the division of multiple logical networks, so that it reduces the overall amount of traffic that's on any one given network. And finally the third big benefit of TCP/IP is that it is open, you or I can write improvements of TCP/IP protocol suite. And it's actually as you see in just a second made up of many different protocols, besides just TCP and IP. These are open standards through a process called request for comments, RFCs, you can propose or people propose improvements to areas of TCP/IP. And therefore improvements of one area can be made without effecting the rest of the architecture. So that lets a world wide community constantly make improvements and suggest improvements to this networking protocol. Now I made mention a couple of the fact that TCP/IP is actually a suite and this suite maps to the OSI or the Open Systems Interconnect model. We have a 7 layer model you might have learned this back in Network Plus, I'm not going to go into the entire OSI model, but just know that it maps to that model which defines how computers communicate with each other. And the way that TCP/IP does this is through a four layer architecture, application layer protocols, transport layer protocols, Internet layer protocols, and network interface layer protocols. Here's what they look like if you were to represent it in a schematic type of thing, here's the TCP/IP model. Think of our computer or applications up here in the model and then applications access the network through the application layer. What kind of application layer protocols are there? FTP, SMTP, DNS, what they should also have up here is very common HTTP. For example there are lots of programs that can use the HTTP protocol to access the network. Internet Explorer, Netscape Navigator and so on, all utilize the HTTP protocol. At the transport layer live protocols such as, TCP, UDP, IGMP, ICMP. At the Internet layer here's IP and IPSEC, which actually helps secure IP packets. And then the network interface layer, you have protocols that define how the network media itself is accessed, and TCP/IP packets can be passed over Ethernet networks, token ring networks, ATM networks and frame relay networks. So this is how the TCP/IP suite maps to that OSI model in this four layer modular architecture. Now the purpose of this entire module is to configure TCP/IP on a server computer. Generally when you setup your computer, actually when you install the Server 2003 operating system, you're going to by default install TCP/IP, also by default you will setup TCP/IP to automatically get an IP address. But when you are setting up a computer, a server in your network that's going to serve as one of the cornerstones of network communication, probably you want to give it a static IP address. Now what does that mean the cornerstone of network communication? If your server is going to be accessed frequently in the role of a domain controller, a DNS server, DHCP server, a routing or remote access server. Here are all instances where a static address is, if not recommended, then absolutely necessary. For example DHCP domain controllers those require a static IP address. How will you configure your computer with a static IP address? Use the network applet through control panel. Here's how this is done. Open up control panel, start, settings, control panel, if your start menu looks like mine does here, it depends on which interface you're using, or you can right click on my network places if this is been added to your desktop and choose properties. Either way you will be launching the network connections applet. Right click on the connection where you're going to configure TCP/IP, choose properties and then from the properties pages you will see TCP/IP, and then you want to configure this protocols properties and then here you will enter in your static IP address. IP address subnet mask default gateway, this is what I call the big three of IP addressing, we'll talk about these 3 parameters of an IP address throughout this entire module. So this is where this is configured, it's not important right now to set a specific IP address, you can use pretty much whichever one you want to, it will effect how your computer is able to communicate. But for now I just want to show you where this is done from and set the table for the other modules to come throughout chapter 2.