Knowledge Base

How to install PC/TCP on LM 2.2B MS-DOS Client

PSS ID Number: Q117495

Article Last Modified on 10-28-1999

The information in this article applies to:

Summary

This article explains how to install PC/TCP on a Microsoft LAN Manager 2.2b MS-DOS client. PC/TCP is the TCP stack marketed by FTP Software, Inc.


More Information

Install the LAN Manager 2.2b client with NetBEUI protocol. Reboot the workstation, then logon and to make sure it works properly.

You have to install PC/TCP while the LAN Manager workstation service is running. Follow the procedure in the PC/TCP manual except as noted below:

  1. Select Application groups to install (This is a screen full of questions) Answer YES only to:

    Do You Want NetBIOS capability?


  2. Enter the path to NETBIOS.EXE: 
          c:\lanman.dos\netprog.com


  3. Would you like Install to reboot automatically? (Answer YES.)


Workstation reboots and asks you to logon. This is NetBEUI and LAN Manager logon. Log on.

  1. At this point of the setup, PC/TCP assumes that you have a bootp server and PC/TCP tries to get configuration information from it. If no bootp server is found, PC/TCP displays this error message after bootp request time out:
    3001: Unable to find any configuration supplied by your system administrator. Install will continue with available configuration.
    Press any key. The PC/TCP Configuration menu appears. Enter IP address, network mask, computer name domain name and router IP address.


  2. Exit the PC/TCP configuration menu. You receive this message:
    PC/TCP Installation complete.
    The files AEXECFTP.BAT and CONFIG.INS contain the setup commands to load PC/TCP. You may want to copy the changes Install makes in these files into AUTOEXEC.BAT and CONFIG.SYS. The procedure follows.


  3. Copy AEXECFTP.BAT and CONFIG.INS to the root directory as AUTOEXEC.BAT and CONFIG.SYS respectively.


  4. Edit AUTOEXEC.BAT and make these changes and save. (Changes you must make to this file are shown in lower-case characters.) 
    REM ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
C:\LANMAN.DOS\NETPROG\NETBIND.COM
C:\DOS\SMARTDRV
PATH=C:\DOS;
@REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
rem NET START WORKSTATION
rem LOAD NETBEUI
rem NET LOGON <YOURNAME> *
@REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2
REM ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
SET PATH=C:\PCTCP;%PATH%
SET PCTCP=C:\PCTCP\PCTCP.INI
C:\PCTCP\TOKDRV.EXE
REM ******* PC/TCP INSTALL ADDED LINE(S) - END ******
c:\pctcp\netbios -s ""
net start workstation
net logon <yourname> *


  5. Reboot the workstation.


All the Configuration files are listed below. An IBM Token Ring NIC (using the IBMTOK.DOS driver) was used for this configuration. Which driver is used depends on which adapter is being used. The DEC ethernet adapter uses the DEPCA.DOS driver. For example, If your computer has a NIC other than the IBM Token Ring, the line: 
   DEVICE=C:\LANMAN.DOS\DRIVERS\TOKENRNG\IBMTOK\IBMTOK.DOS
points to the appropriate driver. 
REM*************Config.Sys***************
device=c:\dos\himem.sys
FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\TOKENRNG\IBMTOK\IBMTOK.DOS
rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
rem ** If you do not have protman and ndis driver already loaded **
rem ** before this, please do so. **
DEVICE=C:\PCTCP\DIS_PKT.GUP
rem ******* PC/TCP INSTALL ADDED LINE(S) - END ******




REM***********Autoexec.Bat*****************************
REM  All the lines with lower-case characters and few "rem"
REM  statements in lower-case  are entered manually.
REM  The rest of the file was copied from AEXECFTP.BAT
REM  See above (#5) for more details.
REM********************************************************
rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
C:\LANMAN.DOS\NETPROG\NETBIND.COM
C:\DOS\SMARTDRV
PATH=C:\DOS;
@REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
rem NET START WORKSTATION
rem LOAD NETBEUI
rem NET LOGON <YOURNAME> *
@REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2
rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
SET PATH=C:\PCTCP;%PATH%
SET PCTCP=C:\PCTCP\PCTCP.INI
C:\PCTCP\TOKDRV.EXE
rem ******* PC/TCP INSTALL ADDED LINE(S) - END ******
c:\pctcp\netbios -s ""
net start workstation
net logon <yourname> *

************ Protocol.ini*******************
[PROTMAN]
  DRIVERNAME = PROTMAN$
  DYNAMIC = YES
  PRIORITY = NETBEUI

[NETBEUI_XIF]
  Drivername = netbeui$
  SESSIONS = 6
  NCBS = 12
  BINDINGS = "IBMTOK_NIF"
  LANABASE = 0

[IBMTOK_NIF]

; protocol.ini section for the IBM Token Ring Adapter

    drivername = IBMTOK$

[PKTDRV]
CHAINVEC = 0x62
INTVEC = 0x60
DRIVERNAME =  PKTDRV$
BINDINGS = IBMTOK_NIF


********************PCTCP.ini***********************
[pctcp general]
host-name = LAB145209
domain = LABRING
time-zone = EST
time-zone-offset = 300
use-old-init-scheme    = no

[pctcp kernel]
interface = ifcust 0
window = 2048
low-window             = 0
use-emm                = no
kernel-int             = 0x61
ip-ttl                 = 64
ip-precedence          = routine
ip-precedence-matching = lax
ip-security            = none
ip-delay               = high
ip-reliability         = low
ip-throughput          = low
large-packets = 5
small-packets = 5
tcp-connections = 6
udp-connections = 6
router-discovery       = no
mtu-discovery          = yes

[pctcp ifcust 0]
ip-address = 141.225.11.11
subnet-mask = 255.255.0.0

[pctcp lpr]
banner                 = yes

[pctcp idprint printer]
when                   = timeout
timer                  = 30
mine                   = no
number                 = 0

[pctcp ip-security]
basic-classification   = unclassified
matching               = lax

[pctcp pd-pctcp]
default                = ipx

[pctcp pd-pctcp ipx]
retain-header          = 0
protocol               = UDP
type-port              = 0x8137,213

[pctcp netbios]
scope                  =

[pctcp host]
umask                  = 644

[pctcp wmsg]
protocol               = UDP
save-protocol          = yes
beep-on-msg            = yes

[pctcp serial n]
port                   = 1
io-addr                = 0x03f8
irq                    = 4
baud                   = 2400
hardware-flow-control  = on

[pctcp comscrpt hostname]
dialup                 = c:\pctcp\dialup.scr
hangup                 = c:\pctcp\hangup.scr
mru                    = 1500
accm                   = 0x000A0000
addr-ctrl-field-comp   = on
ntprotocol-field-comp        = on
local-ip-address       = 0.0.0.0
remote-ip-address      = 0.0.0.0

[pctcp time]
dst-begins             = 94
dst-ends               = 299

[pctcp install]
bindir = C:\PCTCP
etcdir = C:\PCTCP
kernel-name = TOKDRV.EXE
major-version = 2
minor-version = 2
patch-level = 0
do-kappconf            = yes
configure-driver       = yes

[pctcp tn]
back-arrow-key = del

[pctcp vt]
wrap-line = on

***********************LanMan.ini********************************

;*****************************************************************;
;**                  Microsoft LAN Manager                      **;
;**            Copyright(c) Microsoft Corp., 1992               **;
;*****************************************************************;
[networks]
  netservices = chknet, minses

[workstation]
  wrkservices = encrypt,messenger,netpopup
  computername = lc145209
  domain = labring
  othdomains =
  numdgrambuf = 3
  lanroot = C:\LANMAN.DOS

[netshell]
  username = palithaj

[version]
  lan_manager = 2.2.0

[messenger]

[services]
  chknet        = netprog\chknet.exe
  minses        = netprog\minses.exe /n
  workstation   = netprog\netwksta.exe
  messenger     = services\msrv.exe
  netpopup      = services\netpopup.exe
  encrypt       = services\encrypt.exe
  minipop       = services\minipop.exe
The product included here, PC/TCP, is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

You can reach FTP Software, Inc. at (508) 685-4000.
You may reach FTP Software, Inc. Technical Support at (800) 382-4387.

Additional query words: lm22b pc/tcp dos msdos tcp

Keywords:
Issue Type:
Technology: kbAudDeveloper kbLanManSearch kbLanMan220b


Send feedback to Microsoft

© 2002-2003 Microsoft Corporation. All rights reserved.