HDTenEightyP/NetNews huggingface dataset:
From: catfood@wariat.org (Mark W. Schumann)
Subject: Re: Lantastic for tcp/ip and packet drivers
Organization: Akademia Pana Kleksa, Publi Access UNI* Site
Date: Mon, 21 Dec 1992 18:07:23 GMT

In article <henrik.25.0@itekiris.kjemi.unit.no> henrik@itekiris.kjemi.unit.no (Henrik Gudbrandsen) writes:
>In article <1992Dec19.024155.7116@wariat.org> catfood@wariat.org (Mark W. Schumann) writes:
>>Henrik Gudbrandsen writes:
>some deleted
>>>
>>>In my present setup I have 2 network cards, one for Lantastic and the other 
>>>for packet driver (with pktmux). I had hoped Lantastic for tcp/ip used 
>>>packet drivers so I could remove one card (this setup use memory! :-() ).
>>
>>If you are using LANtastic For TCP/IP, on a LANtastic network, then
>>what is the second network card for?  You don't need it for TCP/IP,
>>as far as I can tell.  (Please pardon my ignorance if this is obvious.)
>
>I use the second card with a packet driver (for software requiring packet 
>drivers (popmail, trumpet, gopher and qvtnet)) to be able to run both 
>Lantastic and read news, send mail etc at the same time! (Please pardon my 
>long sentence.)

Okay, that makes sense.  I'm afraid I can't help with the problem then.

-- 
Mark W. Schumann/3111 Mapledale Avenue/Cleveland, Ohio 44109-2447 USA
Preferred: mark@whizbang.wariat.org | Alternative: catfood@wariat.org
"Aren't you glad you didn't marry someone dumber than you?" --my wife
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: bcmatusz@vela.acs.oakland.edu (Brian Matusz)
Subject: TCP/IP for Microsoft Windows
Organization: Oakland University, Rochester MI.
Date: Thu, 31 Dec 1992 02:25:15 GMT

Begin posted for a friend; followup to center03@cps201.cps.cmich.edu
-------------------------------------------------------------------------

A public domain (copyrighted) TCP/IP implementation for Microsoft
Windows will be shortly available.  If you are interested in this
project, especially for beta-testing and application writing, please
send mail to center03@cps201.cps.cmich.edu [141.209.20.201].  DO NOT
send mail to the poster of this article ... it's a followup for me.

Implementation currently includes TCP/IP stack, PPP, program TaskMaster
(coordinator for all network components) and sample finger application.
Windows Sockets is coming soon.  Currently I have an API that is
specifically Windows-oriented (Windows Sockets is a poor example of
good planning!).

Brad Wilson, KA8RJS, Central Michigan University
center03@cps201.cps.cmich.edu
-- 

---
bcmatusz@vela.acs.oakland.edu
"Use DEVICE=EXXON to screw up your environment."
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ziegenfE@moravian.edu (Eric W. Ziegenfus)
Subject: ODITOKPKT
Summary: odi packet driver for token-ring boards
Keywords: ODI, PKT, token-ring
Date: Tue, 29 Dec 92 16:48:01 EST

I was wondering if anyone knows where, or if such a driver exists? I work
with a lot of Intel token-ring boards (run Novell) and would like to be able
to use the packet programs from these PC.
-- 

               /---------------------------------------------\
              | INTERNET:  ziegenfE@moravian.edu              |
              | UUCP:      ...!rutgers!lafcol!batman!ziegenfE |
               \_____________________________________________/

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: Hendrik.Klompmaker@beheer.zod.wau.nl (Hendrik Klompmaker)
Subject: BANPKT and Banyan Vines mistery
Organization: Wageningen Agricultural University
Date: Mon, 21 Dec 1992 21:47:30 GMT

Hello there,

I posted the following message to Dan (He wrote BANPKT the allow packet 
driver over Banyan stack). 
We have been trying to get BANPKT to work in out network but came up with 
the following results. I'm completly in the mist here and from Dan's respons 
I beleive he is as well :-).
-------------------- Original message -----------------------------------

Hi Dan,

I found the following:

I set up a local network with no connections to the outside world nor any 
Banyan servers (that's local isn't it :-)). On one PC I load the Banyan client
software and Banpkt and NCSA's telnet. On an other pc in the network I use an 
ordinary packetdriver and TELNETD (a telnet deamon) and guess what.... it 
works !!!!
Then I disconnect the 'banpkt' pc and connect it the the real live network. No
problems at all. I can connect to all the nodes I wish, until I reboot and try 
to start the same up on the real live network which gives me a 'no go'.
What's wrong here ??

--------------------- End original message ------------------------------

I hope there is someone out there who can give some insides on this.
Any comments are appreciated.

Greetings Hendrik.

===============================================================================
|******** Wageningen Agricultural University. Animal Production Group ********|
-------------------------------------------------------------------------------
Hendrik Klompmaker		Internet : Hendrik.Klompmaker@Beheer.Zod.Wau.Nl
System Manager			Bitnet	 : KLOMPMAKER@HWALHW50.BITNET
Phone : +31 (0)8370-83934	Fax	 : +31 (0)8370-83962
Snail : Marijkeweg 40, 6709 PG	WAGENINGEN, The Netherlands
===============================================================================

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tbenham@cybernet.cse.fau.edu (Tom Benham)
Subject: Re: Winsock available?
Organization: Cybernet BBS, Boca Raton, Florida
Date: Thu, 31 Dec 1992 07:14:57 GMT

geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:

> You're getting confused between API and ABI. Source compatibility is
> achieved by writing to a standard programming interface (API).

Actually, I had a pretty clear understanding of the concept of the
API.  What I overlooked was the differences/opportunities that
Winsock offers for dynamic binding and additional function to support
that type of environment.

I appreciate your detailed explanation, it helped a lot.  Is it
fair to assume that the major TCP vendors will be implementing this
API in their products?  Are we likely to see this in the major UNIX
impelmentations as well as NT & OS/2 for example?

Tom Benham
From: backman@FTP.COM (Larry Backman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Winsock available?
Date: 21 Dec 92 10:24:31 GMT
Organization: The Internet


 >> Let me guess... Marketing?  It is disappointing to see Frontier join
 >> some other WinSock vendors in truth-stretching.  Let's take a look at
 >> appendix C of the WinSock spec v1.1 draft 2:
 >> 

Bless you :-).  This guy came out of the weeds, eh?


L.

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: hitt@Xenon.Stanford.EDU (Daniel Hitt)
Subject: ne2000, ethernet address, set up, ncsa telnet
Summary: how to determine ethernet address of ne2000 clone?
Keywords: ne2000, ethernet address, set up, ncsa telnet
Organization: Computer Science Department, Stanford University.
Date: Mon, 21 Dec 1992 13:14:28 GMT

I have a 16-bit ethernet card which is supposed to be
fully compatible with Novell's NE2000 ethernet interface
board.

I am trying to use it with the NCSA Telnet (which i got
from ftp.ncsa.uiuc.edu).

In the configuration file (config.tel) i have
myip=192.42.172.2
hardware=ne2000
interrupt=3
ioaddr=300

(I've got the board jumpered for the values interrupt=3 and
ioaddr=300 also.)

When i try to run telnet, the program reports the
correct ip address (192.42.172.2) but gives an
ethernet address of 0:0:0:0:0:0 and fails to connect
to the machine i'm telnetting to.  (The network is
very simple, consisting of exactly two machines, the
pc/at and a Unix box.)

I presume that the all-zero ethernet address is incorrect.

Is there a set up program that one normally runs with
Novell cards to initialize them?  Any suggestions on
how i can get the correct ethernet address and make a connection?

Thanks for any help anyone can provide.

dan



Newsgroups: comp.protocols.tcp-ip.ibmpc
From: martineau@MacMartineau.ccr.hydro.qc.ca (Alain Martineau)
Subject: Looking for a graphical 3270 emulator
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Hydro Quebec
Date: Tue, 22 Dec 1992 20:17:24 GMT

The guy in charge of our MVS system says he can't put all the users on
TCP/IP
because there are no good graphical 3270 (3278?) emulators running on top
of
it, on the PCs. Anybody knows anything about a program that does that ?

Alain Martineau
Hydro Quebec
martineau@macmartineau.ccr.hydro.qc.ca
From: brian@SJF.Novell.COM (Brian Meek)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: RARP support for tcp/ip lanman from microsoft
Date: 22 Dec 92 16:13:04 GMT
Organization: Novell, Inc.

Hendrik.Klompmaker@beheer.zod.wau.nl (Hendrik Klompmaker) writes:
>In article <724737581snx@crynwr.com> nelson@crynwr.com (Russell Nelson) 
writes:>>From: nelson@crynwr.com (Russell Nelson)
>>Subject: RARP support for tcp/ip lanman from microsoft 
>>Date: Sat, 19 Dec 92 03:59:41 GMT
>>In article <1992Dec18.110547@roper.mc.ti.com> a722756@roper.mc.ti.com writes:
>>
>>   We have about 300 pcs running lanman tcp/ip from microsoft (or equivalent).  We   just lost a weekly backup for a major vms system on site because a user (again)   misconfigured his pc to the vms  machines ip address.  We are clearly    approaching>>   We have about 300 pcs running lanman tcp/ip from microsoft (or equivalent).  We   just lost a weekly backup for a major vms system on site because a user (again)   misconfigured his pc to the vms  machines ip address.  We are clearly    approaching>>   


a completely unstable situation.
>>
>>   When  and how soon might one exzpect RARP support for the pc
>>   tcp/ip packages.  Since we are heavily lanman  commiotted, it
>>   looks like I need microsoft    support, but other thoughts would
>>   also be considered.
>>
>>Don, RARP is not as well designed as BOOTP.  I'd look for a BOOTP solution
>>before RARP.
>>
>>-russ <nelson@crynwr.com> What canst *thou* say?
>>Crynwr Software           Crynwr Software sells packet driver support.
>>11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
>>Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
>
>If you do any subnetting your in trouble with BOOTP as well. You can't do 
>BOOTP over Cisco's (RARP doesn't either) because the client on the other 
>side of it will get the hardware address of the cisco instead of it's own.

If this is indeed the case, it's a bug in the BOOTP forwarding mechanism 
or (more likely) a bug in the BOOTP server implementation you're talking 
about.  BOOTP works fine across routers if said routers support BOOTP 
forwarding per RFC-951.

-- brian
___________________________________________________________________________
Brian Meek                      Novell, Inc. -- Desktop Systems Group
                                Internet mail:  brian@Novell.COM
From: wawa@arcady.msk.su (Vova Ivanov)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Clarkson Driver -  Address Conflict.
Date: Mon, 21 Dec 92 23:43:30 +0300
Distribution: world
Organization: ARCADY clever projects
Reply-To: wawa@arcady.msk.su

>In article <BzGFt0.Bz2@scholia.wbme.jhu.edu> tkolasny@scholia.wbme.jhu.edu writes:
>
>   I have two IBM clones (an epson and AMI 386SX) that do not load the 3C503
>   Clarkson Driver. Both machines 3C503 have been tested and work fine with
>
>By the way, Crynwr purchased the copyright on the packet driver
>skeleton from Clarkson.  Clarkson insists that I not use their name,
>so I've changed it to "Crynwr Packet Driver Collection".
>
>   Lan Manager using DISABLE for the shared memory jumper. When I set the
>   jumper to any other shared memory jumper, Lan Manager stops working and
>   installing the  3C503 driver using:
>
>     Packet driver for 3-Com 3C503, version 9.4.0
>
>Try the latest publicly released version, 10.5.1, found in
>drivers3.zip on simtel20 or mirrors.  See a recent posting for the
>packet driver's HOWTOGET.IT file.
>
>
	First: check IRQ of your 3c . It may be conflict with
	com. port (COM1 - IRQ4, COM2 - IRQ3) and then some models 
	not support IRQ2. Try to disable memory  shadowing on your 
	PC - it may affect too.

				Vova Ivanov
From: kb7uv@panix.com (Andy Funk)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Wireless Network
Date: 29 Dec 92 22:23:00 GMT
Organization: Panix, NYC

In <199212291002.AA00190@turkey.wes.army.mil> mleber@TURKEY.WES.ARMY.MIL (Mark Leber) writes:

>Hi,

>Does anyone know where I can find some good documentation (ie. articles,
>...ect.) on the subject of Wireless Networks?
>Any help would be appreciated!!



Mark-

Try rec.radio.amateur.packet, here on Usenet.  Also, tapr@tapr.org has
back issues of their newsletter available.  The American Radio Relay
League has held 11 annual Computer Networking Conferences.  They assembled
the papers into "Proceedings Of..." books, and many are still available. 
You can call them at 203-666-1541.

CQ Productions has an excellent videotape operating guide for Amateur
Radio packet operation.  I don't have their numbr handy, but they're
located in Hicksville, NY.

The Radio Amateur Telecommunications Society (RATS, of which I am
Chair-elect) has information available on the RATS Open Systems
Environment (ROSE).  One element of ROSE is the X.25 Packet Switch.  If
you'd like information on this approach to packet radio networking you can
contact me or rats@kb2ear.ampr.org.

I hope this info is helpful!

-Andy-
-- 
    Andrew Funk, KB7UV                     Internet: kb7uv@panix.com
    ENG Editor/Microwave                     Packet: kb7uv@kb7uv.#nli.ny.usa
    WCBS-TV Channel 2 News                      BBS: 718-956-7133
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: books@fsunuc.physics.fsu.edu (Roger Books)
Subject: Elite 16 packet driver
Organization: FSU nuclear physics
Date: Wed, 23 Dec 92 18:07:06 GMT

Does anyone know if there exists a packet driver for the SMC Elite-16?
This is the same as a WD8013, or so my local dealer told me.

Roger
books@fsunuc.physics.fsu.edu
From: a-n@nwu.edu (A. Natarajan)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: PKTMUX and QVT's PKTINT co-existence
Summary: Can I use pktmux along with QVT's pktint?
Keywords: pktmux, QVT, pktint, Novell
Date: 3 Jan 93 19:11:42 GMT
Article-I.D.: news.1993Jan3.191142.15128
Reply-To: a-n@nwu.edu (A. Natarajan)
Organization: Northwestern University, Evanston IL 60208
Originator: nataraj@casbah.acns.nwu.edu

I am trying to pktmux to run the NCSA suite of programs (telnet, ftp, and
Clarkson tn3270), as well as WinQVTNet 3.03 under Windows 3.1, and am
having problems with loading the QVT pktint program - the PC exits to DOS
and displays a C: prompt, and is in a frozen state, whenever I run WinQVT.

My set-up is further complicated by the fact that I am on a Novell network
as well, but let me show you part of my autoexec.bat to clarify....

set config.tel=c:\telnet\config.tel
:...
lsl
rem c:\qemm\loadhi /r:2 lsl
:...
3c501 -w 0x60 3
rem c:\qemm\loadhi /r:1 3c501 -w 0x60 3
:....
ipxodi
rem c:\qemm\loadhi /r:1 ipxodi
:...
odipkt 0 98
rem c:\qemm\loadhi /r:2 odipkt 0 98
:...
pktmux 4
rem c:\qemm\loadhi /r:2 pktmux 4
:....
bnetx
rem c:\qemm\loadhi /r:2 /res=49664 /sqf bnetx
:.....
call c:\telnet\checktim.bat
rem checktim.bat sets the time using NCSA's setclock
:....
pktint
:..
f:login
c:
win :
========================================================================
Forgetting my attempts to use QEMM ( a whole different story), I think I am
using the pktmux shim properly; for instance, to load NUPOP, I have:
:nupop62.bat
pktdrv 62
c:\nupop\nupop
pktdrv 62 /uu

Do I need to load pktint similarly, or am I just doing it in the wrong
order?  I can't seem to find the right incantations for even a non-Novell
set-up :-) - and would appreciate any pointers.

I can't rely on WINQVTNet solely, because I can't seem to use it to connect
to an IBM 4381, and also prefer to use NUPOP instead of QVT's Mail module.

Thanks,

A. Natarajan
From: ganino@newsserver.tasc.com  ("James S. Ganino")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Relative Merits of NDIS vs ODI Poll
Date: Tue, 29 Dec 1992 10:45:40
Organization: TASC
Distribution: USA
Reply-To: jsganino@tasc.com
NNTP-Posting-Host: tardis.read.tasc.com
NNTP-Software: PC/TCP NNTP

     At the risk of being inundated by a flood of strong opinions, I am
interested in soliciting people's opinions and preferences between NDIS
and ODI packet drivers.  I am currently trying to decide which to use
for a group of 50 PC's that will shortly be installed with FTP
Software's PC/TCP.  Please indicate which driver you use, which you
prefer (if different) and for how many machines you speak.

     Please send responses via e-mail to jsganino@tasc.com.  I will be
glad to post a summary shortly after the new year.

Jim

--
James S. Ganino
TASC
55 Walkers Brook Drive
From: ddl@burrhus.harvard.edu (Dan Lanciani)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: new dis_pkt
Date: 31 Dec 92 07:09:22 GMT
Article-I.D.: burrhus.1992Dec31.070922.19010
Organization: Harvard University, Cambridge, MA

A new version of the NDIS/packet driver converter is now available for
anonymous ftp from hsdndev.harvard.edu in pub/dis_pkt.  It attempts to
work around (but does not solve) the problem discussed below:

The Packet Driver spec's send_pkt call requires that the driver be
finished with the passed buffer when the send function completes.  The
NDIS Transmit function can return a status indicating that the request
is queued, with the memory buffer still ``owned'' by the driver.  An
obvious solution is for dis_pkt's send_pkt routine to loop until the
send operation is actually complete.  Unfortunately, some NDIS drivers
will queue but never complete a send request if called at certain ``bad''
times.  Looping would therefore cause deadlock.

Until now, dis_pkt has simply returned from send_pkt even if the underlying
driver indicates that the request is queued.  Because of the structure of
protocol stacks and the relative speed of the network and cpu, things have
worked most of the time:  the protocol stack does not scribble on the buffer
before it gets sent on the network.  Recently, though, I've been able
to see the problem manifest itself (as expected) with duplicate/missing
packet pairs.

As a first step to reducing the impact of the problem, I added a loop
with timeout to the send_pkt routine.  This helps, but for certain
drivers the loop fails too regularly because of an interaction with
the IndicationComplete/chainvec logic.  In particular, the WD/SMC
driver never completes a send request from within an IndicationComplete
routine.  Any protocol that runs on the tail of the chainvec and tries
to send multiple packets can therefore run into problems.

The best work-around appears to be to avoid the IndicationComplete
code and instead advertise the adapter's true interrupt vector
to the packet driver application.  To this end, the chainvec
setting in protocol.ini now accepts arbitrary values.  If the value
is less than 16 it is assumed to be the true interrupt and dis_pkt
never actually calls the vector.  It is necessary to manually
specify the correct vector (i.e., 8+irq) for chainvec.  (Use with
irqs 9-15 is not yet supported.)  When more NDIS v2 drivers become
available, this process may be automated since v2 provides the irq
in a characteristics table.  Extracting the information from protocol.ini
is another possibility but it would require knowing all the defaults...

				Dan Lanciani
				ddl@harvard.*
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Wattcp -> Silicon Graphics: (solution + questions)
Date: 28 Dec 92 18:06:05 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    .... In the meantime however it would be nice to have the pc end ftp
    agent not insist on a password unless the remote site asks for one.  I
    haven't dug out the relevant rfc yet but I would hope there is some kind
    of feedback... perhaps an agreed "password string empty" message rather
    than a "no password required".

RFC 959 says that the client must depend on the server's response to the USER
command:  If the server replies with a 2xx code, then no password is required
and the client shouldn't ask for one.  If the server replies "331...", then
the client *must* prompt for a password.  4bsd-derived Unix FTP servers
afflicted with this bug don't notice that there's no password and send the
"331..." response anyway.  Furthermore, they expect a PASS command next, so
the client can't get anywhere even if it violates the protocol.  Either get
the vendor to fix the server, or put a password on the account.  There's no
other way.

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: SKLEPZI@SSB1.SAFF.UTAH.EDU (Steven Klepzig)
Subject: Re: Token Ring ODI Packet Driver (ODITRPKT.COM)
Organization: University of Utah
Date: Mon, 21 Dec 92 21:09:51 GMT

In article <1992Dec21.164909.10265@mont.cs.missouri.edu> usbill@ustores.missouri.edu (Bill Canning) writes:
>Does this program exist?  I read a posting that someone was nearly done with
>this.  Are you done?  Do you need beta testers?

Yes, it does exist - in fact I'm using it now to post this reply.  I didn't 
write it though and it seems that I've misplaced where it is located.  
ARGH!  I thought it was right here.  Oh well, I'll look further.

But it works well and TERMIN does unload it if necessary.

A satisfied customer...
BTW: I'm using the beta version, I haven't heard if there is an "official" 
release yet.

Steven (sklepzi@ssb1.saff.utah.edu)
From: khweis1@mvmhp.ciw.uni-karlsruhe.de (Karl-Heinz Weiss)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Ne2000 Problems
Date: Tue, 22 Dec 1992 21:47:12 GMT
Organization: University of Karlsruhe, Germany
Distribution: world
NNTP-Posting-Host: mvmweiss.ciw.uni-karlsruhe.de


Is here anyone, who has experience with the NE2000 Packet-Driver 
from Clarksom? I am using some Ne2000- compatible cards on our PC's
which will work fine only if netload is rather *high*. If 
traffic is low, connections or/and the transferrate are breaking down. 
I suppose, there are timing-problems, because all seems to work without 
problems, if I simulate a lot of traffic (5%) by pinging repetivly to 
another host.
BTW: pktstat shows no errors, but some dropped packets (about 2-4%)

Who can help?
From: hgv6241@DSACG3 (Adam R. Fathauer)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: FAQ on running a Print Daemon on IBM PC
Keywords: Print Daemon
Date: 28 Dec 92 13:16:24 GMT
Reply-To: afathauer
NNTP-Software: PC/TCP NNTP

Is there a FAQ that I can FTP on configuring and running a Print Daemon
on a IBM PC - preferably as a background task or under Windows?

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: joe@eng3.sci.com (Joe LaRocque)
Subject: KarlBridge?  Is this PD Software?
Reply-To: joe@eng3.sci.com (Joe LaRocque)
Organization: SCI Technology, Inc., Huntsville, Al.
Distribution: usa
Date: Mon, 28 Dec 92 21:19:21 GMT

For quite a while now we have been looking for a replacement for the PCBRIDGE 
software that we are using on our network.  Don't get me wrong, the PCBRIDGE
is working just fine, but it's lack of support for WD8003EP cards is a 
major problem since the older 'E' series is getting harder to get.

An individual that is visiting our plant mentioned the "KarlBridge" and
gave me a copy of the readme file.  It looks pretty impressive.  It also
looks like it works on dedicated hardware and that any software that is
for it is not going to be in the public domain.

Does anyone have any knowledge about this bridge that they would'nt mind
passing along?  

Thanks for the assist.

Joe La Rocque
SCI, Huntsville