HDTenEightyP/NetNews huggingface dataset:
From: wehr@fmsrl7.srl.ford.com (Bruce Wehr)
Subject: Programming with sockets
Followup-To: poster
Organization: Ford Motor Company Scientific Research Labs, Dearborn, MI
X-Newsreader: Tin 1.1 PL3
Date: Fri, 9 Oct 1992 15:03:50 GMT

    I recently learned Berkeley socket programming on Interactive Unix,
    and I learned just enough to get my job done. Now, I have some
    colleagues learning socket programming on DOS, and they're coming
    to me with questions (some of which I can't answer). They're using
    the PC/TCP Development Kit from FTP Software to develop a client
    that will talk to a server running under VxWorks on a 68K VME box.

    Here's a simple, general socket question straight from Socket
    Programming 101: Once a client is connected, how does one
    disconnect? If one uses close(), then you cannot immediately use
    connect() again ... you have to call socket() again.

    Put another way: when open() is used to open a file, it does two
    things: it assigns a file descriptor and it associates that
    descriptor with a file. You can then jump right in with read()s and
    write()s. With sockets, however, the socket() call (which is like
    open) only does one of those things: it assigns a socket descriptor
    - it doesn't associate that descriptor with a server yet. You must
    call connect() before you can do any read()s or write()s. The
    question then becomes: can one disconnect (thus reversing what
    connect() did) without using close() (which would reverse both what
    connect() and socket() did)?

    Question 2 is probably specific to the FTP Software development
    kit:  they're finding that, when their client attempts to close a
    socket, the process hangs until the server closes its socket. I
    *know* this doesn't happen in the environment I'm familiar with
    (Interactive Unix on a PC). Does anyone know why this happens?
    Currently, they're getting around this by having the client send a
    "All Done" token as its last message, but they'd like to understand
    what's going on (and so would I).

    Question 3: is there any way for a DOS client to check for
    available data on a socket? Since DOS doesn't support multiple
    processes, hanging on a read() from a socket that has no data
    available may not be desirable. I started telling them about
    various ways to check for available data when I realized I was
    giving them Unix solutions, not DOS solutions (they weren't
    familiar with any of the functions I mentioned). So, does DOS or
    the FTP package provide any functions for this?

    If you're still reading this, I must thank you for enduring my
    diatribe.  Any solutions, answers or pointers thereto would be
    greatly appreciated. Please mail your responses and I'll summarize
    if there is interest. I've directed followups to me.

    Thanks.

--
               Bruce Wehr (wehr%dptc.decnet@srlvx0.srl.ford.com)
	           Ford Motor Company - Electronics Division
   Electronics Technical Center - Powertrain Electronic Controls Engineering
       17000 Rotunda Drive, Room B360, Dearborn, MI  48121 (313)248-5530
Newsgroups: comp.protocols.tcp-ip
From: mvm@cbnewsb.cb.att.com (michael.v.murphy)
Subject: Opens and binds on Sparcstation TCP
Organization: AT&T
Distribution: usa
Date: Thu, 8 Oct 1992 18:06:16 GMT

  We are currently running tests on some code that resides on a Sun. The tests
include stress tests that push through tens of thousands of identical and
relatively small (less than 1500 byte) messages. The majority of these
messages flow through ok, however every 500 or so we get a 'system error' on
a t_bind or t_open on one of the messages. I am thinking of putting in retry
logic and possibly a short sleep interval to allow the system to 'catch up',
but I thought I would post the problem first and see if anyone has had
similar experiences or possible reasons/solutions to the problem. 

  Also, could anyone share good/bad experiences with 'mainframe' TCP packages
such as IBM's TCP and Interlink's SNS TCP?

							Many Thanks,
							Mike Murphy
From: andrew@frip.WV.TEK.COM (Andrew Klossner)
Newsgroups: comp.protocols.tcp-ip
Subject: Where to get not-online RFCs?
Date: 7 Oct 92 20:37:18 GMT
Reply-To: andrew@frip.wv.tek.com
Organization: Tektronix Color Printers, Wilsonville, Oregon

[Surely this is a FAQ but I can't find the FAQ list ...]

How can I get an RFC that is no longer online at nic.ddn.mil?

  -=- Andrew Klossner  (andrew@frip.wv.tek.com)
                       (uunet!tektronix!frip.WV.TEK!andrew)
Newsgroups: comp.protocols.tcp-ip
From: tga@oar.net (Germann Associates)
Subject: Re: Network Print under TCP/IP
Organization: Ohio Academic Resources Network
Date: Sat, 17 Oct 1992 01:44:28 GMT


For those of us who forgot to hit the s key in rn, what tcp port does the 
HP TCP card use?

Eric

eric@tga.com

-- 
============================================================================

Eric Germann                               Quote for the time being:
The Germann Associates                     "Lead, follow, or get out of the
From: booloo@framsparc.ocf.llnl.gov (Mark Boolootian)
Newsgroups: comp.protocols.tcp-ip
Subject: Silly Window Problem resolved (WAS: Silly windows, PERSIST timers...)
Date: 8 Oct 92 19:32:30 GMT
Organization: Lawrence Livermore National Laboratory

I'll explain, to the best of my understanding, how we resolved the silly
window problem (for anyone who cares) in a moment.  First, I wanted to
respond to the issue raised in the following post.

In article <1992Oct6.215933.7706@news.eng.convex.com> jjensen@convex.com (James Jensen) writes:
>booloo@framsparc.ocf.llnl.gov (Mark Boolootian) writes:
>
>In your first message you said you filled the 16k window with a single send
>but here you say you are using fddi.  Are you doing something funny 
>with the mtu, or do you mean send, as in "send()"?
>
>if you have a 16k mtu, and a 16k window the behavior you see can
>be explained.  Either up the window or lower the mtu. The window should
>be at least 2*the mtu used by the connection. This should be done
>automaticaly by tcp when it sets up the connection. 
>
>If mtu is 4k then I don't know what your problem is.  I would try
>increasing the send and recieve windows. 
>Jim Jensen - jjensen@convex.com

Good observation.  What we are working with are a Cray and an Amdahl, each
with a HYPERchannel connection, and the HYPERchannels are connected by FDDI.
To be precise, the Amdahl connects directly to HYPERchannel with an NSC
N220 adapter.  The Cray connects to FDDI via an NSC N130 adapter (the N130,
in this situation behaves as a router).  The MTU for the HYPERchannel is
16 KB.  Even though the Cray is "connected" to FDDI, the network interface
the Cray IOS sees is that of HYPERchannel.  Thus, the negotiated MSS is
16 KB.  As a consequence, we end up fragmenting packets on the FDDI ring.
(Probably not a good thing, and we will likely change the MTU to 4K).

Now, the explanation for our silly window situation.  We saw this problem
occur when the Amdahl sent data to the Cray.  The transfer was between
the ftp servers running on these two machines (a third-party or proxy
transfer).  I looked at the Cray daemon and found code which looks something
like this:

		while (buffer not completely filled)
			read data from network;
		write buffer to disk;

It appeared to me likely that we could be leaving data sitting in a socket
buffer when we finally decide to write out the buffer to disk.  So I changed
the code to follow every read from the network by a write to disk (the
typical approach in ftp servers).  This corrected the problem.  However,
there is one other factor which contributed to the cause of the problem.

With an MTU of 16 KB, packets are fragmented by the router tying HYPERchannel 
to FDDI (and reassembled by the Cray upon receipt).  When the MSS used was 
4 KB, and no fragmentation was occuring, we found that SWS did not occur; it
only would occur for transfers in which the MSS was 16 KB.  So, assuming we
change our MTU to 4 KB, the code change above may be superfluous.

Thanks for the responses, sorry for going on for so long.

regards,
mb
-- 
Mark Boolootian		booloo@llnl.gov		+1 510 423 1948
From: heading@breeze.rsre.mod.uk (Anthony J.R. Heading)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Cheap routers: moving on
Date: 16 Oct 92 15:09:40 GMT
Reply-To: heading%hermes.mod.uk@relay.mod.uk
Organization: Defence Research Agency

A clarification. Apparently the US doesn't use X.21, but RS449
instead. So if I were to get a converter, the question becomes how
to connect RS449 to a Sun.

Something which did packet filtering would be nice.

Anthony
------------------------------------------------------------
Defence Research Agency, St. Andrews Road, Malvern, Worcs, UK.
heading@hermes.mod.uk            Work: +44 684 896066
heading@ccint1.rsre.mod.uk       Home: +44 684 563596
From: westes@sti.com (Will Estes)
Newsgroups: comp.protocols.tcp-ip
Subject: Ping Reports: 31% Packet Loss...Possible Causes?
Date: 14 Oct 92 05:57:29 GMT
Organization: Mail Group

I need help in determining possible causes for a network performance
problem.

Here I am by myself on a MS-Windows machine trying to use x-server
software to connect to a UNIX host.  I am alone on an ethernet segment 
that goes through a single router to the second ethernet segment that
attaches to the UNIX host.  Out of nowhere, performance on the network
goes to hell (again, no one is in our office now except for me).

I went to the UNIX host and issued a ping -s command against a few hosts
on the second ethernet segment, and the throughput is great and packet
loss is 0%.  I then did a ping -s back to my host and the results mirror
what I'm experiencing.  Throughput will be great for about four tries, and
then it is poor for one, good for four, poor for one, etc.  Packet loss
is 31%.  

I think something is happening that is localized to my segment.  What
are some possible causes for the symptoms I am describing?  I do not
have a UNIX box on my ethernet, so I can't run etherfind, traffic, etc.

-- 
Will Estes		Internet: westes@netcom.com
From: sam@bsu-cs.bsu.edu (B. Samuel Blanchard)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: telnet & packet size
Date: 12 Oct 92 18:41:04 GMT
Organization: Dept. of CS Ball State University Muncie IN

In article <1992Oct11.224039.11856@bnr.ca> johnh@nnshh127.uucp (John Hawkins) writes:
>   Many of these packets being sent from  pc's contain only one character!
>   Could someone help me out here?
Our terminal serves have an option to send data based on number of characters
or a timeout value.  This is a very common configuration option.  stty on many
UNIX systems has settings for this.  If you convey the package on the PCs then
you might get a more specific response.

>   I have heard of IP header compression, but don't have any useful knowledge.
IP header compression is great where applicable.  Your problem with single
characters/packet is not related.  Your overall traffic problem could be.
I am not really qualified to give much more :-)

>   Any ideas are welcome!  e-mail nvjhh01@NT.COM
>John Hawkins       Internet:  nvjhh01@NT.COM

I am just now placing PCs on our backbone and very much would like to hear
how you solve your problem.

-- 
B. Sam Blanchard        sam@bsu-cs.bsu.edu
418 Winfield Dr         (317) 284-7131   work
Greenfield, IN 46140
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: dv@welch.jhu.edu (Deepak Vaidya)
Subject: Help with ODI and QVTNET27/NCSA Telnet
Reply-To: dv@welch.jhu.edu
Organization: Welch Medical Library, Johns Hopkins University
Date: Mon, 12 Oct 1992 15:50:02 GMT


Hello,

Can anyone help with getting NCSA or QVTNET27 running under windows 3.1.  I am 
able to run NCSA from dos using odipkt but every time that I run it under
windows I am kicked out to the dos prompt.

Here is a list of the software that I am running to connect to netware server.

LSL	v1.2
3c507	v1.00
odipkt	v1.1
pktint	v2.0
ipxodi	v1.2
netx	v3.22

If there are any later version of the above software can you also point out the
ftp site that I can download the software from.

Any help will be greatly appreciated.

Thank You
-Deepak Vaidya
dv@welchgate.welch.jhu.edu
[128.220.59.13]
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: act@softserver.canberra.edu.au (Cyclops)
Subject: Re: VERY Slow Wtnvt for PC/TCP?
Organization: University of Canberra
Date: Thu, 8 Oct 92 22:49:40 GMT

parson@coulomb.pcc.oz.au (Brenda Parsons - x2403) writes:
>We're running PC/TCP 2.1 and would like very much to use the
>WTNVT (windows version of telnet )program, but the speed of it
>is unbearably slow.
>
>Has anyone else had this problem?
>Is there a fix?

Trite fix - Parramatta for the 93 Grand Final!

If you are refer to the slowness of text scrolling within windows then look
firstly to optimise buffering/timing parameters for WTNVT(Have not used the
product).

Secondly in the [386Enh] section of WIN.INI try fiddling with the 
WindowUpdateTime parameter and change it to WindowUpdateTime=200.(default is
50).  As the great sage said 'Suck it and see!".

Thirdly, and not very practical, run on 486/33's or better 486/50's.  Text
scrolling slowness in Windows is my major gripe about Windows!

-- 
Renrut Werdna			Probable-Possible, my black hen,
				She lays eggs in the Relative When.
				She doesn't lay eggs in the Positive Now
act@ss.canberra.edu.au		Because she's unable to postulate how
Xref: sparky comp.protocols.tcp-ip.ibmpc:5700 rec.radio.amateur.packet:2703
From: axa12@po.CWRU.Edu (Ashok Aiyar)
Newsgroups: comp.protocols.tcp-ip.ibmpc,rec.radio.amateur.packet,cwru.ins.general
Subject: Newsreader for KA9Q NOS on PC?
Date: 13 Oct 1992 17:47:50 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: axa12@po.CWRU.Edu (Ashok Aiyar)
NNTP-Posting-Host: slc5.ins.cwru.edu


Can someone suggest a good news reader that can be used in conjunction 
with NOS on a PC?  I will be using PA0GRI NOS 911229 to contact the 
NNTP server and download news.  I am simply looking for a good system 
to read and manage news with - i.e read news, expire articles, and
prepare articles for posting.

Suggestions for news readers would be much appreciated.

Any tips on setting up news with Ka9Q NOS would also be helpful.

Thank you,

Ashok

-- 
                          Ashok Aiyar
   		       axa12@po.cwru.edu
                Visit the IBM-PC Sig on Freenet
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: rar@multix.no (Rolf A. Rennemo)
Subject: Looking for 3Com Etherlink III packet driver
Organization: Multix A.S
Date: Fri, 9 Oct 1992 18:01:26 GMT
Keywords: packet driver 3Com

Subject says it all.

-- 
Rolf

*******************************************************************************
Rolf A. Rennemo                  Multix A/S, Gjerdrumsvei 12, 0486 Oslo, Norway
From: michel@BBN.COM (Tony Michel)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ISDN packet driver + card
Date: 16 Oct 92 16:20:06 GMT
Distribution: world
Organization: The Internet

Is there an ISA bus ISDN interface with a PDI?
AXM
From: mcn@cfa203.HARVARD.EDU (Charley Noecker, Prec Astron)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA Telnet bug report address (Re-post)
Date: 11 Oct 92 03:49:28 GMT
Organization: Smithsonian Astrophysical Observatory, Cambridge, MA,  USA

Sorry to the net if you've already seen this many times.  My Usenet
connection is apparently flaky; I've tried to post this 2-3 times, but
I've never seen it come up when I read later.

I found a while ago that the bug report address listed in the docs is
not working; after I sent a couple of messages into the blackness, I
used 'finger' to locate a working email address.  When I tried

        telbug@ncsa.uiuc.edu

I got a nearly immediate auto-answer and later a personal response to
my report of the non-functioning address.  One final test indicated
that the un-answered letters had not been getting through to the right
person.  If you have sent them mail using the address in the doc
files, and particularly if you never got a response of any sort, you
probably need to try again with the address above.  A recent test
indicated they still hadn't sorted this out as promised.

Charley Noecker
noecker@cfa.harvard.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: fn@junior.mathtok.polymtl.ca (Francois Normant)
Subject: tn3270 with packet drivers
Organization: Mathematiques Appliquees - Ecole Polytechnique - Montreal
Date: Fri, 9 Oct 1992 16:22:35 GMT

Hi,

I look for a version of telnet which works with packet drivers and is able
to reach an IBM 3270 host using TCP/IP. A windows application would be a must!

Please answer via e-mail, I will post a summary to the group.

Thanks in advance.

-- 
Francois Normant (francois_normant@mathappl.polymtl.ca)
Departement de Mathematiques Appliquees - Ecole Polytechnique
C.P. 6079 - succursale A
Montreal - Quebec - Canada - H3C 3A7
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: lewis@erg.sri.com (lewis)
Subject: Anyone have EGP protocol for KA9Q??
Keywords: KA9Q EGP
Organization: SRI International, Menlo Park, CA
Date: Thu, 15 Oct 92 18:32:59 GMT


Hi,

does anyone no of a KA9Q that includes EGP gateway protocol?

I prefer E-mail responses because I will be traveling and news
articles here expire quickly.

thanks,
Mark Lewis -- lewis@sri.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: rbf@sactoh0.sac.ca.us (Bruce Ferrell)
Subject: Re: PC-NFS coexisting with Novell
Organization: Sacramento Public Access Unix, Sacramento, Ca.
Date: Sat, 10 Oct 92 05:27:29 GMT

In article <1992Oct5.030931.29980@gossip.urich.edu> martinher@urvax.urich.edu writes:
>In article <1992Sep29.164225.4935@raid.dell.com>, mikew@thing1.dell.com (Mike Wilson) writes:
>>I am trying to run PC-NFS 4.0 and Novell at the same time using the same network
>>card.  I have PC-NFS set to use the NDIS driver.  I am using the IPX/SPX from
   [Much deleted]

>>
>>Mike Wilson	Dell Computer Corp.	Austin, TX.  
>>
>
You could also do this through Novells ODI driver stack:

LSL
<card driver here>
ODINSUP
IPXODI
NETX

In config.sys you still need to load PROTMAN and the NDIS protocol
modules.  You also need to remark out all of the references in
PROTOCOL.INI to the MAC drivers... It does work and is fairly
clean.  Why buy someones "compatibility" kit when Novell supplies
one?

Bruce Ferrell
LAN Administrator
MCI Western Network Managment Center
Sacramento CA
From: mcn@cfa203.HARVARD.EDU (Charley Noecker, Prec Astron)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Have ethernet, how do I get tcp/ip? (newbie question)
Date: 13 Oct 92 20:57:29 GMT
Reply-To: noecker@cfa.harvard.edu
Organization: Smithsonian Astrophysical Observatory, Cambridge, MA,  USA

From article <1992Oct12.225553.25414@reed.edu>, 
	by nelson@reed.edu (Nelson Minar):

> Someone here has an IBM PC with an Asante ethernet board. She wants to
> put it on the Internet. What do I need to do? Apparantly, there's no
> ready-made software with her ethernet card, nothing like telnet or ftp
> clients.

Available by FTP from wuarchive.wustl.edu (128.252.135.4), in
mirrors/msdos/ncsatelnet: tel2305b.zip, which contains a suite of
public-domain executables for TCP/IP, including telnet, ftp, and lpr.
If you don't know how to do these, consult your local gurus or
write back to me by email.  While you're there, you might want to get
Kermit, mirrors/msdos/kermit/msker311.zip.  It serves some needs
better than Telnet.

> I assume I need a driver. Should there be a software driver with the
> card? Where do I get clients once I have the driver installed?

If you didn't get one with the card, you can find a whole pile of them
in mirrors/msdos/pktdrvr/drivers.zip.  One of them should serve your needs.

You should eventually find the executables you need, without having to
build from source.  Good luck goin fishin'!

Charley Noecker                                  POINTS Group
Harvard-Smithsonian Center for Astrophysics      Mail Stop 63 
60 Garden St                              Cambridge, MA 02138
Email: noecker@cfa.harvard.edu
--------------------------------------------------------------
Charley Noecker                                  POINTS Group
Harvard-Smithsonian Center for Astrophysics      Mail Stop 63 
60 Garden St                              Cambridge, MA 02138
Email: noecker@cfa.harvard.edu
From: CSP1DWD@MVS.OAC.UCLA.EDU (Denis DeLaRoca 825-4580, 310)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WANTED: Opinions on EISA ethernet boards
Date: 15 Oct 92 03:22:00 GMT
Distribution: world
Organization: The Internet

>  I will be purchasing an EISA 486DX50 machine that will be running SC
>  Unix, and I would like others' opinions on which ethernet card I
>  should get.  It will be used primarily for NFS and X11 over TCP/IP.
>  Cost is an issue, but not a very big one (i.e. if it's $500, OK, but
>  if it's $2000 I don't care how fast it transfers data! ;)

How about one of those new spiffy 3COM 3C509 Etherlink III adapters,
supports both ISA and EISA...  I hears it offers high performance
and ease of programming. Russ Nelson (the Crymwr Packet Driver
Collection) may even have a Packet Driver ready for this puppy.
List price may be something like $250, I forget...

-- Denis
From: westes@sti.com (Will Estes)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Want To Buy NetManage NEWTSDK Sockets Library For MS-Windows
Date: 16 Oct 92 05:40:08 GMT
Organization: Mail Group

I am interested in purchasing several NEWT SDKs for something a lot more
reasonable than Chameleon's price of $500 a pop.  If you have one or
more for sale please contact me by mail.
 
-- 
Will Estes		Internet: westes@netcom.com
From: dwright@u.washington.edu (David Wright)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: IMAP client for Windows?
Date: 7 Oct 92 17:01:54 GMT
Article-I.D.: u.1992Oct7.170154.27742
Reply-To: dwright@u.washington.edu
Organization: University of Washington

Are there any IMAP clients for Windows (cf. Mailstrom  
for the Macintosh)?  Specifically, this would allow  
access (via TCP/IP) to unix mail residing on a  
university mainframe, and ideally would provide  
background polling of the remote mailbox.  Commercial  
software OK, as long as it doesn't require using an   
intermediate, non-TCP gateway.   

-- David Wright
Univ. of Washington SM-46
Seattle WA  98195
dwright@u.washington.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: westes@sti.com (Will Estes)
Subject: Packet Driver For WD Elite16 in Promiscuous Mode
Organization: Mail Group
Date: Thu, 15 Oct 1992 02:40:48 GMT

Does anyone know of an ftp source for a packet driver for the SMC
Elite/16 combo card that runs in promiscuous mode?

-- 
Will Estes		Internet: westes@netcom.com
From: ayman@eecs.umich.edu (Ayman I. Kayssi)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Reading mail from a PC, over a TCP/IP link to a unix host
Date: 13 Oct 92 13:43:38 GMT
Organization: ACAL, EECS, University of Michigan, Ann Arbor
X-Newsreader: TIN [version 1.1 PL6]

Steve Luzynski (sal8@po.cwru.edu) wrote:
: For a mail reader, look for POPmail. It requires only a packet driver to 
: operate. 

..or NUPop. It is a complete email package plus other TCP/IP goodies.
Get it from casbah.acns.nwu.edu:/pub/nupop
--
Ayman I. Kayssi                               |    ayman@eecs.umich.edu
EECS Department                               +------------------------
University of Michigan                        |          (313) 764-8033
From: ckelly@fox.nstn.ns.ca (Cameron Kelly)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Request for Info from Commercial Suppliers of TCP/IP software
Keywords: TCP IP Commercial Info
Date: 16 Oct 92 16:35:00 GMT
Article-I.D.: fox.ckelly.3.719253300
Organization: CF Meteorological & Oceanographic Centre - Halifax, NS

I am interested in hearing from any commercial supplier of TCP/IP software
for MS Windows. My e-mail address is ckelly@fox.nstn.ns.ca. I need to know 
about price, licenseing, compatibility with BC 3.0 & 3.1, sockets interface,
etc.

Thanks in advance

C Kelly