Frame Corner

Frame Top

GSW Study Notes Home

GSW MCSE Notes Home Networking Essentials Notes NT Server 4.0 Notes NT Administration Notes

Module 10: Configuring Windows NT Protocols

Installing and Configuring Network Adapter Card Drivers

Each network adapter card has one or more corresponding network driver interface specification (NDIS) 4.0 compatible drivers that coordinate communications between network adapter cards and the computer’s hardware, firmware and software.

To configure network adapter card drivers, in Contol Panel, double click Network and click Adapters tab. This tab has following options:
 

Option

Use this option to

Add Add network adapter card driver to computer
Remove Remove selected network adapter card driver from the system
Properties View and change the settings for a selected driver (IRQ, I/O port address, I/O channel and transceiver type
Update Update the driver info for a selected network adapter card (give pathname) 

Note: Removing protocols or NIC drivers does not remove the files from disks.
 

Installing and Configuring Protocols:

Microsoft TCP/IP Protocol Suite

Protocol

This protocol provides

Simple Network Management Protocol (SNMP)
  • Management Information Base (MIB) monitoring data contained in SNMP
Windows Sockets (WinSock)
  • Standard interface between socket-based application and TCP/IP protocols
NetBIOS over TCP/IP (NetBT)
  • NetBIOS services, including name, datagram and session services
Transmission Control Protocol (TCP)
  • Connection-oriented, guaranteed packet delivery services
User Datagram Protocol (UDP)
  • Connectionless packet delivery services that are not guaranteed
Internet Control Message Protocol (ICMP)
  • Special communication between hosts.
  • Reports messages and errors regarding packet delivery
Internet Protocol (IP)
  • Address and routing functions
Address Resolution Protocol (ARP)
  • IP address mapping to the media access control (MAC) sublayer address

 

Configuring TCP/IP manually

Control Panel, Network, Protocols tab and then double click TCP/IP Protocol. Microsoft TCP/IP Properties dialog box. For each network adapter card that uses TCP/IP three parameters can be configured:

Parameter

Description

IP Address
  • 32-bit address used to identify TCP/IP host;
  • Each address has 2 parts: network ID and host ID
    • the network ID identifies all the hosts that are on the same physical network
    • the host ID identifies a host on the network
Subnet Mask
  • Network in a multiple network environment that uses IP addresses derived from a single network ID, it blocks out part of the IP address, so that TCP/IP can distinguish network ID from host ID
  • When TCP/IP hosts try to communicate, the subnet mask is used to determine whether the destination host is located on a local network or a remote network
Default Gateway
  • For communication with host on another network, an IP address should be configured for the default gateway.
  • TCP/IP sends packets for remote networks to default gateway if no other route is configured. If it is not configured, communication may be limited to local network.
Configuring TCP/IP Automatically
Testing TCP/IP with Ipconfig and Ping

IPCONFIG /renew [adapter]

IPCONFIG /renew [adapter]

Ping

Ping examples

Pinging the IP address and then "localhost"

Using the -a resolves address to host names:

Using the -r switch records the route of the outgoing packet
(3 in the example below is the "count" parameter and specifies the number of hosts to available to hop to.)

 

Using TCP/IP utilities

Utility

Function

Packet InterNet Groper (Ping) Verifies configurations and tests connections
File Transfer Protocol (FTP) Bidirectional file transfer between computer running Windows NT and any TCP/IP host running FTP
Trivial File Transfer Protocol (TFTP) Bidirectional file transfer between computer running Windows NT and any TCP/IP host running TFTP
Telnet Terminal emulation to TCP/IP host
Remote Copy Protocol (RCP) Copies files between computer running Windows NT and Unix host
Remote shell (RSH) Runs commands on Unix host
Remote execution (REXEC) Runs process on remote computer
Finger Retrieves system information from a remote computer that supports TCP/IP and Finger service
Microsoft Internet Explorer Locates resources on Internet
ARP Displays locally resolved IP addresses as physical  (MAC) addresses
Ipconfig Displays current TCP/IP configuration
Nbtstat Displays protocol statistics and connections using NetBIOS over TCP/IP
Netstat Displays TCP/IP protocol statistics and connections
Route Displays or modifies local network routing tables
Hostname Returns local computer’s hostname for authentication by RCP, RSH and REXEC utilities
Tracert
  • Checks route to remote system
  • sends ICMP (Internet Control Message Protocol) echo packets with varying TTL (time to live) values to the destination
  • some routers may be invisible to tracert

EXAMPLES

Netstat

Tracert

Tracert switches

Example of tracert using a remote host name

Hostname


 

NWLink

NWLink IPX/SPX Compatible Transport supports these API's:

Networking API

Description

WinSock Supports existing applications written to comply with the Netware IPX/SPX Sockets interface. Used to communicate with NLMs
NetBIOS over IPX Supports communication between a NetWare client running NetBIOS and a computer running Windows NT and NWLink NetBIOS

Access to file and print resources on Windows NT you must install File and Print Services for NetWare.

Configuring NWLink

Topology

Supported frame type

Ethernet Ethernet II, 802.3, 802.2, and SNAP default 802.2
Token Ring 802.5 and SNAP
Fiber Distributed Data Interface (FDDI) 802.2 and SNAP 
  SNAP = Sub Network Access Protocol
  Default Frame Type
NetWare 2.2; 3.11 802.3
NetWare 3.12 and later 802.2

Some of these notes in this section overlap, but were needed to provide a complete picture

One version:
 

Network number and Internal Network Number
  • Network number is used to identify the network segment that you need to access.
    • Windows NT uses an IPX network number for routing purposes. 
    • IPX network number is also referred to as the external network number and must be unique for each network segment.
    • You then assign a network number to each configured frame type and adapter combination on your computer.

And another version

NWLink IPX/SPX compatible transport protocol included with Windows NT uses two types of network numbers.

  • 0 à NWLink will get network number from running network.
  • IPX network numbers are 4 bytes (8 hexadecimal characters)
PktType value Packet form
0 Ethernet_II
1 Ethernet_802.3
2 802.2
3 SNAP
4 ArcNet
FF Auto-detect

Both are set in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

Services\Nwlnkipx\NetConfig\adapter

One version:

  • Internal Network Number is used to identify your computer on the network.
    • Internal network number uniquely identifies the computer on the network for internal routing.
    • This number is also known as virtual network number and is separated by an eight-digit hexadecimal number. 
    • NT doesn't automatically detect the internal network number. You need to manually assign a unique non-zero internal network number in the following situation.
      • You have File and Print Services for NetWare (FPNW) installed, and you choose multiple frame types on a single adapter.
      • You have bound NWLink to multiple adapters in your computer.

      • Your computer is acting as a Windows NT server for an application that uses the NetWare Service Advertising Protocol (SAP), such as SQL or SNA.

Another version:

Routing Information Protocol

NetBEUI

NetBIOS extended user interface (NetBEUI) is a protocol developed for small LANs (20-200).

NetBEUI Frame (NBF) is the implementation of NetBEUI that is included in Windows NT. It provides interoperability with older network systems such as Microsoft LAN Manager and Microsoft Windows for Workgroups 3.11

Capabilities for Windows NT:

     

  1. Connection-oriented and connectionless communication between computers.
  2. Self-configuration and self-tuning
  3. Error protection
  4. Small memory overhead
Configuring Network Bindings

What is the effect of moving bound protocols up and down the binding order?

Configuring Network Bindings

Select the Bindings tab after double clicking Network program in Control Panel

Option Use this option to
Show bindings for View bindings for all services, all protocols or all adapters
Enable Enable the selected binding path (also beneath selected component)
Disable Disable the selected binding path (also beneath selected component)
Move Up/Move down Move selected binding up or down in binding list

Here's a good example of a whole tree
See what you can learn about how services like WINS and DHCP work from this list

An example of the list by installed protocol:

Top of Page Top of page

E-mail Me! Comments and suggestions? E-mail me at grantwilson21@yahoo.com
I'm sorry, but I can't answer specific network-related, or exam-related questions.
Last Updated: August 6, 2001 Grant Wilson, Edmonton, AB Canada