winter 2005 cmpe 151: network administration clients

35
Winter 2005 CMPE 151: Network Administration Clients

Post on 22-Dec-2015

216 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

CMPE 151: Network Administration

Clients

Page 2: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Client-Server Model

Page 3: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Client-Server Model

Client

Kernel

File Server

Kernel

Printer Server

Kernel

Page 4: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

File transfer

Page 5: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

File transfer

Sharing remote files: “on-line” access versus “file transfer”.

“On-line” access transparent access to shared files, e.g., distributed file system.

Sharing through file transfer: user copies file then operates on it.

Page 6: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

FTP File transfer accounted for most of

the Internet traffic until the Web exploded!

Also uses TCP. Allows interactive access; format

specification (e.g., binary); authentication (clients required to authenticate themselves).

Page 7: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

FTP Operation Client Server

OS

Data Control

OS

Data Control

TCP connection

Page 8: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Anonymous FTP Allows access to public files. No need to authenticate user. Access restricted to publicly

available files (e.g., in /usr/ftp).

Page 9: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

The Web and HTTP

Page 10: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Some History Started in 1989 at CERN, European

center for nuclear research, in Switzerland.

Original motivation: need for scientists around the world to collaborate and share multi-media information.

Tim Berners-Lee came up with initial proposal of a web of linked documents

Page 11: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

More History… First text-based prototype demo in

12.91. Release of first graphical interface,

Mosaic, in 02.93 at NCSA by M. Andreessen.

In 1994, Andreessen creates Netscape. In 1994, CERM and MIT set up the

WWW Consortium to further develop the Web. www.w3.org for more information.

Page 12: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

The Web WWW, or the world-wide web is a

resource discovery service. Resource space is organized

hierarchically, and resources are linked to one another according to some relation.

Hypertext organization: link “granularity”; allows links within documents.

Graphical user interface.

Page 13: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

The client side Users perceive the Web as a vast

collection of information. Page is the Web’s information transfer unit. Each page may contain links to other

pages. Users follow links by clicking on them which

takes them to the corresponding page. This process can go on indefinetly,

traversing several pages located in different places.

Page 14: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

The browser Program running on client that retrieves

and displays pages. Interacts with server of page. Interprets commands and displays page.

Examples: Mosaic, Netscape’s Navigator and Communicator, Microsoft Internet Explorer.

Other features: back, forward, bookmark, caching, handle multimedia objects.

Page 15: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

DNS

Page 16: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Domain Name System (DNS)

• IP addresses are not easy to remember.• The Domain Name System (DNS) maps

IP addresses to host names.• Host name is formed by machine name

followed by domain name.– Host_name.domain_name

• RFCs 1034 and 1035.

Page 17: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

DNS Basic function: translation of

names (ASCII strings) to network (IP) addresses and vice-versa.

Example: zephyr.isi.edu <-> 128.9.160.160

Page 18: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

DNS

• The domain_name is formed by the institutional site name and the Top-Level Domain name (TLD).– So the host name is of the

form:machine_name.Ist_site_name.TLD_name

• Examples: – sundance.ucsc.edu– soe.ucsc.edu (alias for sundance.ucsc.edu)– italia.cse.ucsc.edu– helios.jpl.nasa.gov– www.cnn.com

Page 19: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Top-Level Domains (TLDs)

• TLD names identify organization types or country codes.

• Examples:.comCommercial 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)

Page 20: Winter 2005 CMPE 151: Network Administration Clients

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.

Page 21: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Example DNS Hierarchy

Page 22: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

DNS Name Space

• DNS names are managed by a hierarchy of DNS servers.– Hierarchy is related to DNS domain hierarchy

• Root server at top of tree knows about next level servers.

• Next level servers, in turn, know about lower level servers.

Page 23: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Example of DNS Hierarchy

Page 24: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Example of DSN Hierarchy

Page 25: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Choosing DNS Server Architecture

• Small organizations can use a single server.– Easy to administer.– Inexpensive.

• Large organizations often use multiple servers.– Reliability through redundancy.– Improved response time through load sharing.

Page 26: Winter 2005 CMPE 151: Network Administration Clients

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.

Page 27: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Name resolution (cont’d) Client DNS (running on client

hosts), or resolver. Application calls resolver with

name. Resolver contacts local DNS server

(using UDP) passing the name. Server returns corresponding IP

address.

Page 28: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Name resolution (cont’d) Application wants to resolve name. Resolver sends query to local name server.

Resolver configured with list of local name servers.

Select servers in round-robin fashion. If name is local, local name server returns

matching authoritative RRs. Authoritative RR comes from authority

managing the RR and is always correct. Cached RRs may be out of date.

Page 29: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Name resolution (cont’d) If information not available locally

(not even cached), local NS will have to ask someone else. It asks the server of the top-level

domain of the name requested.

Page 30: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Electronic mail Non-interactive.

Deferred mail (e.g., destination temporarily unavailable).

Spooling: Message delivery as background

activity. Mail spool: temporary storage area

for outgoing mail.

Page 31: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Mail system

Userinterface

Usersends mail

Userreads mail

Outgoingmailspool

Mailboxes incomingmail

Client(send)

Server(receive)

TCPconnection(outgoing)

TCPconnection(incoming)

Page 32: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Observations When user sends mail, message

stored is system spool area. Client transfer runs on background. Initiates transfer to remote

machine. If transfer succeeds, local copy of

message removed; otherwise, tries again later (30 min) for a maximum interval (3 days).

Page 33: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Remote access

Page 34: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Telnet

User’smachine

Telnetclient

OSTCP connectionover Internet

Telnetserver

OS

Page 35: Winter 2005 CMPE 151: Network Administration Clients

Winter 2005

Telnet basic operation When user invokes telnet, telnet client

on user machine establishes TCP connection to specified server.

TCP connection established; user’s keystrokes sent to remote machine.

Telnet server sends back response, echoed on user’s terminal.

Telnet server can accept multiple concurrent connections.