Knowledge Base

Computer with Plug and Play Network Adapter Is Not Found on Network

PSS ID Number: 220586

Article Last Modified on 5/8/2002

The information in this article applies to:

Microsoft Windows 98

This article was previously published under Q220586

If this article does not describe your hardware-related issue, please see the following Microsoft Web site to view more articles about hardware:

http://support.microsoft.com/support/windows/topics/hardware/hwddresctr.asp

SYMPTOMS

After you upgrade to Windows 98 on a Microsoft Windows 95-based computer with a Plug and Play Network Interface Card (NIC) installed, your computer may not be visible in Network Neighborhood to other computers on the network.

CAUSE

This problem occurs because the NetBEUI and IPX/SPX-compatible protocols may not bind to the Windows 98 server component (Vserver.vxd) if a resource used by the network adapter, such as an interrupt request line (IRQ), is reassigned by Plug and Play Configuration Manager during system initialization. Under these conditions, the computer does not announce or register its name on the network.

Your computer also does not internally register or export server and browser names to the network. As a result, the computer does not appear in Network Neighborhood, it does not recognize datagrams addressed to itself, and it does not allow remote computers to initiate connections.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 98 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English-language version of this fix should have the following file attributes or later:

   Date     Time    Version      Size     File name  
   --------------------------------------------------
   02/26/99 07:09pm 4.10.2000    112,912  Vserver.vxd

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Windows 98 Second Edition.

MORE INFORMATION

When the NetBEUI or IPX/SPX-compatible protocol is installed, your computer may not be listed in Network Neighborhood. If you attempt to connect to your computer by typing "net view \\computername" (without the quotation marks) or "net use * \\computername\sharename" (without the quotation marks) at the command prompt of another computer on the network, you may receive the following error message:

Error 53: The computer name specified in the network path cannot be located. Make sure you are specifying the computer name correctly, or try again later when the remote computer is available.

If you type "net view" (without the quotation marks) at a command prompt shortly after Windows 98 is started, you may receive the following error message:

Error 6118: The computer(s) sharing resources in this workgroup cannot be located. The computer(s) might have been restarted. Wait a few minutes, and then try again. If the problem persists, make sure your network-adapter settings are correct.

If you attempt to connect to the computer using Start, Run, and typing \\computername\share, and then clicking OK in Windows 98, you may receive the error message:

The network name cannot be found.

If you attempt to map a network connection to the computer in Windows 98, you may receive the error message:

The computer or sharename could not be found. Make sure you typed it correctly, and try again.

PROTOCOL SCENARIOS

The following scenarios assume that the Microsoft Client for Microsoft Networks is installed.

If only the IPX/SPX-compatible protocol is installed, other computers may not be able to browse or connect to your computer. This occurs because the IPX 'NMPI' (Microsoft Name Management Protocol on IPX) server-name announcement and SMB host browser announcements are not broadcast.

If "NetBIOS support for IPX/SPX-compatible Protocol" is also enabled (this is the default for Microsoft Windows 95, not Windows 98), the SMB host browser announcements are sent since the NetBIOS transport typically binds (note that there is a distinction between NetBIOS support for IPX/SPX and NetBEUI). In this situation, the computer can be browsed by other computers using NetBIOS, but not by those without NetBIOS. In mixed Windows 95 and Windows 98 environments, enabling this can be a temporary solution to the problem, but it is only a partial solution in environments with computers that are not NetBIOS capable.

With the NetBEUI protocol installed, the Add Name Query and Add Group Name values for the names listed below that are normally registered by the "server" components of Windows 98 are not sent.

For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the article number below to view the article in the Microsoft Knowledge Base:

206071 General Information About Windows 98 and Windows 98 Second Edition Hotfixes

Additional query words: HWSYSPNP HWNICTS w98nettop peer

Keywords: kbHardware kbnetwork kbprb KB220586
Technology: kbWin98 kbWin98search

Microsoft KB Archive/220586

Contents