Scribd
Upload
4 views5 pages

Troubleshooting Network Issues and Protocols

The document outlines four scenarios related to networking and communication protocols. It covers troubleshooting website access issues, local vs. internet communication, differences between TCP and UDP in file transfers and video calls, and securing remote access for system administration. Each scenario poses questions that require understanding of network protocols, NAT technology, and security measures.

Uploaded by

Mostafa Abdelkodous
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views5 pages

Troubleshooting Network Issues and Protocols

The document outlines four scenarios related to networking and communication protocols. It covers troubleshooting website access issues, local vs. internet communication, differences between TCP and UDP in file transfers and video calls, and securing remote access for system administration. Each scenario poses questions that require understanding of network protocols, NAT technology, and security measures.

Uploaded by

Mostafa Abdelkodous
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Scenario 1: "The Website is Down!

"

(Merging L3, L4, L7, & Tools)

Question: A user on your internal network (using a Private IP )


complains they can't open the website [Link] As a
network engineer, you use the ping tool, and ping [Link]
works successfully.

Required:

1. Is a successful ping enough to say "the website is working"?


Why or why not?

2. What other command-line tool would you use to verify the


website's name ([Link]) is being translated correctly?

3. Since ping (connectivity) works, but HTTP (the website service)


doesn't, which network device (according to the slides) is the
most likely cause of this problem, and what exactly is it doing?

Scenario 2: "Local vs. Internet Communication"

(Merging L2, L3, & NAT)

Question: You have two PCs in the same office, connected to the
exact same Switch:

 PC A (IP: [Link])

 PC B (IP: [Link])

Required:

1. Explain the protocol PC A uses to find PC B to send it a file


(since they are on the same local network). What "physical"
address is it looking for?

2. Now, PC A wants to open [Link] (which has a Public IP ).


Will it use the same protocol from step 1 to reach Google?

3. Explain how the Router uses NAT technology to allow your


device (with its Private IP ) to communicate with Google (which
has a Public IP ).
Scenario 3: "Video Call vs. File Download"

(Merging L4 - TCP vs. UDP)

Question: An employee is doing two things at the same time:

1. Downloading a large file from a server (using the FTP protocol ).

2. On a live video call (which uses the UDP protocol ).

The employee notices the file downloaded 100% perfectly with no errors, but
the video call was "choppy" and "laggy."

Required:

1. Why does a file download (like FTP) use the TCP protocol?

2. Why does a live video call use the UDP protocol?

3. Based on the difference between these two protocols, explain exactly


why the "choppiness" happened in the call, while the file transfer was
perfect.

Targeted Concepts: TCP , UDP , 3-way handshake , Reliable vs. Unreliable ,


Use Cases (Files vs. Real-time ).

Scenario 4: "Securing Remote Access"

(Merging Security, Protocols, & L4)

Question: You are a System Administrator and need to work from home. You
have two goals:

1. Use Remote Desktop (RDP ) to access a Windows server.

2. Make configuration changes to a router using SSH.

The company Firewall is configured to block the RDP port (3389) and the
SSH port (22) from anyone on the public internet.
1. What technology (mentioned in the slides) will allow you to work from
home by creating a "secure tunnel" for all your device's internet
activity?

2. Your colleague suggests using a Proxy instead. Why is a Proxy a very


bad choice for this situation (especially for sensitive tasks like SSH and
RDP) compared to the first solution?

You might also like