WORKGROUP CONNECTION TROUBLESHOOTING If you have trouble while setting up or using Workgroup Connection, the solutions presented in this document should help. If you don't find the problem you're having addressed in this file, contact Microsoft Product Support Services (PSS). For more information about PSS, see the MS-DOS User's Guide. This document contains the following sections: 1. You Have Problems Setting Up a Network Card 2. Your Computer Stops Running During Workgroup Connection Setup 3. Workgroup Connection Won't Start After a Successful Setup 4. Workgroup Connection Doesn't Work With Windows 5. No Computers Are Listed 6. The Computer You Want To Connect To Is Not Listed 7. Windows Setup Does Not Detect Workgroup Connection 8. Additional Notes About Workgroup Connection ---------------------------------------------- 1. YOU HAVE PROBLEMS SETTING UP A NETWORK CARD ---------------------------------------------- If you encounter problems while installing and configuring a network card, try the following: o Review the instructions in the documentation that came with your network card. o If a diagnostics software program is included with your network card, try running the program. For details, see the documentation that came with your network card. ---------------------------------------------------------------- 2. YOUR COMPUTER STOPS RUNNING DURING WORKGROUP CONNECTION SETUP ---------------------------------------------------------------- If Workgroup Connection Setup stops running, it may be caused by one of the following problems: o Setup was unable to correctly identify your hardware. Run Setup again without hardware detection by inserting the Workgroup Connection Disk in drive A or drive B, and then typing the following at the MS-DOS command prompt: a:wcsetup /i or b:wcsetup /i The /I option causes Setup to skip hardware detection. When Setup displays the list of hardware and software settings, make sure the settings match the hardware you are using. o You are running a memory-resident program (also known as a terminate-and-stay-resident program, or TSR) that conflicts with Setup. Disable any commands in your CONFIG.SYS and AUTOEXEC.BAT files that start memory-resident programs. To do this, carry out the following procedure. To disable memory-resident programs: 1. Use any text editor to open your AUTOEXEC.BAT file. 2. Insert the rem command in front of every command line in your AUTOEXEC.BAT file, except the @ECHO OFF, PROMPT, and PATH commands. 3. Save the file, and then quit the text editor. 4. Restart your computer. 5. Try running Workgroup Connection Setup again. If Setup runs, remove the rem commands you added to your AUTOEXEC.BAT file after Setup is complete. If Setup still doesn't run, repeat the preceding procedure for your CONFIG.SYS file. In your CONFIG.SYS file, disable every command line, except lines that load device drivers that are needed to run hardware (such as a disk drive, monitor, or keyboard) and lines that begin with FILES or BUFFERS commands. If Setup runs, remove the REM commands you added to your CONFIG.SYS file after Setup is complete. ------------------------------------------------------------ 3. WORKGROUP CONNECTION WON'T START AFTER A SUCCESSFUL SETUP ------------------------------------------------------------ This section describes what to do if Workgroup Connection won't start after you complete Setup. The following list is an overview of steps you can take to solve this problem: o Make sure that all connections (cables and connectors) are securely fastened and that the network card is securely in its slot. o If a diagnostics program is included with your network card, try running the program. See the documentation that came with your network card for details. o Make sure the correct base memory address and interrupt (IRQ) are specified for your network card. For more information, see "Checking Your Network-Card Settings" later in this section. o If you are loading the Workgroup Connection device drivers into the upper memory area, try loading them in conventional memory instead. For more information, see "Loading Workgroup Connection Device Drivers into Conventional Memory" later in this section. o Make sure the device command for EMM386 in your CONFIG.SYS file excludes the memory address used by your network card. For more information, see "Making Sure EMM386 Doesn't Conflict with Your Network Card" later in this section. o Make sure that your network card is assigned to a different interrupt (IRQ) than your mouse. For more information about determining what interrupt to assign to your network card, see the documentation that came with your network card. o You may need to change the configuration settings you assigned to your network card. If you have an ISA card that is configured by using jumpers and switches, you may need to change some of these settings. If you have a software-configured card, use the configuration program that came with your network card to change your configuration settings. See the documentation that came with your network card for details. 3.1 CHECKING YOUR NETWORK-CARD SETTINGS The Workgroup Connection Setup program examines your computer's configuration and attempts to determine your network card's base memory address and interrupt (IRQ). If Setup incorrectly identifies these, Workgroup Connection will not start. For information about determining the correct settings yourself, see your network-card documentation. After you determine the correct base memory address and interrupt, you can specify them by running Setup again. To change the base memory address or interrupt setting: 1. Change to the directory that contains your Workgroup Connection files. For example, if the files are in the C:\NET directory, type the following commands at the MS-DOS command prompt: c: cd \net 2. At the command prompt, type the following: wcsetup The Workgroup Connection Setup program starts. After Setup examines your computer's configuration, it displays a list of settings. 3. Select the Network Card field by pressing the UP ARROW key, and then press ENTER. A list of options for modifying your network-card settings appears. 4. Select the "Edit settings for network card driver" option by pressing the UP ARROW key, and then press ENTER. A list of your network-card settings appears. 5. If you want to change the setting for your network card's interrupt, proceed to step 6. If you want to change the setting for your network card's base memory address, do the following: o Select the setting for the base memory address by pressing the UP ARROW key, and then press ENTER. This setting is called Memory Window, RAM Address, or something similar. You may have to press PAGE UP or PAGE DOWN to find this setting. A list of values appears. o Select the base memory address you want by pressing the UP ARROW or DOWN ARROW key, and then press ENTER. The new value appears on the base memory address line in the list of network card settings. 6. If you do not want to change your network card's interrupt setting, proceed to step 7. If you want to change the setting for your network card's interrupt, do the following: o Select the interrupt setting by pressing the UP ARROW key, and then press ENTER. This setting is named IRQ_Level, Interrupt, or something similar. You may have to press PAGE UP or PAGE DOWN to find this setting. A list of values appears. o Select the interrupt you want by pressing the UP ARROW or DOWN ARROW key, and then press ENTER. The new value appears on the interrupt line in the list of network card settings. 7. Choose "The listed options are correct" by pressing ENTER. Then follow the instructions on your screen to complete Setup. 8. When Setup is complete, restart your computer by pressing ENTER. If Workgroup Connection still does not start, proceed to the following section. 3.2 MAKING SURE EMM386 DOESN'T CONFLICT WITH YOUR NETWORK CARD If you use the EMM386 memory manager, make sure that it does not use the same memory that your network card uses. To ensure that EMM386 doesn't conflict with your network card: 1. Use any text editor to open your CONFIG.SYS file. 2. Look for the device command line for the EMM386 memory manager. It should look similar to the following: device=c:\dos\emm386.exe If your CONFIG.SYS file does not contain a device command for EMM386, you are not using it. Proceed to the following section, "Loading Workgroup Connection Device Drivers into Conventional Memory." 3. If your CONFIG.SYS file contains a device command for EMM386, add the following to that command line: x=mmmm-nnnn For mmmm, specify the base memory address of your network card. For nnnn, specify a value that is 32K greater than mmmm by using the following method: If the second character in mmmm is 8, the last three characters you specify for nnnn should be FFF. For example, if the base memory address is D800, your device command line should look similar to the following: device=c:\dos\emm386.exe x=d800-dfff If the second character in mmmm is 0, the last three characters you specify for nnnn should be 7FF. For example, if the base memory address is c000, your device command line should look similar to the following: device=c:\dos\emm386.exe x=c000-c7ff Note: This method for determining the value for nnnn is based on a network card device driver that uses 32K of memory. The values for mmmm and nnnn are hexadecimal numbers. Check your network card documentation to see if your card uses more or less than 32K of memory. If it does, adjust the value for nnnn accordingly. For example, if your card uses only 16K of memory, the characters to specify for nnnn in the preceding two examples would be DBFF and C3FF, respectively. 4. Save your CONFIG.SYS file, and then quit the text editor. 5. Restart your computer. If Workgroup Connection still does not start, proceed to the following section. 3.3 LOADING WORKGROUP CONNECTION DEVICE DRIVERS INTO CONVENTIONAL MEMORY If you used the devicehigh command in your CONFIG.SYS file to load any Workgroup Connection device drivers into the upper memory area, try loading these device drivers into conventional memory instead. It is possible that a device driver loaded into the upper memory area is conflicting with another device driver or program. To load device drivers into conventional memory: 1. Use any text editor to open your CONFIG.SYS file. 2. In your CONFIG.SYS file, look for the DEVICE or DEVICEHIGH command lines that load the following: o PROTMAN.DOS o Your network-card device driver o WORKGRP.SYS These command lines should appear consecutively. 3. If any of these command lines contain a DEVICEHIG command, change it to DEVICE. 4. Save your CONFIG.SYS file, and then quit the text editor. 5. Restart your computer. If Workgroup Connection still does not start, call Microsoft Product Support Services (PSS). For more information about PSS, see "Welcome" in the MS-DOS User's Guide. ------------------------------------------------- 4. WORKGROUP CONNECTION DOESN'T WORK WITH WINDOWS ------------------------------------------------- If you use Windows and Workgroup Connection, make sure Windows is using the correct network device driver by carrying out the following procedure. Note: If you are using Windows for Workgroups, do not carry out the following procedure. Windows for Workgroups Setup automatically installs the correct device drivers for Workgroup Connection. To configure Windows to run with Workgroup Connection: 1. Start Windows. 2. In the Main group, choose the Windows Setup icon. The Windows Setup window appears. It lists your current display, keyboard, mouse, and network settings. 3. From the Options menu, choose Change System Settings. The Change System Settings dialog box appears. 4. Open the list for the Network setting by clicking the arrow to the right of it. Or press TAB until you select the Network setting, and then press ALT+DOWN ARROW to open the list. 5. Click Microsoft Network (or 100% compatible), or select it by pressing the UP ARROW or DOWN ARROW key, and then press ENTER. 6. Choose the OK button. Setup may prompt you to insert a Windows Setup disk in drive A. If it does, insert the disk. Or, if the file for the Microsoft Network device driver is in a directory on your hard disk, type its path instead. 7. Choose the OK button. -------------------------- 5. NO COMPUTERS ARE LISTED -------------------------- If you don't see any computers listed when you display the Browse screen using the pop-up interface or type net view at the MS-DOS command prompt, try the following: o Make sure your network-card settings are correct. For more information, see "Checking Your Network-Card Settings" earlier in this document. o Sometimes, when a computer in your workgroup is turned off or restarted, you won't be able to see other computers on the network for a few minutes. Wait 15 minutes and then check again. o If you know the name of the shared directory or printer you want to connect to, try connecting to it even if it is not listed. Do this by typing the path of the shared directory or printer in the Path field of the Disk Connections or Printer Connections Screen. Or specify the path with the NET USE command at the MS-DOS command prompt. ---------------------------------------------------- 6. THE COMPUTER YOU WANT TO CONNECT TO IS NOT LISTED ---------------------------------------------------- If a particular computer on the network is not listed when you display the Browse screen using the pop-up interface or type NET VIEW net view at the MS-DOS command prompt, one of the following might be the cause: o The computer might have been recently restarted. Wait a couple minutes, and then try again. o If a computer is part of another workgroup (not your own), you cannot use the Browse screen in the pop-up interface to display it. To see a list of computers in another workgroup, you must use the NET VIEW command with the /WORKGROUP option at the MS-DOS command prompt. For more information, type the following at the command prompt: help net view ----------------------------------------------------- 7. WINDOWS SETUP DOES NOT DETECT WORKGROUP CONNECTION ----------------------------------------------------- If you install the MS-DOS 6 Workgroup Connection and Windows 3.1 Setup does not detect your network, carry out the following procedure: 1. If you have successfully installed Windows 3.1, exit Windows and make your Windows directory current. Then type SETUP at the command prompt. If you haven't successfully installed Windows 3.1, run Setup and choose Custom installation. 2. When Setup displays the screen listing your computer's hardware and software components, choose the Network option. 3. Select Microsoft Network (or 100% compatible) if you want basic redirector support. Select Microsoft LAN Manager (version 2.0 Enhanced) if you have full redirector support. 4. Press ENTER. When Setup displays an informational screen, press ENTER again. 5. When Setup displays the software and hardware components screen again, press ENTER, and follow the instructions on your screen. ---------------------------------------------- 8. ADDITIONAL NOTES ABOUT WORKGROUP CONNECTION ---------------------------------------------- 8.1 WORKGROUP CONNECTION INCLUDES THE NETBEUI PROTOCOL ONLY Workgroup Connection includes the NetBEUI transport protocol only. If you want to use a different protocol, you must obtain the drivers for that protocol from a hardware vendor. Workgroup Connection supports only one protocol at a time. 8.2 IF YOU HAVE AN 8088 PROCESSOR You must use the basic redirector if your computer has an 8088 processor. The basic redirector is the default. 8.3 SETUP IS SLOW ON SOME COMPUTERS On some computers, particularly those with 8088 processors, Workgroup Connection Setup may appear to pause for as long as 5 minutes. Do not restart your computer. 8.4 USING QUALITAS MAXIMIZE OR QUARTERDECK OPTIMIZE In some rare situations, Qualitas Maximize and Quarterdeck Optimize may attempt to load some Workgroup Connection commands into the upper memory area. If this causes problems, use Maximize or Optimize in manual mode and do not use it to load Workgroup Connection commands into the upper memory area. Workgroup Connection automatically loads its commands into the upper memory area, if there is enough space. For details on using manual mode, see your Maximize or Optimize documentation. 8.5 WORKGROUP CONNECTION CANNOT BE INSATALLED ON A DOUBLEDISK DRIVE You cannot use Workgroup Connection on a Vertisoft Systems DoubleDisk drive. You must install Workgroup Connection on another type of drive. 8.6 MAKING THE POP-UP INTERFACE VISIBLE ON A MONOCHROME MONITOR To force the Workgroup Connection pop-up interface to appear in monochrome mode, type MODE MONO at the MS-DOS command prompt before you display the pop-up interface, or include MODE MONO in your AUTOEXEC.BAT file. 8.7 USING QEMM LASTDRIVE If you add drive letters using QEMM Lastdrive and then use Workgroup Connection to connect to one of them, the connection will work but no information about the shared resources on it will be displayed. 8.8 IF YOUR COMMAND.COM FILE IS NOT IN THE ROOT DIRECTORY Workgroup Connection won't start if your COMMAND.COM file is not in the root directory of your startup drive unless you have a SHELL command in your CONFIG.SYS file that specifies the location of COMMAND.COM. For information about the COMMAND and SHELL commands, see your MS-DOS documentation. 8.9 ENABLING VALIDATED LOGONS TO LAN MANAGER DOMAINS You must run the Workgroup Connection full redirector to have your user name and password validated by a Microsoft LAN Manager server. 8.10 IF YOUR COMPUTER IS ALREADY USING A NETWORK If your computer is already using a network, you should check with your network administrator before you install Workgroup Connection.