[comp.protocols.tcp-ip] sockets, PC-NFS, X, and Clarkson packet drivers

mayer@columbia.sparta.com (09/29/90)

I've been told that the clarkson packet drivers can solve a problem I
have with PC-NFS sockets (namely that there are only 6 of them).  I
ftp'd the drivers and the "pc-nfs driver compatability kit", but must
admit that the resolution of my problem is not apparent
(unfortunately, network protocols are not my forte).  I'm using an X
server on a MS-DOS machine and constantly bump against the 6 socket
limitation.  Although I need to increase this capability, I don't want
to lose PC-NFS's capabilities to mount remote file server directories
as DOS drives and use remote printers.  Is it indeed true that the
Clarkson stuff can allow an increase numer of sockets for PC-NFS?  And
if so, can anyone give me some pointers on how to configuration the
drivers to work with PC-NFS?  Are there any other "public domain"
solutions to my problem (I'd rather advoid a product other than PC-NFS
for compatability reasons)?  Thanks in advance for any assistance.

Frank Mayer
(mayer@sparta.com)

PS- please CC any response directly to me since I do not usually
follow this list.

jbvb@FTP.COM (James B. Van Bokkelen) (09/29/90)

The Clarkson drivers are a MAC-layer (raw Ethernet frame level) interface,
and have nothing to do with PC-NFS's emulation of 4bsd sockets on DOS.
Yes, you can run one on the other, but if the number of open sockets
isn't documented as being configurable, it is presumably a table size
compiled into PC-NFS.  PC/TCP supports up to 20 sockets (you have to
close your stdio handles to get this many), I believe WIN/PC is also
configurable, I don't know about BWTCP.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901