TITLE: Difficulty Setting up WFWG and PNW DOCUMENT ID: TID021112 DOCUMENT REVISION: 1 DATE: 05Jul95 ALERT STATUS: Yellow README FOR: NA NOVELL PRODUCT and VERSION: PERSONAL NETWARE V1.0 ABSTRACT: NA --------------------------------------------------------------------- DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEAN 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. --------------------------------------------------------------------- SYMPTOMS: Difficulty setting up WFWG and PNW to work simultaneously on a workstation. SOLUTIONS: The following are the instructions to help get Windows for Workgroups (WFWG) v3.11 to work with PERSONAL NetWare. These instructions will NOT work with WFWG v3.1. Currently PNW is NOT supported with WFWG v3.1; it IS supported with WFWG 3.11 First, get Windows for Workgroups to function without NetWare or PERSONAL NetWare installed. 1. Install/configure WFWG 3.11 so that it will run on the ODI shell using IPX. See your WFWG documentation for instructions. 2. Verify that it is working. (for example, map a drive, print to a shared printer, use the chat program) Next, get the PERSONAL NetWare piece working. 1. Remark out the following lines that were added by WFWG: In the CONFIG.SYS, the IFSHLP.SYS line. In the AUTOEXEC.BAT, the NET START and ODIHLP.EXE lines. 2. Install/configure Personal NetWare to run. See your PNW documentation for instructions. 3. Verify that it is working from DOS. (for example, map a drive, print to a shared printer, use the network diagnostics). Finally, get the two networks to work together. 1. Verify that the NWCLIENT directory is before the WINDOWS directory on the PATH line in the AUTOEXEC.BAT file. Both networks ship with a NET.EXE utility. WFWG needs to run its NET once to start the network. You can specify the full path to it in the AUTOEXEC.BAT to avoid confusion with PNW. Because PNW needs to run the NET utility often, it should be first in the PATH. 2. Un-remark the NET START and ODIHLP.EXE lines in the AUTOEXEC.BAT. 3. Verify that the NET START line contains the full path to the WFWG NET command. (for example, C:\WINDOWS\NET START) 4. Restart the computer and load both networks. 5. Run Windows. 6. Go into the Network Setup utility for WFWG. This can be done by opening the Windows Setup icon in the Main program group, and selecting "Change Network Settings..." from the options menu; or by opening the Network Setup icon in the Network program group. 7. Select the "Networks" button. Verify that the "Install Microsoft Windows Network:" radio button is selected. Verify that the "Other:" radio button is selected and that it indicates "Novell NetWare (Workstation Shell 4.0 and above)" as the other network. Then select "OK." 8. Select the "Sharing" button. Verify that the pieces you wish to share with the other workstations on the network are selected. Then select "OK." 9. Select the "Drivers" button. Verify that the proper network interface card (NIC) driver is in place. Verify that the "IPX/SPX Compatible Transport" or the "IPX/SPX Compatible Transport with NetBIOS" driver is loading. Verify that the "Microsoft NetBEUI" driver is loading. Select IPX/SPX as the default protocol. Then select "OK". 10. Select "OK" to close the Network Setup utility and save the changes. You should not replace any of the drivers currently installed. 11. Exit Windows to a DOS prompt. 12. Edit the AUTOEXEC.BAT file to move the NET START and ODIHLP.EXE lines so they execute after STARTNET.BAT. They need to be moved because they rely on LSL and the MLID drivers that are loaded as part of STARTNET.BAT. 13. Edit the NET.CFG file in the NWCLIENT directory to verify that the correct frame type for your network is loading. IPX will only bind to one frame type. The frame type you want IPX to bind to should be the first one listed in the LINK DRIVER section. 14. Reboot. Start both networks, go into Windows, and verify that both networks are functioning correctly by mapping drives to both networks, printing to printers on both networks, and so forth. NOTE: Currently, the Personal NetWare network diagnostics will not function properly if Windows for Workgroups is running. To use the diagnostics, verify that the diagnostics pieces are loading (see your Personal NetWare documentation) and exit Windows. You will have to use NET DIAGS (the DOS version). --------------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ---------------------------------------------------------------------