1. Chapter 3 Chapter 3: Planning Network Protocols and Compatibility

2. Chapter 3 Learning Objectives n Explain basic network concepts, including network terms, types of networks, and network cards n Explain the NDIS and ODI network driver specifications n Explain the communications protocols used in Windows 2000 Server, including TCP/IP, NWLink, NetBEUI, DLC, and AppleTalk

3. Chapter 3 Learning Objectives (continued) n Plan network binding order, change the binding order, and bind and unbind protocols n Plan how to implement protocols on different types of networks

4. Chapter 3 Protocol n A protocol consists of guidelines for: u How data is formatted into discrete units called packets and frames u How packets and frames are transmitted across one or more networks u How packets and frames are interpreted at the receiving end

5. Chapter 3 Packets and Frames n Packets and frames are units of data transmitted from one networked computer or device to another. n Although packets and frames are often used to have the same meaning, there is a difference. Packets operate at a higher communication layer and contain routing information.

6. Chapter 3 General Sections in Packets and Frames n Header n Data n Trailer or footer

7. Chapter 3 Packet and Frame Format Figure 3-1 Basic packet and frame format

8. Chapter 3 Network Design n The basic design of a network is its topology n Topology: The physical layout of the cable and the logical path followed by network packets and frames sent on the cable

9. Chapter 3 Local Area Network n Local area network (LAN): Joins computers, printers, and other computer equipment within a limited service area and generally employs only one topology

10. Chapter 3 Example of a LAN Figure 3-2 A LAN in a building

11. Chapter 3 Metropolitan Area Network n n Metropolitan area network (MAN): A network that links multiple LANs within a large city or metropolitan area

12. Chapter 3 Example of a MAN Research hospital University chemistry building Pharmaceutical company MAN connecting buildings in a city

13. Chapter 3 Enterprise Network n Enterprise Network: A network that often reaches throughout a large area, such as a college campus, a city, or across several states. A distinguishing factor of an enterprise network is that it brings together an array of network resources such as many kinds of servers, mainframes, printers, network devices, intranets, and the Internet

14. Chapter 3 Typical Resources in an Enterprise Network Figure 3-3 Resources in an enterprise network

15. Chapter 3 Wide Area Network n Wide Area Network (WAN): A far- reaching system of networks that can extend across state lines and across continents

16. Chapter 3 Example of a WAN WAN across a continent

17. Chapter 3 Network Interface Card Communication Medium Options n Coaxial cable (thick and thinnet) n Twisted-pair (shielded and unshielded) n Fiber-optic n Wireless (infrared, radio wave, microwave, satellite)

18. Chapter 3 Connecting a Medium to a NIC Figure 3-4 Connecting cable to a NIC

19. Chapter 3 Device Address n Each NIC has a physical or device address that is burned into a PROM on the card n Media access control (MAC) address is another way of describing the device address

20. Chapter 3 Ethernet and Token Ring n Ethernet: A network transport system that uses a carrier sensing and collision detection method to regulate data transmissions n Token ring: A network transport method that uses a token, which is passed from node to node, to coordinate data transmissions

21. Chapter 3 NDIS n Network Driver Interface Specification (NDIS): A set of standards developed by Microsoft and 3COM for network drivers that enables communication between a NIC and a protocol, and that enables the use of multiple protocols on the same network

22. Chapter 3 NDIS Architecture Figure 3-5 Binding a protocol to a NIC

23. Chapter 3 ODI n Open Datalink Interface (ODI) driver: A driver that is used by Novell NetWare networks to transport multiple protocols on the same network

24. Chapter 3 Microsoft-Supported Communication Protocols

25. Chapter 3 Microsoft-Supported Protocols (continued)

26. Chapter 3 TCP/IP n Transmission Control Protocol (TCP) portion performs extensive error checking to ensure that data is delivered successfully n Internet Protocol (IP) portion consists of rules for packaging data and ensuring that it reaches the correct destination address

27. Chapter 3 Dotted Decimal Notation n Dotted Decimal Notation n Dotted Decimal Notation: An addressing technique that uses four octets, such as 100000110.11011110.1100101.00000101, converted to decimal (e.g., 134.22.101.005), to differentiate individual servers, workstations, and other network devices.

28. Chapter 3 Unicasting and Multicasting n In a unicast, a transmission is sent to each client that requests a file or application, such as a multimedia presentation n In a multicast, a transmission is sent to all requesting clients as a group (reducing the total network traffic)

29. Chapter 3 Unicasting and Multicasting Compared Figure 3-6 Unicasting compared to multicasting

30. Chapter 3 Subnet Mask n Subnet mask: A designated portion of an IP address that is used to indicate the class of addressing on a network and to divide a network into subnetworks as a way to control traffic and enforce security

31. Chapter 3 Configuring the IP Address and Subnet Mask in Windows 2000 Figure 3-7 IP address and subnet mask setup

32. Chapter 3 Static and Dynamic Addressing n Dynamic addressing: Involves automatically assigning an IP address to a network host n Static addressing: Involves manually assigning an IP address to a network host

33. Chapter 3 TCP/IP Advantages n Well-suited for medium and large networks n Designed for routing; has high degree of reliability n Used worldwide for directly connecting to the Internet and by Web servers n Enables lower TCO on Microsoft networks

34. Chapter 3 TCP/IP Advantages n Compatible with standard tools for analyzing network performance n Parallel ability to use DHCP and WINS through a Windows 2000 server n Ability for diverse networks and operating systems to communicate n Compatible with Microsoft Windows Sockets

35. Chapter 3 TCP/IP Disadvantages n More difficult to set up and maintain than other protocols n Somewhat slower than IPX/SPX and NetBEUI on networks with light to medium traffic

36. Chapter 3 Routing via TCP/IP Figure 3-8 Router forwarding packets to a designated network

37. Chapter 3 Planning Tip n For medium and large sized networks, plan to use TCP/IP because it enables you to manage and secure network traffic through creating subnets

38. Chapter 3 Protocols and Applications in the TCP/IP Suite

39. Chapter 3 Protocols and Applications in the TCP/IP Suite (continued)

40. Chapter 3 Protocols and Applications in the TCP/IP Suite (continued)

41. Chapter 3 Protocols and Applications in the TCP/IP Suite (continued)

42. Chapter 3 Protocols and Applications in the TCP/IP Suite (continued)

43. Chapter 3 IPX/SPX n IPX: A protocol developed by Novell for use with its NetWare server operating system (particularly for NetWare versions before version 5) n SPX: A Novell connection-oriented protocol used for network transport when there is a particular need for data reliability

44. Chapter 3 NWLink n A network protocol that simulates the IPX/SPX protocol for Microsoft Windows 95, 98, NT, and 2000 communications with Novell NetWare file servers and compatible devices

45. Chapter 3 Client Service for NetWare (CSNW) Components n Client Service for NetWare n NWLink IPX/SPX n NWLink NetBIOS

46. Chapter 3 CSNW Installed in Windows 2000 Figure 3-9 Windows 2000 with CSNW components installed

47. Chapter 3 Configuring NWLink n Configure three elements: u Frame type u Network number u Internal network number

48. Chapter 3 When to Configure the Internal Network Number n When the NetWare server that is accessed uses two or more frame types n When the Windows 2000 host has two or more NICs and NWLink is bound to more than one of the NICs n When an application uses NetWare’s Service Advertising Protocol (SAP)

49. Chapter 3 When to Use NWLink n To enable a computer running Windows 2000 to access a NetWare server (pre- version 5) n To set up Windows 2000 as a gateway to a NetWare server n To enable NetWare clients to access a Windows 2000 server

50. Chapter 3 Planning Tip n If you upgrade NetWare servers to version 5.x or higher, convert from IPX/SPX to TCP/IP for better network communication options and better compatibility with Windows 2000 servers

51. Chapter 3 NetBIOS n A combination software interface and network naming convention n Available in Windows 2000 through the files Netbt.sys, NetBIOS.sys, and NetBIOS.dll

52. Chapter 3 NetBEUI n NetBIOS Extended User Interface (NetBEUI): A non-routable communications protocol native to early Microsoft network communications

53. Chapter 3 NetBEUI and NetBIOS Communication Figure 3-10 NetBIOS/NetBEUIcommunication

54. Chapter 3 Planning Tip n When you upgrade from Windows NT Server to Windows 2000 Server, plan to retire NetBEUI implementations (if possible) and convert upgraded servers and clients to TCP/IP for more functionality

55. Chapter 3 When to Use NetBEUI n For temporary backward compatibility when converting from Windows NT Server to Windows 2000 Server n For small networks that do not have Internet access, that do not use the Active Directory, that do not use routing, and that require only a basic installation n For backward compatibility with particular applications

56. Chapter 3 DLC n Data Link Control (DLC) protocol: Enables communication with older IBM mainframes and minicomputers, and with some older HP print server cards

57. Chapter 3 When to Use DLC n To connect to IBM and other computers that use Systems Network Architecture (SNA) communications n To connect to older peripheral devices, such as printers that use DLC

58. Chapter 3 AppleTalk n AppleTalk: A peer-to-peer protocol used in network communication between Macintosh computers n Windows 2000 Server Services for Macintosh include: u File Server for Macintosh (MacFile) u Print Server for Macintosh (MacPrint) u AppleTalk protocol

59. Chapter 3 When to Use AppleTalk n Use AppleTalk to enable Macintosh clients to connect to Windows 2000 Server

60. Chapter 3 Binding Order n Windows NT and Windows 2000 enable you to set a binding order which establishes the protocol that will be tried first in a network communication (or a communication with a network printer)

61. Chapter 3 Troubleshooting Tip n If network performance is slow and your network uses a combination of protocols, tune the binding order on Windows NT and Windows 2000 clients which can be an inexpensive way to immediately relieve network congestion

62. Chapter 3 Network Planning Considerations n Size and purpose of the organization n Potential growth n Proportion of mission-critical applications n Role of the network to the mission of the organization n Security needs n Budget n Internet and intranet requirements n Interconnectivity requirements

63. Chapter 3 Planning Tip n Begin network planning by understanding: u User needs u Important business processes u Current resources u Potential growth

64. Chapter 3 Considerations in Selecting the Right Protocol(s) n Routing needs n Size of the network in terms of connections n Presence of Windows 2000 servers n Presence of mainframes and other computers that use SNA n Presence of NetWare servers n Access to the Internet or intranets n Presence of mission-critical and multimedia applications

65. Chapter 3 Chapter Summary n Protocols are the life blood of a network, thus plan their use carefully. n The Microsoft NDIS driver enables using one or more protocols such as TCP/IP, IPX/SPX, NetBEUI, DLC, and AppleTalk. n For modern networking TCP/IP implementations are preferred.

66. Chapter 3 Chapter Summary n Plan to use only the protocols necessary. n Tune network binding order in Windows NT and Windows 2000 operating systems to enhance network performance.