Usenet 1994 January/usenetsourcesnewsgroupsinfomagicjanuary1994.iso/answers/ibmpc-tcp-ip

Text File | 1993-11-24 | 113.3 KB | 3,255 lines

Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.answers,news.answers
Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!gatech!europa.eng.gtefsd.com!uunet!world!aboba
From: [e-mail] (Bernard Aboba)
Subject: comp.protocols.tcp-ip.ibmpc Frequently Asked Questions (FAQ)
Message-ID: <[e-mail]>
Followup-To: poster
Summary: Frequently Asked Questions (and answers) about TCP/IP on
                   PC-compatible computers.
Keywords: TCP/IP, IBM PC, SLIP, PPP, NDIS, ODI
Sender: [e-mail] (Bernard D Aboba)
Reply-To: [e-mail]
Organization: MailCom
Date: Wed, 24 Nov 1993 06:26:00 GMT
Approved: [e-mail]
Expires: Fri, 31 Dec 1993 00:00:00 GMT
Lines: 3236
Xref: senator-bedfellow.mit.edu comp.protocols.tcp-ip.ibmpc:22479 comp.answers:2791 news.answers:15053

Archive-name: ibmpc-tcp-ip

comp.protocols.tcp-ip.ibmpc:
FAQ Posting, 12/1/93
Unless otherwise stated, the views expressed herein are my own.  Last
time I looked, I had not been appointed official spokesperson of any
of the following:
    The Planet Earth
    The U.S.Government
    The State of California (not so good)
    The University of California, Berkeley
    The City of Berkeley (bringing you Riot of the Week)
    Any major or minor breakfast cereal (not even oatmeal!)

This FAQlet will be posted monthly. In between it will be
available from the FTP archive on netcom1.netcom.com,
get /pub/mailcom/IBMTCP/ibmtcp.zip.

************** Legalese  **************
This FAQ is presented with no warranties or guarantees of ANY KIND
including correctness or fitness for any particular purpose.  The
author(s) of this document have attempted to verify correctness of the
data contained herein; however, slip-ups can and do happen.  If you use
this data, you do so at your own risk.

*********** Citation entry  ***********
This FAQ may be cited as:
  Aboba, Bernard D.(1993) "comp.protocols.tcp-ip.ibmpc Frequently
  Asked Questions (FAQ)" Usenet news.answers, available via
  file://netcom1.netcom.com/pub/mailcom/IBMTCP/ibmtcp.zip,
  41 pages.

*********** Change History  ***********
Changes from 11/1/93 posting:
Various updates and corrections.

*********** Related FAQs ***************************
There is a FAQ available on features of TCP/IP
Packages for DOS and Windows. This is available at:
file://ftp.cac.psu.edu/pub/dos/info/tcpip.packages.
The Windows Sockets Faq is posted to alt.winsock, and
is available at:
file://SunSite.UNC.EDU/pub/micro/pc-stuff/ms-windows/winsock/FAQ
The PC-NFS FAQ is available at:
file://seagull.rtd.com/pub/tcpip/pcnfs.FAQ.v1.4.Z or pcnfsfaq.zip
file://ftp.york.ac.uk/pub/FAQ/pcnfs.FAQ

*********** EXAMPLE CONFIGURATION FILES  ***********
Many thanks to Dave Fetrow ([e-mail])
for creating an archive of setup files. The archive is
particularly oriented toward sets of applications that
are somewhat tricky, such as combinations involving
different driver sets, mixtures of Novell, TCP/IP,
and W4WG, etc.
Please include not only the setup and configuration files
but some directions. Comments included with the setup files
are highly desirable. The files can include your name if you
desire.
Please mail submissions to [e-mail].
The archive itself is located at:
file://ftp.biostat.washington.edu/ftp/pub/msdos/network.setups

*********** QUICKIE Guide to Useful Stuff ************
HGopher: file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/hgopher.zip
PC-Eudora: file://ftp.qualcomm.com/pceudora/windows/pce14b17.exe
PKTMUX: file://ftp sunee.uwaterloo.ca/pub/wattcp/pktmux12.exe
winpkt: file://biochemistry.cwru.edu/pub/trumpwsk/winsock.zip
ODIPKT: file://hsdndev.harvard.edu/pub/odipkt/odipkt.com, net.cfg,readme
NUPOP: file://ftp.acns.nwu.edu/pub/nupop/nupop201
Minuet: file://boombox.micro.umn.edu/pub/pc/minuet/minuarc.exe
EINet winWAIS: file://ftp.einet.net/einet/pc/eiwais*.zip
WinFinger: file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/finger31.zip
WinTrumpet: file://biochemistry.cwru.edu/
Trumpet Winsock: file://biochemistry.cwru.edu/pub/trumpwsk/winsock.zip
WinTelnet: file://ftp.ncsa.uiuc.edu/Telnet/windows/executables/wtel1b1.zip
WinQVTNet: file://biochemistry.cwru.edu/pub/qvtnet/?
PC Pine: file://ftp.cac.washington.edu/mail/pcpine_p.zip
NCSA Telnet: file://mer.edu/pub/ppp/ncsappp.zip
WinMosaic: file://ftp.ncsa.uiuc.edu/
WinCello: file://ftp.law.cornell.edu/pub/LII/Cello/winsock_alpha/cello.zip,
   viewers.zip, gswin.zip
Packet driver specs: file://vax.ftp.com/pub/packet-d.ascii,packet-d.mss
ODI driver info: file://sjf-lwp.novell.com/anonymous/dev_docs/lan_drv/*,
ODI Protocol stack info: file://sjf-lwp.novell.com/anonymous/dev_docs/pstacks/*
NDIS specs: file://vax.ftp.com/pub/ndis-mac.v101.txt, ndis-mac.v201.txt
******************************************************

TABLE OF CONTENTS

A. Components of a TCP/IP solution

A-1. What do I need to run TCP/IP on the PC?
A-2. What are packet drivers?  Where do I get them?
A-3. What is Winsock?  Where can I get it? How do I set up Trumpet
Winsock?
A-4. What publicly distributable TCP/IP applications are there
     for DOS?  Windows?
A-5. What software is available for doing SLIP?  Compressed SLIP?
     PPP?  For DOS?  For Windows?
A-6. Where can I get ping?  traceroute?
A-7. How do I install packet drivers for Windows applications?
A-8. When do I need to install  WINPKT?
A-9. How to do I run both WinQVT and ODI?
A-10. Is it possible to use BOOTP over SLIP?
A-11. How do SLIP drivers work?
A-12. When do I need to install PKTMUX?
A-13. Can NDIS be used underneath multiple protocol stacks of the same type?
A-14. Is there an NDIS over packet driver shim?
A-15. How do I run NetBIOS over TCP/IP?
A-16. How do I get my BBS to run over TCP/IP?
A-17. Sample Stick Diagrams
A-18. Strange and wonderful configuration files submitted by readers

B. Hints for particular packages

B-1. What do I need to know before setting up SLIP or PPP?
B-2. How do I configure SLIPDISK?
B-3. What version of KA9Q should I use and where do I get it?
B-4. How do I configure KA9Q as a SLIP connection?
B-5. How do I configure KA9Q as a router?
B-6  How do I get KA9Q to support BOOTP?
B-7. How do I get DesQView X to run over the network?
B-8. Why is NFS so slow compared with FTP?
B-9.  How do I get KA9Q to support PPP?
B-10. How do I get KA9Q to support SLIP dialin?
B-11. Where can I get information on running Novell and TCP/IP
      concurrently?
B-12. What Novell TCP/IP NLMs are out there and how do I get them
      to work?
B-13. How do I get a telecom package supporting Int 14h redirection
      to work?
B-14. How do I run SLIP with Windows For Workgroups TCP/IP?
B-15. How do I get Windows For Workgroups to work alongside Novell?
B-16. NCSA Telnet doesn't reassemble fragments. What should I do?

C. Information for developers

C-1. What publicly distributable TCP/IP stacks are there that I can
     use to develop my own applications?
C-2. Where can I get a copy of the Windows Sockets FAQ?

--------------------- FAQlet Begins Here ---------------------------
A. Components of a TCP/IP solution

A-1. What do I need to run TCP/IP on the PC?

To run TCP/IP on the PC you will need:
* Appropriate hardware, such as:
    Ethernet card
    Token Ring card
    AppleTalk card
    Serial Port

  Any other network card with a packet driver or NDIS or ODI driver,
  (such as Arcnet), will also work.  If your card supports NetBIOS,
  this is also acceptable, since you can run a packet-driver-over-
  NetBIOS shim.
* Drivers for your hardware.
  Your card probably came with one or more of the following drivers:

    Network Device Interface Specification (NDIS) drivers
      [spec. by 3Com & Microsoft, used by LAN Manager, Windows
      for Workgroups, and Windows NT. LAN Manager uses NDIS 2.0,
      Windows NT uses 3.0, and WFW supports 2.0 and will support
      3.0]
    ODI Drivers [spec. by Novell, abbreviation for Open DataLink
      Interface]
    Packet Drivers [spec. by FTP Software]

  TCP/IP stacks have been written for each of these driver interfaces,
  so the important thing is whether your chosen stack is compatible
  with the interface available for your card.

  A shim is software that runs on top of one set of drivers to
  provide an interface equivalent to another set. This is useful,
  for example,if you are looking to run software requiring an
  NDIS driver(such as Chameleon NFS) alongside software
  requiring a packet driver interface (such as KA9Q, Gopher, Popmail,
  NCSA Telnet, etc.), or run software intended for, say, a packet
  driver over an NDIS driver instead.

  Shims are available to run packet drivers over NetBIOS, ODI,
  or NDIS, in order to run software expecting a packet driver over
  NDIS, ODI, or NetBIOS instead.

* A TCP/IP protocol stack.
  The TCP/IP protocol stack runs on top of the driver software, and
  uses it to access your hardware. If you are running a TCP/IP
  protocol stack that requires drivers that aren't available for your
  hardware, you're in trouble. Check into this before purchasing!

* If running Windows applications that require it, WINSOCK.DLL.

  Windows Sockets is a sockets interface which was created as a
  Windows DLL. Each  TCP/IP implementation requires its own version
  of Windows Sockets. There is not yet a freely available Windows
  Sockets implementation released yet, although Trumpet WinSock is
  currently in Alpha test. WINSOCK.DLL provides 16-bit support;
  WSOCK32.DLL provides 32-bit support.

* Applications software.
  Although most of us in this newsgroup seem to spend our time
  looking for working combinations of applications,WINSOCK.DLL
  Windows Sockets compliant TCP/IP implementations, shims,
  drivers, and hardware, ultimately your goal is eventually to
  run an application successfully. If and when that ever happens,
  please send me a note, so I can add it to this FAQlet.

A-2. What are packet drivers?  Where do I get them?

Packet drivers provide a software interface that is independent of the
interface card you are using, but NOT independent of the particular
network technology. As Frances K. Selkirk ([e-mail]) notes:
"That's one reason they're easier to write than ODI drivers! If you
write a class three (802.5 Token Ring) driver, you will need to use
software that expects a class three driver, not software that expects
a class 1 (DIX ethernet) driver. There are a few drivers that fake class 1.
I believe only class 1 and class 6 (SLIP) drivers are supported by
freeware packages."

The chances are fair that your Ethernet card came with a packet
driver, and if so, you should try that first. If not, then you
can try one of the drivers from the Crynwr collection (formerly
called the Clarkson Drivers). See the Resource listing for info.
For 3COM drivers, try ftp ftp.3com.com. For technical information,
try [e-mail]. For marketing and product info, try
[e-mail] packet driver specification is available
from vax.ftp.com in packet-d.ascii

The following vendors have packet drivers with source available for
their pocket lan adaptors:
D-Link - [phone]
Solectek - [phone]
Accton - [phone]
Compulan - [phone]
(soon Kodiak's Noteport - [phone])

A-3. What is Windows Sockets?  Where can I get it?

  The idea for Windows Sockets was born at Fall Interop '91, during a
  Birds of a Feather session.
  From the Windows Sockets specification:
  [courtesy of Mark Towfiq, [e-mail]]:

    The Windows Sockets Specification is intended to provide a
    single API to which application developers can program and
    multiple network software vendors can conform. Furthermore, in
    the context of a particular version of Microsoft Windows, it
    defines a binary interface (ABI) such that an application
    written to the Windows Sockets API can work with a conformant
    protocol implementation from any network software vendor.

Windows Sockets will be supported by Windows, Windows for Workgroups,
Win32s, and Windows NT. It will also support protocols other than TCP/IP.
Under Windows NT, Microsoft will provides Windows Sockets support over
TCP/IP and IPX/SPX. DEC will be implementing DECNet. Windows NT will
include mechanisms for multiple protocol support in Windows Sockets,
both 32-bit and 16-bit.

As Mark Towfiq notes:
"The next rev. of Winsock will not be until towards the end of 1993.
We need 1.1 of the API to become firmly settled and implemented first."

Mark continues:
    "Files and information related to the Windows Sockets API are
     available via FTP (user: "anonymous", password: your e-mail
     address) on the host SunSite.UNC.EDU, in
     /pub/micro/pc-stuff/ms-windows/winsock, which is a mirror of
     /pub/winsock on Microdyne.COM (SunSite has a much
     faster connection to the Internet, so you are advised to use
     that).

     If you do not have FTP access to the Internet, send a message
     with the word "help" in the body to either
     [e-mail], or [e-mail], to obtain
     information about the FTP to Mail service there."

  Alternative sources for the Windows Sockets specification include
  rhino.microsoft.com (an FTP server running NT), as well as the
  Microsoft forum on CompuServe (go msl).

  Currently NetManage (NEWT), Distinct, and Frontier are shipping
  Winsock TCP/IP stacks. Wollongong and FTP are in beta. If you are
  looking for a Winsock.dll, you should first contact your TCP/IP
  stack vendor. Windows NT and TCP/IP for Windows for Workgroups are
  currently in beta from Microsoft.

  Peter Tattam is alpha-testing a shareware Windows Sockets compliant
  TCP/IP stack. If you're interested in helping with the testing, you
  can obtain it via ftp ftp.utas.edu.au, cd /pc/trumpet/winsock,
  get winsock.zip, winpkt.com.

The first thing to do after you download WINSOCK.ZIP is to create
a directory for Trumpet Winsock, such as C:/TRUMPWSK, and put it
in your DOS PATH statement.

Trumpet Winsock operates over packet drivers, or over a serial port
using its own built-in SLIP or CSLIP. If you are using a network
adapter, this means that you will have to locate a packet driver
for your adapter, and load it. Trumpet Winsock also comes with
WINPKT, and this is loaded next, via the command
WINPKT.COM 0x60 [or whatever the software interrupt for your packet driver]
You will then enter Windows, and create a group in the Program Manager
for all the files that come with Trumpet Winsock. The stack itself is loaded
by executing TCPMAN. Applications that come with it include WinCHAT,
a chatting program; PINGW, a ping utility; FTPW for FTP, WINARCH for Archie.
When you first execute TCPMAN, you will be asked to fill out the setup
information for the stack. Select whether you will be using a network
adapter or SLIP; you cannot use both.

Note that if you are using SLIP, you must dial the connection yourself;
Trumpet Winsock currently does not include a scripting language, although
this is on the way.

Any comm program will do for this, as long as you don't drop DTR.

A-4. What publicly distributable TCP/IP applications are there for
     DOS?  Windows?

Right now there are a wealth of publicly distributable TCP/IP
applications running under DOS.  Windows also has a wealth of
programs available, including implementations of Gopher, Mail
(POP3/SMTP), FSP, Mosaic, Telnet/FTP, and WAIS.
See the Resource listings for information.

A-5. What software is available for doing SLIP?  Compressed SLIP?
     PPP?  For DOS?  For Windows?  For OS/2?

For SLIP or CSLIP I recommend using SLIPPER or CSLIPPER. These are
packet drivers that can be used along with a dialer. For PPP, I recommend
the EtherPPP packet driver, which while taking up too much RAM
(121K), works just fine, and includes a built-in dialer.

If you are running Windows Sockets, I recommend the Trumpet Winsock,
which comes with its implementation of SLIP/CSLIP, but which does
not appear to work with EtherPPP.

KA9Q supports SLIP/CSLIP/PPP, but unfortunately can not be used as a
TCP/IP protocol stack to run other apps.

There is a special version of NCSA Telnet for PPP, available from
merit.edu, /pub/ppp directory.

IBM is reportedly shipping TCP/IP for OS/2.  Please
see the FAQ from comp.os.os2.networking for details.

IBM, FTP Software, and Netmanage also offer SLIP support in their
products. See the resource listings for details.

A-6. What diagnostic utilities are available to find problems with
my connection?  Where can I get them?

Frequently used diagnostic utilities include ifconfig (checks the
configuration of the network interfaces), ping (tests IP layer
connectivity), traceroute (traces the route that a packet takes
between two sites), netstat (checks the routing table), tcpdump
(protocol analyzer), arp (looks at the IP to Ethernet address
mappings).

KA9Q includes ifconfig, ping and traceroute functions.  In KA9Q hop
check is the equivalent of traceroute.  The Trumpet TCP/IP stack also
has a hopchk2 command that is a traceroute equivalent.
The DNPAP tools (check the resource guide for listings) include
Ethernet packet catchers, networking monitors and a network host
profiler.

Trumpet Winsock comes with a Windows implementation of Ping.

A-7. How do I install packet drivers for Windows applications?

The secret is to load the packet driver, then run Windows. If you
are running Trumpet Winsock, you will also have to load WINPKT
before running Windows, as follows:

winpkt 0x60

If you are running DOS applications within a virtual DOS session
under Windows, you should load PKTMUX after your packet driver, as
follows:

PKTMUX 4 [or however many sessions you want]
WIN [load windows]

Then within each DOS session, load PKTDRV, the virtual packet driver.

A-8. When do I need to install WINPKT?

PKTMUX and WINPKT both accomplish the same thing: allowing you to
connect to a DOS packet driver running in real mode from a virtual
DOS session under Windows. PKTMUX is useful when you are running
more than one TCP/IP stack, and since it takes up more RAM and is
slower than WINPKT, you should only use it when you want to run more
than one stack at a time. If you are running only one DOS app,
or are using Trumpet Winsock, stick with WINPKT.

James Harvey ([e-mail]) notes:
Winpkt is only useful running DOS applications with built-in TCP/IP
stacks under Windows, and for some Windows-based stacks (like the
Trumpet winsock.dll).  When an application registers with a packet
driver TSR to receive packets of a specified protocol type, one of the
things it hasto pass as a parameter to the packet driver in the call
is the address of a routine in the application that the packet driver
is to call when it has a packet to pass back to the application.  In
the case of an application running in 386 enhanced mode in a DOS shell
under Windows that is using a packet driver loaded in real mode before
Windows was loaded, the packet driver must ensure that Windows has the
application in memory when it does the callback, otherwise the callback
jumps off into space and your system locks up.  Winpkt does a Windows
system call to force the app into memory before the callback is done.

Erick Engelke ([e-mail]) notes:
Windows in enhanced mode uses the protected mode of the
386 CPU to create multiple virtual machines.  Winpkt tells
Windows to switch to the correct virtual machine before
trying to pass up the packet.  This reduces the chances of
Windows crashing.

A-9. How do I run both WinQVT/Net and ODI?

My advice is to use the Windows Sockets version of WinQVT/Net, Trumpet
Winsock, and ODIPKT. ODIPKT will allow you to run packet driver software
over ODI. You will also need to load WINPKT for Trumpet Winsock.
The loading sequence is:

LSL [Link support layer]
NE2000.COM [or other ODI driver]
IPXODI [IPX version supporting ODI]
NETX
ODIPKT 1 96
WINPKT 0x60
WIN [run windows]
Then run Trumpet Winsock, and load WinQVT/Net.
A-10. Is it possible to use BOOTP over SLIP?
Yes, but it is easier to use dynamic address assignment to get your IP address.
This is where the SLIP server outputs your IP address before switching
to SLIP.

If you need BOOTP, then you should run a BOOTP server on the SLIP
server so that it can tell which SLIP connection originated the
request. Of course, the BOOTP server will ignore the hardware address
of the request originator, but instead will keep track of the SLIP
interface the request came in on. See the question on adding BOOTP to
KA9Q for info on how to handle this on the PC. Under UNIX, you may
have to add BOOTP capability to your slip driver, and rebuild the
kernel. (Not recommended for the squimish).

A-11. How do SLIP and PPP drivers work?

Some TCP/IP applications are written to only support Class 1 (Ethernet)
packet drivers, but do not support Class 6 (SLIP). For these applications, you
need software to make the application think it is dealing with a class 1
interface. This is done by adding fake ethernet headers to incoming
SLIP or PPP packets and stripping the headers off outgoing packets.

A-12. When do I need to use PKTMUX?

PKTMUX is needed to allow you to use more than one TCP/IP stack at the same
time. This is useful if you have applications that require different stacks.
Note that you do not need PKTMUX to run different protocols, since packet
drivers only look at packets in the protocol they're designed to handle,
and therefore you can use more than one of these at a time without conflict.
You also don't need PKTMUX if all your applications use the same TCP/IP stack.
PKTMUX works by looking at outgoing datagrams, and caching information on
source and destination ports and addresses. Using this information, PKTMUX
tries to sort incoming datagrams by TCP/IP stack. If it can't figure out
which stack to send a datagram to (as might be the case if you were running
a server application on a well-known port, and had not sent any outgoing
packets yet), PKTMUX will send the datagram to all stacks. If all stacks
do not complain about the datagram, PKTMUX will throw away the ensuing outgoing
ICMP error message, assuming that one of the stacks correctly received
the datagram. If all stacks complain, it will send a single ICMP message
and throw the rest away.

While PKTMUX does its job very well, there are some situations that it cannot
handle, such as port conflicts. If two applications open the same TCP port,
chaos is inevitable, and there is little that PKTMUX can do to help.

A-13. Can NDIS be used underneath multiple protocol stacks of the same type?

No. There is no equivalent to PKTMUX for NDIS.

A-14. Is there an NDIS over Packet Driver Shim?

Joe Doupnik writes:
"No. Packet Drivers work by having an application register
for a particular packet TYPE, such as 0800 for IP. NDIS does works much
differently by offering a peekahead of every packet to applications in turn,
a polling operation. The only way NDIS could gracefully sit on a PD would
be to run the Packet Driver in all-types mode and let NDIS see all pkts
not used by other clients. Needless to say, that's an undesirable situation.
The quick solution, costing about US$100 (at least at my place,
more at yours) is a second Ethernet board in the client together with a
second IP address (most important, please)."

A-15. How do I run NetBIOS over TCP/IP?

NetBIOS over TCP/IP is discussed in RFCs 1001 and 1002.
Assuming you don't need any of the extensions to RFC NetBIOS
Microsoft created to make NetBIOS work smoothly in a routed environment
(available only in their IP stack), you can choose from a wide variety of
commercial vendors. For example, FTP Software's PC/TCP includes RFC NetBIOS
support; Performance Technologies has a NetBIOS that runs over packet drivers,
as does Accton (LANSoft).

A-16. How do I get my BBS to run over TCP/IP?

First off, let's clarify what we mean by "over TCP/IP." Usually
this means "accessible via Telnet." Be aware that doing this will
not necessarily work well, since few BBSes have been tested running
over TCP/IP. As a result you may experience frequent crashes, or
abominable transfer rates. For example, I have seen
transfer rates as low as 100 characters/second over a 14.4 Kbps
PPP connection which routinely supports 1600 cps transfers with
FTP.

This situation might be improved by running an FTP server instead.
This could be accomplished for example by running KA9Q in another
window under DesQView, or by putting the files on an NFS-mounted
drive, then using another machine as the FTP server.
One way to hook up a multi-line BBS is to use a terminal server,
and hook up the BBS's serial ports to that. The disadvantage of this is that
if your BBS is really big you will need multiple terminal servers
which will each have their own domain names and TCP/IP addresses.
Confusing.

Brian Clements of Murkworks has a better solution. This is to run
a terminal server NLM. This can hook up BBSes of arbitrary size,
all lines with a single TCP/IP address. This works along with
a FOSSIL compatible communications driver. For info, contact him
at [e-mail].

In this same vein, there is a line of TCP/IP FOSSIL drivers from
Daniel J. Karnes ([e-mail]) of NMS & Systems Engineering,
TASP Development Group, Silverado, CA 92676-0233, [phone].

According to Daniel:
"TASP installs in any IBM PC/AT/XT compatible system as a TSR and once
resident provides an application transparent interface layer for several
major networking protocols. TASP fully conforms to the FOSSIL specification,
which means that it will work with any program that can talk to a FOSSIL,
including Fido, WILDCAT!, PCBoard, Searchlight, and Waffle.

TASP is easily installed and can operate totally independent of any other
software. A user connects to TASP via a LAN, X.25 link or Internet SLIP
line and then TASP communicates with the application as if it were a
modem. All the application need to is to make Int 14 function calls to
talk to TASP. TASP can make use of the internal COM ports on your system,
a multiport or multimodem board, or an ethernet card. "

It may also be possible to use Int 14h redirection, as supported by
the WATTCP Int 14h redirection program (see below).
I haven't used this, but I have heard that it works with both WILDCAT!
and QMODEM Pro. If you know differently, please let me know.

A-17. Stick diagrams

It has been proposed that we begin to collect some diagrams of working
combinations of hardware, drivers, shims, stacks, and applications. I'm
game, and have made a start below. If you've got some other exotic
configuration that works (or if you've tried one of the configurations below
and discovered it doesn't work, drop me a line).

Running an individual DOS application under Windows

    NCSA telnet / DOS Trumpet / POPmail/ PC Gopher III
                 |
             DOS Session
                 |
             Windows 3.1
                 |
               WinPKT
                 |
            Packet driver or Shim
                 |
                DOS

DOS Trumpet, NCSA Telnet, and WinQVT/Net over Ethernet under Windows

                                                QVT/NET
                                                   |
     TRUMPET                    NCSA telbin        |
       |                             |             |
     PKTDRV1                     PKTDRVn           |
       |                             |             |
     DOS Session                DOS Session    Windows Session
       +-----------+-----------------+             |
                   |                               |
                   +                               |
             WINDOWS 3.1 .............        WINDOWS 3.1
                   |                               |
                   |                      PKTINT(QVT/NET own)
                   |                               |
                   |                           PKTDRVx
                   +-------------------------------+
               PKTMUX n
                   |
          CryNwr Driver or SHIM
                   |
                  DOS

PC Gopher III, NCSA Telnet over CSLIP under Windows


  PC Gopher III                 NCSA telbin
       |                             |
     PKTDRV1                     PKTDRVn
       |                             |
     DOS Session                DOS Session
       +-----------+-----------------+
                   |
                   +
             WINDOWS 3.1
                   |
                   |
                   |
                   |
                   +
                PKTMUX n
                   |
               CSLIPPER
                   |
                  DOS
           |
          Serial Port

PC Gopher II and Novell on a LAN - Alternative I
[Didn't work for me, but it's supposed to be OK]

               NOVELL
PC Gopher        |
  III            |
   |             |
DOS Session    NETX
   |             |
 Windows 3.1     |
   |           PDIPX
  WINPKT        /
     \         /
      \       /
       \     /
        \   /
     Packet Driver
          |
     DOS
          |
     Ethernet card
          |
      Ethernet

PC Gopher III and Novell on a LAN - Alternative II

                                  PC-Gopher III
                      |
                  DOS Session
                      |
                      Windows 3.1
                                      |
                                      |
                    Novell            |
                        \            /
                      NETX         WINPKT
                          \        /
                        IPXODI   ODIPKT
                             \   /
                              \ /
                               |
                        ODI driver and LSL
                   |
                  DOS
                               |
                          Ethernet Card
                   |
               Ethernet

WinQVT/Net and PC Gopher II and Novell over a LAN - Alternative I

PC Gopher
  III
   |             Win QVT/Net
 PKTDRV1            |
   |                |
DOS session      Windows 3.1
   |                |
Windows 3.1      PKTINT (QVT/NET own)
   |                |
   |             PKTDRVn
 WinPKT             |
   |                |          NOVELL
   +----------------+            |
   |                             |
   |                             |
 PKTMUX n                      NETX
   |                             |
    \                          PDIPX
     \                           |
      \                          |
       \                         |
        \                        |
     Packet Driver --------------+
          |
     DOS
          |
       Ethernet Card
          |
       Ethernet

WinQVT/Net, PC Gopher III and Novell over a LAN - Alternative II

                                             QVT/Net
  PC Gopher III                 NCSA telbin        |
       |                             |             |
     PKTDRV1        .....        PKTDRVn           |
       |           |                 |             |
     DOS Session                DOS Session    Windows Session
       +-----------+-----------------+             |
                   |                               |
           |                               |
             WINDOWS 3.1 .......................WINDOWS 3.1
                   |                               |
                   |                      PKTINT(QVT/NET own)
                   |                               |
                   |                           PKTDRVx
                     |                               |
           |                           |
           |                           |
           |                           |
           +------------------+------------+
                      |
                    Novell            |
                        \            /
                      NETX         PKTMUX n (use if >1 TCP/IP app)
                          \        /
                        IPXODI   ODIPKT
                             \   /
                              \ /
                               |
                        ODI driver and LSL
                               |
                  DOS
                   |
                          Ethernet Card
                   |
               Ethernet

PC Eudora and Windows Trumpet over CSLIP under Windows using Trumpet Winsock

 PC Eudora    Windows Trumpet
     \         /
      \       /
       \     /
        \   /
       TCPMAN
          |
     Windows 3.1
      |
     WINPKT 0x60
          |
         DOS
          |
      Serial Port

PC Eudora and Windows Trumpet supporting Ethernet and CSLIP under Windows
using NDIS supporting stack [Chameleon]
[Please note: this is not possible under Trumpet Winsock, since it can
only handle a single interface; it requires a stack that routes]

 PC Eudora    Windows Trumpet
     \         /
      \       /
       \     /
        \   /
      Chameleon NEWT
          |
      Windows v3.1
          |
      +------------------+
      |                  |
    Protocol Manager         |
          |                  |
      NDIS Mac Driver     Serial Port
          |
         DOS
          |
     Ethernet card

PC Eudora, Windows Trumpet, and PC Gopher III under Windows
[Don't think this can be done, but here's my guess on how it would work]:

       WinTrump   PC Eudora
            \     /
 PC Gopher   \   /
  III         \ /
   |           |
 PKTDRV      TCPMAN
     \         |
      \       /
       \     /
        \   /
     \ /
      |
        PKTMUX
          |
     Packet Driver
          |
         DOS
          |
     Ethernet Card

HGopher, PC Eudora, and WinTrumpet Under Windows
(Whether the TCP/IP stack is loaded before or
after Windows depends on the stack)

       HGopher
         |
         |
   PC    |
 Eudora  |  WinTrumpet
     \   |   /
      \  |  /
       \ | /
        \|/
       TCPMAN
         |
     Windows 3.1
         |
      WINPKT
         |
  Packet Driver
         |
        DOS
         |
   Ethernet Card

A-18. Strange and wonderful configuration files

Robert Clift ([e-mail]) writes:
"I have WinQVT/Net 3.4, PC Gopher III (including NCSA DOS Telnet), KA9Q
(gopher and FTP server), and POPMail all running together under Windows
over PKTMUX on a 3C503 packet driver (and ehternet card)."

Here is the stick diagram (yikes!):

Win/QVTNet 3.7     KA9Q Gopher      PC POPMail 3.2     PC Gopher III 1.01
on interrupt 65    & FTP Server           \                    /
    \                  |                    \                /
      \                |                      \            /
        \              |                        \        /
          \          PKTDRV                       PKTDRV
            \          |                            /
              \      DOS Session               DOS Session
                \      |                        /
                  \    |    -------------------
                    \  |  /
                  Windows 3.1
                       |
                     PKINT
                       |
         PKTDRV on Int 65 no listeners set
                       |
           PKTMUX 1.2 with 3 channels
                       |
          Clarkson 3C503 Packet Driver
                   |
                  DOS
                       |
           3Com Etherlink II/16 TP
                       |
                    Ethernet

NOTES:

Win/QVTNet must be loaded as the very first Windows application and must be
kept operating as long as your are in Windows.  It appears that its TCP/IP
stack does some strange things when it disconnects and kills access to the
actual packet driver.

I run PC gopher and POPMail alternatively, so they share one channel which
is allocated via PKTDRV before running the application and deallocated
after the application is finished (I usually throw in a reset command to
PMTMUX as well just to be safe).

To explain what is happening (as best I can since a lot of this came from
experimentation):

1.  The packet driver is loaded
2.  PKTMUX is run over the packet driver in order to multiplex it (in this
    case three channels).
3.  A virtual packet driver is loaded for Win/QVTNet on interrupt 65 and
    the packet driver is told that it is not to listen for any server
    requests.
4.  The PKINT shim is loaded over top of the virtual packet driver
5.  Start Windows and run Win/QVTNet as the first application, it must be
    kept running throughout the Windows session.
6.  Load a virtual packet driver from a DOS session and start KA9Q.  I use
    the following batch file to do this:
         c:\network\pktdrv 63 /l
         h:
         cd \
         net091b
         c:\network\pktdrv 63 /uu
         c:\network\pktmux /r
7.  Load a virtual packet driver and run PC Gopher or POPMail as needed.  I
    use the following batch files for PC Gopher and POPMail respectively:
         c:\network\pktdrv 63
         h:\goph-cli\gopher /T=h:\goph-cli\text /X=h:\goph-cli\binary
         c:\network\pktdrv 63 /uu

         c:\network\pktdrv 66 /c
         h:\popmail\popmail /noems
         c:\network\pktdrv 66 /uu
8.  The only problem seems to be that the NNTP module in Win/QVTNet will
    not operate correctly if POPMail is operating.  Otheriwse it seems to
    work okay without too many problems.

B. Hints for particular packages

B-1. What do I need to know before setting up SLIP or PPP?

Before setting up your SLIP or PPP connection, you should
have available the following information:

* The domain name and TCP/IP address of your host.
* Whether your TCP/IP address will be assigned statically,
  dynamically, or from the server.
* The domain name and TCP/IP address of your machine (if you are not
  configuring the address dynamically or via BOOTP)
* The domain name and TCP/IP address of the primary and secondary
  Domain Name Server.
* The subnet mask.
* The domain name and TCP/IP address of an NNTP server.
* Whether your host supports POP, and if so, what version.
* Whether the host supports compressed or uncompressed SLIP, or PPP.
* The size of the Maximum Receivable Unit (MRU).

Do not attempt to connect to your host before you have this
information, since it will just waste your time and money, and may
cause problems for the network.  In particular, do not attempt to
initiate a connection using a made up TCP/IP address! It is possible
that your made-up address may conflict with an existing address.
This is probably the quickest way to get people very angry at you.
Static addressing means that your TCP/IP address will always
be the same.  This makes it easy to configure your setup files.
Dynamic addressing means that the host will send you a message
containing your TCP/IP address when you log on. This can be
problematic if your software doesn't support grabbing the address
and inserting it into the setup files. If not, then you may have
to edit your setup files every time you log on. Yuck!

Chameleon NFS includes a version of SLIP which can handle dynamic
addressing. The most recent version of Novell's Lan Workplace for
DOS does as well.

If your software supports Bootstrap Protocol (BOOTP), then you can
also determine your address by retrieving it from the BOOTP server.
PPP also supports server assignment of TCP/IP addresses.

B-2. How do I configure SLIPDIAL?

From Ashok Aiyar, [e-mail]:

PHONE Script Files:

PHONE comes with several scripts (for various modems) and for the
University of Minnesota Terminal server built into it.  The command
PHONE WRITE writes these scripts to an ASCII file called PHONE.CMD,
which can be edited to your needs (modem and slip server)
The documentation that accompanies PHONE, provides good instructions on
writing script files to get PHONE to dial SLIP servers other than
the University of Minnesota server.  For example here is a script
that I use to dial a CISCO server at the University that I attend.
Background:  To start a SLIP connection, I dial our terminal server,
and login with a username and password.  After doing so, I start a SLIP
session with the following command "slip username-slip.dialin.cwru.edu",
followed by my password -- again.

Here then is the relevant portion of the PHONE.CMD script file -

#
# CWRU-TS2 SLIP login script by Ashok Aiyar 3/26/93
# Last revised 3/28/93
Procedure    Host.CWRU.Login
TimeOut 60      'CWRU-TS2 terminal server is not responding'
Message         "CWRU-TS2 SLIP login script -- Version 1.1"
Message         'Waiting for SLIP server to respond'
Quiet ON
Expect 'Verification'
Message         'Request for User Verification Received from CWRU-TS2'
Message         'Sending your user name and password'
Quiet OFF
Expect   'Username:'
Send '%u<'
Expect   'Password:'
Private
Send '%p<'
Reject    'Access denied'   'Your user name or password was not accepted'
TimeOut 30    'SLIP server did not respond to your validation request'
Expect 'CWRU-TS2>'
Send 'SLIP<'
TimeOut 10    'SLIP server did not respond to SLIP command'
Expect 'IP hostname or address:'
Send '%u-slip.dialin.cwru.edu<'
TimeOut 10 'SLIP server did not respond to hostname'
Reject    'Bad IP address'   'Incorrect Hostname'
Expect 'Password:'
Send '%p<'
Reject    'Access denied'    'Password not accepted.'
TimeOut 10
Expect 'Header Compression will match your system'
Message 'Login to CWRU SLIP server successful'
Wait 1.0
EndProcedure   Host.CWRU.Login
#
#
Procedure      Host.CWRU.LogOut
# Nothing special needs to be done to logout
EndProcedure   Host.CWRU.LogOut
#
#   End of Script file
#
----------------------------------------------------------------------

How to use packet drivers other than UMSLIP with PHONE?

The quick answer -- there is no "clean" way.  Below is a batch file
hack that I wrote to use PHONE with other packet drivers.  In this
example, the packet driver is Peter Tattam's CSLIPPER.  To use a
batch file like this, you must know the parameters with which you
plan to use the packet driver -- i.e interrupt vector, baud rate,
port address, and IRQ.  This batch file requires UMSLIP.COM,
CSLIPPER.EXE, and TERMIN.COM to be in the same directory
or in your path ...
All that the BATCH file does is to let you dial the SLIP connection
using PHONE, load the appropriate packet driver, hangup the
connection, and unload the driver when you are done ...
-- being CWRUSLIP.BAT --
@echo off
rem   this batch file is an ugly hack of U. of Minn. "SLIP.BAT"
rem   awaiting a version of C/SLIPPER that can directly interact
rem   with PHONE
rem   CWRUSLIP.BAT file is used with PHONE.EXE to start a SLIP
rem   connection on CWRU-TS2
rem   last modified 3/28/93 -- Ashok Aiyar
@echo off
cls
goto start
:start
if %1. == ?.         goto help
if %1. == help.      goto help
if %1. == setup.     goto setup
if %1. == dial.      goto forceD
if %1. == hangup.    goto forceH
if %1. == quit.      goto forceH
if %1. == HELP.      goto help
if %1. == SETUP.     goto setup
if %1. == DIAL.      goto forceD
if %1. == QUIT.      goto forceH
goto bogus
goto unload
:forceH
termin 0x60
umslip >nul
phone force hangup
goto unload
:slipper
termin 0x60
REM  the following line must be changed to reflect the COM port,
REM  IRQ, baud rate, and software interrupt
lh c:\packet\cslipper com1 vec=60 baud=57600 ether
goto end
:forceD
termin 0x60
umslip >nul
phone force dial
goto slipper
:setup
termin 0x60
umslip >nul
phone setup
goto help
:unload
termin 0x60
goto end
:bogus
echo %1 is not a valid command.
echo Try "cwruslip help" for a list of valid commands
echo.
:help
echo --------------------------------------------------------------
echo           Case Western Reserve University SLIP Setup
echo                  using Univ. of Minnesota PHONE
echo --------------------------------------------------------------
echo cwruslip setup     modem settings, phone number, username etc.
echo.
echo cwruslip dial      DIAL and establish the SLIP connection
echo cwruslip quit      HANGUP the phone and unload the driver
echo cwruslip help      this screen
echo.
:end
-- end CWRUSLIP.BAT --

B-3. What version of KA9Q should I use and where do I
get it?

I have tried the latest version of KA9Q (January 1993), but found that it
locked up my machine, and have gone back to v2.1.

From [e-mail] (Michael Bernardi):
"Demon Internet Services have a dialin Internet service in the UK.
They also support a customised version of KA9Q optimised for
dialup, they also support the PCElm mailer, SNEWS news reader and
a customised front end. There is also a combined NEWS and MAIL
program called CPPNEWS and an alternative MAIL program called
VIEW, these last are unsupported by [e-mail] but other
DIS users do support them. All these programs can be found on
ftp.demon.co.uk in the pub/ibmpc/ directory, and are written to
work with KA9Q (specifically the DIS version)."
Anthony McCarthy has added a multi-windowing system to KA9Q that
supports the mouse, which has been recommended. See Resource
listings for info.

B-4. What do I need to run KA9Q? Why won't it do VT-100 emulation?

KA9Q is usually run from a startup script, such as my script
startnos.bat:

\nos\drivers\8003pkdr
\nos\net -d \nos
Here I first load the packet drivers for my 8003 Ethernet card, then
run KA9Q (known as net.exe).
The KA9Q package then reads commands from a configuration file, called
AUTOEXEC.NOS.
For VT100 emulation with KA9Q, try using Giles Todd's VT102.COM,
available via ftp from ftp.demon.co.uk, cd /pub/ibmpc/DIS.

B-5. How do I configure KA9Q as a SLIP connection?  a router?

Here is a sample CSLIP only configuration file:

# Set the host name
#
hostname aboba.slip.netcom.com
ip address [192.187.134.3]
#
#
#
# Configure COM3 on Interrupt 5, at 38400 bps with
# RTS/CTS (c) and Van Jacobson Compression (v) and MTU = 1008
#
attach asy 0x3e8 5 VJSLIP sl0 8092 1008 38400 cv
ifconfig sl0 netmask 255.255.255.252
#
#
#
route add default sl0
# route all packets over sl0 by default (sl0 is the route to
# the Internet)
#
# Time To Live is the maximum number of hops a packet can take
# before it is thrown away.  This command prevents an inadvertent
# infinite loop from occuring with packets in the network.
#
ip ttl 400
#
#-------------------------------------------------
#
# The Maximum Segment Size is the largest single transmission that
# you care to receive.  An mss of 216 will force folks to send you
# packets of 256 characters or less (counting the overhead).
#
tcp mss 1048
#
#-------------------------------------------------
#
# The Window parameter establishes the maximum number of bytes that
# may be outstanding before your system expects an ack.  If window is
# twice as big as mss, for example, there will be two active packets
# on the channel at any given time.  Large values of window provide
# improved throughput on full-duplex links, but are a problem on the
# air.  Keep mss <= window <= 2*mss if you're on the air.
#
#
tcp window 6888
#
#-------------------------------------------------
#
# This entry will open net.log in the \spool directory and will
# record the server activity of your system.  If you don't want a log,
# comment out this line; if you do, make sure you have a \spool
# directory!
#
log \spool\net.log
#
#-------------------------------------------------
#
# Each of the servers (services you will provide) must be turned
# on before they will be active.  The following entries turn all
# of them on.  To turn any function off use the command 'stop' after
# NET gets fired up, or just comment out the line here.
#
start ftp
start echo
start discard
#start telnet
start smtp
#
isat on
#
domain addserver 192.100.81.101
domain addserver 192.100.81.105
smtp gateway 140.174.7.1
#
#
#  Display Name and IP Address
#
hostname
ip address
#
# Just for yucks, lets try calling the other end.
comm sl0 atdt14082411528
# THE END

After executing this setup file, you should hear the modem dial out
to your SLIP host. Enter TIP sl0 at the prompt to be connected to the
SLIP interface. You will then see your hosts's login prompt. Give
the login name and password, and when you go into SLIP mode, hit
F10 to get back to the prompt. Note that newer versions of KA9Q
may not be compatible with the comm command, since they support
more sophisticated dialing scripts.

Type RESET 1 at the prompt. This moves session 1 from tip mode into
SLIP mode. Type another RESET to kill any residual processes that
may be operating.

At this point you should have a functioning connection. You might
try to ping your host via the command:
PING <host adddress>

If this works, you will then see the round trip time to your host,
in milliseconds.

Other possible diagnostic commands:
ASYSTAT <interface>    Gives statistics on packets received, sent, etc.
TRACE <interface> 1011    Shows incoming characters
RIP TRACE 1        Traces RIP packets
HOPCHK <address>    Traces the route to the designated system. Useful
            for figuring out routing problems.

Routing
The KA9Q configuration that follows uses two interfaces, one a CSLIP
interface to an annex terminal server (sl0), the other an Ethernet
interface (lan) with another machine (a NeXT) attached.
Note the use of Van Jacobson compression (v) on the slip line, as well
as the strange interrupt settings (Interrupt 5, port is COM3).  One of
the nice things about KA9Q is that it is flexible enough to deal with
such situations.

Here is a sample router configuration file:

# Set the host name
#
hostname gate.slip.holonet.net
#
#
# Configure COM3 on Interrupt 5, at 38400 bps with
# RTS/CTS (c) and Van Jacobson Compression (v)
#
attach asy 0x3e8 5 VJSLIP sl0 8092 576 38400 cv
ifconfig sl0 ipaddress [157.151.0.253] netmask 255.255.255.0
#
# FTP, Inc., compatible packet driver installed at software interrupt number
# 0x60; probably an Ethernet card of some kind.
#
attach packet 0x60 lan 2 1500
ifconfig lan ipaddress [157.151.64.1] netmask 255.255.255.0
#
route add default sl0
# The local Ethernet has a Class C network address so
# route all IP addresses beginning with 157.151.64 to it.
route add 157.151.64/24 lan
#
#
# Time To Live is the maximum number of hops a packet can take
# before it is thrown away.  This command prevents an inadvertent
# infinite loop from occuring with packets in the network.
#
ip ttl 400
#
#-------------------------------------------------
#
# The Maximum Segment Size is the largest single transmission that
# you care to receive.  An mss of 216 will force folks to send you
# packets of 256 characters or less (counting the overhead).
#
tcp mss 576
#
#-------------------------------------------------
#
# The Window parameter establishes the maximum number of bytes
# that may be outstanding before your system expects an ack.
# If window is twice as big as mss, for example, there will be two
# active packets on the channel at any given time.  Large values of
# window provide improved throughput on full-duplex links, but are a
# problem on the air.  Keep  mss <= window <= 2*mss if you're on the air.
#
#
tcp window 6888
#
#-------------------------------------------------
#
# This entry will open net.log in the \spool directory and will
# record the server activity of your system.  If you don't want a log,
# comment out this line; if you do, make sure you have a \spool
# directory!
#
log \spool\net.log
#
#-------------------------------------------------
#
# Each of the servers (services you will provide) must be turned
# on before they will be active.  The following entries turn all
# of them on.  To turn any function off use the command 'stop' after
# NET gets fired up, or just comment out the line here.
#
start ftp
start echo
start discard
#start telnet
start smtp
#
isat on
#
domain addserver 157.151.0.2
domain addserver 157.151.0.1
smtp gateway 157.151.0.2
#
#
# Use Router Information Protocol (RIP) to inform the router at
# 157.151.0.253 about the existence of the local network. Send
# RIP packets every 240 seconds.
rip add 157.151.0.253 240
#
#
# Just for yucks, lets try calling the other end...
#
comm sl0 atdt7041063
#
# THE END

Here is another routing configuration file, using proxy arp:

# Set the host name
#
hostname gate.slip.holonet.net
#
#
# Configure COM3 on Interrupt 5, at 38400 bps with
# RTS/CTS (c) and Van Jacobson Compression (v)
#
attach asy 0x3e8 5 VJSLIP sl0 8092 576 38400 cv
ifconfig sl0 ipaddress [157.151.0.253] netmask 255.255.255.0
#
# FTP, Inc., compatible packet driver installed at software interrupt number
# 0x60; probably an Ethernet card of some kind.
#
attach packet 0x60 lan 2 1500
ifconfig lan ipaddress [157.151.64.1] netmask 255.255.255.0
#
#  Set Routing Tables
#
#
route add default sl0
# The local Ethernet has a Class C network address so
# route all IP addresses beginning with 157.151.64 to it.
route add 157.151.64/24 lan
#
#  Use Proxy ARP
#
arp publish 157.151.64.1 ether 00:00:c0:33:f3:13
arp publish 157.151.64.254 ether 00:00:c0:33:f3:13
#
#  For PC AT
#
isat on
#
# Add Domain Name Servers
#
domain addserver 157.151.0.2
domain addserver 157.151.0.1
smtp gateway 157.151.0.2
#
#
# Time To Live is the maximum number of hops a packet can take
# before it is thrown away.  This command prevents an inadvertent
# infinite loop from occuring with packets in the network.
#
ip ttl 400
#
#-------------------------------------------------
#
# The Maximum Segment Size is the largest single transmission that
# you care to receive.  An mss of 216 will force folks to send you
# packets of 256 characters or less (counting the overhead).
#
tcp mss 576
#
#-------------------------------------------------
#
# The Window parameter establishes the maximum number of bytes
# that may be outstanding before your system expects an ack.
# If window is twice as big as mss, for example, there will be two
# active packets on the channel at any given time.  Large values of
# window provide improved throughput on full-duplex links, but are a
# problem on the air.  Keep  mss <= window <= 2*mss if you're on the air.
#
#
tcp window 6888
#
#-------------------------------------------------
#
# This entry will open net.log in the \spool directory and will
# record the server activity of your system.  If you don't want a log,
# comment out this line; if you do, make sure you have a \spool
# directory!
#
log \spool\net.log
#
#-------------------------------------------------
#
# Each of the servers (services you will provide) must be turned
# on before they will be active.  The following entries turn all
# of them on.  To turn any function off use the command 'stop' after
# NET gets fired up, or just comment out the line here.
#
start ftp
start echo
start discard
#start telnet
start smtp
#
#  Display Name and IP Address
#
hostname
ip address
#
# Just for yucks, lets try calling the other end.
comm sl0 atdt7041063
# THE END

B-6  How do I get KA9Q to support BOOTP?

Steven L. Johnson ([e-mail]) notes:

  KA9Q does have a bootp client but it is not compiled in by default.
  It has a bug that truncates the returned ip address to 16 bits
  which must be corrected before it will work.  It also complains
  about bootp servers that only support RFC 951 bootp without RFC
  1084 (or 1048) vendor extensions.  Other than that it seems to work
  for me.

  To enable the bootp client, add the following line to config.h:

    #define BOOTP 1
  To correct the ip address truncation problem, in bootp.c change:
                Ip_addr = (int) reply.yiaddr.s_addr;    /* yiaddr */
                          ^^^^^problem
  at line 188 to:
                Ip_addr = (int32) reply.yiaddr.s_addr;    /* yiaddr */
                          ^^^^^^^solution
  And of course, recompile.
  This worked on the src1229 (1991) version and may work on the
  most recent version.  I did check to make sure that the bug still
  exists, but I haven't rechecked whether there are additional
  problems in the new version.

B-7  How do I get DesQView X to run over the network?

V1.0 of DesQView X did not include a TCP/IP protocol stack.
Surprise! The FTP software stack or Novell stack was needed to
make it work.  They've corrected the situation in subsequent
revisions.  Contact QuarterDeck for assistance.
[pricing and availability, anyone?]

B-8. Why is NFS so slow compared with FTP?

NFS usually runs over RPC via UDP, rather than utilizing TCP. NFS only
acknowledges a write request when the disk completes; there
are no sliding windows as in TCP. This makes NFS fairly inefficient.
Frances K. Selkirk ([e-mail] ) notes:

"There are NFS implementations that use TCP. They are only
faster over WANs. UDP is faster over most normally functioning LANs.
The lockstep paradigm is inherent to NFS, but some implementations
provide the ability to violate it - a speed win when the net is
reliable, a loss when it is not.

Whatever the transport, NFS will have more overhead than TCP, because
it is trying to transparently imitate an OS, and has to do a lot of
shuffling and translating."

B-9  How do I get KA9Q to support PPP?

Here is a sample ppp configuration file:

# Set the host name
#
hostname aboba.slip.netcom.com
ip address [192.187.134.3]
#
#
#
# Configure COM3 on Interrupt 5, at 38400 bps with
# MTU = 1008
#
attach asy 0x3e8 5 ppp pp0 8092 1008 38400
dialer pp0 dialer.ppp
ifconfig pp0 netmask 255.255.255.252
ppp pp0 trace 2
ppp pp0 quick
ppp pp0 lcp open
ppp pp0 ipcp open
#
#
#
route add default pp0
# route all packets over pp0 by default (pp0 is the route to
# the Internet)
#
# Time To Live is the maximum number of hops a packet can take
# before it is thrown away.  This command prevents an inadvertent
# infinite loop from occuring with packets in the network.
#
ip ttl 400
#
#-------------------------------------------------
#
# The Maximum Segment Size is the largest single transmission that
# you care to receive.  An mss of 216 will force folks to send you
# packets of 256 characters or less (counting the overhead).
#
tcp mss 1048
#
#-------------------------------------------------
#
# The Window parameter establishes the maximum number of bytes that
# may be outstanding before your system expects an ack.  If window is
# twice as big as mss, for example, there will be two active packets
# on the channel at any given time.  Large values of window provide
# improved throughput on full-duplex links, but are a problem on the
# air.  Keep mss <= window <= 2*mss if you're on the air.
#
#
tcp window 6888
#
#-------------------------------------------------
#
# This entry will open net.log in the \spool directory and will
# record the server activity of your system.  If you don't want a log,
# comment out this line; if you do, make sure you have a \spool
# directory!
#
log \spool\net.log
#
#-------------------------------------------------
#
# Each of the servers (services you will provide) must be turned
# on before they will be active.  The following entries turn all
# of them on.  To turn any function off use the command 'stop' after
# NET gets fired up, or just comment out the line here.
#
start ftp
start echo
start discard
#start telnet
start smtp
#
isat on
#
domain addserver 192.100.81.101
domain addserver 192.100.81.105
smtp gateway 140.174.7.1
#
#
#  Display Name and IP Address
#
hostname
ip address
#
# THE END

In file dialer.ppp:

control down
wait 1000
control up
wait 1000
wait 2000
send "at\r"
wait 3000 "OK"
send "atdt8659004\r"
wait 60000 "login: "
send "<userID>\r"
wait 5000 "word:"
wait 1000
send "<password>\r"

B-10. How do I get KA9Q to support SLIP dialin?

If you are willing to settle for little or no security, there is not
much you have to change to allow a KA9Q system to receive calls, as
opposed to originating them. These should include:

1. Setting the system to autoanswer, via use of the ATS0=1 command to
the modem.

2. Setting up a trace on the router end, to figure out if it's working,
via the command:

TRACE <interface> 1011, where <interface> = sl0 for SLIP, or another
value such as LAN or ether0 for the Ethernet interface. It's probably
a good idea to put a trace on all interfaces until the system is
shaken down.

Note that without addition of a special dialing script, this setup
is completely insecure!

B-11. Where can I get information on running Novell and TCP/IP
      concurrently?

The bit.listserv.novell group (NOVELL@SUVM) regularly posts a FAQ
which includes information on concurrent use of TCP/IP and Novell
IPX.

B-12. What Novell TCP/IP NLMs are out there and how do I get them to
work?

There are publicly distributable FTP daemon and BOOTP NLMs for
NetWare v3.11. Some have noted that these NLMs tend to crash the
server after a few hours. [Anyone with better success?] See
the Resource Listings for info.

B-13. How do I get a telecommunications package supporting Int 14h
to work?

Int 14h support is becoming increasing common, with vendors such as
Mustang (QMODEM Pro) having included this feature.
Aside from commercial stacks (such as FTP's PC/TCP),
try the TCPPORT program in WATTCP, available via ftp
dorm.rutgers.edu, get /pub/msdos/wattcp/apps.zip.

B-14. How do I get SLIP working with NDIS products such as
Windows For Workgroup TCP/IP?

Rumour has it that there is a serial NDIS driver available called
NBR11. This is available via ftp complab.gtri.gatech.edu,
cd /pub/lanman/ndis.

B-15. How do I get Windows For Workgroups to work alongside Novell?

ODINSUP from Novell is an NDIS over ODI shim. This allows you to run
software requiring ODI drivers, as well as software requiring NDIS
drivers. Since IPX and TCP/IP are different protocols, you will not
need to run PKTMUX.
Available via ftp.novell.com,
cd /netwire/novfiles/client.kit/doswin/files/WSDOS1.EXE.

B-16. NCSA Telnet doesn't reassemble fragments. What should I do?

Yell at the folks at NCSA to fix the problem, and to notify all
the people who are using the same TCP/IP code to insert the fix in
their software as well. This problem is really common, and
very annoying, and affects NCSA Telnet as well as PC Gopher III,
and POPmail. One possible workaround is to set the MTU to 576,
but this will not always work.

Since Matthew Kaufman ([e-mail]) has
provided the following explanation and fix, as detailed
below, there is really no good reason for this bug not
to be squashed soon:

How to get rid of the message:
"IP: fragmented packet received, frags not supported"
(assuming you have a C compiler and source code)

Many people on the net have complained that NCSA Telnet
(among other useful PC TCP/IP programs) doesn't properly handle
fragmented IP packets. this problem becomes especially evident if
any of your packets are arriving over SLIP connections.
I figured that the fastest way to get it to work would be to go
ahead and do it myself rather than wait for it to get to the
top of the list of desired features.

MANY other programs have used the NCSA TCP/IP implementation, so
if you maintain a program which does, PLEASE add this fix.
I (and MANY OTHERS) are unable to use your software until you do.
I posted the basic form of this fix around the beginning of the year,
but it didn't seem to make it into several subsequent versions of
related software, so I am posting and mailing this once again, in
a revised form, with helpful hints at the end.

I request only the following in return:
    This software revision is in the public domain. It may be
    used anywhere without further permission from the author.
    Please credit the origin of the fix in your release notes
    or bug fix document. (I am "Matthew Kaufman, [e-mail]")
    If you are the official maintainer of a software package
    which you have added this fix to, please send me an
    email note letting me know that the fix made it in.
    (So I don't need to worry that, for instance, the next
    version of NCSA Telnet or WinQVT/Net isn't going to
    include this) And, please add this fix as soon as possible.

So here's my fix:
The following are the changes to the NCSA Telnet TCP/IP engine to add
support for IP fragment reassembly. I also know how to make telnet compile
properly under Borland C without running out of space in DGROUP (see the end of this)
if you have any questions, you can reach me at:

[e-mail].

I am willing to help, within the limits of my schedule.
changes follow:

file: engine\ip.c (the only file that needs to change)
delete the following:
>/*
>*  We cannot handle fragmented IP packets yet, return an error
>*/
>
>    if(p->i.frags &0x20) {           /* check for a fragmented packet */
>        netposterr(304);
>        return(1);
>      }
----------
after the line:
>    iplen-=hlen;
but before the lines:
> /*
> *  check to make sure that the packet is for me.

add this:
    /* check for fragment and handle. note that the &0x20 above is WRONG */
    if(p->i.frags)           /* NOW check for a fragmented packet - mtk add*/
    {
    ipfraghandle(p,iplen);    /* pass in computed iplen to save time */
        return(1);
      }
----------
and then, at the end of that file (ip.c) add this:
/*
* IP Fragment Reassembly Hack
* by Matthew T Kaufman ([e-mail])
* 1/1993, 8/1993
*/
typedef struct ipb {
        DLAYER d;
        IPLAYER i;
        uint8 data[4104];    /* "Big Enough" */
}FIPKT;
#define IPF_CHUNKS 513 /* 4104 / 8 */
#define IPF_BITWORDS 18  /* 513 / 32 round up + 1*/
#define IPF_BUFFERS 7  /* Max # of different fragmented pkts in transit */
typedef struct {
    FIPKT pkt;
    unsigned long bits[IPF_BITWORDS];
    int lastchunk;
    unsigned long lasttime;
    unsigned int iplen;
}FPBUF;
static FPBUF far Frag[IPF_BUFFERS];
ipfraghandle(IPKT *p, int iplen)
{
    uint16 fraginfo;
    uint16 foffset;
    uint16 iden;
    FPBUF far *buf;
    int i;
    fraginfo = intswap(p->i.frags);
    foffset = fraginfo & (0x1fff);
#define morefrags (fraginfo & (0x2000))
    iden = intswap(p->i.ident);
/* we already KNOW that this IS fragmented */
/* see if we can find any friends who've already arrived... */
    buf = (FPBUF *) 0L;
    for(i=0; i<IPF_BUFFERS; i++)
    {
        if(p->i.ident == Frag[i].pkt.i.ident)
        {
            buf = &(Frag[i]);
            goto foundfriend;
        }
    }
    /* otherwise, we must be the first one here */
    {
        long oldtime = 0x7fffffff;
        int oldest = 0;
        for(i=0; i<IPF_BUFFERS; i++)
        {
            if(Frag[i].lasttime == 0)    /* unused buffer? */
            {
                buf = &(Frag[i]);
                goto foundempty;
            }
            if(Frag[i].lasttime < oldtime)    /* track LRU */
            {
                oldtime = Frag[i].lasttime;
                oldest = i;
            }
        }
        /* if we're here, we need to reuse LRU */
        buf = &(Frag[oldest]);
foundempty:    ;
        /* initialize new buffer */
        /* time will be filled in later */
        for(i=0; i<IPF_BITWORDS; i++) buf->bits[i] = 0L; /* reset */
        buf->lastchunk = 0;    /* reset */
        /* fill in the header with the current header */
        movmem(p,&(buf->pkt), sizeof(DLAYER) + sizeof(IPLAYER) );
    }

foundfriend: ;
    /* now, deal with this specific fragment... */
    /* copy data */
    movmem(&(p->x.data),&(buf->pkt.data[8 * foffset]),iplen);
    /* update rx chunks information */
    for(i=foffset; i<= (foffset+(iplen / 8)); i++)
    {
        buf->bits[i/32] |= (unsigned long) (1L<<(i % 32));
    }
    if(!morefrags)
    {
        /* now we can tell how long the total thing is */
        buf->iplen = (8*foffset)+iplen;
        buf->lastchunk = foffset;
            /* actually, lastchunk is more than this, but it */
            /* IS true that we only need to check through    */
            /* this foffset value to make sure everything has */
            /* arrived  -mtk */
    }
    /* now touch the time field, for buffer LRU */
    buf->lasttime = clock();
    /* check to see if there are fragments missing */
    if(buf->lastchunk == 0)
    {
        /* we haven't even gotten a fragment with a cleared MORE */
        /* FRAGMENTS flag, so we're missing THAT piece, at least */
        return 1;
    }
    for(i=0; i<= buf->lastchunk; i++)
    {
        /* scanning to see if we have everything */
        if(0 == ((buf->bits[i/32]) & (unsigned long)(1L<<(i % 32))) )
        {
            return 1;    /* still waiting for more */
        }
    }
    /*  otherwise, done waiting... use the packet we've gathered */
    /* first clear stuff from fragment buffer: */
    buf->lasttime = 0L;    /* mark as free to take */
    buf->lastchunk = 0;    /* need to do this, because we use it as flag */
    buf->pkt.i.ident = 0;    /* so we don't find this later */
    buf->pkt.i.frags = 0;    /* in case anybody above us checks */
    /* then send it on its way... */
    if(!comparen(nnipnum,p->i.ipdest,4)) {     /* potential non-match */
        if(comparen(nnipnum,junk,4) && p->i.protocol==PROTUDP)
            return(udpinterpret((UDPKT *)p,iplen));
        return(1);              /* drop packet */
      } /* end if */
       switch (buf->pkt.i.protocol) {        /* which protocol */
            case PROTUDP:
                return(udpinterpret((UDPKT *)&(buf->pkt),buf->iplen));

            case PROTTCP:
                return(tcpinterpret((TCPKT *)&(buf->pkt),buf->iplen));

            case PROTICMP:
            return(icmpinterpret((ICMPKT *)&(buf->pkt),buf->iplen));

           default:
               netposterr(303);
               return(1);
      }

}

*** helpful hint:

if you run out of space in DGROUP, its because your compiler doesn't
place each 'far' data object in its own segment. To make things work,
you need to make the raw packet buffer be in its own segment.

Here's how:
in include/pcdefs.h search for:
-->  unsigned char far raw[17000];
 (the 17000 might be some other number... smaller, if someone tried to
  fix this before)
 and change to
-->  unsigned char far raw[17000]={0,0};    /* force into own segment */

C. Information for developers

C-1. What publicly distributable TCP/IP stacks are there that I can
     use to develop my own applications?

In writing an application, you can use device drivers provided by
particular vendors, or you can opt for an Application Binary Interface (ABI)
that supports multiple TCP/IP protocol stacks, such as Winsock. For a given
version of Windows, Winsock is an ABI for both Windows 3.x and Windows NT
(via the NT Win16 subsystem).

Device drivers are included with PC-NFS and Beame & Whiteside's
BW-TCP.  Free examples of ABIs are the WATTCP API, the NCSA API
(public domain), the Trumpet ABI from Peter Tattum, and the NuPOP ABI.
As Mark Towfiq notes, all major TCP/IP vendors will be implementing
Windows Sockets:

Company                         BETA    FINAL
---------------------------------------------
3Com Corp                       Q1 '93  Q2 '93
Beame & Whiteside               ?       ?
Distinct Corp                   Q3 '92  Shipping
FTP Software                    Q4 '92  Shipping
Frontier Technologies           Q3 '92  Shipping
IBM                             Q4 '92  Q1 '93
JSB Corporation                 Q4 '92  Q4 '92
Lan Design                      Q4 '92  Q1 '93
Microdyne                       Q4 '92  Q1 '93
Microsoft (Windows NT 32-bit)   Q3 '92  Q2 '93
Microsoft (Windows NT 16-bit)   Q4 '92  Q2 '93
Microsoft (Windows 3.x 16-bit)  Q4 '92  Q2 '93
NetManage                       Q4 '92  Q4 '92
Network Research                ?       ?
Novell                          ?       ?
Sun Microsystems                Q4 '92  First Half '93
Ungermann Bass                  ?       ?
Walker Richer Quinn             Q4 '92  Q1 '93
Wollongong                      Q4 '92  Q1 '93

Source: Martin Hall ([e-mail]), available via ftp sunsite.unc.edu,
get/pub/micro/pc-stuff/ms-windows/winsock/vendors.

C-2. Where can I get a copy of the Windows Sockets FAQ?

A separate developer-oriented FAQ file about Windows Sockets created
by Mark Towfiq is available on
SunSite.UNC.EDU:/pub/micro/pc-stuff/ms-windows/winsock/FAQ
and Microdyne.COM:/pub/winsock/FAQ
An alternative source for the FAQ is rhino.microsoft.com.

RESOURCE LISTING

Key

Downright speculation = I have not used this product personally, nor
has anyone I know.  However, the specifications sounded interesting,
so it's included.

Suggestion = I have not used this enough to pass judgement, but it
has come to me recommended by someone I respect.

Recommendation = I use this package regularly, and like it.

BOOKS

Downright speculation
NOSintro

An Introduction to the KA9Q Network Operating System
Price: 11.50 Pounds sterling, plus postage and handling.
U.S. price, including shipping:  17.34 pounds sterling
This book by Ian Wade (author of NOSView) thoroughly covers
KA9Q. Publisher is Dowermain, 356 pages, 35 chapters, 6 appendices,
illustrated. ISBN 1-897649-00-2.
Dowermain, Ltd., 7 Daubeney Close, Harlington, DUNSTABLE, Bedfordshire,
LU5 6NF, United Kingdom, email  [e-mail]. Written orders only,
no U.S. distributor yet.

Recommendation
InfoPOP - Guide to Internet Resources    Free

InfoPOP/Windows is a smallish guide to the Internet in the form of a
Windows Help application. InfoPOP/DOS is a TSR with the same content.
Available via ftp gmuvax2.gmu.edu, or the fenwick.gmu.edu gopher
 Computers/Info-Technology/Software
  |___under Software available on this  Gopher

MAILING LISTS

Windows Sockets

[e-mail]
[e-mail]
W3 for Windows
mail [e-mail], with
         sub cello-l your full name
in the body of the message.

Firewalls

mail [e-mail], with
        sub firewalls-digest
in the body of the message. Back issues
are available at ftp.greatcircle.com:/pub/firewalls.digest/vNN.nMMM.Z
where NN is the volume number and MMM is the issue number.

Publicly Distributable Software

Key

Recommendation = I use, or have used this software, and I like it.
Suggestion = I have not used this software, but it has been recommended to
me by people that I trust.
Downright Speculation = Neither myself noranyone I know has used this,
but it claims to offer interesting capabilities, so it╒s included.

Drivers

Recommendation
Crynwr drivers       free
Support    Contact Crynwr for info

The Crynwr drivers, formerly known
as the Clarkson University CUTCP drivers, support many Ethernet adapter
boards. Ethernet adapter boards from 3COM, Telesystems, AT&T, Digital,
Mitel, HP, BICC, NCR, Novell, Interlan, MICOM, Racal/Interlan, NTI, Tiara,
Ungermann-Bass, and Western Digital are supported. The Packet Driver
Specification v1.09 is available via:
file://vax.ftp.com/pub/packet-d.ascii, packet-d.mss [check this] Drivers
available at: file://ftp.sun.soe.clarkson.edu/pub/packet-drivers/drivers.zip,drivers1.zip,
drivers2.zip  PC-NFS drivers available in
file://ftp.sun.soe.clarkson.edu/pub/packet-drivers/compat.zip (requires
Sun's PC-NFS).

The drivers are also available at file://wsmr-simtel20.army.mil/
pd1:<msdos.pktdrvr>/drivers.zip, drivers1.zip, drivers2.zip Other mirrored
archives include oak.oakland.edu, wuarchive.wustl.edu, ftp.uu.net,
nic.funet.fi, src.doc.ic.ac.uk, nic.switch.ch, archie.au, nctuccca.edu.tw.

Crynwr Software, 11 Grant St., Potsdam, NY 13676, [phone], fax:
[phone], email: [e-mail]

Recommendation
NDIS Drivers    free

Libraries of free NDIS drivers for DOS and OS/2 are available at FTP
Software, Inc. at file://vax.ftp.com/ndis. Another source of NDIS drivers
is the Windows for Workgroups package.  New drivers are available for
download from Microsoft Product Support Services, available at
(206)936-MSDL, or on CompuServe or GEnie. The Windows Driver LIbrary (WDL),
which includes printer, display and network drivers is also available on
disk from Microsoft by calling [phone].

The NDIS spec is available as: file://vax.ftp.com/pub/ndis-mac.v101.txt,
ndis-mac.v201.txt

Downright Speculation
Slipper v1.3    Free

An improved version of the SLIP8250 driver included with SLIPDISK. It╒s
faster, allowing SLIP operation at up to 38.4 Kbps on a 486. Supports
PKTMUX.

Available from file://ftp.utas.edu.au/pc/trumpet/slipper/slipper.zip
file://biochemistry.cwru.edu/pub/slipper/slippr13.zip

P. Tattam, Programmer; Psychology Department, University of Tasmania,
Hobart, Tasmania, Australia, 61-02-202346; email:
[e-mail]

Downright Speculation
CSLIPPER    Free

A SLIP driver which supports Van Jacobson header compression. Supports
PKTMUX when used in ethernet simulation mode. Available at
file://biochemistry.cwru.edu/pub/slipper/cslipper.exe

Recommendation
ETHERPPP    Free

Glenn McGregor, formerly of Merit Network, has released a new ETHERPPP
packet driver that appears as a class 1 packet driver. It works well
enough, and is simple to configure, but takes up too much RAM (121K).
Available as: file://merit.edu/pub/ppp/etherppp.zip

Downright Speculation
BOOTPQ v1.2    Free

BOOTPQ can take configuration parameters extracted via BOOTP and insert
them into a file or environmental variables.

Available as file://biochemistry.cwru.edu/pub/dos/bootpq12.zip

A bootp client is available at
file://biochemistry.cwru.edu/pub/dos/bootp.zip

Recommendation
PKTMUX v1.2    Free

This program allows multiple TCP/IP protocol stacks to use a single packet
driver. It can also run over shims such as DIS_PKT; I have used it with
four or more simultaneous DOS-based applications. Works great. However, if
you are only using a single DOS TCP/IP application under Windows, use
WINPKT instead, since it takes less memory and is faster.

Available via file://ftp sunee.uwaterloo.ca/pub/wattcp/pktmux12.exe, or
file://biochemistry.cwru.edu/pub/dos/pktmux12.exe, pktmux12.txt

Recommendation
Packet driver over NDIS shim    free

Provides a packet driver over an NDIS driver. This is useful when you need
to run both packet driver software (such as KA9Q or NCSA Telnet) and
NDIS-based software (such as Chameleon NFS).

Available at
file://vax.ftp.com/pub/packet.driver/pubdom/ndis/dis_pkt.asm,dis_pkt.dos,
protman.sys, readme, also:
file://biochemistry.bioc.cwru.edu/pub/qvtnet/dis_pkt9.zip

Also as file://netlab.usu.edu/novell/dis_pkt.zip
file://hsdndev.harvard.edu,/pub/dis_pkt/dis_pktx.asm (experimental)
file://hsdndev.harvard.edu/pub/dis_pkt/dis_pktx.dos (experimental)

Downright Speculation
PDEther v1.03

Supports ODI over packet drivers. I╒ve tried to use this to get packet
driver software to coexist with Novell, but had better results with ODIPKT.

Available as: file://sjf-lwp.novell.com/odi/pdether/getpde103.zip

Recommendation
Odipkt v2.4

Supports packet drivers over ODI. This is the recommended method of getting
Novell to coexist with a packet-driver based TCP/IP stack. Compatible with
WINPKT.

Available as file://hsdndev.harvard.edu/pub/odipkt/odipkt.com,  net.cfg,
odipkt.8, odipkt.asm. Also: Available as
file://biochemistry.cwru.edu/pub/qvtnet/odipkt21.zip

Downright speculation
ODITRPKT v2.0

Supports packet drivers over ODI and token ring.

Available as file://datacomm.ucc.okstate.edu/pub/oditrpkt/BETA9.ZIP

Downright speculation
BYU Netware shell drivers    free

Allows you to build an IPX.COM that runs over packet drivers.  Works by
providing .obj and .lan files for the Neware shell generation program,
shgen.exe. Running shgen.exe produces netX.com as well as an ipx.com for
your interface card. Again, I╒ve had better results with ODIPKT than with
this.

Available at: file://vax.ftp.com/pub/packet.driver/pubdom/byu

Downright speculation
Intel PDIPX    free

Another way of building an IPX.COM that runs over packet drivers.

Available at: file://ftp
sun.soe.clarkson.edu/pub/packet-drivers/intel.pdipx.zip

Recommendation
WINPKT    free

WINPKT is needed for running DOS applications with built-in TCP/IP stacks
under Windows, as well as for some Windows-based TCP/IP stacks (suck as
Trumpet Winsock). Compatible with ODIPKT.

Available at file://biochemistry.micro.umn.edu/pub/slip/dos/winpkt.com

Downright speculation
PKTINT

PKTINT is included with the non-Winsock-compatible version of WinQVT/net,
and is needed to allow WinQVT/Net to communicate with the  real mode TCP/IP
stack.

Available at file://biochemistry.micro.umn.edu/pub/slip/dos/winpkt.com
TCP/IP Stacks for DOS Suggestion WATTCP    free

Development package for TCP/IP.  Available via:
file://dorm.rutgers.edu/pub/msdos/wattcp/winwattcp.zip, readme.1st,
wattcp.zip,

Erick Engelke, WATTCP Architect; email [e-mail]

Suggestion
Trumpet TCP/IP stack

This TCP/IP stack comes in three versions: a TSR version; a Windows Sockets
version (discussed below); and a built-in version. It includes a traceroute
program called hopchk2.

Available as file://ftp.utas.edu.au/pc/trumpet/abi-version/ Available at
file://biochemistry.cwru.edu/pub/trumpet/tcp201.zip

P. Tattam, Programmer; Psychology Department, University of Tasmania,
Hobart, Tasmania, Australia, 61-02-202346; email:
[e-mail]

Downright Speculation
PC-IP    Free

This was the software that started it all. It has been worked on at MIT,
Carnegie Mellon, and Harvard and other places, but by now is out of date.

Harvard version: Source code: file://ftp
hsdndev.harvard.edu,/pub/pcip/pcip.tar.Z, doc.tar.Z, readme, readme.cmu
Binaries: file://hsdndev.harvard.edu/pub/pcip/bin/packet/*.exe
file://hsdndev.harvard.edu/pub/pcip/bin/general/*.exe

Another version: file://netlab.usu.edu/netwatch/pcip96.zip

Windows Sockets

Recommendation
Trumpet WinSock

A shareware version of Windows Sockets that runs over packet
drivers and requires WINPKT. Available as:
file://ftp.utas.edu.au/pc/trumpet/winsock/winsock.zip, or
file://biochemistry.cwru.edu/pub/trumpwsk/winsock.zip,
install.txt, disclaim.txt.

P. Tattam, Programmer; Psychology Department, University of Tasmania,
Hobart, Tasmania, Australia, 61-02-202346; email:
[e-mail]

Downright Speculation
WinTCP

A shareware version of Windows Sockets, running over NDIS, and
implemented as a VxD driver. Available at:
file://biochemistry.cwru.edu/pub/wintcp/vxdtcpa2.zip, wintcpa1.zip Routers,
Bridges,  and Diagnostic Software Downright Speculation CIRCA RARP server

RARP lets machines determine their TCP/IP address by querying a machine on
the local Ethernet.

Available at file://pine.circa.ufl.edu/pc/rarp.dir/rarp.zip

Suggestion
BOOTP server    free

This is a BOOTP server for the PC that runs as a TSR, and is only 900 bytes
long.

Available via file://sunee.uwaterloo.ca/pub/wattcp/bootp.zip, readme.1st

Downright Speculation
Traceroute    free

Two versions of traceroute for DOS are available.

file://biochemistry.cwru.edu/pub/trumpet/tcp201.zip, and
file://ftp-ns.rutgers.edu/pub/wattcp

There are also versions of ping and traceroute by Peter Tattam that work
with Trumpet Winsock.

Downright Speculation
SNMP monitor    Free

Available at file://sun.soe.clarkson.edu/pub/packet-drivers/snmpsrc.zip.
Also available at file://enh.nist.gov/misc/snmpsrc.zip, snmpsup.zip,
snmpsun.tar_Z.

Suggestion
SMTP client v1.1

A Windows Sockets-compatible SMTP client that is limited to ╥send only.╙
Not as functional as PCEudora (which also handles POP3). Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/smtp11.zip

Contact: [e-mail]

Recommendation
SMTP daemon    free

A Windows-Sockets SMTP daemon, complete with source code. Works fine.
Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/wsmtpd15.zip.

contact: [e-mail]

Suggestion
Fergie    Free

Fergie is a packet monitoring and grabbing tool that supports SNMP and
supersedes The Beholder and Gobbler. Spectre is a network host profiler.
Tricklet is a set of SNMP utilities.

Fergie is available at file://dnpap.et.tudelft.nl/pub/Fergie/frgbin2.zip.
The source code is available at
file://dnpap.et.tudelft.nl/pub/Fergie/frgsrc2.zip.

To get on the Fergie mailing list, send mail to:
[e-mail]

Suggestion
NetProbe    Free

An unsupported utility from 3Com that can decode XNS,TCP/IP, ICMP,
AppleTalk, IPX/SPX, SMB, and other protocols, but only supports the
Etherlink, Etherlink II, EtherLink Plus and Token Plus adapters.

Available on CompuServe in the 3Com forum as EPROBE.ZIP in lib 5,
unsupported utilities.

Downright Speculation
Netwatch    Free

Essential network debugging tools for the PC.  Available at
file://netlab.usu.edu/netwatch.dir/netwatch.exe.

Recommendation
KA9Q
Educational Use    Free
Commercial Use    $50

KA9Q can route TCP/IP packets over X.25, Ethernet, LocalTalk (with a
special version), and serial lines (via SLIP/CSLIP/PPP) as well as handling
telnet, mail, and ftp (client and server). It supports connection to 56
Kbps leased lines via a CSU/DSU and an SCC card, and supports up to 4
serial ports per machine. This means you can purchase a 56 Kbps Internet
link, then divide it among 4 users, bringing the cost way down. KA9Q is a
useful tool for sysops looking to hook their systems to the Internet,
regardless of what kind of computer the BBS runs on.

PC version available at: file://ucsd.edu/hamradio/packet/tcpip/ka9q. The
LocalTalk version is available from [help, anyone?]

A Macintosh port (NetMac) is available at
file://sumex-aim.stanford.edu/info-mac/comm/

Textwin (multiwindowing version with mouse support) available at
file://ftp.demon.co.uk/pub/ibmpc/textwin.

Contact: [e-mail], [e-mail],
[e-mail]

Phil Karn, KA9Q; 7431 Teasdale Ave, San Diego, CA 92122; [phone],
fax: [phone]

Downright Speculation
NOSView v3.04

Written by Ian Wade, G3NRW, NOSView is online documentation for KA9Q, which
describes all the NOS commands. It also contains a complete set of
templates for use of KA9Q.

Available at file://ucsd.edu/hamradio/packet/tcpip/nosview/nosvw304.zip

Contact: Ian Wade, [e-mail]

Suggestion
PCRoute v2.24    Free

This package can convert a PC into a TCP/IP router. It works fine on a 386,
and doesn╒t require more than 1 Mb of memory.

Available at file://ftp.acns.nwu.edu/pub/pcroute/pcroute2.24.*

Vance Morrison, LANport, Inc.; 2040 Polk Street #340, San Francisco, CA
94109; [phone], email: [e-mail].

Suggestion
PCBridge v2.77    Free

Originally by Vance Morrison of Northwester, PCBridge has been taken over
by  Alessandro Fanelli and Luigi Rizzo. The latest version of PCBridge is
now ROMable. The  software is available at
file://pical3.iet.unipi.it/pub/bridge/bdg277.tar.Z

Alessandro Fanelli, Luigi Rizzo ([e-mail]), Universita` di Pisa -
via Diotisalvi 2, 56126 Pisa, Italy ; [phone], fax:  [phone]

Downright Speculation
Drawbridge v1.1

Drawbridge is a bridging filter that requires two ethernet cards. It is
comprised of three programs: Filter, Filter Compiler and Filter Manager.

It is available at
file://sc.tamu.edu/pub/security/drawbridge/drawbridge-1.1.tar.Z,
drawbridge-1.1-des.tar.Z

Downright Speculation
KarlBridge v1.41

This software provides a two port Ethernet to Ethernet bridge that can
filter based on any Ethernet protocol, including IP, XNS, DECNET, LAT,
EtherTalk, NetBEUI, Novell IPX, etc. It will also act as an IP firewall by
filtering IP packets based on IP address/network/subnet combinations and
socket numbers. It can also filter DECNET and AppleTalk Phase 1 & 2
packets. Novell SAP and NCR WaveLAN filtering are coming in a future
release. Available at file://128.146.1.7/pub/kbridge

Downright Speculation
Ethload    Free

This is an Ethernet load monitor that will give you an idea when collisions
are getting out of hand and you need to install a bridge.

Available at file://cs.ubc.ca/mirror4/msdos/lan/ethld101.zip. Also
available at file://wsmr-simtel20.army.mil/<msdos.lan>/ethld101.zip.

DOS Applications

Downright Speculation
BOOTP and FTPD NLMs

Available via file://novell.felk.cvut.cs/pub/nw311/ftpd, /pub/nw311/bootpd,
/pub/nw311/resolv.

Downright Speculation
LPD    Free
FTP and BOOTP server  included

This software is a freeware line printer daemon as well as an FTP and BOOTP
server.  Available via file://tacky.cs.olemiss.edu/pub/lpd/lpd.zip,
lpdsrc.zip

Recommendation
TELNETD    Free

TELNETD is a simple, free and unsupported TELNET server for PCs. It works
on top of packet drivers and lets you run most DOS software. However, it
doesn╒t do everything; if you want a commercial-quality implementation, get
Everywhere Access.

Available at file://dorm.rutgers.edu/pub/msdos/wattcp/telnetd.zip

Downright Speculation
IRC client    free

A client for Internet Relay Chat.

Available at file://ftp.utas.edu.au/pc/trumpet/irc/irc100.zip Available at
file://biochemistry.cwru.edu/pub/trumpet/irc100.zip, ircabi.zip, irclwp.zip

P. Tattam, Programmer; Psychology Department, University of Tasmania,
Hobart, Tasmania, Australia, 61-02-202346; email:
[e-mail]

Recommendation
WAIS for DOS    free

A DOS WAIS client which uses the Clarkson drivers is available at
file://sunsite.unc.edu/pub/packages/infosystems/wais/DOS/pcdist.zip.

A DOS WAIS client that requires the PC/TCP software from FTP Software is
available at file://oac.hsc.uth.tmc.edu/public/dos/misc/oacwais.exe.

For information, contact: Steven E. Newton, Office of Academic Computing,
University of Texas Health Science Center, Houston, email:
[e-mail].

There is also a Novell LAN Workplace WAIS client available at
file://ftp.oit.unc.edu/pub/WAIS/UNC/nov-cli-visual.zip.

Downright Speculation
PDCLKSET    Free

Requiring a packet driver, this software sets your PC clock via an Internet
time server.It also offers several useful network testing functions.
Supports ping, and can build an arp table of nodes on the subnet. Available
at file://oak.oakland.edu/pub/msdos/pkdrvr/pdclk207.zip.

Suggestion
NCSA Telnet    Free

Available at file://zaphod.ncsa.uiuc.edu/PC/Telnet/tel2305b.zip,
tel2305s.zip.  Also available at
file://wsmr-simtel20.army.mil/PD1:<MSDOS.PKTDRVR>/tel2305b.zip

Compatible with LocalTalk.  A special version which supports PPP is
available at file://merit.edu/pub/ppp/ncsappp.zip, ncsappp.txt. A PPP FAQ
is available at file://merit.edu/pub/ppp/ppp.faq

Be aware that the current version does not reassemble fragments, even
though a fix is available for this (argghhh....)

Recommendation
Kermit     Free

This version of Kermit supports telnet, VT320 and Tektronix emulation, as
well as SIXEL. It incorporates the WATTCP stack, and also runn╒s over
Novell╒s LWP/DOS+Telapi, FTP Inc╒s PC/TCP+Tnglass, Beame & Whiteside╒s
TCP/IP stack; DEC Pathworks, as well as over NetBIOS. It supports Int 14h
as well as Int 6Bh, and can run over packet drivers.

Available at file://kermit.cc.columbia.edu/kermit/bin/msvibm.zip,
msvibm.pif (Windows PIF file for MS-DOS Kermit)

Downright speculation
PCUCP    Free

This is an X terminal application that runs over a serial port. It supports
multiple windows, and multiple sessions.It is available at
file://ftp.cica.indiana.edu/pub/pc/win3/modem/pcucp11a.zip.

Recommendation
CUTCP Telnet    Free

CUTCP is the premiere DOS telnet application. Aside from VT100, and
Tektronxi emulation, CUTCP also handles 3270 emulation. The latest release
has added ping and ODI support. Now supported by Rutgers University, having
been tranferred from Clarkson University and Brad Clements. This directory
contains the source and binary distributions, both in zip archives. For
information contact [e-mail].

Available at file://ftp-ns.rutgers.edu/pub/msdos/cutcp/current/cutcp-b.zip
(Documentation and binaries), cutcp-s.zip (Source, documentation, and
binaries).

Downright speculation
Clarkson Archie    Free

Available at file://omnigate.clarkson.edu/pub/cutcp/archie.zip

Suggestion
Princeton Telnet Free

The Princeton version of Telnet supports localtalk cards and also does
tn3270 access. Works on all localtalk cards (Sitka, Daystar, Farallon, ...
)

Available at file://pusun3.princeton.edu/pub/PU2-2TN/pu2-2tn.zip

Downright speculation
Clarkson Charon IPX/TCP email and printer gateway v4.0

Available at file://omnigate.clarkson.edu/pub/cutcp/charon40.zip,
file://sun.soe.clarkson.edu/pub/cutcp/charon.zip

Recommendation
SLIPDIAL package    Free

A dialer package which can be used to script the connection to SLIP
via a driver such as CSLIPPER or SLIPPER.

Available at file://biochemistry.cwru.edu/pub/slip/dos/slipdial.zip,

Recommendation
PC Gopher III    Free

An MS-DOS client for the Gopher information server. Be aware that you must
load WINPKT.COM (or PKTMUX if you are running multiple TCP/IP applications)
to get this program to work under Windows. The code for PC Gopher III has
also been incorporated into Minuet.

Available at
file://boombox.micro.umn.edu/pub/gopher/PC_client/docs/pcgopher.txt
file://boombox.micro.umn.edu/pub/gopher/PC_client/00README, also:
file://biochemistry.cwru.edu/pub/dos/pcg3.zip, pcg3doc.zip

WINPKT available at
file://biochemistry.micro.umn.edu/pub/slip/dos/winpkt.com

Downright Speculation
KA9Q Gopher Server

Available at: file://boombox.micro.umn.edu/pub/gopher/PC_server/ka9q

Downright Speculation Hamburg Gopher Server

Available at: file://boombox.micro.umn.edu/pub/gopher/PC_server/hamburg

Recommendation DOS
Trumpet v1.06b     Shareware, $10.

Trumpet is an NNTP newsreader for DOS that can be placed on a Novell
server, while storing news groups and configuration files in each user's
directory. It supports packet drivers, LAN WorkPlace for DOS, and Trumpet
ABI.

Available at file://ftp.utas.edu.au/pc/trumpet/dostrump/trmp106b.zip
Available at file://biochemistry.cwru.edu/pub/trumpet/trmp106b.zip,
newsabi.zip, newslwp.zip

Contact: [e-mail]

Multi-user site licenses

Trumpet will be charged by the total number of users who have  access to
Trumpet on  a  network. A site is designated  as  being one organization
located within a radius of10 km.

The pricing structure is:

1-99 users    $10 US per user 100-999 users    $1000 US + $2 US per
additional user above 100 1000-4999 users    $2800 US + $0.20 US per
additional user over 1000 5000+    $3600 US

P. Tattam, Programmer; Psychology Department, University of Tasmania,
Hobart, Tasmania, Australia, 61-02-202346; email:
[e-mail]

Downright Speculation
Stan's Own Server    Free

Available at file://sun.soe.clarkson.edu/pub/packet-drivers/soss.zoo,
sossread.me.  Also available at file://spdcc.com/pub/sos/soss.zoo,
sossexe.zoo

A version with a couple of bugs fixed is available at
file://hilbert.wharton.upenn.edu/pub/tcpip

For info, contact: Richard Bruan, [e-mail], or Seemong Tan,
[e-mail].

Downright Speculation
Broadcast    Free

This is a PC client for the Macintosh Broadcast program, by Kai Getrost.

Available at file://caisr2.caisr.cwru.edu/pub/net/bdcst11.zip [check this]

Suggestion
NuPOP/PC v2.01 free

A menu driven version of POP for DOS.  Can be gotten to support LocalTalk
via the provided LocalTalk driver. Do not use the Clarkson drivers for
this. By the way, NuPOP also supports serial access, as well as Gopher.

Available at file://ftp.acns.nwu.edu/pub/nupop/nupop201/nupopdoc.zip,
nupoppro.zip, nupopps.zip, nupoprea.zip, nupopsch.zip, nupopsup.zip

Suggestion
POPmail-PC v3.2.2

Supports Ethernet, AppleTalk, and SLIP. Use the AppleTalk driver that works with NuPOP.

Available at
file://boombox.micro.umn.edu/pub/pc/popmail/popmail-3.2.2/program/popmail.exe,
popmail.hlp

file://boombox.micro.umn.edu/pub/pc/popmail/popmail-3.2.2/manuals/manual.asc,
popmail.doc, popmail.sty

A POP3 server for VMS and MS-DOS client software is available at
file://logos.ucs.indiana.edu/INDEX.

Recommendation
Minuet

A smorgasbord of DOS TCP/IP applications, including gopher, mail, ftp,
news, and telnet, Minuet includes code from PC Gopher III, and POPmail. It
supports multiple windows, as well as Ethernet, AppleTalk and SLIP packet
drivers. Use the AppleTalk driver that works with NuPOP.  Since Minuet does
so much, and does it well, you may not want to use anything else, unless
you don╒t have enough RAM for it.

Available at file://boombox.micro.umn.edu/pub/pc/minuet/minuarc.exe

Suggestion
PC-Pine v3.88    Free

This is a PC-compatible version of Pine, running under DOS. There are
versions written for FTP Software's PC/TCP, Novell's Lan WorkPlace for DOS,
and WATTCP.

Available at file://ftp.cac.washington.edu/mail/pcpine_p.zip (WATTCP
version), pcpine_n.zip (Novell LWP), pcpine_f.zip (FTP PC/TCP) . Note that
PC Pine relys on the Interactive Mail Access Protocol (IMAP2) rather than
POP. You must have an IMAP server installed in order to use it. IMAPd is
available at file://ftp.cac.washington.edu/mail/imap.tar.Z.

For a listing of other IMAP-compatible clients, get
file://ftp.cac.washington.edu/mail/imap.software.

Downright Speculation
Ph client

University of Illinois CCSO name server client.

Available at file://uxc.cso.uiuc.edu/net/ph/dos/pcph.com, pcph.README

Downright Speculation
FTPNuz    $10/shareware

Gene Mangum's shareware newsreader for DOS, which requires FTP Software's
PC/TCP kernel. Runs under MS-DOS, as well as in a DOS window under MS
Windows and OS/2. Features include support for NNTP,pull-down menus,
reading and posting of news, reply by mail via SMTP.

Available at file://calvin.sfasu.edu/pub/dos/network/ftp-pctcp/ftpnuz10.zip

Gene Mangum; email: [e-mail]

Windows Applications

Insanely great
Windows Mosaic v1.0    free

The Internet╒s Swiss army knife: supports hypertext links, font styles,
embedded pictures, sounds, and movies. An amazing application. Compatible
with Windows Sockets. Make sure you get the viewers for sounds, JPEG, and
MPEG. Download this, now!

Available at: file://ftp.ncsa.uiuc.edu/PC/Mosaic/wmos10.zip (Windows
Mosaic), file://ftp.ncsa.uiuc.edu/PC/Mosaic/viewers/lview30.zip (JPEG
viewer) file://biochemistry.cwru.edu/pub/dos/mpeg2.zip (MPEG viewer)

Downright Speculation
WinIRX    free

A Windows Sockets program that makes it easier to search or retrieve from
the National Center for Biotechnology Information (NCBI) Retrieve Email
server.

Available via file://biochemistry.cwru.edu/pub/dos/win-irx.zip,
win-irx.txt.

Insanely great
PCEudora v1.4b17    Free

The Windows version of Eudora, now compatible with Windows Sockets. Handles
SMTP, POP3. This is the nicest TCP/IP mail client available anywhere.  To
be able to send and receive file enclosures, make sure to obtain
BINHEX.EXE.

Available at: file://ftp.qualcomm.com/pceudora/windows/pce14b17.exe (PC
Eudora) file://boombox.micro.umn.edu/pub/pc/binhex/binhex.exe (BINHEX)

Downright speculation
Windows Telnet beta 3    free

A Telnet implemenation for Windows. Windows Sockets compatible.

Available at: file://ftp.ncsa.uiuc.edu/PC/Telnet/windows/wintelb3.zip

Downright Speculation
Windows FTP client    free

This isn╒t a full FTP implementation (I couldn╒t get it to work), but a
future release might be more trouble free.

Available at: file://microdyne.com/pub/incoming/ws_ftp.zip,
file://ftp.usma.edu/pub/msdos/ws_ftp.zip
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/ws_ftp.zip

John Junod; [e-mail]; [e-mail] NCOIC,
Technology Integration Branch, Computer Science School, FT Gordon, GA
30905; [phone]  AV:780-3245

Downright Speculation
Windows Ping    free

Available at: file://microdyne.com/pub/incoming/ws_ping.zip,
file://ftp.usma.edu/pub/msdos/ws_ping.zip

John Junod; [e-mail]; [e-mail] NCOIC,
Technology Integration Branch, Computer Science School, FT Gordon, GA
30905; [phone]  AV:780-3245

Downright Speculation
WAIS for Windows

A Windows WAIS client is vailable at
file://ftp.oit.unc.edu,/pub/WAIS/UNC/Windows/winwais.zip. Now compatible
with Windows Sockets.

For information, contact Jim Fullton, UNC Office of Information Technology,
Computing Systems Development Group, [phone]; email:
[e-mail].

Recommendation EINet
winWAIS v1.52    shareware, $35

The most mature Windows WAIS client,  Windows Sockets-compatible. Available
at file://ftp.einet.net/einet/pc/EWAIS152.ZIP

EINet Windows Shareware, MCC, 3500 West Balcones Center Drive, Austin, TX
78759-6509

Recommendation
Windows Trumpet v1.0a

WinTrumpet is a Windows-Sockets compatible NNTP client from P. Tattam that
supports the Trumpet ABI, packet drivers, Novell Lan Workplace for DOS and
WinSock v1.1. It is the nicest shareware NNTP newsreader for Windows
Sockets.

Available at: file://ftp.utas.edu.au/pc/trumpet/wintrump/*
file://biochemistry.cwru.edu/pub/wintrump/wtwsk10a.zip (Windows Sockets
version), wtpkt10a.zip, wtabi10a.zip, winpkt.com, wtlwp10a.zip (Lan
Workplace for DOS)

Downright speculation
Cookie server    Free

This is a Windows-Sockets compatible fortune cookie server (RFC 865) that
runs on port 17. Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/cooksock.zip.

Contact: [e-mail]

Recommendation
HGopher v2.3    Free

This is a Windows-sockets compatible version of Gopher. Looks good.

Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/hgopher2.3..zip,
hngopher2.3.zip (PC-NFS version).

Recommendation
Windows NT FTP daemon    Free

This is a Windows NT version of ftpd. Quite fast.

Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/nt-ftpd.zip

Downright Speculation
WinLPR v1.0    Shareware

This looks good, even though I can╒t get it to work. It is an
implementation of lpr, lpq, and lprm. Contact: [e-mail]

Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/winlpr10.zip

Recommendation
Winfsp v1.2    Free

A Windows Sockets-compatible implementation of the File Slurping Protocol.
I got it working with no problem. Be aware that the ╥protocol search╙
option can take quite a while; you may have be asking the client to
individually test hundreds of ports, at a second per port.

Available at: file://biochemistry.cwru.edu/pub/dos/winfsp12.zip

Downright Speculation
WinLPD    Free

An lpd implementation for Windows.  Contact: [e-mail]

Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/wslpd.exe

Downright speculation
Text server

This is an extended finger client, which can also serve text files.
Available at
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/txtsrv.zip

Recommendation
WinQVT/Net v3.94
Shareware    $40
Students    $20

QVTNet is a Windows v3.1 application that supports FTP client and server
(not fully graphical; commands are entered at the bottom of the window),
telnet (up to 15 simultaneous sessions), mail (SMTP and POP3), NNTP (up to
30 newsgroups) and lpr.  It is written as a DLL, and comes in several
versions: a Windows Sockets-compatible version (recommended); a Windows NT
version;  and a version with it╒s own built-in TCP/IP stack. The version
with the built-in stack requires that you load PKTINT in DOS before running
it, and also requires you to supply your own packet drivers, and is
compatible with AppleTalk as well as class 6 SLIP drivers.

Available at file://biochemistry.bioc.cwru.edu/pub/qvtnet/qvtne394.zip
(Windows version), qvtnt394.zip (Windows NT version), qvttcp21.zip
(build-in TCP/IP version)

Contact: [e-mail]

Downright Speculation
WinVN v0.80

A semi-graphical Windows application for reading news which supports NNTP
over TCP/IP or serial line connections.  Compatible with Winsock v1.1; a
version is also available for Windows NT. Does not support LocalTalk.
Current version has been tested with:

NetManage's WINSOCK FTP Inc.'s WINSOCK Wollongong's WINSOCK NT's WSOCK32
DEC's Pathworks MS's Lan Man

Available at file://titan.ksc.nasa.gov/pub/win3/winvn Also:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/winvnstd080.zip

Sam Rushing, email: [e-mail],
hoggle!hoggle2![e-mail]

You╒ll find a bunch of zip files. Be sure to use binary mode. Read the file
announce-2.txt first.

Recommendation
Finger v3.1    Free

The Windows version of Finger, which requires a Winsock DLL. It works; try
it out.

Available at:
file://sunsite.unc.edu/pub/micro/pc-stuff/ms-windows/winsock/apps/finger31.zip.

Downright Speculation Uwho    Free    Uwho is Stan Barber╒s interface to
whois and ph e-mail address servers that runs under MS-DOS. An alpha test
version is available at
file://punisher.caltech.edu/pub/dank/uwho/uwho218b.tar.Z, uwho218b.zip, or
unarchived in subdir uwho218b.  The archived text files are inUnix format.

Recommendation
Cello WWW client v1.0    Free

Unlike Mosaic, Cello WWW does not support inline pictures, although it does
support viewing of sounds, pictures, postscript and movies through external
viewers. The current version supports Windows Sockets.

Available at file://ftp fatty.law.cornell.edu/pub/LII/Cello/cello.zip,
viewers.zip, the graphics viewer and sound player; gswin.zip, a Ghostscript
Postscript viewer for Windows. TCP/IP Vendors

Applications

Downright Speculation
3Com TCP w/ DPA v2.0

3Com; [phone]

Downright Speculation
AIR for Windows

Spry Inc.; 1319 Dexter Ave North, Seattle WA 98109; [phone], email:
[e-mail]

Suggestion
BW-NFS v3.0c

The BW-NFS protocol stack is available as a TSR, rather than as a DLL,
which means that it takes up DOS memory even if you are primarily using it
with Windows.  The package supports SLIP, NFS client, Telnet (VT220 and
3270 emulation), finger, talk, ftp, and SMTP mail.  It also can act as a
server for telnet, FTP, finger, and lp.  The 3270 emulation is reportedly
OK.

Beame & Whiteside Software, Ltd.; P.O. Box 8130, Dundas, Ontario, Canada
L9H 5E7; [phone], fax: [phone], email: [e-mail]

Suggestion
Chameleon v3.15    $125 (upgrade price)
ChameleonNFS v3.15  $400

Chameleon is a Windows 3.x TCP/IP implementation that can handle FTP,
Telnet (3270, ANSI, VT-52, VT100 and VT220 emulation), ping, SMTP, POP2,
and NFS (client and server) all in multiple windows, simultaneously.  The
package also supports DNS via an implementation of BIND, as well as SNMP.
ChameleonNFS is compatible with the IPX/Link product for Netware from
NetManage.  Most of the code resides in a DLL. Chameleon supports multiple
interfaces, and can route betweenthem. The newest release supports CSLIP,
PPP and NNTP.

NetManage, Inc.; 20823 Stevens Creek Blvd.,Cupertino, CA 95101;
[phone], fax: [phone], email: [e-mail]

Downright speculation
Distinct Network Applications v3.02    $395
Distinct Software Development Kit    $495
Network & Developer Combination            $695

Distinct TCP/IP for Windows - Network Applications v3 integrates several
Windows based TCP/IP utilities under a single interface.

These include: Distinct Telnet which allows multiple concurrent Telnet
sessions on different remote hosts, allowing you to cut and paste
information between these systems as well as between the systems and your
local host. Distinct FTP is a drag and drop FTP which allows you to drag a
local or remote file to a local printer. Distinct FTP has both a client and
a server; this means that files can be also transferred by selected users
from PC to PC (password protection is included). TFTP provides file
transfer services to  communications servers and routers that do not have
FTP. Network Monitor monitors host-to-host communication and data
transmission traffic and is able to capture network traffic to a file.

Distinct TCP/IP for Windows - Software Development Kit

This product is engineered as 100% DLL, and requires only 4 Kb DOS memory
for a driver. The product supports up to 64 concurrent sockets, and buffers
are allocated and deallocated as they open and close.

Includes three development kits:

Distinct TCP/IP for Windows - Berkeley-style Sockets (TCP, UDP, ICMP,
Telnet, FTP)

Distinct TCP/IP for Windows - Windows Sockets ver. 1.1

Distinct RPC - a complete ONC RPC/XDR toolkit for Windows (Client and
Server RPC over both TCP and UDP; includes RPCGEN)

Distinct Corporation;14395 Saratoga Avenue, Suite 120, Saratoga, CA 95070;
[phone], fax: [phone], email: [e-mail]

Distinct Corporation; P.O. Box 3410, Saratoga, CA 95070-1410;
[phone], email: [e-mail]

Suggestion
Everywhere Access

This is a remote access package for TCP/IP, including support for telnet
server, FTP and Kermit transfers, VT100, VT220, VT300 emulation, password
security. Includes versions working with WATTCP as well as other
implementations.

Supro Network Software Inc.; P.O. Box 18, Warsaw, Ontario, Canada K0L-3A0;
[phone], email: [e-mail]

Downright Speculation
Fusion

Pacific Software; [phone]

Downright Speculation
ICE/TCP

James River Group; 125 North First St., Minneapolis, MN 55401;
[phone], email: [e-mail]

Downright Speculation
Lanera TCPOpen/Standard v2.2

Lanera Corporation; 516 Valley Way, Milpitas CA 95035; [phone],
email: [e-mail]

Downright Speculation
Lantastic for TCP/IP

Artisoft, Inc.;  691 East River Road, Tucson, AZ 85704; [phone]

Suggestion
LAN Workplace for DOS v4.1r8

Novell, Inc.; 122 East 1700 South, Provo, UT 84606; (800)772-UNIX

Downright Speculation
NS & ARPA Services v2.5

Hewlett-Packard; 19420 Homestead Rd., Cupertino, CA  94014; [phone]

Downright Speculation
Wollongong PathWay Access v2.1.1
Access for DOS/WIndows    $350
Client NFS    $95
Access for Macintosh    $295
ClientNFS    $295
Access for OS/2    $350
API Developer╒s Kit (Mac/DOS/Windows) $200

Wollongong offers TCP/IP for DOS/Windows, Mac, OS/2, and Vax/Alpha; SNMP
Management products, and Electronic Messaging based on OSI/TCP X.400/X.500
Standards. Discounts are available for educational institutions and
multiple users.

Features of the API Developer's Kit include:

* DOS AND true Windows applications * VT100-220, VT320-330, VT340, IBM 3270
2-5, IBM 3179g, Tek 4105-4010 * High performance FTP * Scripting,
Remapping, Printing Services * Ethernet, Token-Ring, Async, X.25 support *
28K DOS/Windows (Most of which can be loaded high) Windows Sockets
Compliant * ODI, NDIS, PDS, ASI, ODI/NDIS, SLIP, PPP, IPX/NDIS, IP/IPX,
IP/NetBIOS support * Extensive 3rd Party Support

The Wollongong Group; 1129 San Antonio Rd, Palo Alto, CA 94303;
800-872-8649 (Outside Cal), 800-962-8649 (In Cal), [phone],
[phone], email: [e-mail]

Downright Speculation
PC-LINK for DOS
PC-LINKW for Windows

X LINK Technology; 741 Ames Avenue, Milpitas CA 95035; [phone], fax:
[phone], email: [e-mail]

Suggestion
PC-NFS v5.0    $395

PC-NFS from SunSelect (a Sun Microsystems business) includes a TCP/IP
stack, TCP/IP utilities under DOS and Windows, an NFS client, remote
printing support, SNMP, and Windows Sockets. Add-on packages support email
and advanced telnet. A Programmer╒s Toolkit is available which provides DOS
and Windows support for TCP/IP over sockets and XTI, as well as TIRPC, NIS
and supporting APIs.

SunSelect; 2 Elizabeth Drive, Chelmsford, MA 01824-4195;(800)24-SELECT or
[phone]; fax: [phone]

Recommendation
PC/TCP v2.2    $400
Kernel Only    $200

PC/TCP v2.2 offers a solid implementation of TCP/IP for DOS, with some
Windows applications.  It includes NFS for UDP or TCP, remote login
(telnet, rlogin, supdup) with a variety of terminal emulators, file
transfer (FTP, TFTP, rcp), electronic mail and news (pop2, pop3, pcmail,
mail, SMTP, NNTP), printing (LPR and print redirection) and informational
utilities (whois, ping, finger, host). Some kerberos support is available
to domestic customers. If used alongside ConcordCommunications Mapware
controllers, this product is capable of handling both OSI and TCP/IP
concurrently. 3270 support is OK.

It is available for Ethernet (DIX or 802.3), Token Ring, SLIP, PPP,
LocalTalk and X.25 interfaces, over packet drivers, ODI drivers, NDIS
drivers, banyan drivers, and ASI drivers.

This package does not route; you are therefore restricted to installing it
with PPP, SLIP or Ethernet, but not some combination of the above.

PC/TCP is incompatible with Stacker. As of version 2.2, the Windows
applications have been improved. New to Windows support is the ability to
mount and unmount NFS drives from within Windows, and to use PCNFSD printer
services from Windows.

The 2.2 manual includes a 6-page install guidelette, and now offers a
menu-driven installation and configuration program.

FTP Software, Inc.; 2 High St., North Andover, MA 01845; [phone],
Support: 1-800-382-4ftp, fax: [phone], email: [e-mail]

Downright Speculation
Piper/IP    $375
Developer's Kit    $375

Piper/IP runs under DOS protected mode, using less than 6K of lower DOS
memory. The company claims that FTP transfers take place at100K/second over
a LAN. They also claim the ability to run concurrrently with NetWare,
VINES, LAN Manager, LAN Server, and WFW. The package includes a FTP, Telnet
(client and server), and SMTP.

Ipswitch, Inc.; 580 Main St, Reading, MA 01867; [phone], email:
[e-mail]

Downright Speculation
Super-TCP v3.00r    $495
Super-NFS client v3.00r

SuperTCP supports telnet (3270, VT100, VT102, and VT220 emulation), talk,
SMTP, ftp, ping, and with Super-NFS, NFS client.  SuperTCP supports both
TCP/IP and Novell IPX protocols, as well as SNMP.

It is written as a DLL, although a TSR version of the protocol stack is
also available for those who want to use DOS as well. Network statistics
(arp, ICMP messages, etc.) are available. A shareware version (WinTCP v1.0)
is also available for download from EXEC-PC and other BBSes.

Frontier Technologies;10201 North Port Washington Road, Mequon, WI 53092,
[phone], fax:[phone], email: [e-mail]

Downright Speculation
TCP/IP for DOS v2.10

IBM; Dept. E15, P.O. Box 12195, Research Triangle Park, NC 27709;
(800)IBM-CALL

Downright Speculation
TCP/IP Utilities for LanManager v1.0
Windows for Workgroups TCP/IP
Windows NT

Microsoft; One Microsoft Way, Redmond WA 95052-6399; [phone]

Downright Speculation
TCP/2 for DOS

Essex Systems; [phone]

Downright Speculation
TTCP v1.2r2

Turbosoft Pty Ltd; 248 Johnston St., Annandale, NSW Aus. 2038; +61 2 552
1266, email: [e-mail]

XWARE

Suggestion
PC-Xview

PC-Xview is available for DOS or Windows, supporting use of X over the
network.  It also supports NCD's Xremote protocol that allows X to run over
a modem much faster than could be achieved running a standard X package
over SLIP or PPP.

Network Computing Devices, Inc.; [phone]

Downright speculation
XVISION    $449

XVision allows X applications to run under Windows.  You have a choice of
running each X app in its own Window, or all X applications within one big
Window.

VisionWare, Ltd.; 57 Cardigan Lane, Leeds, England; 44-0-532-788858,
[phone], fax:[phone]

Downright Speculation
DesQView X

DesQView X integrates networks of DOS and UNIX machines using the X-Windows
protocol, allowing DOS machines to act as X-Windows clients and servers.

Quarterdeck Office Systems; 150 Pico Boulevard, Santa Monica, CA90405;
[phone], fax:[phone] Development Software Epilogue Technology:
Includes source code. [e-mail], fax: [phone]

Spider Systems Available for many architectures. [e-mail], fax:
44-31-555-0664

Marben Produit
TCP/IP Source

available, fax: [phone]

Network Research
FUSION
Source available, fax: [phone]
------------------------------ END OF FAQlet ------------------------

Please send comments to:
Bernard Aboba
Author "The Online User's Encyclopedia", Addison-Wesley, 1993
MailCom
5337 College Ave., Suite 326
Oakland, CA 94618,
Fax: [phone]
email: [e-mail]