Avoiding "Error 58" messages with Windows for Workgroups 3.11

The information presented below was found in the Microsoft Knowledge Base and is presented for information only. Support for installing Windows for Workgroups (WFW) protocols is the responsibility of the user and Microsoft Corporation. Call Microsoft Technical Support for questions regarding information in this tech tip.

When installing Windows for Workgroups 3.11, the following messages may display:

"Error 58: The network hs responded incorrectly. The following error occurred while loading protocol number 0."

There may be several causes for these errors in WFW. They are usually related to incorrect protocol information. The user must know the appropriate protocol for the network when installing WFW. Microsoft suggests possible causes and solutions for these messages, which are provided below:

1. "Error 58: The network has responded incorrectly"

The User installs WFW and executes "net start" to load WFW and gets an error message.

Problem:

a. The above error message may be caused by an incorrect I/O base address, an incorrect RAM address, or an improper IRQ setting in PROTOCOL.INI.

b. This error may be generated if the Transport= line in the [386Enh] section contains protocols that are not in use.

e.g. The Transport= line contains the following information:

Transport=netbeui.386,nwlink.386,nwnblink.386

If the only protocol in use is NetBeui, errors may occur.

Solution:

a. Correct the invalid setting.

b. If the Transport= line contains invalid references, remove them.

(e.g. remove the references to nwlink.386, nwnblink.386, and IPX/SPX compatible transport).

If the User is not sure which transports to use, the User's network administrator or Microsoft Technical Support should be called.

Problem: Error message may occur if NET START NETBEUI is run before loading Windows for Workgroups with the "IPX/SPX Compatible Transport with NetBIOS" and NetBEUI protocols installed.

Solution: To correct this problem:

a. Use NET START without the NetBEUI parameter or remove the "IPX/SPX Compatible Transport with NetBIOS" protocol.

b. Before loading Windows for Workgroups, type:

net stop netbeui

This unloads the real-mode NetBEUI protocols installed.

2. "The following error occurred while loading protocol number 0"

When starting Microsoft Windows for Workgroups version 3.11 with Novell connectivity installed through IPXODI, the following error may occur:

"The following error occurred while loading protocol number 0. Error 58: The network responded incorrectly. You may need to reconfigure the protocol using Network Setup. If your computer is a portable, make sure it is connected to its docking station."

Problem: When Novell IPXODI support is installed in Windows for Workgroups 3.11, Setup must make certain assumptions about the IPXODI configuration since Windows for Workgroups 3.11 does not ship with any of the Novell ODI files. One of the assumptions concerns the specific name of the multiple link interface driver (the Novell ODI network interface card driver). This name is referenced in the PROTOCOL.INI file on the Bindings= line(s). If the driver name specified on the Bindings = line does not match the name of the multiple link interface driver (MLID) being used, the above error may be generated.

Solution: To correct this error:

a. Make a note of the actual name of the MLID file listed after LSL.COM in the AUTOEXEC.BAT or STARTNET.BAT file.

b. Edit the PROTOCOL.INI file and verify that the Bindings= line matches the MLID file described above. If the Bindings= ent

| Note - On some configurations there may be two Bindings= lines. |
+-------------------------------------------------------------------+

Example:

The following example uses a 3Com EtherLink III (3C5X9) NIC, which is one of the more common cards with which the above error message occurs. Below are
excerpts of the files created by Network Setup.

AUTOEXEC.BAT:
C:\WINDOWS\NET START
C:\<PATH>\LSL.COM
C:\<PATH>\<3C5X9.COM> (This is the MLID.)
C:\<PATH>\IPXODI.COM
C:\WINDOWS\ODIHLP.EXE
C:\<PATH>\NETX.EXE

PROTOCOL.INI:

[NWLINK]
Bindings=3C509 or 3C509.COM

[NETBEUI]
Bindings-=3C509 or 3C509.COM

Note that the MLID filename in the AUTOEXEC.BAT file is 3C5X9.COM, but the PROTOCOL.INI file references 3C509. The corrected PROTOCOL.INI should read
as follows:

[NWLINK]
Bindings=3C5x9 or 3C509.COM

[NETBEUI]
Bindings-=3C5x9 or 3C509.COM

For more information about this error in non-ODI configurations, contact Microsoft Technical Support.