Top Issues for October 1992 Q: Is Novell's security fix on NetWare Express? A: Yes. In the NSE Online - Update area the security fix is found in two folders. The 286 VAP is under the 2.2/Patches folder as SECUR.286. The 386 NLM is found in the 3.11/Patches folder as SECUR.386. Q: When running NetWare v2.2, is there an alternative to typing the print server name every time I start the file server? A: Yes, the new PSERVER.VAP (07-10-91) in PSERV1.ZIP prompts for the print server name the first time you load PSERVER.VAP, then it will never prompt for it again. PSERV1.ZIP is found on NetWire in Library 6. NetWare Requester for OS/2 v2.0 Issues Q: What should I do when the system displays the following error messages when booting OS/2 v2.0 with the NetWare Requester v2.0 installed: NWD0115: Error getting connection ID (0x880F) SYS0059: An unexpected network error has occurred A: These error messages indicate that the workstation is unable to communicate with the NetWare file server. Use the following procedure to isolate the cause of the errors: 1. Verify that the LAN hardware is working by booting the workstation to DOS and using the DOS ODI drivers to connect to the NetWare file server. Note: This test under DOS does not necessarily prove that there are no interrupt or memory conflicts in the workstation. Drivers for different operating systems function differently. For example, a LAN card using interrupt line 2 or interrupt line 9 (the default for most Token-ring cards) may conflict with a VGA card and not work under OS/2, while it does work under DOS. This can occur because the standard DOS video driver does not service interrupt line 2. However, the selected OS/2 video driver may hook interrupt line 2 causing a conflict with the network interface card using interrupt line 2. It is also important to note that NDIS drivers share interrupts and that NetWare ODI drivers do not! You may find it necessary to try a different interrupt or memory address for the LAN card to avoid conflicts. 2. Ensure that each frame type specified in the NET.CFG matches each the frame type loaded and bound with the LAN driver at the file server. 3. If Extended Services or LAN Services has been installed, the CONFIG.SYS, NET.CFG, and the PROTOCOL.INI need to be modified correctly. (Note: The PROTOCOL.INI is located in the IBMCOM subdirectory.) Refer to Chapter 6 in the NetWare Requester for OS/2 v2.0 manual and also the README.TXT on the NetWare Requester for OS/2 v2.0 diskette for details of how to properly modify the above three files. Note: Installing Extended Services or LAN Services and ensuring that they are working correctly before installing the NetWare Requester for OS/2 v2.0 is highly recommended. 4. Use the AUI port on the 3Com 3C503 card with the 3C503.SYS driver. This card uses a software setting to select either the BNC or AUI connector. When using the AUI connector on the 3C503 card, add the 1=DIX to the 3C503.SYS line of the CONFIG.SYS file. Example: Device=C:\NETWARE\3C503.SYS 1=DIX Q: What problems are fixed by NSD201.ZIP found on NetWire in Library 5? A: NSD201.ZIP corrects the following problems: 1. VSHELL.SYS and DOSVSHLL.SYS have been changed to allow NetWare commands to function properly in the AUTOEXEC.BAT file. VIPX.SYS and DOSVIPX.SYS have been changed to resolve applications hanging or running out of memory under DOS. 2. NMPIPE.SYS has been modified to avoid hanging during intensive asynchronous transmissions. It has also been enhanced to resolve resource errors and allows a user to see up to 100 Named Pipe servers at one time. NPSERVER.SYS now terminates SPX connections properly and does not run out of LSL buffers or other resources. 3. SPX.SYS has been made more reliable, and it has been modified to allow fewer packets to be sent when the network is in a "congested" state. 4. The NWIFS.IFS has been enhanced to allow the requester to function correctly when 32-bit applications are used. It also fixed a problem with copying files on from the desktop from one NetWare server to another. The problems with logging into a NetWare 2.2 file server, repeated use of a shared resource, and slow performance with database applications running have been resolved through changes to the NWREQ.SYS file. 5. RPRINTER.EXE now works properly in getting a connection to the print server. Note: If you are using Token-Ring, use the old TOKEN.SYS dated 04-17-92 (26,896 bytes) and the old NWTOOLS.EXE dated 05-28-92 (103,648 bytes). Q: I am running OS/2 v2.0 and the NetWare Requester for OS/2 v2.0. How can I use NW Tools to automatically log into a server, MAP drives, and CAPTURE printers when I power on my computer? A: Use the following procedure: 1. Open the Startup folder found in the OS/2 System folder. 2. Open the Templates folder and drag a Program icon to the Startup folder. This will open the settings notebook for the new icon. 3. Click on "Sessions." Click on "Startup Minimized." 4. Click on "Program." 5. Type "\NWTOOLS.EXE" in the "Path and file name:" box. 6. Type the name of the settings file (.NWS) you want to use at startup in the "Parameters" box. 7. Type the path to the directory where NW Tools and the .NWS files are stored (usually C:\NETWARE) in the WORKING directory. 8. Click on "General." 9. Type "NW Tools" in the "Title" box. 10. Double click on the upper left corner of the window. Now, you have an icon that will pop up a login dialog each time you start the machine. NW Tools will minimize to the desktop or the Minimized Window Viewer after you type your password and press . Q: Will the NetWare Requester for OS/2 v2.0 support OS/2 v1.3? A: No. You need the NetWare Requester for OS/2 v1.3. This product is available from Novell at 1-800-Update1, choose option 1. International customers call 408-434-2300 and ask for international order entry. NetWare for Macintosh Issues Q: Can DOS workstations print to AppleTalk printers? A: NetWare for Macintosh includes printer definition files for the LaserWriter and the ImageWriter. After you set up the VAP or NLM so that Macintoshes can print, you only need to run PRINTDEF to import the needed printer definition file (PDF) and define a form. Then run PRINTCON to define a job. Use CAPTURE and NPRINT, along with the DOS application's printer drivers, to send jobs to the queue. A common problem with DOS workstations printing to the Macintosh queues is that print jobs do not print after being submitted to the queue. This happens if a text job, such as a screen print, is sent to a queue through a PostScript job. If you want to print a non-PostScript job, be sure to configure and use APLASER2.PDF for Apple LaserWriter printers, or PSTSCRPT.PDF for th ird-party PostScript printers. These files convert a text file into PostScript so the LaserWriter can print it. They are posted to NetWire on CompuServe and are shipped with v3.01 and v3.011 NetWare for Macintosh. Configuration through PRINTCON and PRINTDEF is documented in NetWare for Macintosh Installation and Maintenance. Other oversights that will result in a failure to print include these: _Not using a print header = 255 command in the SHELL.CFG file on the DOS workstation. _Setting a printer to "reinitialize" mode in a PRINTCON job configuration. _Attempting to print under Windows without the XMS shell. Q: How do I set up printing so my Macintoshes can print to network printers? A: With versions of NetWare for Macintosh below v3.01, all printers (either true Apple LaserWriters or LaserWriter-compatible printers) need to be connected to an AppleTalk network. The AppleTalk network on which the printer resides does not need to be connected directly to the file server, but it must be accessible to the file server via AppleTalk. There are also third-party solutions available for connecting LaserWriter printers to a dedicated AppleTalk device, that is connected to Ethernet. With NetWare for Macintosh v3.01 and above, ATPS (AppleTalk Print Services) queues can be serviced by PostScript printers attached via serial or parallel cables to the NetWare v3.11 file server or NetWare DOS client. You must configure the ATPS.CFG file to set up a queue that will be handled by a print server other than ATPS. The syntax in the configuration file should be similar to this: -o -wb -l -f This syntax also works for PostScript printers that are attached to Ethernet but don't use the AppleTalk protocol, such as the HP IIIsi. The print server that handles this queue is configured in PCONSOLE. Look to the NetWare for Macintosh and Print Server documentation for more detailed information. NetWare Communications Issues Q: Can you run NetWare WAN/Links on the same machine as Runtime and NetWare SAA? A: Yes Q: How many and what type of ports come on the NetWare Synchronous adapters used for the WAN/Links? A: The NetWare Synchronous V.35 adapter comes with two V.35 ports and two RS232 ports. If you want to use all four ports as V.35, swap out the two RS232 ports with two V.35 ports. These are available from Newport Systems. This is also the case with the NetWare Synchronous RS422+ adapter. The NetWare Synchronous RS232+ adapter has four RS232 ports. Q: How much disk space does NetWare WAN/Links take? A: Approximately 10 MB. Q: How can I tell what hardware and software is compatible with: _Access Server _Asynch Router _Multiprotocol Router _NACS _NetWare for SAA _SNA Links _WAN Links A: Each of these products has a published "Rules of Thumb" document. Reading each "Rules of Thumb" document before making any assumptions about hardware and software compatibility is extremely important. In addition to information about compatibility, the "Rules of Thumb" document provide vital tips regarding installation. The "Rules of Thumb" document can be found "in the box" or ordered from Novell dealers. In addition, these documents can be downloaded from NetWire, NOVLIB Library 9 under the following file names: _ACERU2.TXT for Access Server _ARORUL.TXT for Asynch Router _MPRRUL.TXT for MultiProtocol Router _NACSRU.TXT for NACS _SAARUL.TXT for NetWare for SAA _SNALNK.TXT for NetWare SNA Links _WANRUL.TXT for WAN Links Q: How can I find the current "patches" for the following products: _LAN Workstation for DOS _LAN Workstation for MAC _LAN Workstation for Windows _Access Server _Asynch Router _Host Print _NACS _NetWare for SAA _SNA Links A: NetWire NOVLIB, Library 9 contains CURPTF.TXT. CURPTF.TXT is a list of all of the newest "patches" product by product. Q: How can I attach my system asynchronously to a NetWare v3.11 or v2.2 LAN without having to buy any additional software? A: You can do that with the "NetWare Asynch Router" software. As a courtesy to owners of NetWare v3.11 and NetWare v2.2 operating systems, the most current version is available for download from NetWire NOVLIB, Library 9 as ARO.ZIP. The following contains some advice regarding the Asynch Router: 1. Because the Asynch Router is not an NLM, it can not be an internal router for NetWare v3.11. 2. The Asynch Router is slightly different than what was known as the Asynch Bridge. _You do ACONFIG instead of ARCONFIG. _ The network addresses must be unique instead of the same. 3. Although the current Asynch Router is somewhat improved over earlier versions, it still has limitations: _It is very difficult to use modems not listed on the ACONFIG menu. _It is very fragile if line noise exists. _It is much slower than a high speed synchronous router; therefore, it is only practical for light duty transfer of small files. _It does not load balance. _It will not work on data lines. NetWare Lite Issues Q: A new file for NetWare Lite is on CompuServe called NWL102.ZIP. What is the difference between this file and NWL101.ZIP that was removed? A: NWL102.ZIP supersedes NWL101.ZIP and has all the files that NWL101.ZIP had in it plus three new patches that are for NetWare Lite v1.1. The description of all the patches are listed below: OPENDEV.PAT - NetWare Lite Client Open Device Patch Target: CLIENT.EXE Problem: When attempting to get file attributes (int21 function 4300h) on a device (not a file), CLIENT would returned an incorrect error to the calling application. Symptoms: Print jobs were disappearing when sent to an LPT port which had been opened using the C fopen function. Two examples of applications that require this patch for CLIENT.EXE are MPM by CYMA and dBASE IV by Borland. STACKFIX.PAT - NetWare Lite Server stack fix patch Target: SERVER.EXE Problem: The server switches to its DOS reentrency stack during initialization. The Norton antivirus device driver interrupts the server after initialization and does some work. The server timer interrupts, then kicks in, switches to the top of the server DOS reentrency stack, and corrupts the data that the server had on the stack before the timer interrupt. Symptoms: When the Norton antivirus device driver is loaded and SERVER.EXE attempts to load, the server will hang. INT28FIX.PAT - NetWare Lite Client int 28 ISR patch. Target: CLIENT.EXE Problem: Applications doing background printing on a NetWare Lite server/client where printing is captured to a printer connected locally may experience a server lock up. The problem requires the station to be rebooted. Each time the station is rebooted because of this problem, lost clusters are left on the hard drive. If this happens enough times without running CHKDSK /F, the FAT table will become corrupted. Symptoms: You may have this problem when running an application that performs background printing on a server/client with a printer connected locally and the station locks. An application which exhibits this problem is FoxPro. COMPOPEN.PAT Target: SERVER.EXE Problem: FCB Opens fail on read only files. This patch inserts the FCB open code that was removed from NetWare Lite v1.1 during product development. RECONFIX.PAT - NetWare Lite Client reconnect patch. Target: CLIENT.EXE Problem: The reconnection between server and client fails to occur when the NET CAPTURE or NET PRINT commands are issued by a client to a server that has just been rebooted. Subsequent NET CAPTURE or NET PRINT commands from the client station will work normally. Symptoms: When using the NET CAPTURE or NET PRINT commands as the first commands from a client to a server that has just been rebooted, the error messages "Redirect device -- Too many open files." or "Write file -- Access denied." will be displayed and the command will fail. Q: I am running NetWare Lite and garbage prints out after my print job. The only way that it will quit printing garbage is to delete the print job. What am I doing wrong? A: Check to see if you have TBMI2 loaded in the AUTOEXEC.BAT or the STARTNET.BAT files. The TBMI2 file needs to be loaded after SERVER.EXE for it to work properly. NetWare Connectivity and Global Messaging Q: Can I run TN3270 for LAN Workplace v3.13a or NFS Client for LAN Workplace v2.3 with LAN Workplace for OS/2 v3.0? A: You can run TN3270 for LAN Workplace v3.13a with LAN Workplace for OS/2 v3.0. However, NFS Client for LAN Workplace v2.3 is not supported. Q. Is NetWare Global Messaging Stackable? For example: If a 20-user pack is wanted, can two 10-user packs be installed for 20-user usage? A. No, only one licensed package is allowed on each messaging server. Q. Will NetWare Global Messaging run on Runtime NetWare? A. The current version of NetWare Global Messaging, v1.0b, does not support Runtime Netware; however, this is being considered for future versions. {page |5} {page |1}