NOTE; This documented has been formated for .5" margins. Addendum to NetWare Access Server Administration Guide OnLAN/PC User's Reference OnLAN/Mac User's Guide Version 1.2 2/92 Installing Access Server V1.22 Changes to Access Administration Guide, pages 2-11, 6-2, 6-3, 6-10, 6-12, 7-48, 7-49, and Glossary-5. If you are installing NetWare Access Server for the first time, follow the preparation and procedures described in the "NetWare Access Administration Guide". However, for NetWare Access (version 1.22 or later), disregard all instructions in the "NetWare Access Administration Guide" for installing special NetWare Access versions of the following files on connecting NetWare file servers: > LOGIN.EXE > LOGOUT.EXE > ONFILEM.EXE These files are no longer necessary and have been eliminated from the distribution diskettes. Supporting MS-DOS Version 5.0 Addition to "NetWare Access Administration Guide" NetWare Access supports MS-DOS Version 5.0; however, if you are using MS-DOS Version 5.0, do not configure MS-DOS to run in the High Memory Area. OnLAN Script PARITY Command Addition to "OnLAN/PC User's Reference", Appendix F You can insert a new PARITY command in OnLAN/PC script files to automatically change the OnLAN parity checking mode from NONE to a parity mode required by an intermediate device. For example, the default parity for OnLAN is NONE; however, you might want to set parity to EVEN if connecting to an Access Server through an X.25 public data network (PDN). Any parity setting other than NONE also changes the data bits (per character) setting from 8 to 7. After the connection through the intermediate device is established with the Access Server, NetWare Access and OnLAN/PC automatically reset parity to NONE and data bits to 8 for the rest of the session. PARITY command syntax is: parity even | odd | mark | none | space where: even sets parity to EVEN. odd sets parity to ODD. mark sets parity to MARK. none sets parity to NONE. space sets parity to SPACE. Additional OnLAN Modem Support Additions to OnLAN/PC User's Reference, Table 4-1 OnLAN/PC v1.22 supports an expanded set of modems. In addition to the modems listed in Table 4-1 of the OnLAN/PC User's Reference, OnLAN/PC software now supports the modems listed below: Apollo V. 32 turbo ATI 9600 etc/e Codex 3220 Codex 3260/3265 CompuCom Speedmodem Combo Forval 14400 Forval 9600 V.32 Hayes Smartmodem OPTIMA 96 Hayes V-series Ultra 144 Practical Peripherals 2400SA V.42bis Racal Vadic 9632 VP Touchbase Worldport 1200 Touchbase Worldport 9600 UDS FasTalk V.32/42bis File Transfer with OnLAN/Mac Workstations Changes to NetWare Access Administration Guide, pages 2-11, 6-3, 6-12, 7-48, and 7-49; and OnLAN/Mac User's Guide, pages 2-3, and 7-1. You can now use ONFILE.EXE to transfer files between a NetWare file server and an OnLAN/Mac workstation. ONFILEM.EXE, the utility previously used for this task, has been eliminated. Starting ONFILE from an OnLAN/Mac Workstation To run the ONFILE program, run your OnLAN/Mac session and enter the following at the DOS command line: ONFILE When the File Transfer window appears, follow the file transfer procedures described in Chapter 7 of the OnLAN/Mac User's Guide. Running ONFILE by Command Line You have the option of carrying out an ONFILE transfer entirely from a command line. The command line syntax is: onfile source_file to|from server|remote [destination_file] where: SOURCE_FILE is the name of source file you are transferring (include the full path if you are not sure of the current directory). TO|FROM indicates the transfer direction (to or from). SERVER|REMOTE indicates the origin or destination of the transferred file. DESTINATION_FILE is the name of destination file (this is optional) For more information on using the ONFILE utility, see the OnLAN/PC User's Reference. LOGIN.EXE and LOGOUT.EXE Changes to NetWare Access Administration Guide, pages 2-11, 6-2, 6-10, 7-48, 7-49, and Glossary-5 Special versions of LOGIN.EXE and LOGOUT.EXE are no longer required on NetWare file servers connected to the Access Server. All versions of NetWare later than 2.15d use LOGIN.EXE and LOGOUT.EXE files that support Access Server connections. The special versions of LOGIN.EXE and LOGOUT.EXE included with Access 1.2 have been removed from this version. Adjusting NetWare Access IPX Packet Size Addition to NetWare Access Administration Guide The default Internetwork Packet Exchange (IPX) packet size setting on the Access Server is 512 bytes. If your network is configured to support larger packet sizes, you can edit configuration files on the Access Server to increase its IPX packet size also. Increasing the IPX packet size increases throughput, but it can also force the IPX.COM file to use base memory rather than high memory space in the Access Server. To increase the IPX packet size, do the following: > Edit the DVINTF.CFG file to increase IPX packet size. See Editing DVINTF.CFG. > Edit the NASAUTO.BAT file to configure IPX.COM to handle the new packet size. See Editing NASAUTO.BAT. > If you want to configure IPX.COM to handle the largest IPX packet possible without using base memory, you will require some additional calculations. See Maximizing High Memory for IPX.COM. Editing DVINTF.CFG Use the MAX BUFFER LENGTH setting in the DVINTF.CFG file to increase IPX packet size. 1. Look for the DVINTF.CFG file in the ACCESS directory. If no such file exists, create one. 2. Using a text editor, add or edit the following line in DVINTF.CFG: max buffer length = dvintf_packet_size where: dvintf_packet_size is the size, in bytes, of the IPX packet issued from the Access Server. The default setting for this parameter is 512; the maximum setting is 4069 (to accommodate token ring capacities). 3. After editing DVINTF.CFG, edit the NASAUTO.BAT file. See Editing NASAUTO.BAT. Editing NASAUTO.BAT After editing the DVINTF.CFG file to increase the IPX packet size, edit the NASAUTO.BAT file to configure IPX.COM to handle the new packet size. 1. Locate the NASAUTO.BAT file in the ACCESS directory. 2. Using a text editor, open NASAUTO.BAT. Locate and change the following line from: loadhi /SIZE:old_ipx_size ipx.com TO: loadhi /SIZE:new_ipx_size ipx.com WHERE: OLD_IPX_SIZE is the memory, in bytes, currently specified in the LOADHI command line for IPX.COM. NEW_IPX_SIZE is the memory, in bytes, required for IPX.COM to handle the larger packet size you specified in the DVINTF.CFG file. To calculate new_ipx_size, use the following formula: ((dvintf_packet_size - 512) * 30) + old_ipx_size =new_ipx_size NOTE: If the new memory size specified for IPX.COM exceeds its available block of high memory, IPX.COM will run in base memory, using up memory that could otherwise be used to run applications. To avoid this situation, see Maximizing High Memory for IPX.COM. Maximizing High Memory for IPX.COM If you want to configure the largest IPX packet size possible without forcing IPX.COM from high memory, adjust the IPX.COM size to run in the largest contiguous block of high memory available. 1. Start an operator session at the Access Server and go to the ACCESS directory. 2. Enter LOADHI This command displays all occupied and available ranges in high memory. 3. Look for the largest contiguous block of available memory. Note the available kilobytes. For example, the following line: 3 C400 - C800 16K Available indicates 16K of high memory available at this range. 4. Look for the block of memory occupied by IPX.COM and any blocks of available memory immediately next to this block. Then add these blocks together. For example, the following lines: 3 F478 - FE63 39K Used (IPX) 3 FE64 - FFFC 6.3K Available indicate a total of 45.3K of high memory usable by IPX.COM at these adjacent locations. 5. Use the larger memory value (from Step 3 or Step 4) to calculate the new size of IPX.COM. Multiply that value by 1024. This gives you the maximum high memory, in bytes, available for IPX.COM. For example, if a block of 45.3K is available in high memory, then 45.3K x 1024 = 46387 bytes. 6. Edit NASAUTO.BAT. Edit the following line: loadhi /SIZE:size_in_bytes ipx.com where: size_in_bytes is the number of bytes calculated in Step 5. 7. Edit DVINTF.CFG. Add or edit the following line: max buffer length = new_packet_size where: new_packet_size is the new packet size in bytes. Start with a value of 1024. If that works, try increasing the size by 1K (1024 bytes) until you get an IPX segment overflow message. After you get this message, reduce the packet size by 1K. Setting File Capacity Addition to NetWare Access Administration Guide To increase the number of network files that applications can open at one time in a NetWare Access session, edit the FILE HANDLES parameter in the DVNET.CFG file of your Access Server. 1. Find the DVNET.CFG file in the ACCESS directory of your Access Server. 2. Using a text editor, add or edit the following line in DVNET.CFG. file handles = open_files where: open_files is the maximum number of files on the NetWare file server that your application might need to open at one time. The maximum setting for this parameter is 255. WARNING: The total value of the Access Server FILES setting in CONFIG.SYS plus the FILE HANDLES setting in DVNET.CFG must not exceed 255. Any larger combined value will cause system failure. The FILE HANDLES setting applies to all sessions being run through NetWare Access. For example, the following setting in DVNET.CFG: file handles = 100 allows applications in any NetWare Access session to open up to 100 concurrent files. If applications were running in 8 simultaneous NetWare Access sessions, each application could open 100 concurrent files. Altogether, up to 800 concurrent files could be opened by applications running in 8 concurrent sessions. Using DVNET.CFG Addition to NetWare Access Administration Guide The Access Server DVNET.CFG file is the equivalent of a NetWare workstation's SHELL.CFG file. Any parameter that you can include in a workstation's SHELL.CFG file, can be entered in the Access Server DVNET.CFG file with the same results. Supporting NetBIOS Sessions Addition to NetWare Access Administration Guide You can configure the Access Server to support up to 16 NetBIOS sessions if you install version 3.02 of the Novell NetBIOS emulator. 1. Obtain a copy of NETBIOS.EXE, version 3.02 or later, and copy it to the Access Server ACCESS directory. If you do not have version 3.02 or higher of NETBIOS.EXE available with your NetWare product, you can obtain it through NetWire in a zipped file called NASNET.ZIP. 2. Copy MEMMGR.EXE from the NetWare Access v1.22 distribution diskettes to the Access Server ACCESS directory. MEMMGR.EXE allows multiuser access to the NetBIOS emulator. 3. Edit the Access Server NASAUTO.BAT file to call the following files in the following order: a. IPX.COM b. MEMMGR.EXE c. NETBIOS.EXE 4. If you need to modify the NetBIOS emulator parameters, create and edit a NET.CFG file in the Access Server ACCESS directory. The NET.CFG file is the NetBIOS equivalent of a NetWare workstation's SHELL.CFG file. You can optimize performance of NetBIOS applications that are being run through the Access Server by entering SHELL.CFG parameters in the NET.CFG file. Any parameter that you can include in a workstation's SHELL.CFG file can be entered in the NET.CFG file with the same results applied to NetBIOS sessions. 5. Restart the Access Server. Loading NASI Version 2.11 or Earlier Changes to OnLAN/PC User's Reference, pages 4-1, 4-16 and 5-5 To load versions 2.09 to 2.1x of the NASI driver (NASI.EXE), enter nasi /d Multiplexed Connections from OnLAN/PC Changes to OnLAN/PC User's Reference, pages 4-21, 5-6, 6-4, and 7-24; and NetWare Access Administration Guide, pages 7-16 and 7-19 When setting up multiplexed connections to the Access Server from an OnLAN/PC workstation, specify the following settings in OnLAN/PC, in NetWare Access, and at the multiplexer: 1. At the OnLAN/PC workstation, set the Modem field in the OnLAN/PC Configuration screen to None. 2. Set the Flow control field to None in the OnLAN/PC Configuration or the Current Terminal Settings screen. 3. Set the Error correction field to Maximum in the OnLAN/PC Settings screen or in the Special Options screen. 4. From the Access Server Information Menu, set the Modem and Flow control fields to None in the Port Configuration screen(s) for the port(s) supporting the multiplexed connection(s). 5. Make sure the multiplexer is set to 8 data bits, no parity. Direct Connections from OnLAN/PC DIRECT CONNECTIONS FROM OnLAN/PC Changes to OnLAN/PC User's Reference, pages 4-21, 5-6, 6-4, and 7-24; and NetWare Access Administration Guide, pages 7-16 and 7-19. When setting up direct connections to the Access Server from an OnLAN/PC workstation, specify the following settings in OnLAN/PC and in NetWare Access: 1. At the OnLAN/PC workstation, set the Modem field in the OnLAN/PC Configuration screen to None. 2. Set the Flow control field to RTS/CTS in the OnLAN/PC Configuration or the Current Terminal Settings screen. 3. Set the Error correction field to None in the OnLAN/PC Settings screen or in the Special Options screen. 4. From the Access Server Information Menu, set the Modem field to None and the Flow control field to RTS/CTS in the Port Configuration screen(s) for the port(s) supporting the direct connection(s). 5. If unwanted printer control characters appear in your OnLAN/PC sessions, reset your OnLAN/PC Error correction field to Maximum. ASTATUS.EXE Addition to NetWare Access Administration Guide A new utility, ASTATUS.EXE, located in the ACCESS directory of the Access Server, enables users to determine their port and session number on the Access Server. The next three sections, Installing ASTATUS.EXE, Using ASTATUS.EXE, and Displaying LAN Connections, describe installation and usage of this utility. A fourth section, Using APORT and ASESSION Variables, describes the use of two related variables that ASTATUS.EXE writes to the environment space of the connecting DOS workstation. Installing ASTATUS.EXE To install ASTATUS.EXE, copy the file from the ACCESS directory of the Access Server to an accessible directory on the NetWare file server and give all NetWare Access users who need to use ASTATUS.EXE read and execute rights to that directory. Using ASTATUS.EXE After logging in from a DOS workstation as a NetWare Access user to the NetWare file server, enter ASTATUS ASTATUS.EXE displays the available session memory, the number of the Access Server port you are logged in to, and the number of the Access session you are in. For example: Available Session memory: 534112 bytes Access Server Port Number: 01 Access Server Session Number: 01 Displaying LAN connections ASTATUS.EXE returns special server port values to indicate OnLAN/PC and OnLAN/Mac LAN connections. > If you run ASTATUS.EXE and have logged in through an OnLAN/PC LAN connection rather than a dial-in connection, the server port line displays a value of 134: Access Server Port Number: 134 > If you have logged in on an OnLAN/Mac LAN connection rather than a dial-in connection, the server port line displays a value of 138: Access Server Port Number: 138 Using APORT and ASESSION Variables When invoked, ASTATUS.EXE also writes two variables, APORT and ASESSION, to the connecting DOS workstation's environment space. For example, assuming that ASTATUS.EXE was run and displayed a server port number of 1 and session number of 1, running the DOS SET command at the DOS workstation would display the following lines: APORT = 01 ASESSION = 01 Variables written into the environment space can be retrieved and used by batch files and programs. For example, if a user logs in through Port 01 on the Access Server and that user's login script invokes ASTATUS.EXE and then calls a batch file, then the following batch file line: if %aport%==01 echo Connected to 2400 baud port. would display the following line to the user: Connected to 2400 baud port. For more information on retrieving variables from the DOS environment space, see a DOS reference. Increasing RAM Disk Space Change to NetWare Access Administration Guide, page A-15 Under some circumstances, the Access Server may fail to start and displays the following message: *** The terminal configuration file could not be found. This message might indicate that the internal files that NetWare Access writes to its specially configured Random Access Memory (RAM) disks have gotten too large for the RAM disks to hold. If this is the case, you must edit the Access Server CONFIG.SYS file to increase NetWare Access RAM disk space. 1. Using a text editor, open the Access Server CONFIG.SYS file. 2. Find the CONFIG.SYS device lines that configure NASDISK.SYS. For example: device=C:\access\nasdisk.sys /p18 /s device=C:\access\nasdisk.sys /p9 /s In the above example, the first line configures eighteen 16K pages of RAM for NetWare Access RAM drive D. The second line configures nine 16K pages of RAM for NetWare Access RAM drive E. 3. Reconfigure the second RAM disk device line for more RAM. For example, you would change the following line: device=C:\access\nasdisk.sys /p9 /s TO: device=C:\access\nasdisk.sys /p11 /s 4. Restart the Access Server. Connecting to AppleTalk Phase 1 and Phase 2 Change to NetWare Access Administration Guide, Appendix G. To support OnLAN/Mac connections to NetWare Access through an AppleTalk LAN, you must set up an AppleTalk-to-NetWare connection through a NetWare for Macintosh server, load the special MACTONAS NLM on that server, edit that server's AUTOEXEC.NCF file, and create and edit a MACTONAS.CFG file. 1. Install the Access Server as described in the NetWare Access Administration Guide. To enable AppleTalk LAN connections, read the instructions for the General Configuration Screen in Chapter 7, Installing NetWare Access Software. AppleTalk LAN connections are allowed when the Allow LAN Connections menu item is set to OnLAN/Mac via AppleTalk or Both. 2. Install a NetWare v3.11 server on the network as described in the NetWare manual titled NetWare Version 3.11 Installation (Part number 183-000298-001). The server installation must provide an IPX connection to the Access Server. During installation, add lines to the NetWare file server's AUTOEXEC.NCF file to carry out the following: > Specify the NetWare server name. > Specify an internal IPX network number for the NetWare file server. > Load and configure the LAN driver for the LAN adapter attached to the network to which the Access Server is connected. > Bind IPX to the LAN driver and specify the number for the network on which the NetWare file server and the Access Server are attached. EXAMPLE The following example AUTOEXEC.NCF lines establish an IPX connection to the network containing the Access Server: file server name TEST311 ipx internal net F12345A load ne2000 int=2 port=300 frame=ethernet_802.3 name=ne20 bind ipx to ne20 net=F0000 IMPORTANT: The above AUTOEXEC.NCF lines are examples only. The lines you enter must be consistent with your actual network configuration. The first line specifies TEST311 as the NetWare file server name. The second line specifies F12345A as the server's internal network number. The third line loads an NE2000 LAN driver, specifies an Ethernet 802.3 frame type, and names the LAN adapter NE20. The fourth line specifies F0000 as the number for the network connecting to the LAN adapter. 3. Install NetWare for Macintosh v3.0x on the NetWare v3.11 file server that you just set up. Follow the procedure described in the NetWare for Macintosh Version 3.0 Installation and Maintenance Guide (Part number 100-000914-001). The NetWare for Macintosh installation must provide an AppleTalk connection to a network or internet on which OnLAN/Mac users are located. During installation, add lines to the AUTOEXEC.NCF file to carry out the following tasks: > Load the NetWare for Macintosh AppleTalk module and specify an internal AppleTalk network number and internal AppleTalk zone name. > Load and configure the LAN driver for the LAN adapter attached to the network to which the OnLAN/Mac nodes are connected. > Bind the AppleTalk module to LAN adapter board name and specify the network number(s) and zone names containing the connecting OnLAN/Mac nodes. > Load the NLM for the AppleTalk Filing Protocol. For detailed instructions on entering the above lines, see pages 29-31 in the NetWare for Macintosh Version 3.0 Installation and Maintenance Guide. Phase 1 Example The following example AUTOEXEC.NCF lines support an AppleTalk Phase 1 configuration: load appletlk net=12121 zone={appletalklan} load ne2000 int=2 port=300 frame=ethernet_II name=apphase1 bind appletlk apphase1 net=43231 zone={sales} load AFP IMPORTANT: The above AUTOEXEC.NCF lines are examples only. The lines you enter must be consistent with your actual network configuration. The first line assigns the NetWare file server an internal AppleTalk network number of 12121 and an internal zone name of appletalklan. The second line loads the driver for the NE2000 LAN adapter through which the Macintosh network nodes are connected. This line specifies an Ethernet II frame type, and assigns the board name apphase1. The third line binds the Appletalk module to the apphase1 board and to Appletalk network 43231 and AppleTalk zone sales, the network and zone on which the connecting Macintosh nodes are located. The fourth line loads the AppleTalk Filing Protocol. Phase 2 Example The following example AUTOEXEC.NCF lines support an AppleTalk Phase 2 configuration: load appletlk net=12121 zone={appletalklan} load ne2000 int=2 port=300 frame=ethernet_snap name=apphase2 bind appletlk apphase2 net=1-5 zone={sales} load AFP IMPORTANT: The following AUTOEXEC.NCF lines are examples only. The lines you enter must be consistent with your actual network configuration. The first line assigns the NetWare file server an internal AppleTalk network number of 12121 and an internal zone name of appletalklan. The second line loads the driver for the NE2000 LAN adapter through which the Macintosh network nodes are connected. This line specifies an Ethernet Snap frame type, and assigns the board name apphase2. The third line binds the AppleTalk module to the apphase2 board and to Appletalk networks 1-5 and AppleTalk zone sales, the networks and zone on which the connecting Macintosh nodes are located. A net setting of 1-5 allows 1265 AppleTalk nodes. The fourth line loads the AppleTalk Filing Protocol. 4. Transfer the file MACTONAS.NLM from the Access Server distribution diskettes to SYS:SYSTEM on the NetWare v3.11 file server. 5. Add the following statement at the end of the AUTOEXEC.NCF file: load mactonas The following example is one possible AUTOEXEC.NCF configuration supporting Macintosh-to-NetWare Access LAN connections: file server name TEST311 ipx internal net F12345A load token int=2 port=a20 mem=c800 name=tkn bind ipx to tkn net=F0000 load appletlk net=10 zone={appletalklan} load ne2000 int=2 port=300 frame=ethernet_snap name=apphase2 bind appletlk apphase2 net=1-5 zone={sales} load AFP load mactonas The above AUTOEXEC.NCF lines are examples only. The lines you enter must be consistent with your actual network configuration. 6. Create the file MACTONAS.CFG and place it in SYS:SYSTEM on the NetWare v3.11 file server. The MACTONAS.CFG file is required and must include a line description for every Access Server that will support OnLAN/Mac LAN access to this NetWare file server. The format for each line of this text file is as follows: nas_name/num_macs where: nas_name is the name assigned to the Access Server during installation. num_macs is the total number of OnLAN/Mac connections the NetWare file server allows between the Access Server (1-16) and computers on the AppleTalk LAN. For example, the following MACTONAS.CFG file: NAS_SALES/10 ACCESS_SERVER_TEST/5 NAS_ACCT_DEPT/15 specifies that three Access Servers, supporting respectively 10, 5, and 15 OnLAN/Mac connections, are able to access the NetWare file server on which this file is installed. Permitting Grace Logins Addition to NetWare Access Administration Guide If you want to allow any grace login for NetWare Access users who log in to a NetWare file server with expired passwords, do not set the Limit Grace Logins option in that NetWare file server's SYSCON Account Restriction menu to less than 2. For more information on limiting grace logins, see NetWare Version 3.11 Utilities (Part number 100-000930-001), pages 442-445. Configuring QEMM386.SYS Addition to NetWare Access Administration Guide, Appendix C Memory conflicts caused by various devices competing for the same areas of high memory on the Access Server can prevent the Access Server from starting or cause it to fail after startup. You might be able to resolve high memory conflicts by reconfiguring the device line for QEMM386.SYS in your Access Server CONFIG.SYS file. NetWare Access uses the Quarterdeck Expanded Memory Manager 386 (QEMM386) to configure and manage expanded memory on the Access Server. To support NetWare Access, the QEMM386 page frame requires one or more contiguous 64K ranges of high memory in which to operate. QEMM386.SYS utilizes as much memory in the Access Server C000-EFFF range as it finds available. If other devices, such as network adapters and third-party communication cards, require some of this memory area, QEMM386.SYS normally detects this and automatically writes include (i=) or exclude (x=) parameters to its CONFIG.SYS device line to reconfigure itself to work in other areas of high memory. > If for some reason, QEMM386.SYS neglects to exclude a high memory range used by another device, you can manually add include or exclude parameters to the QEMM386.SYS device line. > Other QEMM386 parameters noted in this section configure QEMM386 to do the following: > Operate on old versions of COMPAQ 386S computers. > Disable features such as ROM hole detection, use of shadow RAM, use of top memory, and relocation of the extended BIOS data area. > Support computers using nonstandard methods of extended memory detection. Viewing High Memory You can use the QEMM.COM utility to detect addressing conflicts between QEMM386.SYS and other device drivers in base memory and high memory. 1. Follow the procedure described on page C-6 of the NetWare Access Administration Guide to do the following: > Make a special startup diskette with QEMM specified as a device in the startup diskette's CONFIG.SYS file. > Use this diskette to start the computer on which NetWare Access is installed. > Run QEMM.COM and view the current memory assignments. 2. If you detect a memory conflict between QEMM386 and the driver for an installed device, edit the device line for QEMM386.SYS in the Access Server CONFIG.SYS file. See Editing the QEMM386 Device Line. Editing the QEMM386 Device Line 1. Using a text editor, open the CONFIG.SYS file in your Access Server root directory. 2. Find and edit the following line: device=C:\access\qemm386.sys ...[X=aaaa-bbbb] ... [I=cccc-dddd]...[other_params] where: aaaa is the hexadecimal address of the start of a memory range to exclude from use by QEMM386.SYS. bbbb is the hexadecimal address of the end of a memory range to exclude from use by QEMM386.SYS. cccc is the hexadecimal address of the start of a memory range to include for use by QEMM386.SYS. dddd is the hexadecimal address of the end of a memory range to include for use by QEMM386.SYS. other_params are additional parameters. These parameters are described in Other QEMM386 Parameters. Example Include and Exclude Parameters The following CONFIG.SYS device line excludes a range of high memory from use by QEMM386.SYS and sets aside an additional range for use by QEMM386.SYS: device=C:\access\qemm386.sys X=C000-C7FF I=D000-DFFF Other QEMM386.SYS Parameters You can add other parameters to the CONFIG.SYS device line for QEMM386.SYS. These parameters are described as follows: C386S Specify this parameter on the QEMM386.SYS device line if NetWare Access is running on a COMPAQ 386S computer that was set up with a COMPAQ Setup program earlier than version 6.02. For example: device = c:\access\qemm386.sys c386s NRH Disables QEMM386.SYS automatic detection of Read-Only Memory (ROM) holes, or unused addresses in ROM. Some system ROM chips that are addressed between F000 an FFFF have large unused areas of ROM. QEMM386.SYS normally checks for these areas and includes them for its own use. System failure can occur if ROM areas that are initially unused (and thus appropriated by QEMM386.SYS) are later required for other tasks. If the Access Server functions properly at first, and fails later, use this instruction to prevent QEMM386.SYS from using ROM holes. For example: device = c:\access\qemm386.sys nrh NOSH Disables QEMM386.SYS use of shadow RAM in the Access Server. Some PCs put 384K of reserved memory in low memory with an I/O port-selectable method of accessing some of it. QEMM386.SYS normally determines automatically if your PC has shadow RAM capability. If shadow RAM does not work, you might need to disable it with the NOSH parameter. For example: device = c:\access\qemm386.sys nosh NT Disables QEMM386.SYS use of "top memory" in the Access Server. Some Pcs put 384K of memory just below the top of the 16-megabyte address space. QEMM386.SYS normally checks that address space to determine if there is any memory. In some Pcs checking this space can cause the system to fail. If your computer fails during startup, use the NT parameter. For example:device = c:\access\qemm386.sys nt NX Disables QEMM386.SYS from relocating the extended BIOS data area from the original 639K address in the Access Server. Specify this parameter if you want to run applications that require the extended BIOS data area to be located at the 639K address. For example: device =c:\access\qemm386.sys nx UX Supports NetWare Access on computers that use nonstandard methods of determining the amount of extended memory. If your Access Server does not start correctly with QEMM386.SYS, try specifying this parameter on the QEMM386.SYS device line. For example: device = c:\access\qemm386.sys ux Connecting to TCP/IP Networks You can make a TCP/IP connection to a UNIX host via the Access Server by installing the multiuser version of Novell's LAN Workplace for DOS on a NetWare file server and installing an additional Ethernet connection and Novell DOS Open Data-link Interface (ODI) drivers on the Access Server. 1. Install files for the multiuser version of LAN Workplace for DOS on a local NetWare file server in the XLN\BIN40 directory. XLN\BIN40 should contain the TNVT220 application that opens TELNET sessions using VT220)terminal emulation. See the LAN Workplace for DOS Administration Guide (Part number: 100-000882-001) for details. 2. Use the NetWare SYSCON utility to configure a special TCP user on the NetWare file server containing LAN Workplace for DOS. 3. Use the NetWare SYSCON utility to edit the NetWare file server's system login script to automatically map Access Server users to the NetWare file server's XLN\BIN40 directory. For example, the following lines, added to the NetWare file server's system login script, map users who log in through the Access Server with the username TCP to the NetWare file server's XLN\BIN40 directory: if access_server and login_name="TCP" then begin map f:=\xln\bin40 end For more information on setting up login scripts for Access Server users, see the NetWare Access Administration Guide. 4. If you have not already done so, install the Access Server on another node on the network. See the NetWare Access Administration Guide for installation details. 5. After installing NetWare Access, insert an additional Ethernet LAN adapter in the Access Server and connect to the network so that the Access Server has two network connections. The Access Server original LAN adapter will transmit and receive IPX packets. The additional LAN adapter will transmit and receive TCP/IP packets. 6. Create a special ODI directory on the startup drive of the Access Server and copy the following files to that directory: NET.CFG This is the NET.CFG file that you created in the LAN Workplace for DOS installation to define I/O,RAM, Interrupt Request (IRQ), and TCP/IP parameters. Copy from the NetWare file server to the Access Server. LSL.COM Copy from your Novell LAN workstation diskette. Make sure you have the latest ODI drivers. TCPIP.EXE Copy from your LAN Workplace for DOS distribution diskette. TELAPI.EXE Copy from your LAN Workplace for DOS distribution diskette. MLID driver This is the driver for the additional Ethernet LAN adapter; it has a filename like NE2000.COM or WDPLUS.COM, for example. Copy from your NetWare diskettes or from the diskettes accompanying the LAN adapter. 7. Using a text editor, add the following CAPITALIZED lines to the Access Server AUTOEXEC.BAT file: set name=username set excelan=xln_path c: C:\ODI\LSL C:\ODI\MLID_driver C:\ODI\TCPIP C:\ODI\TELAPI cd c:\access Naskey Nasauto Where: username is the user name as specified for LAN Workplace for DOS. The set name= line stores the username in the Access Server DOS environment space. See the LAN Workplace for DOS Administration Guide for more information. xln_path is the pathname to the directory containing the LAN Workplace for DOS files on the network server. The set excelan= line stores the xln_path in the Access Server DOS environment space. See the LAN Workplace for DOS Administration Guide for more information. MLID_driver is the filename (minus extension) of the LAN driver for the additional Ethernet LAN adapter. See AUTOEXEC.BAT Example, later in this addendum, for a complete AUTOEXEC.BAT file example. 8. Using a text editor, add or edit the following lines in the Access Server NET.CFG file: Link Driver MLID_driver Port io_address Mem sharedram_adr Int interrupt Frame Ethernet_II where: MLID_driver is the filename (minus extension) of the LAN driver for the additional LAN adapter you are installing. io_address is the port I/O address configured for the additional Ethernet LAN adapter. sharedram_adr is the starting address in high memory configured for the LAN driver of the additional Ethernet LAN adapter. interrupt is the interrupt setting for the additional Ethernet LAN adapter. NOTE: Some LAN drivers might not require all of the above parameters specified in NET.CFG. See the NetWare ODI Shell for DOS (Part number 100-000871-001) manual for details. See "NET.CFG Example" later in this addendum for a complete NET.CFG file example. 9. Using a text editor, modify the Access Server CONFIG.SYS file to accommodate the newly installed LAN driver. To avoid high memory conflict, you may have to edit the QEMM386.SYS device line to exclude any range of high memory that may be occupied by the second LAN driver. For example, in the following sample device line, the boldfaced string excludes QEMM386.SYS from operating in the CC00-CFFF address range, which is the range used by the LAN driver for the additional Ethernet LAN adapter: device=c:\access\qemm386.sys maps=32 handles=64 vrems i=a000-afff x=cc00-cfff x=c800-c9ff i=ca00-cbff i=d000-dfff 10. Start the Access Server. The Access Server is ready to communicate using TCP/IP and IPX. Sample Configuration Files on the Access Server The following sample AUTOEXEC.BAT and NET.CFG files on the Access Server support user access to LAN Workplace for DOS. AUTOEXEC.BAT Example The following CAPITALIZED lines were added to the sample Access Server AUTOEXEC.BAT file to support NetWare Access connectivity to LAN Workplace for DOS: SET NAME=TCP REM STORES LWP USERNAME TO ENVIRONMENT SPACE SET EXCELAN=F:\XLN REM STORES PATH TO LWP DIR IN ENVIRONMENT SPACE c: C:\ODI\LSL REM LOADS THE LWP LINK SUPPORT LAYER DRIVER C:\ODI\NE2000 REM LOADS THE LAN DRIVER FOR THE TCPIP PACKETS C:\ODI\TCPIP REM LOADS THE TCPIP STACK C:\ODI\TELAPI -ST 10 -SN 10 REM LOADS THE LWP TELAPI INTERFACE REM CONFIGURES IT TO SUPPORT 10 SESSIONS cd c:\access naskey nasauto NET.CFG Example The following example NET.CFG file was copied from the NetWare file server running LAN Workplace for DOS to the specially created ODI directory on the startup drive of the Access Server. The bold lines were added to support the LAN driver for the additional Ethernet LAN adapter on the Access Server. The Link Support and Protocol TCPIP sections were previously generated by the LAN Workplace for DOS installation program. Link Support Buffers 8 1586 MemPool 4096 Link Driver WDPLUS Port 300 Mem 000cc000 Int 10 Frame Ethernet_II Protocol TCPIP ip_address129.47.6.84 ip_router129.47.4.254 ip_netmas255.255.252.0 tcp_sockets8 udp_sockets8 raw_sockets1 Sample OnLAN/PC Script File Change to OnLAN/PC User's Reference, page F-7 The following sample OnLAN/PC script file corrects the sample script file in the OnLAN/PC User's Reference, page F-7. In the corrected example, WAIT STRING rather than simple WAIT commands are used to await user input. set disconnect on ;abort script if ;disconnect on disconnect goto label10 ;if disconnect ;end script send string "^M" ;send CR code wait string "Enter ID:" ;wait for ID prompt send string "My ID^M" ;send ID wait string "Enter service:" ;wait for service ;prompt send string "Access Server 1^M" ;send service exit ;end script label10: ;error label type string "No connection" ;display message exit ;end script ONLINE SECURITY CONFIGURATION Addition to Access Administration Guide, pages 9-7 to 9-8 NetWare Access v1.22 includes an online Security Configuration screen that you can bring up from Configuration Options in the NetWare Access Information Menu. This screen allows you to reconfigure your NetWare Access security configuration online, without shutting down the NetWare Access Server and rerunning the NASGEN installation program. To display the online Security Configuration screen, do as follows: 1. Select the Configuration option in the NetWare Access Information Menu. 2. Select Security Configuration in the Configuration Options menu. When you select Security Configuration, you are presented with the online Security Configuration screen, similar to the Security Configuration screen displayed in NASGEN. The two differences are: > The online Security Configuration screen contains an additional field, Access Server name. The Access Server name field lets you rename the NetWare Access Server online. > The Activate use of user profiles field, present on the NASGEN Security Configuration screen, is not present on the online Security Configuration screen. For a description of the remaining security fields see the NASGEN description, "Setting the Security Configuration Screen", pages 7-26 to 7-32, in the NetWare Access Administration Guide. OnLAN/PC and Downloadable Fonts Addition to OnLAN/PC User Reference, pages 7-19 to 7-21 OnLAN/PC does not support the use of downloadable fonts in print jobs sent to a printer located at the OnLAN/PC remote workstation site. OnLAN/PC does support downloading of fonts in print jobs sent to a printer on the LAN attached to the Access Server.