Organizing II.


69 views
Uploaded on:
Category: Sales / Marketing
Description
The correspondence programming utilized by PCs on a system must consent to take after the same convention ... PCs whose selective (or principle) systems administration needs are to talk ...
Transcripts
Slide 1

Organizing II Communication Protocols TCP/IP

Slide 2

Communication programming Regardless of the equipment used to associate arranged PCs, they additionally require correspondence programming so as to convey adequately The product principles and dialect utilized by PCs on a system to speak with each other is known as the system convention Rules incorporate things like: Transmission rate Pre-settled upon codes for things like "are you prepared yet—I\'m going to start sending an information record" or "Did you get the document I simply sent" The correspondence programming utilized by PCs on a system must consent to take after the same convention Eg : If two PCs don\'t concur on transmission speed (one "talks" at 56,600 bps and alternate "tunes in" at 28,800, the message won\'t get past.

Slide 3

Forms of correspondence programming Communication programming can take an assortment of structures Computers whose selective (or fundamental) organizing necessities are to talk with different PCs on a LAN may utilize system working framework programming (NOS, for example, Novell\'s Netware or Microsoft\'s Windows Server or Apple\'s AppleTalk similarly that an OS conceals the internal workings of huge numbers of a PC\'s doings, a NOS shrouds the inward workings of system interchanges A NOS must have the capacity to react to demands from different PCs on the LAN and must be designed to concur on the different conventions

Slide 4

Quick audit of some system sorts: Peer-to-Peer Client Server Host-Terminal

Slide 5

Host-Terminal Network An exceptionally essential and to some degree dated type of correspondence includes a host which has the greater part of the data. A progression of "idiotic terminals" can associate with that host The "imbecilic" terminal (that is, a console and a screen with no preparing power) interfaces with a host The host holds the greater part of the essential data All the terminal can do is send inquiries to the host. The host sends back the answers which are imprinted on the screen. There is no graphical client interface. That is, it\'s all content based. Was exceptionally prominent in reservations frameworks, for example, when buying plane or prepare tickets Less normal these days

Slide 6

Peer-to-Peer system Users can share assets and documents on their PCs with different clients on the system No concentrated source E.g. On the off chance that the common printer on your system happens to be in somebody elses\' office and that individual is out for the day with their PC off, you\'re in a tough situation. Has the upsides of being entirely simple to set up and not requiring a committed server Disadvantages of not being concentrated and not having the security includes generally found in devoted system programming

Slide 7

Client-server organize The system can bring together documents and assets in one or more servers Computers associated with the system can get to the server to ask for those assets (records, peripherals, and so forth)

Slide 8

NOS and LAN Type The decision and usefulness of a NOS relies on upon the kind of system. Numerous systems are set up as indicated by a customer server model One or more PCs go about as devoted servers to serve information (records, music, spreadsheets, and so on), peripherals (print server), or other system assets These are normally speedier, higher limit PCs most of the PCs go about as customers who "ask for" these assets from the server The server will run NOS Server programming, and the customers will run NOS Client programming Small systems are here and there outlined utilizing the distributed model (P2P) in which every PC goes about as both a server and a customer. That is, any one PC can make a solicitation of whatever other PC on the system Many home desktop OSs, for example, Windows and Mac frameworks have this kind of systems administration pre-introduced This is the way you can share documents and peripherals among various PCs in your home Many systems are mixtures of these two models (Client/Server and P2P)

Slide 9

A case of P2P being used This discourse box permits me to share the \'My Music\' organizer on my PC with some other PC on my system. Be that as it may, some sort of P2P programming must be available both on this PC and on all other on the system with the end goal them should have the capacity to share the asset.

Slide 10

Example – Client for MS Networks Here is an illustration demonstrating P2P programming introduced on a PC Most Windows PCs come introduced with a fundamental NOS customer called \'Customer for Microsoft Networks\' This customer permits the PC to speak with different PCs on the same system (e.g. different PCs at your home) to do things like offer records, organizers, printers, and other system assets The last choice (not appeared) is TCP/IP – we\'ll talk about this without further ado

Slide 11

Example: a PC with Novell\'s Netware introduced

Slide 12

Intranets These days, numerous LAN chairmen no more try obtaining and introducing NOS programming. Rather, they outline their system convention taking into account an intranet framework. An intranet is a framework worked around the conventions and principles utilized by the web.

Slide 13

The Mother of all Networks: The Internet We\'ll talk about specifics of the web in a later address For now we will concentrate on the system convention utilized by the web, TCP/IP

Slide 14

Why TCP/IP? Two noteworthy focal points over other system conventions/NOSs Internetworking : this convention was produced as an examination in internetworking – that is, interfacing distinctive sorts of systems and NOSs E.g. A Novell system can converse with an AppleTalk system gave that they can both "speak TCP/IP" Open Standard : The TCP/IP specs are not claimed by any organization. Any organized PC can unreservedly introduce TCP/IP accordingly, when the web was at first imagined (as something many refer to as ARPANET), TCP/IP was picked as the systems administration convention

Slide 15

Overview of TCP/IP TCP/IP is one method for controlling how messages can be conveyed over a system. TCP: Transmission Control Protocol IP: Internet Protocol Some of the "standards" determined by this convention: Every bit of information sent over a system must be broken into a progression of little bundles . A parcel is normally 1000-1500 bytes Each bundle must contain: The information (eg a little bit of a MP3 melody) Sender\'s area (IP address) Receiver\'s area (IP address) An arrangement number (so that the bundle can be reassembled once more into its unique entire) And a couple of different things This entire procedure takes milliseconds! Breaking a message into parcels Sequencing the bundles Assigning locations to every bundle Routing bundles to the destination Reassembling the parcels into the entire

Slide 16

An improved perspective of a parcel

Slide 17

Routing Every parcel is directed through a progression of switches to its definitive destination. Diverse parcels from the same message may take an alternate course, yet every one of the bundles will at last make it to the suitable destination. One at the destination, the parcel is reassembled into the entire message (e.g. the complete MP3 tune) The TCP part is in charge of doling out an appropriate arrangement to every parcel with the goal that it can be reassembled IP part is in charge of organizing the sending and getting addresses The reason the web all in all never goes "down" is that a solitary bundle can take a large number of various courses to touch base at its destination So regardless of the possibility that a given zone is down or moderate, the bundle can utilize an alternate course to achieve its destination

Slide 18

IP – Internet Protocol IP is the tending to arrangement of the web Every PC associated with the web has a one of a kind "IP address" No two PCs have the same address An IP location is comprised of 4 numbers isolated by periods ("specks") E.g. 140.192.1.6 is the IP location of the PC facilitating the web server www.depaul.edu Every bundle directed through the web contains the IP location of both the sending and accepting PC Conversion between the IP address (e.g. 140.192.1.6) and the recognizable names that we get a kick out of the chance to utilize (www.depaul.edu) is the obligation of a space name framework server (DNS server) More on this in no time

Slide 19

Who appoints IP addresses? Locations are dispensed by a territorial web registry (RIR) Larger associations are given whole squares of locations (e.g. 140.192 was given to DePaul) The association can then dispense the staying two arrangements of numbers to the greater part of the PCs in its system For instance, DePaul possesses 140.192 (and can assign the staying two arrangements of numbers as it wishes) E.g. it designated the 1.6 (140.192. 1.6 ) toward the end to the college\'s primary web server Similarly, ABC News claims 199.181 and can assign the rest of it wishes

Slide 20

Static v.s . Dynamic IP Addresses An IP location can be static or element A static IP location is for all time doled out to a PC Most web servers have static IP addresses If a PC has a dynamic IP address, it implies that the IP address for that PC transforms This is quite often the situation when you interface with the web utilizing WiFi . The ISP giving the web association doles out you a one of a kind IP address for the span of your association. When you detach, the location is arranged for another person to utilize. Whenever you interface, you get a fresh out of the plastic new IP address, which, once more, will last until you detach This circumstance at times applies to broadband (dependably on) associations also

Slide 21

What\'s my IP Address ? www.whatsmyipaddy.com

Slide 22

Why we don\'t regularly utilize/see IP addresses Clearly, www.depaul.edu is significantly more easy to use than 140.192.1.6 TRY IT! Go to your program and sort: http://140.192.1.6 The reason we don\'t need to manage those revolting numbers is on account of the web\'s area name framework (DNS) Some case of space names : depaul.edu newyorktimes.com facebook.com DNS servers keep up tables that guide area names (e.g. depaul.edu) to IP addresses (e.g. 140.192) E.g. At whatever point you t

Recommended
View more...