Network Communication

To make network communication possible we will need a Driver. Here are some specifications of different drivers available:

• Packet drivers - freely available set of drivers on the net maintained by ftp Software and also in part by Russell Nelson of Crynwyr.
• NDIS v2.0 & v3.0 - Network Device Interface Specification developed by Microsoft and 3Com. Version 2.0 is the current version for MS-Windows and Windows for Workgroups. Version 3.0 is the new specification for MS-Windows NT.
• ODI - Open Driver Interface developed by Novell, Inc.
• SLIP, PPP - These are more protocol specifications for serial and distance links. Both are defined in the Internet RFCs. PPP is described initially in RFC 1172 with related descriptions in 1331, 1332, 1333, 1334, 1376, 1377, 1378, and several newer ones. SLIP is described in RFC 1055.

We will also need a NOS (Network Operating System). Here are some comparsons of different systems and there features:

* W4W = Microsoft Windows for Workgroups

* ATalk = AppleTalk

* LAN Srv/Sp = IBMs PC LAN Server or LAN Support

This diagram is in the process of revision. Come back soon!

Thanks to Rawn Shah for this great diagram...

You will also need a Socket

For example lets look at Novell's Netware. The Socket Client used is Winsock. Winsock is an API developed as a standard for network based communications in MS Windows.

So How do they all work together?

The user makes a request (Novell's network Protocol is SPX/IPX). The request is sent in the form of Packets. A 25 page document might take hundreds of Packets to send from one computer to another, but on a good Ethernet network this would take about 1/3 of a secound. Here is a diagram I made of a packet.

In order to send a packet you must have the source IP Address (Your Computer) and the destination IP Address (Computer you are sending Info to)... These IP Addresses are assigned by the InterNIC, and are necessary in the network communication process.

The NIC sends out an ARP (Address Resolution Protocol) An ARP packet listens for addresses. If the IP address is within its Ethernet the Packet stays within the LAN. If not then it is passed on to the Router were the Ethernet Address is striped off & it is assigned a Gateway IP Address. The Packet is then sent to the ISP Router where it is then sent to its destination address on the internet.