Microsoft KB Archive/100652

From BetaArchive Wiki
Knowledge Base


"Invalid Keyword" with Windows for Workgroups, TCP/IP

Article ID: 100652

Article Last Modified on 7/30/2001

This article was previously published under Q100652

SUMMARY

After installing TCP/IP protocol from the Microsoft Windows for Workgroups Connectivity Diskette, you may receive the following error messages:

NET0101: Value for keyword not found in PROTOCOL.INI or TCPUTILS.INI
file by TCP
Unloadable TCP 1.0 not loaded.

NET0116: TCP access failure by Tiny RFC
Tiny RFC 1.0 not loaded

The errors occur because the TCP/IP addresses have not been established in the PROTOCOL.INI. The installation program does not force entry of the addresses.

The PROTOCOL.INI will look like the following:

[TCPIP]
DriverName=TCPIP$
NBSessions=6
NetFiles=C:\WFW31
tcpsegmentsize=1450
tcpwindowsize=1450
BINDINGS=MS$DECGEN
LANABASE=1
                

It needs to look like the following:

[TCPIP]
DriverName=TCPIP$
NBSessions=6
NetFiles=C:\WFW31
tcpsegmentsize=1450
tcpwindowsize=1450
BINDINGS=MS$DECGEN
LANABASE=1
IPAddress0= (Valid IP Address)
SubNetMask0= (Valid Sub Net Mask)
DefaultGateway0= (Optional)
                

To have Windows Control Panel make the correction to the PROTOCOL.INI do the following:

Steps to add TCP/IP Addresses

  1. Within Windows for Workgroups Version 3.10 select Control Panel.
  2. Within Control Panel select Network.
  3. Within Network select Adapters.
  4. Select Protocols.
  5. Highlight TCP/IP.
  6. Select Settings
  7. Within the Advanced Protocol settings :

    Highlight Default Gateway enter values and select SET (Optional)
    Highlight IP Address enter values and select SET
    Highlight Subnet Mask enter values and select SET

  8. Exit and Restart Windows for Workgroups

Reference:

"Integrating Microsoft Windows for Workgroups with Microsoft LAN Manager 2.2"


Additional query words: wfw wfwg 2.20

Keywords: KB100652