1 / 35

CMPE 151: Network Administration

CMPE 151: Network Administration. Clients. Client-Server Model. Client-Server Model. Client. File Server. Printer Server. Kernel. Kernel. Kernel. File transfer. File transfer. Sharing remote files: “on-line” access versus “file transfer”.

jud
Download Presentation

CMPE 151: Network Administration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CMPE 151: Network Administration Clients Winter 2005

  2. Client-Server Model Winter 2005

  3. Client-Server Model Client File Server Printer Server Kernel Kernel Kernel Winter 2005

  4. File transfer Winter 2005

  5. 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. Winter 2005

  6. 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). Winter 2005

  7. FTP Operation Client Server Data Control Data Control OS OS TCP connection Winter 2005

  8. Anonymous FTP • Allows access to public files. • No need to authenticate user. • Access restricted to publicly available files (e.g., in /usr/ftp). Winter 2005

  9. The Web and HTTP Winter 2005

  10. 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 Winter 2005

  11. 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. Winter 2005

  12. 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. Winter 2005

  13. 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. Winter 2005

  14. 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. Winter 2005

  15. DNS Winter 2005

  16. 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. Winter 2005

  17. DNS • Basic function: translation of names (ASCII strings) to network (IP) addresses and vice-versa. • Example: • zephyr.isi.edu <-> 128.9.160.160 Winter 2005

  18. 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 Winter 2005

  19. Top-Level Domains (TLDs) • TLD names identify organization types or country codes. • Examples:.com 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

  20. 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

  21. Example DNS Hierarchy Winter 2005

  22. 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. Winter 2005

  23. Example of DNS Hierarchy Winter 2005

  24. Example of DSN Hierarchy Winter 2005

  25. 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. Winter 2005

  26. 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

  27. 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. Winter 2005

  28. 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. Winter 2005

  29. 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. Winter 2005

  30. 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. Winter 2005

  31. Mail system User sends mail Outgoing mail spool TCP connection (outgoing) Client (send) User interface Mailboxes incoming mail User reads mail TCP connection (incoming) Server (receive) Winter 2005

  32. 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). Winter 2005

  33. Remote access Winter 2005

  34. Telnet User’s machine Telnet client Telnet server OS OS TCP connection over Internet Winter 2005

  35. 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. Winter 2005

More Related