Lesson 1: Overview of TCP/IP

• The TCP/IP Protocol Suite

• Protocols in the TCP/IP Suite
• TCP/IP Applications
• What Is a Socket?
The TCP/IP Protocol Suite

TCP/IP Protocol Suite

HTTP FTP SMTP

Application
DNS POP3 SNMP

Transport TCP UDP

ARP IGMP
Internet IPv4 ICMP
IPv6

Network Mobile
Ethernet Wi-Fi broadband
Interface
Protocols in the TCP/IP Suite

OSI TCP/IP TCP/IP Protocol Suite

Application HTTP DNS

Presentation Application FTP POP3
Session SMTP SNMP

Transport Transport TCP UDP

Network Internet ARP

IPv4
IGMP
ICMP IPv6

Data Link Network Mobile

Interface Ethernet Wi-Fi
Physical broadband
TCP/IP Applications

Some common application layer protocols:

• HTTP
• HTTPS
• FTP
• RDP
• SMB
• SMTP
• POP3
What Is a Socket?

• A socket is a combination of IP address,

transport protocol, and port
TCP/IP Protocol Suite

HTTP (80) SMTP (25)

HTTPS (443) DNS (53)
POP3 (110) FTP (21)

TCP/UDP

IPv4 IPv6
Lesson 2: Understanding IPv4 Addressing

• IPv4 Addressing
• Public and Private IPv4 Addresses
• How Dotted Decimal Notation Relates to Binary
Numbers
• Simple IPv4 Implementations
• More Complex IPv4 Implementations
IPv4 Addressing
An IPv4 configuration identifies a computer to other computers on a network

IP Address Subnet 1
192.168.2.180
255.255.255.0
IP Address
192.168.2.181
255.255.255.0

Default gateway defines

the preferred router
IP Address
192.168.2.182 IP Address
255.255.255.0 192.168.1.200
255.255.255.0

Dotted decimal
IP Address
representation
192.168.1.201
of the address 255.255.255.0
and subnet mask IP Address
192.168.1.202
Subnet 2 255.255.255.0
Public and Private IPv4 Addresses

Public Private
• Required by devices and • Not routable on the
hosts that connect directly Internet
to the Internet • 10.0.0.0/8
• 172.16.0.0/12
• Must be globally unique • 192.168.0.0./16
• Routable on the Internet • Can be assigned locally
• Must be assigned by by organization
IANA/RIR • Must be translated to
access the Internet
How Dotted Decimal Notation Relates to
Binary Numbers

8-Bit Octet
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

27 26 25 24 23 22 21 20

128 64 32 16 8 4 2 1

Decimal Value
Simple IPv4 Implementations

Class A (/8) Network Host ID

Large ID
0
Network w x y z

Class B (/16) Network ID Host ID

Medium 10
Network w x y z

Class C (/24) Network ID Host ID

Small Network 110
w x y z
 More Complex IPv4 Implementations

172.16.17.1
172.16.16.0/22

172.16.17.0/24
172.16.20.0/22

172.16.16.1/20 172.16.24.0/22 172.16.17.254

172.16.18.0/24

172.16.28.0/22
Lesson 3: Subnetting and Supernetting

• How Bits Are Used in a Subnet Mask or Prefix

Length
• The Benefits of Using Subnetting
• Calculating Subnet Addresses
• Calculating Host Addresses
• Discussion: Creating a Subnetting Scheme for a
New Office
• What Is Supernetting?
How Bits Are Used in a Subnet Mask or Prefix Length

Class B Address with Subnet

Number of Subnets 32
2
8
128
64
16
4
0
256

Network ID Subnet ID Host ID

1 0

Number of Hosts 16,382

32,766
1,022
2,046
4,094
8,190
510
65,534
254
254
The Benefits of Using Subnetting

When you subdivide a network into subnets, you

create a unique ID for each subnet that is derived
from the main network ID
By using subnets, you can:
• Use a single network address across multiple
locations
• Reduce network congestion by segmenting
traffic
• Increase security by using firewalls
• Overcome limitations of current technologies
Calculating Subnet Addresses

When determining subnet addresses you should:

• Choose the number of subnet bits based on the
number of subnets required
• Use 2n to determine the number of subnets
available from n bits

For five locations, the following three subnet bits

are required:
• 5 locations = 5 subnets required
• 22 = 4 subnets (not enough)
• 23 = 8 subnets
Calculating Host Addresses

When determining host addresses you should:

• Choose the number of host bits based on the
number of hosts that you require on each
subnet
• Use 2n-2 to determine the number of hosts
that are available on each subnet

For subnets with 100 hosts, seven host bits are

required:
• 26-2 = 62 hosts (not enough)
• 27-2 = 126 hosts
Discussion: Creating a Subnetting Scheme for a
New Office

• How many subnets are required?

• How many bits are required to create that
number of subnets?
• How many hosts are required on each subnet?
• How many bits are required to allow that
number of hosts?
• What is an appropriate subnet mask to meet
these needs?

20 minutes
What Is Supernetting?
• Supernetting combines multiple small networks
into a larger network
• The networks that you are combining must be
contiguous
• The following table shows an example of
supernetting two class C networks:
Network Range

192.168.00010000.00000000/24 192.168.16.0 - 192.168.16.255

192.168.00010001.00000000/24 192.168.17.0 - 192.168.17.255

192.168.00010000.00000000/23 192.168.16.0 - 192.168.17.255

Lesson 4: Configuring and Troubleshooting IPv4

• Configuring IPv4 Manually

• Configuring IPv4 Automatically
• IPv4 Troubleshooting Tools
• Using Windows PowerShell Cmdlets to
Troubleshoot IPv4
• The IPv4 Troubleshooting Process
• What Is Network Monitor?
• Demonstration: How to Capture and Analyze
Network Traffic by Using Network Monitor
Configuring IPv4 Manually

Example using the netsh command-line tool

Netsh interface ipv4 set address name="Local Area
Connection" source=static addr=10.10.0.10
mask=255.255.255.0 gateway=10.10.0.1

Example using PowerShell cmdlets

New-NetIPAddress –InterfaceAlias “Local Area
Connection” –IPAddress 10.10.0.10
-PrefixLength 24 –DefaultGateway 10.10.0.1

Set-DNSClientServerAddresses –InterfaceAlias
“Local Area Connection”
–ServerAddresses 10.12.0.1,10.12.0.2
Configuring IPv4 Automatically

DHCP Server IPv4 DHCP

with Client
IPv4 Scope

An APIPA address on an interface indicates that a

DHCP server could not be contacted
Code example using Powershell:
Set-NetIPInterface –InterfaceAlias "Local Area
Connection" –Dhcp Enabled
Restart-NetAdapter –Name "Local Area Connection"
IPv4 Troubleshooting Tools

Use the following tools to troubleshoot IPv4:

• Ipconfig • Netstat

• Ping • Resource Monitor

• Tracert • Windows Network
• Pathping
Diagnostics
• Event Viewer
• Telnet
Using Windows PowerShell Cmdlets to
Troubleshoot IPv4

Some of the new Windows PowerShell cmdlets:

• Get-NetAdapter
• Restart-NetAdapter
• Get-NetIPInterface (similar to ipconfig in cmd)
• Get-NetIPAddress
• Get-NetRoute
• Get-NetConnectionProfile
• Get-DNSClientCache (similar to ipconfig/displaydns)
• Get-DNSClientServerAddress
The IPv4 Troubleshooting Process

• Identify the scope of the problem

• Use tracert to identify the network path
between hosts
• Use ipconfig to verify the network configuration
is correct
• Use ping to see if the remote host responds
• Use an application to test the service on a
remote host
• Use ping to see if the default gateway responds
What Is Network Monitor?
Demonstration: How to Capture and Analyze
Network Traffic by Using Network Monitor

In this demonstration, you will see how to:

• Capture network traffic with Network
Monitor
• Analyze the captured network traffic
• Filter the network traffic

• filtering is useful when you want to display

only specific packets when troubleshooting
a specific problem. For example, you could
display only communication with a specific
IP address.
Lab: Implementing IPv4

• Exercise 1: Identifying Appropriate Subnets

• Exercise 2: Troubleshooting IPv4

Logon Information
Virtual machines: 20410B-LON-DC1
20410B-LON-RTR
20410B-LON-SVR2
User name: Adatum\Administrator
Password: Pa$$w0rd

Estimated Time: 45 minutes

Lab Scenario
A. Datum Corporation has an IT office and data center
in London, which supports the London location and
other locations. They have recently deployed a
Windows 2012 Server infrastructure with Windows 8
clients. You have recently accepted a promotion to the
server support team. One of your first assignments is
configuring the infrastructure service for a new branch
office.
After a security review, your manager has asked you to
calculate new subnets for the branch office to support
segmenting network traffic. You also need to
troubleshoot a connectivity problem on a server in the
branch office.
Lab Review

• Why is variable length subnetting required in this lab?

• The criteria in the scenario calls for one subnet with 100 IP
addresses for clients. It is not possible to make all of the subnets
this large. Variable length subnetting allows you to subdivide the
single /24 network into variable sized subnets to allow for one large
subnet and two smaller subnets.
•
• Which Windows PowerShell cmdlet can you use to view
the local routing table of a computer instead of using
route print?

• You can use the Get-NetRoute cmdlet to view the local routing
table of a computer.
Module Review and Takeaways

•Question
•You have just started as a server administrator for a small organization with a
single location. The organization is using the 131.107.88.0/24 address range
for the internal network. Is this a concern?

•Answer
•Yes, that is a concern because those are Internet-routable addresses. Most
IPv4 networks use private addresses with NAT to allow access to the Internet.
This organization will not be able to access the 131.107.88.0/24 network on
the Internet.

•Question
•You are working for an organization that provides web hosting services to
other organizations. You have a single /24 network from your ISP for the web
hosts. You are almost out of IPv4 addresses and have asked ISP for an
additional range of addresses. Ideally, you would like to supernet the existing
network with the new network. Are there any specific requirements for
supernetting?
•Answer
•Yes. To perform supernetting the two networks must be consecutive.
The networks must allow you to remove a single bit from the subnet
mask and identify both as the same network.

•Question
•You have installed a new web-based application that runs on a
non-standard port number. A colleague is testing access to the new
web-based application, and indicates that he cannot connect to it.
What are the most likely causes of his problem?

•Answer
•When a server application runs on a non-standard port, you need to
provide the client application with the port number to which it should
be connecting. For example, http://servername:port. It is also possible
that your colleague is attempting to connect using http, when he
should be using https.
•Best Practice: When implementing IPv4, use the following best
practices:
 Allow for growth when planning IPv4 subnets. This ensures that you
do not need to change you IPv4 configuration scheme.

 Define purposes for specific address ranges and subnets. This

allows you to easily identify hosts based on their IP address and use
firewalls to increase security.

 Use dynamic IPv4 addresses for clients. It is much easier to manage

the IPv4 configuration for client computers by using DHCP than with
manual configuration.

 Use static IPv4 addresses for servers. When servers have a static
IPv4 address, it is easier to identify where services are located on
the network.
•Common Issues and Troubleshooting Tips
•Common Issue: IP conflicts
•Troubleshooting Tip: In most cases, computers that are
running Windows operating systems display a pop-up
message when they have an IP conflict with another
network device. However, some network devices do not.
When performing a packet capture, duplicate TCP
acknowledgements can be an indication that two devices
have the same IP address, and that both are responding
to connection attempts.
•To prevent IP conflicts, clearly document which IPv4
addresses are in use on your network, and do not assign
new IPv4 addresses without checking the documentation.
•Common Issue: Multiple default gateways defined
•Troubleshooting Tip: On hosts with multiple network cards, only one
should have a default gateway defined. Windows Server 2012 is
designed to function with only a single default gateway. When multiple
default gateways are defined, network communication may be
unpredictable. You can verify that only a single default gateway is
configured by using the Get-NetRoute cmdlet.

•Common Issue: Incorrect IPv4 configuration

•Troubleshooting Tip: Incorrect IPv4 configuration information is most
commonly a result of a manual configuration error. To ensure that this
does not affect a production environment, you should test network
connectivity thoroughly for any new servers that you place into
production. You should also perform testing after making any network
configuration changes.