Network Protocols

1
Network Protocols

• Transmission Control Protocol/Internet Protocol
  (TCP/IP)
• Asynchronous Transfer Mode (ATM)
• NWLink
• NetBIOS Enhanced User Interface (NetBEUI)
• AppleTalk
• Data Link Control (DLC)
• Infrared Data Association (IrDA)
• SNA not included in Windows 2000
• Separate SNA Server product available

2
Introduction to Network Protocols

• A protocol is a set of rules and conventions for
  sending information over a network.
• Protocols can be added or deleted at will and
  selectively bound to all network interfaces.
• Binding order is determined by the order in which
  the protocols were initially installed.
• Binding order can be changed at any time on a
  per-interface basis.
• Network services can be selectively enabled or
  disabled on a per-adapter or per-protocol basis.

3
TCP/IP

• The TCP/IP suite has been adopted by Microsoft as
  the strategic enterprise transport protocol for
  Microsoft Windows 2000.
• The Windows 2000 TCP/IP suite is designed to make
  it easy to integrate Microsoft enterprise
  networks into large-scale corporate, government,
  and public networks.

4
ATM

• Voice, video
• Very high speed networking
• Up to T3 - 44.736 Mbps
• Fixed length cells
• PVCs or SVCs
• QoS
• Window 2000 supports
• LANE
• IP over ATM
• ATM over xDSL
• Native ATM

5
ATM

• LANE
• Connectionless protocols can communicate over ATM
• IP over ATM
• Alternative to LANE
• ATMARP server maps IP addresses to ATM address
• ATM over xDSL
• Uses POTS
• Connects to a ATM backbone
• Preserves ATM speed and QoS characteristics
• Native ATM
• Provided through WINSOCK 2.0
• Applications can create VCs and access QoS
  guarantees

6
NWLink

• NWLink is Microsofts implementation of the
  Novell NetWare IPX/SPX protocol.
• NWLink supports a number of topologies and frame
  types
• If Windows 2000 is to access Netware files and
  printers
• Client Service for Netware (CSNW)
• Gateway Service for NetWare (GSNW)
• Can not be primary protocol when running Active
  Directory

7
Frame Types

• Ethernet
• Token Ring
• FDDI

• Ethernet II, 802.3,802.2, SNAP
• 802.50and SNAP
• 802.2 and 802.3

8
NetBEUI

• NetBEUI is broadcast-based and is not routable
• NetBEUI provides compatibility with existing LANs
  that use the NetBEUI protocol.
• NetBEUI provides computers running Windows 2000
  with several capabilities.
• Can not be primary protocol when running Active
  Directory

9
AppleTalk

• Windows 2000 includes support for AppleTalk.
• AppleTalk allows Windows 2000 to be a router and
  a dial-up server.
• For the AppleTalk protocol to function properly,
• a Windows 2000 Server computer must be configured
  with Services for Macintosh and must be available
  on the network.

10
DLC

• Developed by IBM for Mainframe Communications
• Used by HP to communicate with some printers
• Only Printer Server might require DLC

11
IrDA

• IrDA is a group of short-range, high-speed,
  bidirectional wireless infrared protocols.
• IrDA allows a variety of devices to communicate
  with one another.
• The IrDA protocol stack is accessed by using
  Network Driver Interface Specification (NDIS)
  connectionless drivers.

12
Overview of the TCP/IP Suite

• Routable
• Required to run AD
• Can communicate with dissimilar systems
• Robust, Scalable
• Used Internet
• A Suite of protocols from Application layer thru
  Internet layer

13
Configuring TCP/IP to Use a Static IP Address
14
Configuring TCP/IP to Obtain an IP Address
Automatically

• Using DHCP
• Using the Internet Protocol (TCP/IP) Properties
  dialog box to configure a DHCP client

15
Using Automatic Private IP Addressing

• Windows 2000 implementation of TCP/IP.
• Automatic Private IP Addressing (APIPA) follows
  specific steps in assigning an IP address.
• Attempts to find a DHCP server
• If known found APIPA will assign an IP address
• Address is broadcast to all network computers
• APIPA generates addresses between 169.254.0.0 -
  169.254.255.255
• Although APIPA can assign a TCP/IP address to
  Dynamic Host Configuration Protocol (DHCP)
  clients, it does not generate all the information
  that is provided by DHCP.
• Disabling automatic private IP addressing.
• Registry Hack

16
Troubleshooting TCP/IP

• Windows 2000 offers several utilities to assist
  you in troubleshooting TCP/IP.
• PING
• NSLOOKUP
• IPCONFIG
• NETSTAT
• ARP
• NBTSTAT
• ROUTE
• HOSTNAME
• TRACERT

17
TCP/IP Utilities

• File Transport Protocol (FTP)
• Trivial File Transport Protocol (TFTP)
• Telnet
• Remote Copy Protocol (RCP)
• Remote shell (RSH)
• Remote execution (REXEC)
• Finger

18
Using Ipconfig

• Use ipconfig to verify the TCP/IP configuration
  parameters on a host.
• Executing the ipconfig /all command provides more
  detail
• Can use IPCONFIG to renew or release DHCP leases

19
Using Ping

• To test connectivity
• To test TCP/IP configurations and diagnose
  connection failures
• To determine whether a particular TCP/IP host is
  available and functioning
• Ping ip-address or hostname
• Ping /?

20
Using Ipconfig and Ping

• The ipconfig command is used to verify that the
  TCP/IP configuration has been initialized.
• The ping command is used against the loopback
  address (127.0.0.1) to verify that TCP/IP is
  correctly installed and bound to your network
  adapter card.
• The ping command is used with the IP address of
  the local computer to verify that the computer is
  not a duplicate of another IP address on the
  network.
• The ping command is used with the IP address of
  the default gateway to verify that the default
  gateway is operational and that the computer can
  communicate with the local network.
• The ping command is used with the IP address of a
  remote host to verify that the computer can
  communicate through a router.

21
Overview of DHCP

• DHCP is a TCP/IP standard for simplifying the
  management of IP configuration.
• Each time a DHCP client starts, it requests IP
  addressing information from a DHCP server.
• IP Address
• Subnet Mask
• Other optional values may be provided
• When a DHCP server receives a request for an IP
  address, it selects IP addressing information
  from a pool of addresses (scope) defined in its
  database and offers the IP addressing information
  to the DHCP client.

22
The DHCP Lease Process
23
Authorizing the DHCP Server

• A DHCP server must be authorized in Active
  Directory services before it can assign IP
  addresses.
• Authorization is a security precaution that
  ensures that only authorized DHCP servers run on
  your network.
• Use the DHCP snap-in to authorize the DHCP server.

24
The WINS Name Resolution Process

• Every time a WINS client starts, it registers its
  NetBIOS name/IP address mapping with a designated
  WINS server. It then queries the WINS server for
  the computer name resolution.
• When a WINS client initiates a NetBIOS command to
  communicate with another network resource, it
  sends the name query request directly to the
  WINS server instead of broadcasting the request
  on the local network.
• The WINS server finds a NetBIOS name/IP address
  mapping for the destination resource in this
  database, and it returns the IP address to the
  WINS client.

25
Name Renewal

• A WINS server registers all NetBIOS names on a
  temporary basis so that other computers can use
  the same name later if the original owner stops
  using it.
• To continue using the same NetBIOS name, a client
  must renew its lease before the lease expires.
• A WINS client first attempts to refresh its lease
  after one-eighth of the Time to Live (TTL)
  interval has expired.
• When half the TTL interval has expired, the WINS
  client attempts to refresh its lease with a
  secondary WINS server.
• When a WINS server receives the name refresh
  request, it sends the client a name refresh
  response with a new TTL interval.

26
Name Release

• When a WINS clients name is no longer in use,
  the client sends a message to the WINS server to
  release the name.
• Proper shutdown procedures
• When the WINS server receives the name release
  request, it checks its database for the specified
  name.

27
Name Query

• After a WINS client has registered its NetBIOS
  name and IP address with a WINS server, it can
  communicate with other hosts by obtaining the IP
  address of other NetBIOS-based computers from the
  WINS server
• By default, a WINS client attempts to resolve
  another hosts NetBIOS name to an IP address
  cache
• If no response form a WINS server client issues a
  BROADCAST
• LMHOSTS

28
WINS Server Configuration

• A WINS server requires a computer running Windows
  2000 Server however, the server does not have to
  be a domain controller.
• A WINS server can include additional
  configurations.
• Static Mapping of non-WINS clients
• Support through DHCP

29
WINS Client Configuration

• A WINS client must be running one of the
  supported operating systems.
• A WINS client also requires the IP address of a
  primary WINS server and optionally, the IP
  address of a secondary WINS server.

30
WINS Installation

• The WINS service is not installed as part of the
  default Windows 2000 Server installation.
• Use ADD/REMOVE PROGRAMS
• After you install the WINS Service, you should
  configure its TCP/IP properties so that the
  computer points to itself.

31
Static Mappings

• Non-WINS Clients
• Unique single IP address
• Group - Maps to a Group
• IP Addresses of Group members not stored in the
  WINS database
• Domain Name NetBIOS name/ IP Address
• 16th character 0x1C
• Can store up to 25 mappings
• Internet Group User defined groups that are
  used to organize resources
• Multihomed a unique name that can have more
  than 1 IP address

32
WINS Snap-In
33
DHCP Server Configuration
34
Overview of DNS

• WINS resolves NetBIOS names to IP addresses,
  while DNS resolves IP host names to IP
  addresses.
• IP host names resolved by using DNS or other
  means provide a number of benefits
• Names are user friendly
• Names remain more constants than IP addresses
• Can connect to local server using same naming
  convention as Internet
• Namespace is hiearchical
• HOSTS

35
Domain Namespace
36
Host Names

• Host names refer to specific computers on the
  Internet or a private network.
• A host name is the leftmost portion of the fully
  qualified domain name (FQDN), which describes the
  exact position of a host within the domain
  hierarchy.
• DNS uses a hosts FQDN to resolve a name to an IP
  address.

37
Domain Naming Guidelines

• Limit the number of domain levels.
• Use unique names.
• Use simple names.
• Avoid lengthy domain names max 63 characters
  includingperiods
• FQDN can be up to 255 characters
• Use standard DNS characters and Unicode
  characters.

38
Zones

• A discrete part of the namespace
• Domain can have multiple zones
• Delegate administration
• Must encompass a contiguous namespace
• Zone files stored in plain text in
  systemdrive\WINNT\SYTEM32\DNSFile name
  zonename.DNS

39
Name Servers

• A DNS name server stores the zone database file.
• Name servers can store data for one zone or
  multiple zones.
• There must be at least one name server for a
  zone.
• A zone can have multiple name servers associated
  with it.
• Multiple name servers provide several advantages.
• Zone transfers
• Redundancy
• Performance
• Load balancing

40
Introduction to the Name Resolution Process

• Name resolution is the process of resolving names
  to IP addresses.
• DNS name servers resolve forward and reverse
  lookup queries.

41
Forward Lookup Query
42
Name Server Caching

• When a name server is processing a query, it
  might be required to send out several queries to
  find the answer.
• When a name server receives a query request,
  several events occur.
• Caching query results enables the name server to
  quickly resolve other queries to the same portion
  of the domain namespace.

43
Reverse Lookup Query

• A reverse lookup query maps an IP address to a
  name.
• Because the DNS distributed database is indexed
  by name and not by IP address, a reverse lookup
  query would require an exhaustive search of every
  domain name.
• The in-addr.arpa domain is based on IP addresses,
  not domain names.
• 4.168.192.in-addr.arps