Invisible Software

If Windows 95 Network Neighborhood is Empty

 

Here are some things to check if Windows 95 Network Neighborhood can't see any other computers in the network.

Problem Description

The problem symptoms are as follows: The Invisible LAN drivers are installed. Windows 95 starts normally, and there are no error messages. But when you open Network Neighborhood, you can only see yourself; you can't see any other computers in the network.

Check the Hardware Driver Configuration

This problem is almost always caused by an incorrect configuration of the hardware driver.

For most hardware drivers, you need to enter the I/O port address and IRQ interrupt level into the driver configuration. If the driver's I/O port and IRQ level don't match the network board's actual I/O port and IRQ level, then this problem will occur. (Unfortunately, most Windows 95 hardware drivers don't show any error messages when you enter the I/O port or IRQ level incorrectly; they just don't work.)

To check the hardware driver configuration, proceed as follows:

  1. Right-click on Network Neighborhood, then choose Properties.
     
  2. Click on the network hardware driver, then click Properties.
     
  3. Click the Resources tab. (If there is no Resources tab, then your hardware driver doesn't require you to enter the I/O port or IRQ level; in this case, skip to the next section.)
     
  4. Check the I/O port address and IRQ interrupt level displayed on the Resources page. Make certain that they are identical to the network board's actual I/O port address and IRQ interrupt level.
     
  5. If the I/O port and IRQ level on the Resources page don't match your network board, then change them so they match. (You may have to select a different configuration in the drop-down box before Windows 95 will let you edit the I/O port and IRQ level fields.)
     
  6. Click OK to exit from the properties box.

If you are unsure of the configuration of your network board, you should examine the jumpers on the board or, in the case of jumperless boards, run the setup utility supplied with the board. Please, double-check and triple-check the jumper settings (for jumper-configured boards) or setup program (for software-configured boards). Make absolutely certain that the I/O port and IRQ level match the settings in the driver's Resources page. This will almost always solve the problem.

If your network board has a jumper for "turbo mode" or "bus timing" or "system compatibility", try changing the setting of that jumper.

Check for Conflicts in Device Manager

Other possible causes of the problem are: (1) a hardware conflict between the network board and other hardware in your computer; (2) installing the wrong hardware driver for your network board; or (3) installing more than one hardware driver for your board.

You can use the Windows 95 Device Manager to check for these problems. To run Device Manager, do the following:

  1. Click Start, then choose Control Panel.
     
  2. Double-click System.
     
  3. Click the Device Manager tab.
     
  4. Click the plus sign next to Network Adapters.

Underneath "network adapters" you should see the hardware driver for your network board. If it isn't listed, then you need to install the hardware driver for your network board. (Starting from Control Panel, you can install the driver manually by clicking Network, then Add, then Adapter. Or, you can let Windows 95 identify the correct driver automatically by clicking Add New Hardware.)

Check to make sure that the hardware driver listed under "network adapters" is the correct driver for your network board. If it isn't, then remove the incorrect driver (click on the driver and then click Remove). Then, install the correct driver.

Check to make sure that there is only one driver installed for your network board. If there is more than one, then remove the extra ones.

Check if there is an "X" or an "!" showing next to the hardware driver. If there is, then Device Manager has detected a hardware conflict or malfunction. Double-clicking on the hardware driver may reveal additional information about the problem. The error indication might be caused by (a) a malfunctioning network adapter; (b) installing an incorrect driver; (c) setting the driver's I/O port or IRQ level incorrectly; or (d) setting the network adapter's I/O port or IRQ level to the same value used by other equipment in the computer. Whatever the problem is, you must correct it before Invisible LAN can function.

Double-click on the network hardware driver and then click Resources to view the hardware resources (I/O ports and IRQ level) that your driver is using. Check to make certain that these match the network board's actual I/O ports and IRQ level. Check to make sure they don't conflict with other hardware in the computer. Read the dialog box to see if there are any error messages. Check to make sure that an IRQ level is listed in the dialog box; if none is listed, it means that the IRQ level you selected conflicts with other equipment in the computer and must be changed.

Check the Connection Type for DEC PCI Ethernet Boards

If you have a PCI Ethernet board based on the DEC controller chip (this includes Invisible Ethernet PCI boards), then you may have to set the connection type in the driver configuration. To do this, proceed as follows:

  1. Right-click on Network Neighborhood, then choose Properties.
     
  2. Click on the network hardware driver (which should say "DEC"), then click Properties.
     
  3. Click Advanced.
     
  4. Click Connection Type for 32 Bit Driver.
     
  5. Choose the correct value from the list on the right. The default value is AutoSense, but that doesn't always work. Instead of AutoSense, choose the actual connection type you are using.

Use Invisible LAN for DOS to Verify the Board Configuration

As a last resort, if you still can't get the network working, you can use the DOS version of Invisible LAN to check your network board's actual I/O port address and IRQ interrupt level, and to test the operation of the board. To do this:

  1. Exit from Windows 95 to a DOS prompt. (Click Start, then Shut Down, then Restart computer in MS-DOS mode.)
     
  2. Make a directory on your hard disk called NET30, and copy the Invisible LAN for DOS files into that directory. (Insert your Invisible LAN distribution diskette #1, run SETUP30 from the diskette, and choose Copy Files.)
     
  3. Change to the NET30 directory.
     
  4. Run NETDIAG. When the program asks for your network hardware type, select the correct choice from the list.

The NETDIAG screen shows all the computers in the network that have Invisible LAN software running. If you can see other computers besides yourself, then you know the network board is working properly.

The line marked with an asterisk "*" is your computer. Check the I/O port and IRQ level that are displayed in NETDIAG. These are the actual I/O port and IRQ level that your network board is using. Make sure the Windows 95 network hardware driver is configured to the same I/O port and IRQ level.

Press Esc to exit from NETDIAG. Then, press Ctrl-Alt-Del to restart your computer.

 

Notices: Copyright 1997 by Invisible Software, Inc. Invisible Software and InvisibleLAN are trademarks of Invisible Software, Inc. Other trademarks are the property of their respective holders.

This document was prepared on 11/15/97, and was believed to be accurate as of that date. Procedures, specifications, and compatibility may change without notice, and therefore this document may be out-of-date and/or inapplicable to current product versions. Invisible Software provides this document "AS IS" and without warranty of any kind. Under no circumstances shall this document be construed as creating or expanding any warranty of product performance.

 

Go back to Support FAQ.