Net Start Fails When TCP/IP is the Only Protocol

ID: Q114839

The information in this article applies to:

Microsoft Windows for Workgroups versions 3.1, 3.11
Microsoft Windows for Workgroups TCP/IP version 1.0a

SYMPTOMS

When 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.

CAUSE

When 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=FULL

The 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.

WORKAROUND

Edit AUTOEXEC.BAT and replace the line


   NET START

with:


   NET START NETBIND

After 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 LOGON

This will correct the binding sequence of both TCP/IP and the redirector.

Additional query words:

Keywords : ntprotocol nttcp
Version : 3.11
Platform : WINDOWS
Issue type :