Microsoft KB Archive/100699

= Using FTP PC-TCP with LAN Manager 2.2 =

Article ID: 100699

Article Last Modified on 7/30/2001



This article was previously published under Q100699



SUMMARY
FTP Software's PC/TCP can be used several ways with LAN Manager on an MS-DOS enhanced workstation.


 * the "Generic Kernel" protocol driver can be used as a transport for just PC/TCP applications in conjunction with a LAN Manager Transport providing services for the LAN Manager redirector and software
 * it can also be used as a LAN Manager transport through FTP's NetBIOS driver

To do this, you need the NDIS driver version of PC/TCP and FTP's NetBIOS driver. The tests on which this article is based were conducted using version 2.2 of PC/TCP, which includes both drivers.



MORE INFORMATION
First install the LAN Manager Enhanced Workstation software and use NetBEUI as the transport protocol. If you intend to use PC/TCP as the LAN Manager transport, you can remove the LOAD NETBEUI command from AUTOEXEC.BAT.

Then install the PC/TCP software as instructed in its "Installation and Configuration Guide" under the section describing using an NDIS driver with the generic kernel. If you want to use the PC/TCP kernel as the LAN Manager transport, you need a copy of NETBIND.COM--you can use the version provided with PC/TCP on the "Unsupported Network Software" diskette. You can ignore the section on modifying PROTOCOL.INI.

A sample of the configuration files are given here for using the PC/TCP as a LAN Manager transport. Several important notes are listed at the end of the article.

CONFIG.SYS
device = c:\dos\himem.sys device = c:\dos\emm386.exe noems x=d800-dfff dos=high,umb files=30 buffers=20 rem ***** LASTDRIVE=Z DEVICEHIGH=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICEHIGH=C:\LANMAN.DOS\DRIVERS\ETHERNET\ELNKII\ELNKII.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. ** DEVICEHIGH=C:\PCTCP\DIS_PKT.gup (*1) rem ******* PC/TCP INSTALL ADDED LINE(S) - END ******

AUTOEXEC.BAT
rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ****** rem **** @REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2 ==== SET PATH=C:\LANMAN.DOS\NETPROG;%PATH% @REM ==== LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.2 ==== rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ****** LOADHIGH C:\WINDOWS\SMARTDRIVE.EXE LOADHIGH C:\DOS\SHARE.EXE LOADHIGH C:\DOS\DOSKEY.COM SET PATH=C:\PCTCP;%PATH% SET PCTCP=C:\PCTCP\PCTCP.INI (*2) C:\PCTCP\NETBIND.COM (*3) C:\PCTCP\ETHDRV.EXE (*4) c:\pctcp\netbios -S "" (*5) rem ******* PC/TCP INSTALL ADDED LINE(S) - END ****** NET START WORKSTATION

PROTOCOL.INI
[PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES PRIORITY = NETBEUI

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

[ELNKII_NIF] DRIVERNAME = ELNKII$ INTERRUPT = 3 IOADDRESS = 0x300 DMACHANNEL = 1
 * 3c503 3Com EtherLink II adapter
 * 3c503 3Com EtherLink II adapter

[PKTDRV] CHAINVEC = 0x62 INTVEC = 0x60 DRIVERNAME = PKTDRV$ BINDINGS = "ELNKII_NIF" NOTES:

(*1) This is the packet driver to NDIS converter module and must be loaded.

(*2) This is the configuration module for the PC/TCP Kernel. The interface= parameter in the [pctcp kernel] section of this file must be set to the kernel driver loaded (see below) for proper operation.

(*3) Netbind is used to bind the NDIS driver to the PC/TCP coversion module.

(*4) This is the PC-210 Generic Kernel for DIX Ethernet. IEEEDRV.EXE is used for 802.3 Ethernet and TOKDRV.EXE is used for 802.5 Token Ring.

(*5) This is the PC/TCP NetBIOS driver which must be loaded for RFC 1001 and 1002 compliance to provide a session layer to allow LAN Manager to communicate with the PC/TCP Kernel.

