TCP/IP & The BASIS License Manager - PowerPoint PPT Presentation

tcp ip the basis license manager l.
Skip this Video
Loading SlideShow in 5 Seconds..
TCP/IP & The BASIS License Manager PowerPoint Presentation
Download Presentation
TCP/IP & The BASIS License Manager

play fullscreen
1 / 57
Download Presentation
TCP/IP & The BASIS License Manager
Download Presentation

TCP/IP & The BASIS License Manager

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. TCP/IP & The BASIS License Manager • The BASIS License Manager Requires TCP/IP & TCP/IP Hostname Resolution • Overview of the the TCP/IP 4 Layer Model • Hostname Resolution • Using TCP/IP Utilities

  2. When Is The BLM Needed? • All PRO5 Products REV 2.10 And Up. The Exception Is Windows Single-user VPRO5 and Single-user ODBC. • Multi-user ODBC License • All BBj Products, Single Or Multi-user Note: The BLM Can Run on All Operating Systems That Basis Builds Products For, Including Win95 or Win98. However, a Server O/S Is Highly Recommended, Like WINNT, SCO, HP-UX, AIX, Etc.

  3. BBj and the BASIS License Manager The BLM Gives You the Ability to Dispense Licenses Anywhere on the Network, Regardless of the Operating System. And Now With the Implementation of BBj, Our Customers Are Ready for E-commerce and Enterprise Computing Like Never Before. This Process of Dispensing Licenses Is Done Through the Use of TCP/IP Hostname Resolution.

  4. Basis License Manager Install Checklist • Identify Server(s) That Will Run the BLM • Must Have Working Network Card. This Is Required for (V)PRO5 Multi-user, ODBC Multi-user, All PRO5 Data Server Licenses and ALL BBj Licenses, Single or Multi-user. • TCP/IP Must Be Configured for Hostname Resolution • BASIS Product Media, Serial and Authorization Numbers Available

  5. THE TCP/IP 4 LAYER MODEL Transmission Control Protocol & Internet Protocol Has 4 Main Layers • Application Layer • Transport Layer • Internet Layer • Network Layer

  6. Window Socket Applications Uses port number and an address to which it will send and receive data; type of socket (stream or datagram); and an interface to which it is bound (protocol) Sockets A socket is part if Inter Process Communication, in which two processes, either local or remote, exchange data (communicate) Applications Like the PRO5 DATA SERVER or the BLM Netbios Applications Netbios Over TCP/IP For Example, Many NT Services Run Netbios Over TCP/IP; Like The ‘Server’ Service(browsing, Making Or Connecting To A Network Share) APPLICATION LAYER

  7. Services Applet in Control Panel

  8. TCP Provides Connection Orientated, Reliable Communications For Apps That Transfer Large Amounts Of Data Like The Pro5 Data Server. UDP Provides Connectionless Communications And Does Not Guarantee To Deliver The Packets. Generally Used For Transferring Small Amounts Of Data. TRANSPORT LAYER

  9. TCP Transmission Control Protocol • Stream Connection • Reliable and Sequenced • Ongoing Connection

  10. UDP User Datagram Protocol • Unreliable and Unsequenced • No Ongoing Connection • Allows Broadcast


  12. IP INTERNET PROTOCOL • Primarily Responsible For Addressing And Routing Packets Between Hosts And Networks • IP Uses Either TCP or UDP to Move the Data Packets Across the Network.

  13. ARPADDRESS RESOLUTION PROTOCOL • Obtains Hardware Addresses Of Hosts Located On The Same Physical Network. • Once The Hostname Is Resolved To The IP Address, ARP Map’s The Host IP Address To The Mac Address Of The Network Card

  14. ICMPINTERNET CONTROL MESSAGE PROTOCOL • Sends Messages And Reports Errors Regarding The Delivery Of The Packets • It Is Useful to Think of ICMP As One IP Package Talking to Another Host's IP Package, in Terms of Echo Request and Reply, Destination and Source, Time-Stamping, Time-to-Live, Etc.

  15. IGMP INTERNET GROUP MANAGEMENT PROTOCOL • Used By IP Hosts To Report Host Group Memberships To Local Multicast Routers • Similar to ICMP, but the Messages Sent Are Referred to Groups of Nodes Instead of Individual Nodes. Routers Use IGMP to Multicast Out Messages to Multiple Nodes.

  16. NETWORK LAYER • Lan Technologies Such As Ethernet, Token Ring, FDDI • Wan Technologies Such As Frame Relay, Fiber Optic, ATM, Serial Lines (Dial Up) Where PPP (Point To Point Protocol) Is Used, For Example With VPN.

  17. This Can Be Defined As the Process of Converting Humanly-Friendly Names Into Computer-friendly Numbers (IP Addresses) TCP/IP Hostname Resolution

  18. TCP/IP HOSTNAME RESOLUTION • When You Attempt To Access A Remote System Via It’s Hostname, The Hostname Resolution Process Begins In This Order. • Local Cache • Hosts Files • DNS Server

  19. To Minimize The Number Of Broadcasts over The Network, Arp Maintains Address Mappings For Future Use. Each Time You Communicate With A Host, An Entry Is Made In Arp Cache. The Entry Is Time stamped. If Not Used Again Within Two Minutes, It Is Deleted. Note: You Can Set the ‘Arpcachelife’ Parameter in the Registry. LOCAL CACHE USES ARP

  20. HOSTS FILES USED IN UNIX AND WINDOWS In ASCII Format. • Simplest Method, Using A Lookup Table • Hosts Files List Ip Addresses, Each Followed By One Or More Hostnames (Separated By Spaces Or Tabs) To Act As Aliases. • Windows 95/98: File Is Located In /Windows/ Directory • Windows NT: File Is Located In /Winnt/system32/drivers/etc/ Directory • Unix: File Is Located At Root In The /etc/ Directory.

  21. HOST FILE EXAMPLE #Host Files local host # Loopback to local host mypc # Local PC scosysv # Frequently used server orion # gateway server #end file Entries in the Host File Are Resolved Quickly, and Do Not Require Connection to a Name Server. Frequently Used for Ftp, Telnet Sessions, As Well As Client Server Applications Like Basis Products, in Small User Environments.

  22. DOMAIN NAME SERVICE (DNS) • The Standard For Name Resolution On The Internet And Used Locally In Medium & Large User Environments • First Developed For Unix • A DNS Client Sends A Hostname To A DNS Server, And Receives An IP Address In Response. • These Names Can Be Simple Netbios Node Names Like Leghorn, To FQDN Like Leghorn.Basis.Com

  23. DOMAIN NAME SERVER (DNS) UNIX Note: DNS Is a Little to Complex for Our Discussion Here. DNS Should Only Be Done By a Qualified Network System Administrator. We Will However, Briefly Review the Topic.

  24. UNIX DNS USES CONFIGURATION FILES • named.conf file: found in /etc/ directory // type domain source file or host zone "." { type hint; file "db.cache"; zone "" in { type master; file "db.basis"; check-names warn; zone "" in { type master; file "db.192.168.1"; check-names warn; • Resolv.conf

  25. db.cache file • A Host can use the db.cache file to remember names and • Addresses it has learned. Mainly used for quick name resolution • for an intranet. • #db.cache file • \par kazoo2:/usr/lib/named$ more db.cache • \par ; • \par ; Cache file for the Internal DNS domain for • \par ; Each non-internet connected name server for should load this. • \par ; • \par ; don't use this on our internet connected host!. • \par ; • \par . 99999999 IN NS • \par . 99999999 IN NS • \par 99999999 IN A • \par 99999999 IN A

  26. Provides Name to Address Mapping for Basis.Com • ; The origin "" is added to all names not ending with a dot. • ; • @ IN SOA ( • 434 ; Serial • 300 ; Refresh after 5 minutes • 3600 ; Retry after 1 hour • 604800 ; Expire after 1 week • 86400 ) ; Minimum TTL of 1 day • ; • ; Name servers ( the name '@' is implied ) • ; • IN NS • IN NS • IN MX 0 • ; • ; Address for canonical names on external network • ; • ;basis IN A • ;elroy IN A • ; Address for canonical names on internal network • ; • ; IN A • abu IN A • addon IN A • addon2 IN A db.basis file

  27. Address to Name Mapping for Basis.Com • kazoo2:/usr/lib/named$ more db.192.168.1 • ; • ; Address-to=Name mapping for • ; • ; The origin "" is added to all names not ending with a dot. • ; • @ IN SOA ( • 434 ; Serial • 10800 ; Refresh after 3 hours • 3600 ; Retry after 1 hour • 604800 ; Expire after 1 week • 86400 ) ; Minimum TTL of 1 day • ; • ; Name servers ( the name '@' is implied ) • ; • IN NS • IN NS • Addresses point to canonical names • ; • 1 IN PTR • 2 IN PTR • 3 IN PTR • 4 IN PTR db.192.168.1 file

  28. Combining ApproachesDNS & HOSTS Files • Some Systems Allow the Sysadmin to Use DNS and HOSTS • Files, and You Can Then Specify the Order in Which They Are • Consulted. • Depending Upon the Unix Flavor an Entry Would Be Made in • Hosts.Conf or Resolv.Conf File • A Typical Entry Would Be: Order Hosts, bind • With This Entry, the HOSTS File Is Parsed First, If No Entry Is • Found, Then the DNS Server Is Consulted.

  29. (UNIX) CLIENT CONFIGURATION FOR DNS RESOLV.CONF FILE IDENTIFIES THE DOMAIN AND THE DNS SERVERS $ cd /etc/ $ more resolv.conf domain nameserver # kazzoo2 nameserver # dino

  30. DOMAIN NAME SERVER (DNS) Note: DNS Is a Little to Complex for Our Discussion Here. DNS Should Only Be Done By a Qualified Network System Administrator. We Will However, Briefly Review the Topic. WINDOWS NT SERVER 4.0

  31. WINDOWS NT USES A DNS MANAGER TO CONFIGURE THE DNS SERVER • To Install It, Select The Services Tab In The Network Control Panel • You Can Then Access The DNS Manager From The Administrative Tools Menu • You Must First Add The DNS Server’s IP Address With The ‘New Server’ Command In The DNS Menu

  32. CONFIGURING THE DNS SERVER • The Configuration Will Consist Of Zones Or DNS Databases • You Will Then Create A New Zone And Choose ‘Primary’ As Zone Type • Next You Would Create Domain Entries, Hostnames And Resource Records Under The Primary Zone • If You Are Using Multiple DNS Servers, You Would Create Secondary Zones To Be Used For Redundancy Between DNS Servers

  33. DNS CONFIGURATION FOR THE CLIENT • First Select The Protocol Tabs In The Network Control Panel • Highlight TCPIP, Select Properties, And Select The DNS Tab. Here You Specify The Client Hostname, Domain, DNS Server IP Address And Search Order, If More Than One

  34. DNS Client Configuration

  35. THE DNS DATABASE • The DNS Server Stores It’s Information In Simple ASCII Database Files • Each DNS File Includes An SOA (Start Of Authority) Record, Specifying Administrative Information For The Zone • Followed By A Number Of Records Describing The Hosts And Other Entries In The Zone

  36. DNS AND WINS CAN WORK TOGETHER • If DNS Is Unavailable It Can Optionally Access A WINS Server To Resolve The Name As A Netbios Name • To Do This, Select Properties In The DNS Menu In The DNS Manager • Select The WINS Lookup Tab, And Select ‘Use Wins Resolution’ Option • Add At Least One WINS Server To The List

  37. NETBIOS HOSTNAME RESOLUTION • WINS Server • B-node Broadcast • Lmhosts Files

  38. WINDOWS INTERNET NAMESERVICE (WINS) • Microsoft's Implementation Of NetBios Name Service(NBNS), Which Avoids Heavy B-node Broadcasts • WINS Uses H-node Broadcasting By Default: Netbios Apps/services First Query Wins For Netbios Names, The WINS Server Replies With A Positive Response, If The Name Is Registered • If WINS Is Not Available, Then Netbios Names Are Resolved By A B-node Broadcast

  39. Here You Can View WhatNetBios Is Bound To

  40. INSTALLING WINS • WINS Is Installed From The Network Control Panel. Select Services Tab And Then Select ’Add’& Choose Wins • WINS Manager Is In Administrative Tools Menu • To Configure, Launch The WINS Manager And Select Configuration From The Menu • WINS Can Cross Routers. Also, At Least One WINS Server Is Recommended Per 5000 Clients

  41. CONFIGURING WINS • Windows NT And Windows 95/98 Can Select Both A Primary & Secondary WINS Server In TCP/IP Properties • Any Windows NT Server Can Act As A WINS Server. WINS Clients Access Servers Strictly By IP Address, So WINS Like DNS Servers Must Have Dedicated IP Addresses (Or Reserved IP Addresses If Using DHCP)

  42. B-NODE BROADCASTING If Hosts Files And DNS Servers Fail To Resolve The Hostname To An IP Address, Then Netbios Name Resolution Begins. The Node Sends A Netbios Name Query To The Entire Local Subnet. If A Machine Finds A Match, It Sends A Reply To The Original Node And A Netbios Session Is Established.

  43. LMHOSTS FILES (WINDOWS ONLY) • Lmhosts Files Are Searched If A Negative Response Is Received Rom A B-node Broadcast Or From WINS • Windows NT The File Is Located In \Winnt\system32\drivers\etc\ • Windows 95/98 The File Is Located In \Windows\ Directory • Similar To Hosts File And Is Also A Standard ASCII File

  44. LMHOSTS USES IP ADDRESSAND NETBIOS NAMES • HERE IS A SAMPLE SYSTEM1 SYSTEM2 #PRE #SEE BELOW ORION #DOM: BASIS • #Note: #Pre Determines Which Entries That Should Be Preloaded Into Cache • #Dom Facilitates Domain Activity Such As User Login Validations Over A Router, Account Synchronization And Browsing

  45. Using TCP/IP UTILITIES For Information & Troubleshooting • Ping • Hostname • Nslookup • Netstat • Ifconfig • Ipconfig • Trace Route

  46. HOSTNAME UTILITY • You Can Type Hostname At The Unix Or DOS Prompt And This Will Return The Netbios (Computer Name) Assigned To That System • We Commonly Use This When We Configure The Basis License Manager • Example: Microsoft Windows NT (C) Copyright 1985-1996 Microsoft Corp. C:\>hostname server

  47. PING A DIAGNOSTIC UTILITY • Sends An Echo Request ICMP Packet To A Remote Node And Waits For A Response • Used To Troubleshoot Network Connectivity • Test Hostname Resolution By Pinging Hostnames From Server To Client And Client To Server

  48. PING EXAMPLE C:\>ping server Pinging [] with 32 bytes of data: Reply from bytes=32 time<10ms TTL=128 Reply from bytes=32 time<10ms TTL=128 Reply from bytes=32 time<10ms TTL=128

  49. TROUBLESHOOTING DNS WITH NSLOOKUP • A Diagnostic Utility For DNS That Allows You To Display Resource Records On The DNS Server • You Can Use Nslookup With Windows Or Unix DNS Implentation • From A DOS Or Unix Prompt Type • Nslookup Hostx • WHERE Hostx Is A Host In Your Domain • This Will Return The IP Address As Stored In The DNS Database

  50. NSLOOKUP UTILITY (UNIX or WINDOWS) $ nslookup leghorn Name Server: Address: Name: Address: