NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: DHCP2B.EXE; DHCP & BOOTP for NetWware IP README FOR: DHCP2B.EXE NOVELL PRODUCTS and VERSIONS: NetWare 3.12 NetWare MultiProtocol Router 3.0 NetWare 4.1 NetWare IP-NW312 NetWare IP-NW410 NetWare MultiProtocol Router 3.1 ABSTRACT: DHCP2B.EXE contains NetWare DHCP Server v2.0B. This is the latest version of DHCP and provides both DHCP and BOOTP functionality to NetWare IP servers. Not to be used on servers running MPR 2.x or NetWare Connect. (this is the same DHCP that sips with LAN WorkPlace Pro). ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- ISSUE: DHCP2B.EXE contains NetWare DHCP Server v2.0B. This is the latest version of DHCP and provides both DHCP and BOOTP functionality to NetWare IP servers. Not to be used on servers running MPR 2.x or NetWare Connect. Self-Extracting File Name: dhcp2b.exe Files Included Size Date Time ..\ DHCP2B.TXT (This file) DHCPDNST.NLM 7548 4-15-96 1:08:06 pm DHCPINST.NLM 2452 4-15-96 1:07:18 pm DHCPSRVR.RMV 393 10-26-95 1:03:50 pm PINSTALL.HLP 3753 10-13-94 1:58:48 pm PINSTALL.NLM 119868 12-9-94 9:56:20 am PSCRIPT.DAT 3339 4-11-96 3:41:06 pm RSPAWN.NLM 23087 1-3-96 5:15:32 pm ..\DHCP\ DHCPCFG.NLM 219759 4-15-96 1:06:58 pm DHCPIO.NLM 159436 4-15-96 1:25:20 pm DHCPSRVR.NLM 53991 4-15-96 1:23:30 pm ..\DHCP\NLS4\ DHCPCFG.HLP 108358 3-14-96 6:08:40 pm DHCPCFG.MSG 9131 4-15-96 1:06:56 pm DHCPSRVR.MSG 1853 4-15-96 12:59:10 pm ..\NLS4\ DHCPDNST.MSG 752 4-15-96 1:08:06 pm DHCPINST.MSG 267 4-15-96 1:07:18 pm RSPAWN.MSG 1658 1-3-96 5:15:32 pm ..\UTILS\ CSLSTUB.NLM 3122 11-21-94 6:21:08 pm SNMP.NLM 90428 1-3-96 3:21:32 pm SNMPLOG.NLM 13477 11-22-94 8:59:18 am TCPIP.NLM 392249 1-25-96 1:50:22 pm ..\UTILS\3X\ NETDB.NLM 53978 6-7-93 4:02:06 pm ..\UTILS\NLS4\ SNMP.MSG 3816 1-3-96 3:21:30 pm SNMPLOG.MSG 615 11-21-94 7:41:24 pm TCPIP.MSG 14509 1-18-96 12:47:38 pm Installation Instructions: NOTE1: DHCP2B is not compatible with MPR 2.0, 2.1 or 2.11. To use DHCP2B with MPR, you must upgrade to a later version (MPR 3.0 or MPR 3.1). NOTE2: Do not load the files in DHCP2B, on the same server as the DHCPD.NLM released with NetWare Connect. NOTE3: DHCP2B contains a TCPIP.NLM version which must not be used with NetWare Connect! NOTE4: DHCP2B contains a TCPIP.NLM version which can be used on a NetWare 3.12 server, but, only in the environment provided by DHCP2B! NOTE5: We suggest that you save the following files in a separate directory, as DHCP2B could install later versions of the NLMs and MSG files. CSLSTUB.NLM NETDB.NLM SNMP.NLM SNMP.MSG SNMPLOG.NLM SNMPLOG.MSG TCPIP.NLM TCPIP.MSG TUI.NLM TUI.MSG FIRST: Unload (and never reload) BOOTPD.NLM, LWGCON.NLM, and LWGIO.NLM. DHCP2B provides both DHCP and BOOTP functionality and in essence obsoletes BOOTPD.NLM. DHCPSRVR.NLM can not run with BOOTPD.NLM running on the same Server. SECOND: Create a DHCPSRVR directory. THIRD: "Explode" DHCP2B.EXE into the DHCPSRVR directory. Then go on to either "Local Install" or "Remote Install". NOTE: If you put the files in DHCP2B.EXE on a floppy, volume lable the floppy, DHCPSRVR. A. A Local Install ------------------ A1. At the sever console; LOAD INSTALL. A3. Go to "Product Options". A4. Select "Product Not Listed". A5. Hit "F3" and enter the volume and path to the directory you exploded DHCP2B into. A6. Install will proceed automatically. A7. The DHCP2B install program will automatically copy your SYS:\ETC\BOOTPTAB file in to the new SYS:\ETC\DHCPTAB. Do not manually edit this file! After installation is completed, load DHCPCFG.NLM and ensure that all the BOOTP records have copied properly. A8. DHCP2B will ignore any IP addresses bound to WAN boards. B. Remote Install ----------------- NOTE: If, while doing the remote install, you receive the error message "version of rspawn.nlm is incompatible with the one on the remote server", load the RSPAWN.NLM in DHCP2B on the remote server. B1. Bring up Rconsole. B2. Create a directory called DHCPSRVR on the remote server. B3. Copy the files in DHCP2B to a to the DHCPSRVR directory on the remote server. B4. At the sever console; LOAD INSTALL. B5. Go to "Product Options". B6. Select "Product Not Listed". B7. Hit "F3" and enter the volume and path to the directory you exploded DHCP2B into. B8. Install will proceed automatically. B9. The DHCP2B install program will automatically copy your SYS:\ETC\BOOTPTAB file in to the new SYS:\ETC\DHCPTAB. Do not manually edit this file! After installation is completed, load DHCPCFG.NLM and ensure that all the BOOTP records have copied properly. B10. DHCP2B will ignore any IP addresses bound to WAN boards. C. Configuration ---------------- - Configuration changes If you bind any new IP address on the server after DHCPIO.NLM has been loaded, and will use DHCP2B to distribute IP addresses on newly bound IP address's subnet, you must use DHCPCFG.NLM to manually configure the subnet profile. - To Configure Workstation Address Assignment Mode Use the (-m) option when loading DHCPIO.NLM, to configure workstation address assignment mode. Load dhcpio -m where mode is: DeleteDuplicate = If a workstation was in subnet A, it moves to subnet B later. When the workstation sends out request from subnet B, DHCPSRVR.NLM will delete the address of that workstation in subnet A, and reassigned a new address to it in subnet B. YesDuplicate = If a workstation moves from subnet to subnet, DHCPSRVR.NLM will give out an address to it in every subnet when it is available. NoDuplicate = If a workstation moves from subnet A to subnet B, before the address in subnet A is deleted (bootp case) or expired (dhcp case), DHCPSRVR.NLM will drop the request. For Example: load -mYesDuplicate ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------