Here's a paste of the most frequently seen solutions to 98 network visibility problems:

* IPX/SPX protocol added/enabled on all machines as Default protocol. * Enabled NetBIOS support over IPX/SPX on all.

* Latest* NIC drivers from manufacturer (especially Realtek & 3Com) * Your network client as "primary logon" (If Novell LAN, then go for Novell's latest clients 2.2 or 2.5 (or 3.0 if you have access to the "latest")). * Explicitly* chosen the IPX frame type (not "automatic"; I prefer Ethernet_II) * Browse master "Enabled" for *only* one of each OS type, otherwise disabled on all others. * File&Print Sharing explicitly "on". * Folders and/or Drives *explicitly* set to "shared" * Unique identifications (no spaces, keep short) * Same* workgroup name (no spaces, keep short) and even if they appear to be identical: change the workgroup name on ALL Win95 and Win98 systems (this helped in a few cases) * Unreported but actual NIC IRQ/memory range conflicts - run NIC's setup/diagnostics program from a DOS boot (not a DOSbox) to compare to what Win thinks the IRQ resources are and then get them into agreement. * Disable PnP OS in the 98 CMOS setup (seems rarest "blocker", but this one does cure for some hardware) (details in another message below). * All the machines on my LANs also have TCP/IP installed. None have NetBEUI installed (unless one wants to "split the hair" regarding the relationships between NetBIOS support over IPX and NetBEUI) ------------ Best Regards,

Rory McGarity in Tokyo, Japan

Newsgroup message posted by Art Wong on Jan.3,99:

The problem came down to the Award v4.51PG BIOS setting for PnP/PCI Configuration. I built Win98 with the PnP OS Installed set to YES. During boot up the NIC had IRQ 5. When Win98 took over it assigned it IRQ 11 using IRQ Steering. Only by using the RSET8029.EXE configuration and diagnostic program in DOS, I found communications occurred when the NIC had IRQ 5. Win98 wouldn't run if IRQ Steering was turned off. It also wouldn't boot if I set PnP OS Installed to NO in the BIOS. What worked for me was to reinstalled Win98 after a DOS boot with PnP OS set to NO, then disable IRQ Steering. Now the BIOS IRQ setting for the NIC matches the Win98 Resources described in Control Panel, System, Device Manager, Network Adapter.

Another suggestion made in the NewsGroup message: Turn on (set to Yes) in Windows98 "LM Announce" in the Properties of the "File and Print Sharing" (according to Microsoft's Resource Kit, this should only be required for communication to 'old' LanManager (LM) Systems, but it seems to help also on communications between Windows95 and Windows98. But be aware: turning this on will cause additional Network traffic, when Windows98 is now sending out these broadcast messages to advertize its existance).

This behavior can occur if a Peripheral Component Interconnect (PCI) network adapter is being used on one of the computers on the network. If the network adapter is in PCI slot 1 and an Accelerated Graphic Port (AGP) video adapter is installed, a conflict between the network adapter and the AGP video adapter can occur and prevent you from browsing the network.

RESOLUTION

To resolve this behavior, use as many of the following steps as is necessary. After following each step, test to see if the behavior is resolved. If the behavior is not resolved, go to the next step until the behavior is resolved.

1.

Verify that resources are being assigned automatically to the network adapter. To do so, follow these steps:

On the Resources tab, click the Use Automatic Settings check box to select it, click OK, and then click OK again.

2.

Move the network adapter from slot 1 to another available PCI slot. For information about how to do so, refer to the documentation included with the computer or contact the computer's manufacturer.

3.

Disable PCI bus IRQ steering

4.

In the computer's basic input/output system (BIOS), change the shared interrupt request line (IRQ) to Industry Standard Architecture (ISA) so that it cannot be assigned by PCI bus IRQ steering. For information about how to change BIOS settings, refer to the documentation included with the computer or contact the computer's manufacturer.

5.

Verify that a resource conflict does not exist between the network adapter and another device in the computer. NOTE: If there is a resource conflict between the network adapter and another device, it may not be apparent in Device Manager.