FTP, TFTP, DNS, NTP, HTTP Basics

FTP, TFTP, DNS, NTP, HTTP Basics

Quick Answer: FTP (TCP 21/20) is reliable and feature-rich; TFTP (UDP 69) is simple and connectionless. DNS (port 53) maps names to IPs. NTP (UDP 123) keeps clocks aligned. HTTP/HTTPS (80/443) deliver web apps and management UIs—use HTTPS whenever credentials or sensitive data are involved.

Routing and switching move packets, but operators still depend on network services to load images, resolve names, timestamp logs, and open management pages. HCIA-Datacom expects rapid recall of how FTP differs from TFTP, what DNS and NTP provide, and how HTTP versus HTTPS affects security. Earlier port tables listed numbers; this section focuses on behavior, operational use on Huawei devices, and exam traps when services interact with ACLs and NAT.

Service map for day-2 operations

| Service | Primary ports | Transport | Operator use on campus/edge | |---|---| | FTP | TCP 21 (control), TCP 20 (active data) | TCP | Transfer VRP images, patches, config archives with authentication | | TFTP | UDP 69 | UDP | Quick lab image/config copy; minimal overhead, weaker controls | | DNS | UDP/TCP 53 | Both | Resolve names for users and for device features that call hosts by name | | NTP | UDP 123 | UDP | Sync device clocks to a hierarchy of time servers | | HTTP | TCP 80 | TCP | Unencrypted web apps / some legacy device GUIs | | HTTPS | TCP 443 | TCP | TLS-protected web apps and secure management portals |

When an ACL or firewall question says “allow image download from the jump host,” translate the human task into protocol + port + direction before choosing permit rules.

FTP: reliable file transfer

File Transfer Protocol runs over TCP, so lost segments are retransmitted and a byte stream is delivered in order. Classic model:

1. Client opens a control connection to the server on TCP 21 for login and commands (GET, PUT, directory listing).
2. A separate data connection carries the file.
   • Active mode: server typically sources data from TCP 20 toward the client.
   • Passive mode: client initiates the data connection to a server-chosen port (easier through many firewalls).

Exam implications:

• Blocking only TCP 21 may still confuse data channels depending on mode—know that control and data are separate.
• Credentials on classic FTP can be sniffed; associate-level guidance is to prefer SSH-based SFTP (TCP 22) or other encrypted methods when the stem stresses security.
• FTP is the right mental default when the scenario needs directory listing, resume, or authenticated bulk transfer rather than a tiny config blip.

TFTP: simple and lightweight

Trivial File Transfer Protocol deliberately strips features:

Because TFTP is simple, it appears in many bootstrap and lab stories. Because it lacks strong authentication and encryption, it is a poor fit for untrusted networks. HCIA items often contrast:

• “Need quick unauthenticated lab transfer” → TFTP.
• “Need reliable authenticated transfer of large images across a WAN” → FTP (or better, SFTP).

Exam trap: Assigning TCP 69 to TFTP, or claiming TFTP uses the same control/data split as FTP. TFTP is UDP 69 and does not use FTP’s dual TCP channels.

DNS: resolving names to addresses

Users type www.example.com, not 93.184.216.34. Domain Name System (DNS) stores resource records and answers queries from resolvers.

Transport notes:

• Most ordinary queries use UDP 53.
• TCP 53 appears for large responses and zone transfers between servers.

Operational failures that look like “Internet is broken”:

On Huawei networks, ensure DHCP pools hand out reachable DNS IPs, and that security policies permit client → DNS server traffic. Devices themselves may need DNS if features reference hostnames (logging hosts, controllers, license portals).

NTP: time synchronization

Network Time Protocol keeps clocks aligned. Accurate time is not cosmetic:

NTP uses UDP 123. Devices act as clients toward upstream servers and may serve downstream peers in a hierarchy (stratum levels). HCIA-level expectations:

1. Know why NTP exists (logs, security, consistency).
2. Know the port and that it is UDP.
3. Recognize symptoms of wrong time (TLS failures, confusing log order) as possible NTP issues.

Prefer reliable internal NTP sources or trusted Internet pools depending on design policy; random public servers without oversight can be a governance concern, but the exam cares more about protocol role than vendor pool URLs.

HTTP and HTTPS basics

HTTP is the application protocol of the web. HTTPS is HTTP over TLS.

Campus relevance:

• User applications (portals, SaaS) overwhelmingly need 443 outbound through NAT/Easy IP.
• Device web management should not sit on the open Internet over clear HTTP when avoidable.
• Captive portals and WLAN guest flows often intermingle HTTP redirects with HTTPS—know both ports appear in ACL designs.

Exam trap: Claiming HTTPS uses UDP, or swapping 80/443. Another trap: assuming NAT Server for a web server should map port 80 when the stem clearly specifies HTTPS only—map 443 unless both are required.

Putting services together with NAT, DHCP, and ACLs

Real tickets rarely isolate one protocol:

1. PC receives IP/gateway/DNS via DHCP.
2. User opens HTTPS site → DNS query (53) then TCP 443 through Easy IP.
3. Engineer upgrades a switch → FTP/TFTP pull of a new image; confirm ACL allows the chosen method.
4. After change, logs disagree across devices → check NTP.
5. Partner must reach internal web tools → NAT Server for 443 plus DNS name pointing at the public IP.

FTP vs TFTP decision table (memorize)

Troubleshooting vignettes

Practice goals for this chapter

1. Recite FTP vs TFTP ports, transport, and security posture in one breath each.
2. Trace a failed web session: DHCP options → DNS → TCP 443 → NAT.
3. Explain two business reasons to deploy NTP on every managed Huawei device.
4. Write an ACL intent list for allowing DNS and HTTPS for a user VLAN while denying clear-text device Telnet.

DHCP assigns addresses, NAT translates them at the edge, and these services keep files, names, time, and web applications usable. Together they form the network-services slice of the HCIA-Datacom blueprint—expect scenario questions that combine at least two of them on a single topology.