Net Start Fails When TCP/IP is the Only ProtocolLast reviewed: September 9, 1996Article ID: Q114839 |
The information in this article applies to:
SYMPTOMSWhen you use TCP/IP as the only network protocol on a Windows for Workgroups 3.11 network installation (using the SETUP /N command), upon starting the computer, when the NET START command is started and after seeing the banner for the TCP/IP driver successful load you may receive the following message:
ERROR 7361: IPX or NetBIOS must be running in order to load the network services. CAUSEWhen you install Windows for Workgroups 3.11 in network mode, network functionality is enabled by default so that the real mode full redirector loads and the following lines are added :
AUTOEXEC.BAT : NET START SYSTEM.INI / [Network]: AutoStart=FULLThe TCP/IP protocol needs to load several modules (UMB, TCPTSR, TINYRFC, NMTSR.EXE, EMSBFR.EXE) after the NDIS2 protocol binding and before the redirector load, and thus the error message.
WORKAROUNDEdit AUTOEXEC.BAT and replace the line
NET STARTwith:
NET START NETBINDAfter the lines that load other modules needed by TCP/IP (UMB, TCPTSR, TINYRFC, NMTSR.EXE, EMSBFR.EXE) add one of the following lines:
NET START WORKSTATION -or- NET LOGONThis will correct the binding sequence of both TCP/IP and the redirector.
STATUSMicrosoft has confirmed this to be a problem in Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional reference words: wfw wfwg 3.11
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |