CMPE 151: Network Administration: Clients
CMPE 151: Network Administration: Clients
CMPE 151: Network Administration: Clients
Administration
Clients
Winter 2005
Client-Server Model
Winter 2005
Client-Server Model
Winter 2005
File transfer
Winter 2005
File transfer
FTP
FTP Operation
Client
Server
Data Control
Data Control
OS
OS
TCP connection
Winter 2005
Anonymous FTP
Winter 2005
Winter 2005
Some History
More History
The Web
The browser
DNS
Winter 2005
Winter 2005
DNS
Winter 2005
DNS
The domain_name is formed by the institutional
site name and the Top-Level Domain name
(TLD).
Examples:
sundance.ucsc.edu
soe.ucsc.edu(alias for sundance.ucsc.edu)
italia.cse.ucsc.edu
helios.jpl.nasa.gov
Winter 2005
Commercial org.
.au Australia
.edu Educational site in US
.ca Canada
.gov Government site in US
.fr France
.mil Military organization in US .de Germany
.net Network site
.uk Great Britain
.org Nonprofit organization
.it Italy
.es Spain
Countries define their own internal hierarchy (e.g., .ac.uk, .edu.au)
Winter 2005
DNS hierarchy
Organizations can create any internal DNS
hierarchy.
Authority for creating new subdomains within
a domain name is delegated to each domain.
Administration of ucsc.edu has authority to
create cse.ucsc.edu and need not contact
any central naming authority.
Winter 2005
Winter 2005
Winter 2005
Winter 2005
Winter 2005
Winter 2005
Name Resolution
Resolving a name means mapping the host
name to the IP address.
Reverse mapping is also possible.
A client computer calls a DNS server for
name resolution
DNS request contains name to be resolved.
DNS reply contains IP address for name in
request.
Winter 2005
Winter 2005
Electronic mail
Non-interactive.
Spooling:
Mail system
User
sends mail
User
interface
User
reads mail
Outgoing
mail
spool
Mailboxes
incoming
mail
Winter 2005
Client
(send)
TCP
connection
(outgoing)
Server TCP
(receive) connection
(incoming)
Observations
Remote access
Winter 2005
Telnet
Users
machine
Telnet
client
Telnet
server
OS
OS
TCP connection
over Internet
Winter 2005