Chapter 7:

Networking with Windows

Server 2019
Learning outcomes
• By the end of this lesson, you should be able to:
• Networking with Windows Server 2019.
Content:
1. Introduction to IPv6.
2. Your Networking Toolbox.
3. Building a Routing Table.
4. NIC Teaming.
5. Software-defined Networking
1. Introduction to IPv6.
• IPv6, or Internet Protocol version 6, is the most recent version of
the Internet Protocol (IP), which is used to identify devices across
the internet so they can communicate with each other. IPv6 was
developed to deal with the long-anticipated problem of IPv4
address exhaustion.
• Key Features of IPv6:
• Larger Address Space: IPv6 addresses are 128 bits long, compared to
the 32-bit addresses used in IPv4. This allows for a vastly larger number
of unique IP addresses.

• Simplified Header: The IPv6 header has been simplified compared to

IPv4 to improve the efficiency of packet processing.

• No Need for Network Address Translation (NAT): The larger address

space eliminates the need for NAT, which allows for simpler network
designs.
• Auto-configuration: IPv6 supports both stateless and stateful address
configurations, enabling devices to automatically obtain an IP address
without the need for a DHCP server.

• Integrated Security: IPv6 was designed with security in mind, and

IPsec (Internet Protocol Security) support is mandatory in IPv6,
whereas it was optional in IPv4.

• Improved Multicasting: IPv6 improves multicast routing by eliminating

the need for broadcast addresses and providing more efficient routing.
• Anycast Addressing: IPv6 introduces anycast addressing, where
multiple devices can share the same IP address and the network
automatically routes packets to the nearest one.

• Pv6 is gradually being adopted around the world, and while IPv4 is
still in widespread use, the transition to IPv6 is necessary to
support the continued growth of the internet and the increasing
number of devices connected to it.
Summary
• IPv6 provides a significant advantage over IPv4 in terms of the
number of IP addresses that can be contained within a single
network, which resolves the issue of creating subnets to
accommodate numerous physical devices. An IPv6 address is
128-bit length address, while an IPv4 address is only 32-bit
length. Eventually, organizations will need to deal with IPv6, and
it is worth noting its advantages.
• Understanding IPv6 IP addresses
• Understanding IPv6 IP addresses is crucial as they are the
backbone of the next generation of internet communication.

• Here are some key points to understand about IPv6 IP

addresses:
• IPv6 addresses are 128 bits long, which is four times the length of IPv4 addresses. This
means that there are a significantly larger number of available addresses in IPv6 than in
IPv4.
• IPv6 addresses are represented in hexadecimal notation, separated
by colons ":". For example, an IPv6 address might look like this:
2001:0db8:85a3:0000:0000:8a2e:0370:7334.

• IPv6 addresses are divided into eight 16-bit blocks, with each block
represented by four hexadecimal digits. Leading zeros in each block
can be omitted.

• IPv6 addresses can be shortened by replacing consecutive blocks of

all zeros with double colons "::". This can only be done once in any
given IPv6 address, to avoid ambiguity.
• IPv6 addresses can be shortened by replacing consecutive blocks of
all zeros with double colons "::". This can only be done once in any
given IPv6 address, to avoid ambiguity.

• IPv6 includes several new features and improvements over IPv4,

including better support for mobile devices, built-in security features,
and simplified network configuration.

• IPv6 is gradually being adopted by networks and devices around the

world, but many networks and devices still use IPv4. Both protocols
are expected to coexist for many years to come, with various
mechanisms for translating between them as needed.
2. Your Networking Toolbox.
• There are useful tools for testing and monitoring network connections in
the Windows Server world. Some tools are built into the operating system
and can be used from the Command Prompt or PowerShell, while others
require installation and have graphical interfaces. These tools are
beneficial for server and network administrators.
• Here are some notes on the built-in Windows network tools
you mentioned:

• Ping: This tool is used to test the connectivity between two

devices on a network by sending packets of data and
measuring the response time. It can be used to troubleshoot
network issues like slow connection or packet loss.
• Tracert: Tracert is a command that helps in tracing the path
taken by packets of data from one device to another. It can be
used to identify network congestion, routing issues, and other
network problems.

• Pathping: Pathping is similar to tracert, but it provides more

detailed information about the network path and includes
statistics about packet loss at each hop. It can be used to
diagnose network performance issues.
• Test-Connection: This PowerShell command is used to test the
connectivity between two devices on a network. It can be used to
diagnose network connectivity problems.

• Telnet: Telnet is a protocol used to establish a connection with a

remote device over a network. It can be used to test the availability
of services like web servers or mail servers.

• Test-NetConnection: This PowerShell command is used to

diagnose network connectivity issues by testing the connection to a
remote device, resolving DNS names, and pinging devices on a
network.
• Wireshark: Wireshark is a network protocol analyzer that
allows you to capture and analyze network traffic. It can be
used to troubleshoot network issues, detect security threats,
and monitor network performance.

• TCPView: TCPView is a tool that displays all active TCP and

UDP connections on a Windows computer. It can be used to
monitor network activity and diagnose network problems related
to network connections.
3. Building a Routing Table.
• Building a routing table involves configuring a set of rules that dictate how
data packets should be directed through a network. The routing table is
crucial for ensuring that data is efficiently and correctly sent from a source
to a destination. Here's a guide to understanding and building a routing
table:

• Understanding Routing Tables

• A routing table is a data structure used by routers and networking devices
to determine the best path for forwarding packets. It contains information
about network destinations and how to reach them. The routing table
typically includes:
• Destination Network: The network address or IP range for which the
route is applicable.
• Subnet Mask: Defines the size of the network segment.
• Next Hop: The IP address of the next router or gateway to which packets
should be sent.
• Interface: The network interface through which packets should be sent.
• Metric: A value representing the cost of the route; lower values indicate
preferred routes.
• Types of Routes
• Static Routes: Manually configured routes that do not change
unless manually updated. Useful for specific, fixed routes.
• Dynamic Routes: Learned and updated automatically through
routing protocols (e.g., OSPF, EIGRP, BGP). Adapt to network
changes and failures.
• Default Route: A catch-all route used when no other route
matches the destination. Often referred to as the "gateway of last
resort."
• Building a Routing Table

• Static Routing
• To build a static routing table, follow these steps:

• 1. Identify the Destination Network: Determine the IP network or

subnet you need to route traffic to.

• 2. Determine the Next Hop or Exit Interface: Identify the next hop IP
address or the outgoing interface to reach the destination network.
• 3. Configure the Static Route:
• On Linux Systems:
• ip route add [destination network]/[prefix length] via [next hop IP
address]

• ip route add [Link]/24 via [Link]

• 4. Verify the Routing Table:
• ip route show
• Dynamic Routing
• To build a routing table with dynamic routing, follow these steps:
• 1. Select a Routing Protocol: Choose a routing protocol based on
network size, complexity, and requirements (e.g., OSPF, EIGRP,
BGP).
• 2. Configure the Routing Protocol:
• For OSPF:
• Router(config)# router ospf [process ID]
• Router(config-router)# network [network address] [wildcard mask]
area [area ID]
• Router(config)# router ospf 1
• Router(config-router)# network [Link] [Link] area 0

• 3. Verify the Routing Table:

• For OSPF:
• Router# show ip ospf route
Summary
• Building a routing table involves configuring static or dynamic
routes to ensure data packets are correctly directed through the
network. Static routes are manually configured and suitable for
fixed paths, while dynamic routes are learned through protocols
and adapt to network changes. Proper management of routing
tables, including the use of administrative distance, redundancy,
and documentation, is key to maintaining an efficient and reliable
network.
Additional information : Routing tables
• Routing tables are used to determine how packets should be
routed through a network. Each device on a network has its
own routing table, which contains information about the paths
available to reach various destinations.

• Multi-homed servers:
• A multi-homed server is a computer that has multiple network
interfaces and can be connected to multiple networks. When
configuring a multi-homed server, it is important to set up the
routing table correctly to ensure that packets are sent to the
correct network interface.
• Only one default gateway:
• It is important to note that a device can only have one default
gateway in its routing table. If there are multiple default gateways
configured, the device may not be able to reach destinations on
either network.

• Building a route:
• A route is a set of instructions that tells a device how to reach a
specific destination on a network. To build a route, you need to know
the IP address of the destination and the IP address of the next hop
device. The next hop device is the device that the packet should be
sent to next to reach the destination.
• Adding a route with the Command Prompt:
• You can add a route to a device's routing table using the
Command Prompt in Windows. The command to add a route is
"route add".
• For example, to add a route to reach the destination IP address
[Link] through the next hop device
• at IP address [Link],
• the command would be: "route add [Link] mask
[Link] [Link]".
• Deleting a route:
• To delete a route from a device's routing table, you can use the "route delete"
command in the Command Prompt.
• For example, to delete the route to the destination IP address [Link], the
command would be: "route delete [Link]".

• Adding a route with PowerShell:

• You can also add a route to a device's routing table using PowerShell in
Windows.
• The command to add a route is "New-NetRoute". For example, to add a route to
reach the destination IP address [Link] through the next hop device at IP
address [Link], the command would be: "New-NetRoute -DestinationPrefix
[Link]/32 -InterfaceIndex 3 -NextHop [Link]".
4. NIC Teaming.
• NIC Teaming, also known as Link Aggregation or Network
Interface Card Bonding, is a network configuration strategy that
allows multiple physical network interfaces to be combined into a
single logical interface. This technique enhances network
performance, provides redundancy, and improves the availability
of network connections.
• Purpose of NIC Teaming
• NIC Teaming is used to achieve several key objectives:
• Increased Bandwidth: By combining multiple NICs, the total available
bandwidth is increased, allowing for higher throughput.

• Redundancy and Fault Tolerance: If one NIC fails, the others in the
team continue to operate, ensuring that the network connection
remains active.

• Load Balancing: Traffic can be distributed across multiple NICs,

balancing the load and preventing any single NIC from becoming a
bottleneck.
• There are different types of NIC teaming configurations,
including static link aggregation, where all the NICs are
connected to the same switch, and dynamic link aggregation,
where the NICs can be connected to different switches.

• NIC teaming is commonly used in enterprise environments

where high network availability and performance are critical. It
allows for redundancy and failover capabilities, ensuring that if
one NIC fails, the others will take over seamlessly.
• It's important to note that NIC teaming requires specific configuration on
the switch and operating system side, and not all network adapters support
teaming. Additionally, teaming may not necessarily improve performance in
all scenarios, and it's important to test and measure the impact before
implementing it in a production environment.
Configuring NIC Teaming
• NIC Teaming can be configured on both Windows and Linux systems.
Below are the steps for Windows:

• On Windows Server:
[Link] Server Manager:
1. Launch Server Manager on the server where you want to configure NIC Teaming.

2. Navigate to NIC Teaming:

• In Server Manager, go to Local Server, and then click on the NIC
Teaming link next to the NIC Teaming status.
• 3. Create a New Team:
• In the NIC Teaming window, click on Tasks > New Team.
• Enter a name for the team and select the NICs you want to include
in the team.

• 4. Configure Teaming Properties:

• Choose the Teaming Mode, Load Balancing Mode, and other
relevant settings.
• Click OK to create the team.
• 5. Assign IP Configuration:
• The new team will appear as a virtual network adapter. Assign an
IP address and configure other network settings as needed.
5. Software-defined Networking
• Software-Defined Networking (SDN) is an innovative approach
to network management that decouples the control plane from
the data plane in network devices, allowing for more centralized
and dynamic network configuration. This separation enables
administrators to manage network behavior more efficiently,
making it a powerful tool in modern IT environments.
• Key Concepts of Software-Defined Networking (SDN):

• Control Plane vs. Data Plane:

• Control Plane: Responsible for making decisions about where network
traffic is sent. In traditional networks, this logic is embedded in network
devices like routers and switches.
• Data Plane: Responsible for the actual forwarding of traffic based on the
decisions made by the control plane. This plane handles the movement of
packets through the network.

• In SDN, the control plane is abstracted from the data plane and centralized in
a software-based controller, which communicates with the network devices.
• Centralized Control:
• SDN centralizes network control by using a software controller
that manages the entire network. This controller has a global view
of the network, enabling more intelligent and efficient decision-
making.
• The controller can dynamically adjust network policies, optimize
traffic flow, and automate network management tasks, all from a
single point of control.
• Programmability:
• One of the most significant advantages of SDN is network programmability.
Administrators can program the network directly through software applications,
automating complex configurations and management tasks.
• This programmability allows for faster deployment of services, more flexible network
configurations, and the ability to adapt quickly to changing business requirements.

• OpenFlow Protocol:
• OpenFlow is one of the first and most widely adopted protocols used in SDN to
enable communication between the SDN controller and the network devices
(switches, routers).
• It allows the controller to instruct the devices on how to handle traffic, including
routing, blocking, or prioritizing certain packets.
• Network Virtualization:
• SDN facilitates network virtualization, enabling multiple virtual networks to
run on top of a shared physical infrastructure. This allows for more efficient
use of resources and easier management of complex networks.
• Virtual networks can be created, modified, and deleted programmatically,
without needing to change the underlying physical infrastructure.

• Automation and Agility:

• SDN supports automation of network management tasks, reducing the need
for manual intervention and minimizing human error.
• This agility enables organizations to rapidly adapt to new business demands,
deploy applications more quickly, and respond to network events in real-
time.
• Benefits of SDN:
• Cost Efficiency: By decoupling(separate) hardware from software, organizations can reduce the need
for expensive, proprietary network devices and instead use more cost-effective, standardized
hardware.

• Flexibility: SDN allows for more flexible network designs, where administrators can easily implement
new policies, reroute traffic, or adjust bandwidth allocations as needed.

• Scalability: Centralized control and automation make it easier to scale networks to accommodate
growth or changing demands without significant reconfiguration.

• Enhanced Security: SDN provides better network visibility and the ability to implement consistent
security policies across the entire network. It can also quickly respond to threats by isolating affected
network segments.

• Simplified Management: The centralized nature of SDN simplifies network management,

troubleshooting, and policy enforcement, leading to a more efficient and responsive network
environment.
• Hyper-V Network Virtualization.
• Hyper-V Network Virtualization is a network virtualization technology that
allows multiple virtual networks to share the same physical network
infrastructure without interfering with each other. This enables
organizations to create isolated virtual networks for different applications or
tenants, which can help improve network security and simplify network
management.
• Private Clouds
• Private clouds are cloud computing environments that are dedicated to a single
organization or business. Private clouds can be hosted on-premises or in a third-party
data center and provide organizations with greater control and customization over their
computing resources.

• Public Clouds
• Public Clouds are cloud computing environments where services and resources, such as
servers, storage, and applications, are provided by a third-party cloud service provider
(CSP) over the internet. These resources are shared among multiple customers (also
known as tenants), which allows the CSP to offer services at a lower cost compared to
private clouds. Public clouds are widely used for their scalability, flexibility, and cost-
efficiency.
• Hybrid Clouds
• Hybrid Clouds are cloud computing environments that combine the advantages of both
public and private clouds, allowing organizations to leverage the benefits of each while
maintaining greater flexibility, control, and efficiency. In a hybrid cloud setup, an
organization uses a mix of on-premises private cloud resources and public cloud services,
with orchestration between the two platforms to ensure seamless operation and data
portability.
• How does it work?

• System Center Virtual Machine Manager is a management tool that enables organizations to create
and manage virtual machines (VMs) and virtual networks.

• Network Controller is a centralized management tool for configuring and managing SDN
components such as virtual networks, network policies, and virtual appliances.

• Generic Routing Encapsulation (GRE) is a tunneling protocol that can be used to encapsulate and
transport network traffic over an SDN.

• Microsoft Azure Virtual Network is a cloud-based networking service that enables organizations to
create and manage virtual networks in the cloud.

• RAS Gateway/SDN Gateway is a network gateway that enables organizations to connect their on-
premises networks to an SDN.
• Virtual Network Encryption
• Virtual Network Encryption refers to the process of encrypting
data as it travels across a virtual network, ensuring that the data
remains secure from unauthorized access or tampering while in
transit between virtual machines (VMs) and other networked
resources within a cloud environment or across hybrid cloud
architectures.
• Key Concepts of Virtual Network Encryption:

• Data-in-Transit Encryption:
• Virtual network encryption focuses on protecting data as it moves
across the network. This is known as data-in-transit encryption, as
opposed to data-at-rest encryption, which protects data stored on
disk.
• Encryption ensures that even if the data is intercepted during
transmission, it cannot be read or altered without the correct
decryption keys.
• Transport Layer Security (TLS):
• A common method for securing data in transit is through the use
of protocols like Transport Layer Security (TLS), which encrypts
the data exchanged between applications or services. TLS is
widely used to secure web traffic, email, and other
communication channels.
• In a virtual network, TLS or similar protocols can be employed to
secure communication between VMs, containers, or other
services.
• IPsec (Internet Protocol Security):
• IPsec is a suite of protocols designed to secure Internet Protocol (IP)
communications by authenticating and encrypting each IP packet in a data
stream. It is commonly used for setting up secure connections (VPNs)
between on-premises networks and cloud environments.
• Within a virtual network, IPsec can be used to encrypt communication
between different network segments, between on-premises networks and
cloud networks, or even between different VMs within the same virtual
network.
• Virtual Private Networks (VPNs):
• VPNs are a practical application of virtual network encryption,
where data traffic is encrypted as it moves between remote
locations and the central network. This is particularly important
for securing data across public networks, such as the internet.
• VPNs can be used within a cloud environment to create secure
tunnels between different parts of a virtual network, between on-
premises and cloud networks, or between different cloud regions.
• Azure Virtual Network Encryption:
• For example, Microsoft Azure offers a feature called "Azure Virtual
Network Encryption," which automatically encrypts the traffic
between virtual machines (VMs) within the same virtual network.
This encryption occurs without requiring any changes to the VM
configurations.
• This feature is particularly useful for ensuring that data
transmitted within the cloud environment remains secure, even if
the network infrastructure itself is compromised.
• Encryption Keys and Management:
• Encryption within virtual networks requires careful management
of encryption keys. These keys are used to encrypt and decrypt
data and must be securely stored and managed to prevent
unauthorized access.
• Cloud service providers often offer key management services,
such as AWS Key Management Service (KMS) or Azure Key Vault,
to help organizations securely manage and rotate encryption keys.
• End-to-End Encryption:
• In some cases, virtual network encryption may be part of an end-
to-end encryption strategy, where data is encrypted at the source
(e.g., on the client or application side) and remains encrypted until
it reaches its final destination. This ensures that data is protected
not only in transit but also within the network infrastructure itself.
• Benefits of Virtual Network Encryption:

• Enhanced Security:
• Encrypting data in transit within a virtual network helps protect against data
breaches, man-in-the-middle attacks, and other security threats that could
compromise sensitive information.

• Compliance:
• Many industries have regulatory requirements that mandate the encryption of
data in transit to protect customer information and ensure privacy. Virtual
network encryption helps organizations meet these compliance
requirements.
• Data Integrity:
• Encryption not only protects the confidentiality of data but also
ensures its integrity. Encrypted data cannot be tampered with or
altered without detection, making it a critical component of secure
communications.

• Protection Against Insider Threats:

• Virtual network encryption can help mitigate risks associated with
insider threats, such as malicious employees or compromised internal
systems, by ensuring that even those with access to the network
cannot easily intercept or manipulate sensitive data.
• Bridging the gap to Azure
• Bridging the gap to Azure is a feature of SDN that enables organizations to
connect their on-premises networks to Microsoft Azure using SDN
technologies. This can help organizations extend their on-premises
networks to the cloud and enable hybrid cloud scenarios.
• Azure Network Adapter

• The Azure Network Adapter is a feature that simplifies the process of connecting on-
premises servers to Azure Virtual Networks (VNets) using a point-to-site (P2S) VPN
connection. It is particularly useful for organizations that need to extend their on-premises
infrastructure into Azure without setting up complex network configurations or deploying
additional hardware.

• Azure Network Adapter is a feature of SDN that enables organizations to easily connect
their on-premises networks to Microsoft Azure by providing a streamlined setup
experience for configuring SDN components.
• Key Features of Azure Network Adapter:

• Simplified Connectivity:
• Azure Network Adapter provides an easy way to connect a Windows Server
on-premises to an Azure VNet using a point-to-site VPN connection. This
feature is designed to be user-friendly, requiring minimal configuration.

• Point-to-Site VPN:
• The connection is established using a point-to-site VPN, which is ideal for
scenarios where you need to connect individual servers or small groups of
servers to Azure. Unlike site-to-site VPNs, point-to-site VPNs do not require a
VPN device on the on-premises side.
• Integration with Windows Admin Center:
• Azure Network Adapter can be deployed and managed through the
Windows Admin Center, a web-based interface for managing Windows
servers. This integration allows for seamless configuration and
monitoring of the network adapter directly from the management
console.

• Secure Connection:
• The connection between the on-premises server and Azure is secured
using standard VPN protocols, ensuring that data in transit is encrypted
and protected from unauthorized access.
• Support for Various Workloads:
• Once connected to the Azure VNet, the on-premises server can
access resources in Azure, such as virtual machines, databases,
and other services, as if they were part of the same local network.
This makes it easier to extend on-premises applications to the
cloud.
Activity 1
• Add a route to the windows server routing table.
THANK YOU