To Previous Chapter To Table of Contents To Bottom of Page To Next Chapter

Chapter 8 TCP/IP and Networks

  1. TCP/IP and Other Protocols
    A simple layered architecture
    Upper-Layer Protocols
    TCP
    IP
    Ethernet

    • LAN Layers
      Data LinkLLC(Logical Link Control)
      MAC(Media Access Layer)
      • LLC usually used with the HDLC (Higher-Level Data Link Control) link standard
      • for connectionless services - uses unnumbered information (UI) message frame
      • for connectionbased services - uses asynchronous balanced mode (ABM)
      • MAC layer is responsible for managing traffic on network (collision detection & transmission times)
      • NDIS (Network Device Interface Specification) [developed by MS & 3Com] - defines an interface between the MAC sublayer and the higher layers
      • ODI (Open Data-Link Interface) [developed by Novell & Apple] - same use as NDIS
      • PROTMAN (Protocol Manager) - routes packets from the MAC layer to the correct protocol stack in the NDIS model (not required in NT)

      PhysicalAUI (Attachment Unit Interface)
      PMA (Physical Medium Attachment)
      MDI (Medium Dependent Interface)

      • AUI - provides attachment between the machine's physical layer and the network medium
      • Medium Attachment Unit (MAU) [PMA & MDI] - responsible for manging the connection of the machine to the LAN medium including checking the signal quality and test routines

      IP/802

      • TCP uses LLC Type 1 which supports UI
      • UDP uses LLC Type 2 to provide data integrity

    • NetBIOS and TCP/IP
      NetBEUI is a transport protocol that serves as an extension to MS's Network Basic Input/Output System. NetBEUI is small, easy to implement, and relatively fast. NetBEUI is non-routable, but the NDIS standard allows NetBEUI to coexist with other, routable protocols like TCP/IP. NetBEUI includes functions at the Network and Transport Layers.
      NetBIOS uses 3 Internet ports:
      • 137 - NetBIOS name service
      • 138 - datagram service
      • 139 - session service
    • XNS (Xeros Network System) and TCP/IP
      uses SPP (Sequential Packet Protocol) to assume some of the TCP functions
    • IPX (Internetwork Packet Exchange)/SPX(Sequenced Packet Exchange)
      generally smaller and faster than TCP/IP
      The NetWare protocol architecture
      Application
      Presentation
      Session
      Transport
      Network
      Data Link
      Physical
      NCP
       
      Named PipesNEtBIOS
      SPX
      IPX
      LAN Drivers
      ODINDIS
      Physical
      • IPX - Network Layer protocol that provides connectionless (datagram) service. Responsible for internetwork routing and maintaining network logical addresses. Relies on hardware physical addresses found at lower layers to provide network device addressing. [easier to manage than TCP/IP]
      • SPX - Transport Layer protocol that provides connection-oreiented services with reliable delivery. Reliable deliviery is ensured by retransmitting packets in the event of error.
      • Netware Core Protocol (NCP) - ULP that provides remote function calls that support network services, such as file sharing, printing, name management, etc. Netware client software uses NCP to access NetWare services.
    • AppleTalk network architecture devloped by Apple for the Macintosh
      • Datagram Delivery Protocol (DDP) - Network Layer protocol that provides connectionless service between two AppleTalk systems.
      • AppleTalk Transaction Protocol (ATP) - Connectionless Transport Layer protocol that provides reliable service though a system of acknowledgements and retransmissions
      • AppleTalk File Protocol (AFP) - provides remote file services; responsible for enforcing file system security; verifies and encrypts logon names and passwords
      • AppleShare - client/server system that provides file and print sharing services
    • Data Link Control(DLC) used to access HP JetDirect network printers; traditionally used for connecting to IBM maiframes via 802.2 LLC Type 2.
    • ARCNet and TCP/IP - uses ARP and RARP
      ARCnet-based network architecture
      ULP
      TCP
      IP
      LLC
      ARCNET
      MAC
      Physical
    • FDDI (Fiber Distributed Data Interface) Networks
      • ANSI-defined, high speed network that uses fiber-optic cable
      • requires two sublayers for the physical layer
      • uses same addressing scheme, but frame size is large (4500 bytes)
    • X.25 and IP - an older packet-switching network standard
      uses a TP4 layer above the IP layer and a PLP (Packet Layer Procedures) layer below IP
    • ISDN (Integrated Services Digital Network) and TCP/IP - supports packet-switching TCP/IP networks; uses terminal adapters instead of routers and gateways
      ISDN-based network architecture
      ULP
      OSI TP4
      CLNP
      X.25 PLP
      LAPB
      EIA 232/V Series

      • Basic Rate ISDN (BRI) - uses 2 64K data channels & 1 16K service channel
      • Primary Rate ISDN (PRI) - uses 23 64K channels and 1 64K service channel
      • Broadband ISDN (B-ISDN) - supports higher bandwidths; uses ATM & SONET for the Physical Layer

    • Switched Multi-Megabit Data Services and IP - public, packet-switched, connectionless service; interfaces IP with the LLC layer using LLC Type 1 frames
    • Asynchronous Transfer Mode (ATM) and B-ISDN
      ULP
      Transport
      ATM
      ATM
      SONET/SDH, FDDI, etc.
    • Windows 95 and TCP/IP
      32-bit Windows Apps16-bit Windows Apps
      API
      Multiple Provider ROuter (MPR)
      SPI
      Network ProviderNETWORK.DRV mapper
      IFS Manager16-bit Network Driver
      Network FSDReal Mode Redirector
      Transport
      Network Transport
      NDIS
      Network Adapter Driver

      • API - standard Win32 Application Programming Interface (handles remote file operations and remotes resources)
      • Multiple Provider Router (MPR) - routes all network operations for Win 95, as well as implementing network functions common to all network types (mpr.dll)
      • Network Provider - implements the network service provider interface
      • IFS Manager - routes filesystem requests to the proper filesystem driver (FSD)
      • Network Filesystem Driver - implements the particular filesystem characteristics (Vfd.vxd)
      • Network Transport - implements the device-specific network transport protocol
      • Network Driver Interface Specification (NDIS) - defines interactions between the network transport and device drivers (ndis.vxd)
      • Network Adapter Driver - controls the actual network hardware device
      1. protocol.ini
        [ndishlp$]
        DriverName=ndishlp$
        Bindings=MS2000$
        
        [protman$]
        DriverName=protman$
        priority=ndishlp$
        
        [data]
        version=v4.00.950
        netcards=MS2000$,*PNP80D6
        
        [MS2000$]
        DriverName=MS2000$
        Interrupt=11
        IOBase=0x300
        
        [NETBEUI$]
        sessions=10
        ncbs=12
        Bindings=MS2000$
        DriverName=NETBEUI$
        Lanabase=1
        

  2. Optional TCP/IP Services
    • Active Users - port 11
    • Character Generators - port 19 [returns a list of all printable ASCII characters]
    • Daytime - port 13 [returns date, time, day of week, month of year]
    • Discard - port 9 [discards all received messages]
    • Echo - port 7 [returns any message]
    • Quote of the Day - port 17 [returns a quotation]
    • Time - port 37 [returns the time since 1/1/1900]
    • Using the Optional Services

To Previous Chapter To Table of Contents To top of page To Next Chapter