History
Carrying instructions between calculation machines and early computers was done by human users. In September 1940 George Stibitz used a teletype machine to send instructions for a problem set from his Model K at Dartmouth College in New Hampshire to his Complex Number Calculator in New York and received results back by the same means. Linking output systems like teletypes to computers was an interest at the Advanced Research Projects Agency (ARPA) when, in 1962, J.C.R. Licklider was hired and developed a working group he called the "Intergalactic Network", a precursor to the ARPANet. In 1964, researchers at Dartmouth developed the Dartmouth Time Sharing System for distributed users of large computer systems. The same year, at MIT, a research group supported by General Electric and Bell Labs used a computer (DEC's PDP-8) to route and manage telephone connections. Throughout 1960s Leonard Kleinrock, Paul Baran and Donald Davies had independently conceptualized and developed network systems consisting of datagrams or packets that could be used in a packet switching network between computer systems. In 1969 the University of California at Los Angeles, SRI (in Stanford), University of California at Santa Barbara, and the University of Utah were connected as the beginning of the ARPANet network using 50 kbit/s circuits.
Networks, and the technologies needed to connect and communicate through and between them, continue to drive computer hardware, software, and peripherals industries. This expansion is mirrored by growth in the numbers and types of users of networks from researcher
By network layer
See the seven layer OSI reference model and the four or five layer TCP/IP model
* Application layer
* Presentation layer (Only in the OSI model)
* Session layer (Only in the OSI model)
* Transport layer
* Network layer
* Data Link layer
o Media access control sublayer
o Logical link control sublayer
* Physical layer
By scale
* Personal area network (PAN)
* Local area network (LAN)
o Wireless local area network(WLAN)
* Campus area network (CAN)
* Metropolitan area network (MAN)
* Wide area network (WAN)
By connection method
* HomePNA
* Power line communication
* Ethernet
* WiFi
By functional relationship
* Active Networking (Low-level code movement versus static data)
* Client-server
* Peer-to-peer (Workgroup)
By network topology
* Bus network
* Star network
* Ring network
* Mesh network
* Star-bus network
* Tree topology network
By Services provided
* Storage area networks
* Server farms
* Process control networks
* Value-added network
* SOHO network
* Wireless community network
* XML appliance
* Jungle Networks
Protocol stacks
Computer networks may be implemented using a variety of protocol stack architectures, computer buses or combinations of media and protocol layers, incorporating one or more of:
* ARCNET
* AppleTalk
* ATM
* Bluetooth
* DECnet
* Ethernet
* FDDI
* Frame relay
* HIPPI
* IEEE 1394 aka FireWire, iLink
* IEEE 802.11 aka Wireless LAN (Wi-Fi certification)
* IEEE-488
* Internet protocol suite
* IPX
* Myrinet
* OSI protocol suite
* QsNet
* RS-232
* SPX
* System Network Architecture
* Token ring
* TCP
o TCP Tuning for discussion of improving performance of same
* USB
* UDP
* X.25 protocol suite
For a list of more see Network protocols.
For standards see IEEE 802.
Suggested topics
Further reading for acquiring an in-depth understanding of computer networks include:
* Communication theory
Data transmission
Wired transmission
* Public switched telephone network
o Modems and dialup
* Dedicated lines – leased lines
* ISDN
* DSL
* Time-division multiplexing(TDM)
* Packet switching
* Frame relay
* PDH
* Ethernet
* RS-232
* RS-485
* Optical fiber transmission
o Synchronous optical networking(SONET)
o Fiber distributed data interface
Wireless transmission
* Extreme Short range
o ZigBee
* Short range
o Bluetooth
o InfraRed(IrDA)
* Medium range
o WiFi(IEEE 802.11)
o WiMax(IEEE 802.16)
* Long range
o Satellite
o MMDS
o SMDS
o Mobile phone data transmission (channel access methods)
+ CDMA
+ CDPD
+ GSM
+ TDMA
o Paging networks
+ DataTAC
+ Mobitex
+ Motient
Other
* Computer networking device
o Network card
* Naming schemes
* Network monitoring
2006-12-01 00:05:35
·
answer #1
·
answered by mr nice 2
·
0⤊
2⤋
If your organization can afford fiber optic cabling and appropriate connecting networking hardware, it's the best solution. --300-400 feet is well within the typical 6000 foot distance that multi-mode fiber can work on a link. --electrical isolation. This seems unimportant until you have electrical problems or a lightning strike in one building, and the path to ground is through your underground link and your networking equipment. Another option is coaxial cable, though it's quite old-school. 10-base-2 on ancient thicknet or RG-58 thinnet can run 200 meters. However, electrical grounding of one end is important to avoid the electrical ground problems mentioned above. While all unshielded twisted pair solutions (10-base-T, 100-base-T, 1000-base-T) all give 100 meters as the operational radius, you can push it beyond the limit, such as a link between two routers or two switches. The pitfalls are --possible signal degradation problems over extended distance --possible signal delay problems due to excessive distance that will cause poor performance - excessive signal collisions and re-transmissions. A final option is a point-to-point radio link using wireless ethernet bridges and directional antennas. This also gives the electrical isolation and no hassle with right-of-way for burying cable, but has the disadvantages of unpredictable performance and subject to weather and other interferences. But given the relatively short distance, I believe this may be your easiest option.
2016-03-13 01:20:56
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋
A network segment is a portion of a computer network separated by a computer networking device, including:
Repeater or Ethernet hub (both OSI layer 1 devices)
Bridge or switch (both OSI layer 2 devices)
Router (OSI layer 3 device
2006-12-03 20:29:27
·
answer #3
·
answered by abhi 2
·
0⤊
0⤋
You're asking a whole lot more than you can answer in a post. Configuring router protocols alone is a job for a dedicated professional. You need to spring for a network essentials book to get started.
2006-12-01 00:38:55
·
answer #4
·
answered by Nomadd 7
·
0⤊
0⤋