1 / 58

Windows NT Networking

Windows NT Networking. Bruno Sinkovic 5 October 99. Windows NT Networking Problems that affect Objectivity. Windows NT Architecture. Object-Based Computing process, threads, devices, access rights, .. Component-Based Architecture modular design Kernel and User Mode Protected Subsystems

shandi
Download Presentation

Windows NT Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Windows NT Networking Bruno Sinkovic 5 October 99

  2. Windows NT Networking Problems that affect Objectivity

  3. Windows NT Architecture • Object-Based Computing • process, threads, devices, access rights, .. • Component-Based Architecture • modular design • Kernel and User Mode • Protected Subsystems • Executive Services

  4. Windows NT Architecture • Example of NT Executive components • I/O Manager ( cache manager, file system drivers, network drivers, hardware device drivers) • Object Manager • Security Monitor • Process Manager • Virtual Memory Manager • Window Manager • Graphics Device Interface & Drivers • Hal …..

  5. Windows NT Architecture • Protected Subsystems : • win32 (native) • posix • os/2 • win16 (Ms-Dos + NTVDM)

  6. Winnt Networking • Layered Network Architecture • Peer Relationships Protocols • Vertical Relationships Interfaces

  7. Winnt Networking : Layered Architecture • Applications (User Mode) • I/O Manager • TDI Transport Driver Interface (Boundary Layer) • Transport Protocols (tcp/ip, netbeui, ipx/spx, …) • NDIS (Boundary Layer) • Network Adapter Card Drivers • Network Interface Cards (NIC)

  8. Layered Network Architecture User Mode Kernel Mode NetBIOS Driver Redirectors Servers Winsock Driver TDI (Transport Driver Interface) Transport Protocols NDIS Interface Network Adapter Card Driver Hardware Network Inteface Card

  9. Winnt Networking : Boundary Layers (1) • TDI : Transport Driver Interface • Common interface for a driver (such as NT Redirector or NT Server for example) to communicate with the various network transports (tcp/ip, ipx/spx, netbeui, …) • TDI allows user applications and file systems to remain independent of transports • TDI is a standard for passing messages between 2 layers

  10. Winnt Networking : Boundary Layers (2) • NDIS : Network Driver Interface (3.0) • Allow multiple network adapters and multiple protocols to coexist • Enables the high level component (transport protocol) to be independent of the Network Interface Card (NIC)

  11. Windows NT Network Protocols • TCP/IP • Netbeui • Lan, broadcast based • Not routable • IPX/SPX • Novell Proprietary • Poor performance across Wan • Others (DecNet, Streams, ….)

  12. IPC (Inter-Process-Communications) • Named Pipes (NPFS) • Mail Slots (MSFS) • Windows Sockets • NetBIOS • RPC • NetDDE (network dynamic data exchange) • SMBs (Server Messages Blocks) • DCOM

  13. WINNT Networking Services • Server Service • Workstation Service (Redirector) • Protocols (TCP/IP, NetBeui, IPX/SPX, ..) • Network Resource Access • Multiple Universal Naming Convention Provider (MUP) • Universal Naming Convention Names (UNC) • Multi-Provider Router • RPC, DNS, WINS, DHCP , …

  14. Accessing Remote Files • Workstation Service • I/O Manager • RDR File System (NT Redirector) • SRV Server Driver (NT Server Service) Remote Machine

  15. NT Redirector • Part of I/O Manager. Resides above TDI • Component through which one computer gain access to another computer • The workstation Service receives a request from a user application, passes it to the kernel-mode Redirector • Allows connection to MS-Net based computers

  16. NT Redirector (2) • Implemented as a winnt file System Drivers (such as FAT, NTFS, HPFS, …) • Applications use a single API ( I/O API) • Can Coexist with Other Redirectors (Netware, NFS, etc …)

  17. The Server Service • Implemented above TDI, as a File System Driver • Server supplies the connection requested by client-side redirectors

  18. More Networking Options • Binding Options • Bind network components to Network Adapters • Binding can be ordered • Remote Access Services (RAS) • RAS Client • RAS Server • Point-to-point Protocol

  19. UNC : Network Resource Access • UNC : Universal Naming Code • unc requests are passed to the Multiple Universal Naming Convention Provider (MUP) • MUP selects the appropriate UNC provider (redirector) to handle the I/O Request • \\Server\share\subdirectory\filename • Use Dos command : “net share”

  20. Security & Authentication • NT Domains Vs Local Domain • Domain Controllers (PDC, BDC) • Trust Relationships • Logon Processes (netlogon) • Interactive and Remote Logon • Dialog box displayed or not • User Manager for Domains • domain\username

  21. NT Server Domains • Single logon procedure • Universal Resource Access • Centralized Network Administration • Directory Database (SAM) • Local Database for Local Computer • Domain Controllers • primary (PDC) • secondary (BDC)

  22. NT Server Domains (2) • Computer Accounts • each computer has an account in the Directory Database • Secure Communication Channels • used during authentication

  23. NT / UNIX Interoperability • Using 3rd Party Products (Netmanage, Hummingbird, …) • Using NFS Server and Redirector • Requires Unix Client Authenticating to NT Servers • Requires NT Clients Authenticating on UNIX Servers

  24. Host/Computer Name Resolution • Browser Services • WINS • DNS • DHCP • /etc/hosts File • NetBios Names

  25. Name And Address • Understanding Address and Name Resolution • IP Address • Host Name • NetBios Name

  26. Netbios Names • Flat Name • Is also known as “Computer Name” • Can be different from hostnames !

  27. NT Browser Service • Maintain a “Browse list” of all available domains and servers on the network • Provides this information to programs that require it • Displayed in • Network Neighborhood • Net View • Map Network Drive

  28. Dynamic IP Addressing : DHCP • DHCP Client and DHCP Server • DHCP Server maintains a Database of IP Addresses • DHCP Server is assigned a “Range” of IP Addresses

  29. DNS (Domain Name Services) • Resolve Hostname <--> IP Address • Global Distributed Database on a hierarchical naming system • Depends on Static File for name resolution • Static Configuration of IP Addresses to perform name-to-IP-address mapping

  30. WINS • Resolve NetBIOS Name <--> IP Address • WINS provide a dynamic, distributed database for registering and querying dynamic NetBios computer names to IP-Address • Supports DHCP dynamic allocation of IP Addresses and can resolve a NetBIOS computer Name to a dynamic IP Address mapping

  31. WINS and DNS Interaction • NT DNS server “talks” to WINS Server • Windows NT based DNS Server provides connectivity between WINS and DNS. • DNS Server can pass through an unresolved DNS name query to a WINS Server for final name resolution

  32. Name Resolution • Network Application Interfaces • Winsock interface • NetBios over TCP/IP (NetBT)

  33. NetBIOS Application Netbios API NETAPI32.dll User Mode Kernel Mode NetBIOS Emulator TDI NetBEUI TCP/IP IPX/SPX NDIS Netbios and Winsock Interfaces Winsock Application Winsock API WSOCK32.dll User Mode Kernel Mode Winsock Emulator TDI TCP/IP IPX/SPX NDIS

  34. Name Resolution (1) : Winsock • Steps for Winsock Name & Address Resolution • Ex: gethostbyname() , gethostbyaddr(), ping • 1. Check local computer host name • 2. Check the Hosts file for a matching name entry • 3. If a DNS server is configured, query it • 4. If not match found, try the Netbios name resolution

  35. Name Resolution (2) : netbios • Steps for Netbios Name resolution • if hostname > 15, query DNS • query Netbios Cache Name • Local Broadcast for resolution • Query WINS Server (Netbios Name Server) • Query LMHOSTS (Netbios hosts name on another segment) • Query local HOSTS file • Query DNS

  36. NT Networking Configuration and Tools • Tools & Utilities • Control Panel • ipconfig • netstat, nbstat • net command • nslookup • tracert • hostname • ping

  37. How UNC Paths are Resolved Application Using I/O Call with UNC name (\\server\share) User Mode Kernel Mode MUP Windows NT Redirector Other Redirectors ( NFS, Netware, ..) TDI MUP = Multiple Universal Naming Convention Provider

  38. More Information ? • Windows NT Resource Kit • winnt Server • winnt Workstation

  39. Objectivity and NT Networking Deploying a WINNT-Based Objectivity Application

  40. NT + Objy : Possibles issues …. • Name resolution • File Access Security & Permissions • UNC names • Virtual Mapped Drives • DHCP - DNS - WINS • …..

  41. Deploying : Things to consider (1) • Which Domains Participate in the Deployed Application ? • Verify Access rights (domains, users, computers, files, …) • UNC or AMS ? • Defining and using Mapped Drives (ex : r:\)

  42. Deploying : Things to consider (2) • Is WINS running ? • Is DNS configured ? • Do hosts use DHCP ? • Set Hostname and/or Computername

  43. NT / UNIX Interoperability • NFS or Samba will enable File Sharing between Unix and NT hosts • FD or DB created using UNC or Virtual mapped drives can not be accessed by Unix based application

  44. NT Domains and File access Domain1 PDC Domain1 WS Domain2 WS Domain2 PDC Win95/98

  45. Using UNC • Objectivity will automatically use oo_local_host:: • DB name : oo_local_host::\\server\dir\file.db • UNC or AMS , not both

  46. Using Virtual Drive Mapping • Mapping Shares , ex : r:\ • Make sure the same letter is mapped to the same shared directory on every possible Objy client machine • Verify that the mapped drive is accessible from all possible Objy Clients

  47. What is oo_local_host :: ? • Always been resolved as the machine from where the Objy client runs • Automatically set by oonewfd and oonewdb when using UNC and Virtual Drive mapping • Thus, bare this in mind when creating federations or databases files

  48. Objectivity Tools Involved • Lockserver • oonewfd • oonewdb • Client (C++, Java) • AMS

  49. Objy Files • Where to place them ? • How to share them ? • FDB • DB • JNL • Boot

  50. Boot File : where to place it ? • Use AMS (recommended) • Put the boot file on a Windows NT node and share the file using virtual drive mappings • Put the boot file on a Windows 95 node and share the file using UNC names instead of virtual drive mappings

More Related