Home
Islam and Internet
ALAM Maritime
MISC Malaysia
What is Internet
American People
Rotterdam
50 States
Provinces of Canada
Palm Tree
TCP IP
Concept of Network
Specialized Servers
Workstaion Vs Server
Quraan in English
Dr Israr Ahmad
Poetry
Introducing NT
NT Protocols
Win NT Services
The Islands
Cool Links
Islamabad
|
| NT Networking Protocols |
 |
| The Protocols used by Windows NT OSs |
Windows NT provides the following networking protocols
TCP/IP
NWLink
NetBEUI
DLC
AppleTalk
____________________________________________________________
A brief description of the protocols follows.
TCP/IP:
TCP/IP is one of the most popular network protocols on LANs. It is a scalable routable protocol ideal for large networks. The popularity of TCP/IP on the Internet has meant a renewed interest in support for the protocol. Within TCP/IP each device gets a unique IP address. No two devices on the sane network should have the same IP address or conflicts will occur and networking will become unstable.
The TCP/IP protocol also uses a subnet mask which is applied to IP addresses to determine whether a destination machine is on the same network as the source. After the subnet mask has been applied (a binary AND) the sending device compares the result for the destination machine with the result for its own IP address. If they are the same then the destination machine is on the same network and communication commences. If they are different then the sender routes the packets via the default gateway. This is a simplified explanation of the TCP/IP protocol and more information can be found in the TCP/IP training guide.
____________________________________________________________
NWLink:
NWLink is Microsofts IPX/SPX protocol. IPX was originally developed by Xerox and became popular in Novell networks. Like TCP/IP it is a routable protocol with peach packet being able to travel 15 hops through a network. The main reason to implement IPX today would be for interoperability with Novell NetWare machines.
NWLink has two possible frame types and it is important to understand the implications of this. The frame types are
802.2
802.3
Interestingly 802.3 was used in NetWare 3.x and 802.2 was used in NetWare 4.x The implication for NT administrators is that it is possible to configure the wrong frame type. NT offers the ability to autodetect the frame type, but even this can cause problems.
NetWare servers allow the binding of more than one frame type to the same network card, NT will try and auto detect 802.2 frame type first. What this can mean is NT successfully manages to communicate with one NetWare machine on 802.2 so configures that as its default protocol. Unfortunately all the other NetWare machines are configured for 802.3 and the NT machine will not be able to see them on the LAN.
____________________________________________________________
NetBEUI:
NetBEUI is a fast protocol with one major limitation. NetBEUI is not routable. This means that if a network has been subnetted NetBEUI will only allow communication on the local subnet. This is one of the reasons NetBEUI is fast. It does not have the packet overhead involved in trying to deal with route information.
NetBEUI is also notorious for causing lots of broadcasts on the network. These are recognised as being bad for network performance. Many small networks can make use of NetBEUI, they are not routed, the traffic is not high so broadcasts are not an issue, and NetBEUI is very easy to configure.
____________________________________________________________
DLC:
Unlike the other protocols DLC does not provide a full interface to the Transport Driver Interface. This means that the NT server and workstation service cannot make use of DLC to communicate with another NT device elsewhere on the network. DLC is used in an NT environment for two reasons.
Accessing IBM Mainframes.
Printing to network enable HP printers.
DLC only needs to be installed on the print server. All the computers printing to the HP printer can print to the queue on one NT machine. And that one NT machine is the only one that requires DLC installed.
____________________________________________________________
Appletalk:
Appletalk is used for the connectivity between NT and Apple Macintosh. Appletalk is actually a collection of protocols.
LocalTalk 230.4 Kbps
EtherTalk 10 Mbps
TokenTalk 16/4 Mbps
LocalTalk is Apples built in networking system. Although it is possible to install a LocalTalk card in an NT machine you can see from the table above that speed becomes an issue. It may be preferable to install EtherTalk cards in the existing Macintoshes.
____________________________________________________________
|
|