[Intel Navigation Header]

    ProShare Software: Troubleshooting Network Problems

    Contents:

    • TROUBLESHOOTING NETWORK PROBLEMS
    • 1. NETWARE CONNECTION PROBLEMS
    • NETWARE INITIALIZATION FAILED
    • NETWARE CONNECTION FAILED. CONNECTION TIMED OUT
    • 2. NETBIOS CONNECTION PROBLEMS
    • ERROR: NETBIOS NETWORK NAME IN USE
    • NETBIOS CONNECTION FAILED
    • NETHEAPSIZE ERROR
    • 3. TCP/IP CONNECTION PROBLEMS
    • PROSHARE SOFTWARE TCP/IP REQUIREMENTS
    • TCP/IP CONNECTION FAILURES
    • SYSTEM LOCKUPS AND GPFS
    • 4. DOS INT14H NETWORK MODEMS
    
    

    TROUBLESHOOTING NETWORK PROBLEMS

    
       This document is divided into the following sections: 
    
    
    
         1.  NetWare Connection Problems:
    
            Error: NetWare Initialization Failed
    
            Error: NetWare Connection Failed. Connection Timed Out
    
    
    
         2.  NetBIOS Connection Problems:
    
            Error: NetBIOS Network Name In Use
    
            Error: NetBIOS Connection Timed Out
    
            NetHeapSize error
    
    
    
         3.  TCP/IP Connection Problems:
    
            TCP/IP Requirements
    
            TCP/IP Connection Failures
    
            System Lockups and GPF's
    
    
    
         4.  DOS INT14h Network Modem Pools
    
    
    
    

    1. NETWARE CONNECTION PROBLEMS

    
       The Communications Test program that comes with the ProShare software
    
       has NetWare specific tests that can diagnose several common problems. 
    
       Always run the Communications Test program when troubleshooting.
    
    
    
    

    NETWARE INITIALIZATION FAILED

    
       Symptom:
    
       NetWare Initialization Failed
    
    
    
       Description:
    
       The IPX or IPXODI driver version is too old.  The ProShare software
    
       requires IPX v3.10 or later, or IPXODI v1.20 or later.  
    
    
    
       Solution:
    
       Run the NetWare tests in the Communications Test program.  Use the Help
    
       button on the NetWare Test dialog box for specific instructions on each
    
       test and what to do if a test fails.  The VIPX Presence Test will fail
    
       if the IPX version is too old.
    
    
    
       Solution:
    
       You can also type NVER at a DOS prompt to get the IPX version.
    
    
    
       Solution:
    
       If a version is older than required, contact your network administrator
    
       or Novell to obtain an updated version.
    
    
    
    

    NETWARE CONNECTION FAILED. CONNECTION TIMED OUT

    
       Symptom:
    
       NetWare Connection Failed.  Connection Timed Out
    
    
    
       Description:
    
       Windows for Workgroups 3.11:  This error can occur if the IPX frame type
    
    
    
       does not match between the two systems.
    
    
    
       Solution:
    
       If the frame types already match, try adding the following lines to the
    
       PROTOCOL.INI file under the [NWLINK] header.  (The PROTOCOL.INI file is
    
       in the WINDOWS directory).
    
            [NWLINK]  
    
            Max_Commands=4
    
            Max_Sessions=4 
    
    
    
       (Also refer to document 8123 - ProShare Software: Windows for
    
       Workgroups, Symptoms and Solutions for more information.)
    
    
    
       These are instructions for setting up IPX with Windows for Workgroups
    
       3.11 for the ProShare software.
    
    
    
         1. Click on the Network Setup icon in Program Manager.  If you cannot
    
            find your Network Setup icon, you can select File...Run, from
    
            Program Manager and enter WINSETUP.EXE /Z.  You are now in the
    
            Network Setup dialog box.
    
    
    
         2. Double click on your IPX/SPX driver in the Network Drivers list
    
            box.  Or you can click the Drivers button, highlight the IPX/SPX
    
            driver and click the Setup button.  You will now be in the IPX/SPX
    
            Setup dialog box.
    
    
    
         3. Click on Frame Type from the Advanced Protocol Settings list box.
    
    
    
         4. Click on "Value" in the "Frame Type" box and open the drop down
    
            list box.
    
    
    
         5. Select the correct value for your network from the list
    
            (Ethernet_II, Ethernet_802.3,  Ethernet_802.2 or Token Ring).
    
    
    
         6. Click on Set.
    
    
    
         7. Click on O.K., and choose O.K. again, until you are out of Setup.
    
    
    
       Note: If you are on an Ethernet network and you do not know the correct
    
       Ethernet frame type, consult your network administrator, or look at the
    
       settings in your NET.CFG or the server's AUTOEXEC.NCF file.  Also, the
    
       use of Ethernet II is not a requirement for the ProShare software. The
    
       only requirement is that both participants be running the same frame
    
       protocol.
    
    
    
    

    2. NETBIOS CONNECTION PROBLEMS

    
       When using NetBIOS or NetBEUI with the ProShare software it is a
    
       requirement to increase the NetHeapSize value to 60 in the Windows
    
       SYSTEM.INI file.  Run the NetBIOS test in the Communications Test
    
       program to verify that your NetHeapSize value is sufficient.
    
    
    
    

    ERROR: NETBIOS NETWORK NAME IN USE

    
       Symptom:
    
       ERROR: NetBIOS Network Name In Use
    
    
    
       Description 1:
    
       There aren't enough NetBIOS resources available.
    
    
    
       Solution 1a:
    
       Run the NetBIOS test in the Communications Test program to check for
    
       NetHeapSize.  Use the Help button on the NetBIOS Test dialog box for
    
       specific instructions on each test and what to do if a test fails.
    
    
    
       Solution 1b:
    
       Try larger values for NCBS (Network Control Blocks), Max Sessions, and
    
       Max Commands.  Often you can change these values by editing your
    
       PROTOCOL.INI file in the WINDOWS directory, or a NET.CFG file in the
    
       network software directory, depending on your network.
    
    
    
       Description 2:
    
       The NetBIOS Net Address is already being used by the workstation or
    
       other device.
    
    
    
       Solution 2:
    
       Check that the NetBIOS Net Address of the ProShare software is unique. 
    
       To edit the Net Address, from the Conference menu choose Setup.  The
    
       NetBIOS Net Address is arbitrary.  Be aware that the Net Address is
    
       case-sensitive.  Do not use the workstation's address as a NetBIOS Net
    
       Address in the ProShare software.
    
    
    
    

    NETBIOS CONNECTION FAILED

    
       Symptom:
    
       NetBIOS Connection Failed
    
    
    
       Description:
    
       There are not enough NetBIOS resources available.  
    
    
    
       Solution:
    
       Run the NetBIOS test in the Communications Test program to check for
    
       NetHeapSize.  Use the Help button on the NetBIOS Test dialog box for
    
       specific instructions on each test and what to do if a test fails.
    
    
    
       Solution:
    
       Try larger values for NCBS (Network Control Blocks), Max Sessions, and
    
       Max Commands.  These parameters can often be changed by editing a
    
       PROTOCOL.INI file in the WINDOWS directory, or a NET.CFG file in the
    
       network software directory, depending on your network.
    
    
    
    

    NETHEAPSIZE ERROR

    
       Symptom
    
       NetHeapSize Error
    
    
    
       Description:
    
       Windows sometimes issues an error message that includes the following
    
       text:
    
    
    
            "Include or modify the following setting in the [386Enh] section of
    
    
    
            your SYSTEM.INI. NetHeapSize=20"
    
    
    
       Solution:
    
       Set the "NetHeapSize=" value in your SYSTEM.INI file (WINDOWS directory)
    
       to at least 60 (not 20).  This specification is in the [386Enh] section.
    
       If the line is missing, add it to the file.
    
    
    
    

    3. TCP/IP CONNECTION PROBLEMS

    
       Note: In troubleshooting, try using any TCP/IP utilities provided by the
    
       TCP/IP product vendor (e.g. "ping", File Transfer ("FTP"), "Telnet",
    
       etc.) Also try running the TCP/IP tests in the Communications Test
    
       program.  If any of the tests fail, possible causes are listed in the
    
       Help.
    
    
    
    

    PROSHARE SOFTWARE TCP/IP REQUIREMENTS

    
       The ProShare software requires one of the following WINSOCK 1.1
    
       compliant TCP/IP stacks:
    
    
    
         *  Novell LAN Workplace 4.1  (v4.0 is problematic). 
    
    
    
         *  FTP TCP/IP 2.3. 
    
    
    
         *  Super TCP 3.0. 
    
    
    
         *  Windows for Workgroups 3.11 TCP/IP. 
    
    
    
         *  NetManage Chameleon 4.0  (v3.11 can be really slow and cause
    
            GPF*s).
    
    
    
         *  Trumpet 1.0 Rev A is not officially supported but appears to work. 
    
            Earlier versions of Trumpet do not work, only v1.0 Rev A.
    
    
    
    

    TCP/IP CONNECTION FAILURES

    
       Description:
    
       The TCP/IP address you're attempting to connect with is wrong or
    
       miss-typed.
    
    
    
       Solution:
    
       Use a valid host address (e.g. mypc.jf.intel.com).  You can use a
    
       hostname (e.g. mypc) by itself only if you have a Domain Name server (or
    
       some other kind of TCP/IP name service) which will resolve the hostname
    
       into a full address.
    
    
    
       Solution:
    
       You can use an IP address (e.g. 123.145.67.89) instead of a host
    
       address. If you do, be sure to use periods and not commas.
    
    
    
       Solution:
    
       Do not use Internet E:mail addresses or login ID's when connecting using
    
       TCP/IP (e.g. john@pc45.psu.edu is not valid).
    
    
    
    

    SYSTEM LOCKUPS AND GPFS

    
       Symptom:
    
       System lockups and GPFs
    
    
    
       Description 1:
    
       Duplicate or outdated TCP/IP files are a major cause of problems.
    
    
    
       Solution 1:
    
       Make sure you have only one WINSOCK.DLL.  Check your PATH as well as the
    
       WINDOWS and WINDOWS\SYSTEM directories for duplicate WINSOCK.DLL files. 
    
       Keep the one that came with your TCP/IP package.  Make sure your TCP/IP
    
       software directory is in the path and delete or rename the rest.
    
    
    
       Description 2:
    
       Low DOS memory can cause problems.  
    
    
    
       Solution 2a:
    
       To check the current amount of free DOS memory, run the MEM command (DOS
    
       5.0 or higher) in a DOS window.  The Largest Executable Program Size
    
       reported by the MEM command must be at least 400K.  More than 500K free
    
       memory is recommended.
    
    
    
       Solution 2b:
    
       When running Novell's LAN Workplace for Windows, General Protection
    
       Faults can occur if the TCP/IP DOS executable is loaded, but VTCPIP.386
    
       is not loaded under Windows.  VTCPIP.386 should be loading in the
    
       [386Enh] section of the SYSTEM.INI, (Device=vtcpip.386).
    
    
    
    

    4. DOS INT14H NETWORK MODEMS

    
         *  Due to the way that Windows and DOS must interact to communicate
    
            with Int14 devices, the maximum performance of an Int14 modem is
    
            approximately 9600 bits per second.
    
    
    
         *  During a file transfer using Int14, the file transfer bar may not
    
            be updated until the transfer is complete -- it remains at 0
    
            percent.
    
    
    
         *  Application sharing over Int14 modems is extremely slow, and should
    
            only be done with applications that do not require many screen
    
            rewrites.
    
    
    
         *  If you are using Shiva's LanRover for NetWare*, do not select the
    
            Int14 option in the Set Modem dialog box. Select the COM port you
    
            have assigned for the Shiva LanRover software to use, just as you
    
            would for a modem connected to your computer.  Also, you must use
    
            v2.1 of the Shiva LanRover software with the ProShare application.
    
    
    
         *  If you are using the Novell* add-on driver NASI 3, it does not
    
            function as an Int14 driver and the ProShare software cannot use
    
            it.
    
    

    Trademark information