TCP/IP is a networking protocol suite that allows computers to communicate over the internet. It uses TCP and UDP as transport layer protocols. TCP provides reliable, connection-oriented communication and guarantees delivery, while UDP provides faster but unreliable connectionless communication. The document then provides further details on the differences between TCP and UDP.

1. Reply needed 1
TCP/IP is a networking protocol suite that Microsoft Windows
uses to communicate over the internet with other computers. It
interacts with DNS and security tech such as IPsec to assist in
the successful and secure transfer of IP packets between
machines. TCP/IP is most commonly used to communicate over
networks.
TCP, or Transmission Control Protocol, handles the sequencing
and acknowledgment of packets sent, and the recovery of
packets lost during transmission.
UDP, or User Datagram Protocol, provides a one-to-one or one-
to-many, connectionless, unreliable communications server that
is used when the amount of data to be transferred is small, such
as data that fits into a single packet.
Both UDP and TCP use ports to identify communications for
each TCP/IP program.
TCP
· Connection-oriented service; a session is established between
hosts.
· TCP guarantees delivery through the use of acknowledgments
and sequenced delivery of data.
· Programs that use TCP are provided assurance of reliable data
transport.
· TCP is slower, has higher overhead requirements, and only
supports point-to-point communication.
UDP
· Connectionless Service; no session is established between
hosts.
· UDP does not guarantee or acknowledge delivery, or sequence
data.
· Programs that use UDP are responsible for providing
reliability needed to transport data.
· UDP is fast, has low overhead requirements, and can support
point-to-point and point-to-multipoint communication.

2. References
Microsoft. (2005). User Datagram Protocol (UDP). Retrieved
from https://technet.microsoft.com/en-
us/library/cc785220(v=ws.10).aspx
Microsoft. (2003). How TCP/IP Works. Retrieved from
https://technet.microsoft.com/en-
us/library/cc786128(v=ws.10).aspx
Reply needed 2
TCP and UDP are both intent protocol that relay data from one
computer to another through a network. The difference between
the two is TCP is connection oriented which means it
establishes connection between the devices before actual data is
sent. This is done by a 3 way handshake, syn, syn-ack, and ack.
Since TCP is connection oriented it is more reliable because
packets are sure to arrive at the destination. Although TCP is a
lot slower than UDP, it is used for instances that requires
guaranteed data transmission such as and during virtual terminal
connection (TELNET), FTP for transferring files, HTTP and
HTTPs for world wide web connection.
UDP on the other hand is a “connection-less” protocol which
means data is sent whether the receiving end get it or not. It is a
lot faster than TCP but does not guarantee packets will arrive at
the destination. UDP exist when speed is a factor, and is used
during real-time data transmission such VOIP or skype, DNS,
DHCP, or online gaming. (Rodriguez, 2014)
Reference:
Rodriguez, E. (2014). TCP vs. UDP. Retreived from:
http://www.skullbox.net/tcpudp.php
Reply needed 3
TCP and UDP are both Layer 4 or Transport Layer protocols.
That being said TCP and UDP are used as the transport protocol
to send and receive data. The man differences between the two
is that TCP is connection oriented and UDP is connection-less.
TCP is considered reliable and UDP is unreliable. TCP numbers

3. every packet with what is called a sequence number to make
sure the packets can be in order. Even though UDP is unreliable
and doesn't guarantee the packet to the destination, it is faster
than TCP. You normally use UDP when the speed of the
transmission of the data is more important then the integrity of
the data. An example of why you would use UDP is phone calls,
live TV, and playing online video games.
Reply needed 1
I believe that DHCP reservation has its advantages over static
IP. Using DHCP reservations help administrators by offering a
centralized reference point for all IP allocations. It allows them
to assign these reservations and check the status of them from a
single point instead of having to log on administratively to a
specific machine to set a static IP address. DHCP reservations
also make it easier if you plan on moving a printer to different
network. You only have to log on and change the subnet in
DHCP and it will automatically move all devices to the new
subnet. DHCP reservation is basically the same concept of
setting a static IP on a device but just adds the convenience
factor. In some of the research I have done people recommended
that the actual server itself be set with a Static IP then set a
DHCP scope and reservations for specific connected devices.
The only downfall to setting reservations is that you must know
the MAC address of the said device. Although this is something
easy to figure out, it can sometimes become a little repetitive if
you have to acquire the MAC for each device. In all though,
DHCP reservation has the potential to be a very useful function
for administrators who need to allocate specific IPs with
specific devices and do not have physical contact with each
device.
BIBLIOGRAPHY:
(n.d.). Networking, VPN, TS, Remote Access and Internet
Troubleshooting. Retrieved July 25, 2016, from
http://www.chicagotech.net/netforums/viewtopic.php?f=1&t=43

4. 32
(n.d.). Advantages of DHCP Reservation over Static IP
Assignment. Retrieved July 25, 2016, from
http://support.microsoft.com/en-us/kb/170062
Reply needed 2
Manually assigning static IP addresses is a very straightforward
process. An administrator logs into each of the devices on the
network and assigns a static IP address that will be used until
someone else manually reconfigures it again. The problem with
this method arises when the network becomes midsize or larger.
It would be really challenging for an administrator to
individually assign and manage hundreds or maybe even
thousands of IP addresses, subnet masks, default gateways, and
all other configuration options.
In large networks a preferable solution would be to use DHCP
reservations, except one caveat. For mission critical systems it
would much safer to use static IPs for the reason that with a
reservation in DHCP, the client device will still go through the
DHCP process to get an the IP which can come at a cost if the
DHCP server goes “down”. From the security standpoint, the
network becomes more vulnerable to the man in the middle
attack. An attacker could setup a rogue DHCP server and
redirect all traffic to a different router that is under that
attacker’s control.
I think, like any other technology, DHCP reservations have its
pros and cons. It allows the administrators to manage the IP
assignment process from one central location as well having a
complete list of active leases and reservations readily available.
The downside is that the initial configuration still requires
manual interaction in terms of getting the MAC address for the
device.
With all of the mentioned above, for non-vital systems such as
printers, cameras, application servers I would definitely use
DHCP reservations for ease of management. For mission critical
servers I would go static and exclude those IPs from the main

5. scope.
References
Panek, Will & Wentworth, Tylor & Chellis, James. ( © 2008).
Mcts: windows server 2008 network infrastructure configuration
(exam 70-642). [Books24x7 version] Available from
http://common.books24x7.com.ezproxy.umuc.edu/toc.aspx?book
id=25194.
Reply needed 3
Overview of the DHCP Lease Process when a DHCP Server is
Unavailable
1. The DHCP client will initiate a request for an IP address
when it first attempts to connect to the network. The client will
broadcast a DHCPDiscover message to the local subnet
requesting IP address information from a DHCP server.
2. If, for whatever reason, the DHCP server does not respond to
the client’s request, the client will continue to send
DHCPDiscover messages using a randomized exponential
backoff algorithm. Subsequent messages will be sent at 4, 8, 16,
32, and 64 seconds with a random interval of plus or minus 1
second.
3. If after one minute (64 seconds) there is no response from a
DHCP server, the client will continue with an alternate
configuration, such as Automatic Private IP Addressing
(APIPA). APIPA is a common alternate configuration where the
client will self-configure an IP address in the range of
169.254.0.1 to 169.254.255.254 and a subnet mask of
255.255.0.0 and use this for its interface until DHCP is
available. If an alternate configuration is not supported or IP
auto-configuration has been disabled, the client network
initialization will fail, there will be no network access, and an
error message will be generated.
4. In either case, the client will begin a new cycle of
DHCPDiscover messages every five minutes using the 0, 4, 8,
16, 32, and 64 second intervals randomized with a plus or minus
1 second interval. It will continue broadcasting these messages

6. every five minutes in this manner until it receives a DHCPOffer
message from a DHCP server.
5. Once the DHCP server is back online and it receives the
DHCPDiscover message, it will respond by broadcasting a
DHCPOffer message to the client. The DHCPOffer message
contains the TCP/IP configuration information: an unleased IP
address, subnet mask, and default gateway. If more than one
DHCP server responds with a DHCPOffer message, the client
will accept the best offer, usually the first DHCPOffer message
it receives.
6. The client will indicate acceptance of the offer by
broadcasting a DHCPRequest message. This message contains
the IP address from the DHCPOffer selected, but it is not yet
being used by the client. Until it receives a DHCPAck message
from the DHCP server, the client does not officially have an IP
address.
7. Finally, the DHCP server will acknowledge the
DHCPRequest message by broadcasting a DHCPAck message.
This message assigns the address to the client and finalizes the
terms of the lease. It is at this point that the client can use the
leased IP to configure its TCP/IP properties, complete its
initialization, and connect to the network.
Citations:
· How DHCP Technology Works. (2003, March 28). Retrieved
from https://technet.microsoft.com/en-
us/library/cc780760(v=ws.10).aspx
· Droms, R. (1997, March). RFC2131 - Dynamic Host
Configuration Protocol. Retrieved from
https://www.ietf.org/rfc/rfc2131.txt
· Kozierok, C. (2005, September 20). DHCP Message
Generation, Addressing, Transport and Retransmission:
Retransmission of lost messages. Retrieved from
http://www.tcpipguide.com/free/t_DHCPMessageGenerationAdd
ressingTransportandRetrans-3.htm