CHAPTER 10
CONFIGURING WINDOWS NT PROTOCOLS
Lesson 1:
Using the Network Program in Control Panel
The Network program in Control Panel is used to install and configure Windows NT networking
components such as protocols and network adapter card drivers, and to configure bindings.
It is also used to change a computer name, specify a workgroup or domain, and establish
domain account for the computer.
Installing and Configuring Network Adapter Card Drivers
Network adapter card drivers are typically installed during Setup, when hardware is changed,
or when drivers need to be
updated. Use the Adapters tab in the
Network dialog box in Control
Panel to configure network adapter card drivers.
=====================================================================
Option Use this option to
=====================================================================
Add Add a network adapter card driver to a computer.
Remove Remove the selected network adapter card driver from the
System configuration. Removing the driver does not
Delete the file from the hard drive. Therefore, you can
Add the driver again, if necessary.
Properties View and change the settings for the selected driver. Click
the Properties button and the Setup dialog box to configure
the appropriate settings, such as the IRQ level, I/O ports
address, I/O channel, and the tranceiver type for a selected
network adapter card.
Update Update the driver information for a selected network
adapter card. When you click this button, you are prompted
to provide a path to the upgrade driver files.
======================================================================
wntsup10.html PAGE 2 2001/11/13
Installing and Configuring Protocols
Protocols, such as NWLink IPX/SPX Compatible Transport, NetBEUI, and TCP/IP provide a
mechanism for computers to connect with each other and exchange information over a network.
Protocols communicate with network adapter cards by means of NDIS 4.0 compatible network
adapter card drivers.
In addition, Windows NT supports multiple protocols, bound to one or
more adapters, simultaneously.
Use the Protocols tab in the Network dialog box, in the Control Panel to install and configure protocols.
=======================================================================
Option Function
=======================================================================
Add Add a protocol to the system configuration.
Remove Remove the selected protocol from the system configuration.
removing the protocol does not delete the protocol files from
the hard disk. Although the protocol can be added again by
using the files that are currently on the hard disk, the
recommended method is to use the original source, such as a
network share or the Microsoft Windows NT operating system
Compact disc.
Properties View and configure settings for the selected protocol
Update Update the selected protocol. When you click the Update
button, you are prompted for the path to the upgrade files.
======================================================================
Lesson 2:
NWLink
NWLink IPX/SPX Compatible Transport protocol is the Microsoft 32-bit NDIS 4.0 compliant
version of Novell’s Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX)
protocol.
NWLink is most commonly used in network environments where Microsoft clients need to access
client/server applications running on Novell NetWare servers, or NetWare clients need to access
client/server applications running on computers running Windows NT.
NWLink allows computers running Windows NT to communicate with other network devices that
are using IPX/SPX, such as HP Jet Direct printers.
=====================================================================
wntsup9.html PAGE 3 2001/11/09
NWLink supports the following networking APIs that provide IPC
services:
with the NetWare IPX/SPX Sockets interface. WinSock is commonly used for
communicating with NetWare Loadable Modules (NLMs). Customers implementing
client/server solutions using NLMs can port them to Windows NT Server and still
retain compatibility with their clients.
NetWare workstation running NetBIOS and a Windows NT-based computer running
NWLink NetBIOS.
Configuring NWLink
There are two options that must be configured when installing and configuring NWLink IPX/SPX
Compatibile Transport. Frame type and Network Number.
NWLink is routable, chatty, and has a frame type
of 802.2.
Frame Types
A frame type defines the way in which the network adapter card formats data to be sent over the
network.
Novell = 3.11 version
with a frame type of 802.3.
Novell = 3.12 version
with a frame type of 802.2 (variable length, default)
It is possible for a connection to be established between two computers that are using different
frame types on the network, when
one of those computers is a NetWare computer acting as a router.
A router is a device that is used to connect networks of different types, such as those using different
architectures and protocols.
Configuring Frame Types
Frame types are configured through the Network program in Control Panel. Use the NWLINK
IPX/SPX Properties dialog box to designate a frame type for each network adapter card on the
computer.
=====================================================================
wntsup9.html PAGE 4
2001/11/09
Network Number and Internal Network Number
The network number ID number is a 8 bit hexadecimal number. By Default, the internal network
number is (00000000).
Two Network numbers must be connected to Novell Netware, and you need an 8-digit Virtual
Network Number, which the user chooses.
SAP is used on Novell. It is an advertising Service Protocol. SAP allows service-providing nodes,
file servers, print servers, gateways servers, and application servers to advertise their services and
addresses. SAP is very chatty. By default the SAP broadcasts its presence every 60 seconds.
RIP is also supported by NWLink. RIP or Routing Information Protocol is an extra field of data
added to the packet to improve the decision criteria for selecting the fastest route. Each time the
RIP goes to the router it is called a HOP, and it can have a limit of 16 hops. Microsoft NT is the
only Operating System that supports RIP.
Lesson 3:
NetBEUI
NetBIOS extended user interface (NetBEUIP) is a protocol developed for small departmental
local area networks (LANs) of 20 to 200 computers. NetBEUI is not suitable for wide-area
networks because it cannot be routed. But it is FAST.
NetBEUI is non-routable, broadcast-based protocol. Because NetBEUI relies on broadcasts
from many of its functions, such a name registration and discovery, its use cause more broadcast
traffic than other protocols.
NetBEUI is backward compatible, and is great for quick setups.
NetBIOS/NetBEUI is like the three-way handshake, doing many functions at the same time.
Lesson 4:
Microsoft TCP/IP **KNOW for MCSE test**
TCP/IP is a networking protocol that provides communication across interconnected networks
made up of computers with diverse hardware architectures and various operating systems.
TCP/IP is a flexible suite of protocols designed for wide area networks (WANs) and adaptable
to a wide range of network hardware. TCP/IP can be used to communicate with Windows NT
systems, with devices that use other Microsoft networking products, and with non-Microsoft
systems, such as UNIX systems.
TCP/IP is free, is routable, there are lots of utilities for it, and it is universal.
=====================================================================
wntsup9.html PAGE 5
2001/11/09
SNMP is simple Network Management Protocol and uses MIBs to monitor data, it is used at
the Application layer of the TCP/IP.
WinSock is a standard interface between socket-based applications and TCP/IP protocols.
WinSock is at the Application Layer of the TCP/IP.
NetBIOS over TCP/IP BetBT includes name, datagram and session services.
This is at the Application layer of the TCP/IP protocol stack.
TCP or Transmission Control Protocol is connection-oriented, and guarantees packet
delivery services. This
is a Transport Layer Protocol.
UDP or User Datagram Protocol is connectionless packet delivery services that are not
guaranteed. This is a Transport Layer Protocol.
ICMP or Internet Control Message Protocol is special communication between hosts.
Reports messages and errors regarding packet delivery. This is a Internet Layer Protocol.
IP or Internet Protocol is address and routing functions. Works at the Internet layer of the
TCP/IP protocol stack.
ARP or Address Resolution Protocol uses the IP address mapping to the media access
control sublayer address. ARP works at the Internet layer of the TCP/IP.
Use this shortcut first with the
you are connected correctly to the network. If it does not, then you must go through the
entire process.
Configuring TCP/IP Manually
If you are not using Dynamic Host Configuring Protocol (DHCP) to automatically assign the
P addresses, you have to configure TCP/IP manually. To configure TCP/IP manually after
it has been installed, you use the
Protocols tab in the Network program in Control
Panel.
Here is an example of
some TCP/IP Protocol Addresses:
=====================================================================
wntsup9.html PAGE 6
2001/11/09
IP Address: 131 .107 .2 .200
Subnet Mask: 255 .255 .0 .0
Default Gateway: 131 .107 .2 .1
(NOTE: The loop-back address is 127 .0
.0 .1)
The selections in
Control Panel/Network/Properties tabs are:
Using TCP/IP Utilities
Windows NT utilities that work with TCP/IP protocols to provide networking capabilities:
=======================================================================
Utility Function
=======================================================================
PING Verifies configuration and tests connections.
Packet Internet Groper utility.
FTP File Transfer Protocol, bi-directional file transfers between a computer
Running Windows NT and any TCP/IP host running FTP. Allows you
To download files from the Internet, at the Command Line.
FTP is an anonymous site, uses E-Mail address to verify.
TFTP Bi-directional file transfers between Windows NT and any TCP/IP
Host running TFTP.
Telnet Provides terminal emulation to a TCP/IP host running Telnet.
RCP Copies files between a computer running Windows NT and a
UNIX hosts.
RSH Remote Shell, runs commands on a UNIX host.
REXEC Runs a process on a remote computer.
Finger Points and retrieves information from a remote computer.
=====================================================================
wntsup9.html PAGE 7
2001/11/09
======================================================================
Utility Function
======================================================================
Microsoft
Internet
Explorer Locates resources on the internet.
ARP Displays a cache of locally resolved IP addresses to physical
Addresses. Likes to work with #s versus Names.
Ipconfig Displays the current TCP/IP configuration.
Nbtstat Displays protocol statistics and connections using NetBIOS
Over TCP/IP.
Netstat Displays TCP/IP protocols statistics and connections. Shows who
Is opening and closing ports.
Route Displays or modifies the local routing table.
Hostname Returns the local computer’s host name for authentication by the
RCP, RSH, and REXEC utilities.
Tracert Checks the route to a remote system.
Shows each Hop on an internet path.
DHCP Dynamic Host Configuration Protocol
=======================================================================
When DHCP is configured on a network, clients that support DHCP, such as Windows NT Server
and Windows NT Workstation, can request the TCP/IP configuration parameters from the DHCP
server, (IP address, subnet mask, and a default gateway).
Lesson 5:
Network Binding:
Network bindings are links that enable communication between network adapter card drivers,
protocols, and services.
You can bind a network component to one or more network component above or below it.
The services each component provides can be shared by all other components bound to it.
Bindings are enabled or disabled depending on their need.
Start/Control
Panel/Network/Bindings tab.
=====================================================================
wntsup9.html PAGE 8
2001/11/09
Summary:
and configured using the Network program in Control Panel.
clients to access client/server applications on computers running Windows NT, and allows
Microsoft clients to access client/server applications on a NetWare Server.
because it cannot be routed. NetBEUI is mostly used for older, existing LANs because it is
compatible with the NetBEUI protocol driver shipped with older Microsoft networking products.
To configure TCP/IP manually you must supply an appropriate value for the IP address and the
subnet mask. For communication with a remote network, you must also specify a default gateway.
The default gateway is where the IP sends packets that are destined for remote networks. If you do
not specify a default gateway, communications are limited to the local network. TCP/IP configuration
values can also be configured automatically by using a DHCP
server. Use the
network connections after TCP/IP is configured.
services and enable communication between these components. Windows NT automatically
binds all dependent network components. However, bindings can be enabled, disabled, and
ordered to optimize network communication.