HDTenEightyP/NetNews huggingface dataset:
From: trier@slc6.ins.cwru.edu (Stephen C. Trier)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: fragmented packets with slip driver
Date: 29 Dec 1992 23:37:33 GMT
Organization: Case Western Reserve University, Cleveland OH (USA)
NNTP-Posting-Host: slc6.ins.cwru.edu
Keywords: slip packets fragment

In article <1hqhedINN986@usenet.INS.CWRU.Edu> trier@slc6.ins.cwru.edu (Look!  It's me!) writes:
>The MTU setting to worry about is not on your end -- it's on your SLIP
>server.  Get that MTU bumped up to something larger like 576 bytes, and
>you won't have problems.

OK, I could have said this better.  How about the following:

     The MTU setting to worry about is not on your end -- it's on
     your SLIP server.  Get its MTU bumped up to something like 576
     bytes, set your MTU to match, and you won't have problems.

The rest of what I said is right, at least until someone proves me
wrong.  :-)

-- 
Stephen Trier                      "We want to offer you a price that you
Network software type               just can't afford to take advantage of."
Case Western Reserve University         - Sales blurb from HSC Software
trier@ins.cwru.edu
From: trier@odin.ins.cwru.edu (Stephen C. Trier)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Macintosh News Group?
Date: 31 Dec 1992 13:32:37 GMT
Organization: Case Western Reserve University, Cleveland OH (USA)
NNTP-Posting-Host: odin.ins.cwru.edu
Keywords: TCP-IP, Macintosh, AFP

In article <C040C8.20p@ucunix.san.uc.edu> brettsch@ucunix.san.uc.edu (Steve Brettschneider) writes:
>#1	Does anyone know of a news group just like this one, only for the
>        macintosh?  I do a lot of work in which I use TCP/IP to move data
>        in between Mac's and PC's

No, there is no Mac-specific TCP group.  You can put TCP-on-Macs questions
in comp.protocols.tcp-ip or comp.sys.mac.comm, though such questions can
also be found in comp.protocols.appletalk.

Ed Vielmetti suggested a comp.protocols.tcp-ip.mactcp about a week ago,
but I haven't read news.groups recently enough to know how the discussion
is proceeding.

>#2 (MAC)I've heard a little about something called AFP.  It's supposedly
>	a program that lets you mount volumes across a net like NFS.  Does
>	anyone have _ANY_ information that could give me a clearer
>	picture?

Yes, and you already have it.  AFP is the "AppleTalk Filing Protocol",
and its implementation from Apple is called AppleShare.  If you have
System 7, you have both an AFP client and server: the "AppleShare" icon
in the Chooser and the "Personal AppleShare" server built into the OS.
If you are still using System 6, you have only the client, the icon in
the Chooser.  In either case, read your manual for details.

There are also AFP implementations, both commercial and free, on non-Mac
platforms.

Questions about AFP and AppleShare belong in comp.protocols.appletalk.

-- 
Stephen Trier                      "We want to offer you a price that you
Network software type               just can't afford to take advantage of."
Case Western Reserve University         - Sales blurb from HSC Software
trier@ins.cwru.edu
Organization: Penn State University
Date: Wed, 23 Dec 1992 10:38:21 EST
From: Christopher Sacksteder <CJS@psuvm.psu.edu>
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Winsock available?

In article <8ik3VB1w165w@cybernet.cse.fau.edu>, tbenham@cybernet.cse.fau.edu
(Tom Benham) says:
>
>I tried to FTP ftp.uu.net but the connection was refused.
>Any other ideas?  By the way, thanks.

There are several versions of the document at microdyne.com, some of
which I just got (slowly).  A Windows help file was quite good looking.
The .ps file (postscript) printed nicely (72 pages).
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: slewis@cbnewsm.cb.att.com (scott.b.lewis)
Subject: IBM TCP/IP for OS/2 Lanman 2.1a
Organization: AT&T
Distribution: usa
Date: Mon, 21 Dec 1992 23:34:44 GMT
Keywords: OS/2 Windows Lan Manager DOS IBM Microsoft

Does anyone have any experience with running IBM's TCP/IP for
OS/2 (including nfs add-on) on an OS/2 (1.3) machine that is
also a Lanmanager 2.1a server?  How can IBM's tcp be used
successfully over NDIS?  Any info on the config changes needed
to make this work would be appreciated. 

Also, assuming that I can get the ibm tcp working with lanman,
will the lanman server be able to share nfs mounted drives?  Any 
experiences would be helpful.

Please reply to slewis@hound.att.com.

Thanksinadvance,

Scott

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: gt@rundart.demon.co.uk (Giles Todd)
Subject: Re: ka9q terminal emulation?? 
Distribution: world
Organization: Rundart Limited
Reply-To: gt@rundart.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Thu, 24 Dec 1992 00:54:39 +0000

In article <BzMo4C.347@csn.org> ben@teal.csn.org writes:

>Is there a termcap entry which can be used with the ka9q
>network operating system (NOS) telnet program?  My experience
>using it to login to Unix systems indicates that it isn't
>a vt100 emulator.

There's a vt102 emulator program which works with KA9Q available for
anonymous ftp from ftp.demon.co.uk:/pub/ibmpc/DIS/vt102.zip.  No special
termcap entries needed.

Three caveats:

1) DR-DOS's console driver bypasses it unless you install it as a full
   device driver.  Works fine as a removable TSR with MS-DOS.
2) Auto line wrap doesn't work properly.  I must fix this.
3) No function keys.  If you want them then you will have to add them
   yourself.  My standard rant on the evils of function keys is
   available separately by email on request.

Source is included.

Giles.
-- 
Giles Todd                      gt@rundart.demon.co.uk (Internet)
Rundart Ltd                     Demon Internet Services
Voice: +44 925 33472            PGP 2.0 public key available.
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: FTP packet driver spec.
Date: 29 Dec 92 16:42:19 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    Does anyone know where can I get a copy of the Ethernet FTP packet driver
    spec(preferable via e-mail or ftp)...

V1.09 of the Packet Driver Spec is (like the NDIS and WinSockAPI specs)
available for anonymous FTP from vax.ftp.com.  V1.10 is still on hold,
pending resolution of how to do PPP, ISDN and friends.

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
From: cagleip@ETSUODT.ETSU.EDU (Cagle PCIP-L account)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: PS2/70 with Assante Ethernet & WFW
Date: 26 Dec 92 22:30:11 GMT
Distribution: world
Organization: The Internet

I have two PS2 Model 70's with Assante ethernet cards that I am trying to
get working with Windows for Workgroups. These cards emulate NE2000 cards.
We are using them in a 10 based T network. The machines work fine using
packet drivers and public domain TELNET's. They also work using the
protocol stack that Windows for Workgroups installs if you add DIS_PKT.DOS
and make the appropriate changes to PROTOCOL.INI. In the latter case,
the public domain TELNET's work fine until you start Windows. Once windows
starts the Ethernet board appears to be busy. On the FILE MANAGER menu,
you see your Workgroup name and you see your machine but you cannot see
other machines. Other machines cannot see your machine.

Any ideas would be greatly appreciated.

Michael R. Cagle
cagleip@etsuodt.etsu.edu
903-886-5421
Data Processing Services
East Texas State Univerity 
Commerce, Texas 75429
From: ALB@celio.uvm.edu (Allan Bazinet)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: RARP support for tcp/ip lanman from microsoft
Date: 23 Dec 92 13:35:36 GMT
Reply-To: alb@celio.uvm.edu
Organization: University of Vermont

> >Don, RARP is not as well designed as BOOTP.  I'd look for a BOOTP solution
> >before RARP.

> 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.

Doing BOOTP here for ~600 client machines from an RS/6000 server.
Crossing 2 Cisco AGS+ routers in the process doesn't pose a problem.
One must ensure to set the default ip-helper address for the Ciscos
to the address of the server, or a subnet broadcast (we have a few
servers on the same subnet) in our case.

  ----------------------------------------------------------------
    Allan L. Bazinet, Computer Operations, University of Vermont
      alb@celio.uvm.edu   alb@uvmadmin.uvm.edu   (802)656-8785
  ----------------------------------------------------------------
From: markp@cranham.cc.earlham.edu (Mark Pearson)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Ph client for DOS ...
Date: 23 Dec 92 22:34:36 GMT
Reply-To: markp@cranham.cc.earlham.edu

In article <david.hoisve.133.725133135@UUSERV.CC.UTAH.EDU>  writes:
}Does anyone have a great PH (CSO NameServer) client for DOS?
}
}Thanks in advance...
}
}-- Dave.
}David Hoisve
}University of Utah Computer Center
}HOISVE@CC.UTAH.EDU

It's incorporated into Nupop PC mailer available from acns.nwu.edu in  
pub/nupop. It's an excellent mailer that also has Webster support.

--
Mark H Pearson	            Coordinator of Academic Computing
Earlham College, Richmond, In 47374
regular e-mail: 	markp@yang.earlham.edu
NeXT mail     : 	markp@cranham.cc.earlham.edu	
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tbenham@cybernet.cse.fau.edu (Tom Benham)
Subject: Winsock
Organization: Cybernet BBS, Boca Raton, Florida
Date: Wed, 23 Dec 1992 22:22:05 GMT

I've gotten an explanation as to why Winsock mackes sense.
I also found out IBM is shipping support for it in the DOS
product next month.  So I guess that aswers many of my 
questions.  Now I need to read the doc.  Thanks to all.

Tom Benham
From: cparker@centerline.com (Charles Parker)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: WinSock & SLIP, any thoughts ?
Date: 24 Dec 92 15:59:11 GMT
Reply-To: cparker@centerline.com
Organization: CenterLine Software
NNTP-Posting-Host: 140.239.2.37

Does anyone know how those of us doing the 
SLIP8250.COM -> pktint -> WinQVT 

thang are going to be able to appreciate the WinSock 
revolution? eg.

SLIP????.COM -> ... -> WINSOCK.DLL -> million&1 TCP apps

---
---------------------------------------------------------

Charles Parker			  Phone.(800) 669 9165
Technical Support			(617) 498 3321
CenterLine Software, Inc.	    Fax.(617) 868 6655

                                       cyberspace
momma, don't let yer children grow up to be ^ cowboys ...
---------------------------------------------------------
From: system@SPIKY.RSINET.TN (SYSTEM)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ka9q help.
Date: 22 Dec 92 14:59:33 GMT
Distribution: world
Organization: The Internet

Hello,
Please can you tell me where can I find a doucumentation about the ka9q
ip router ? (how configure it in order to have a small PC lan).
any documentation about the ka9q will be useful.
any example of ka9q configuration will be useful too.
your help will be very appreciated.
best regards.
   Mourad.
--------------------------------------------------------------------
   Zouari Mourad                          // Phone : (216-1) 799-293
Institut Regional Des Sciences           //  Fax   : (216-1) 787-827
Informatiques et des Telecommunications //   Mail Drop :
(I.R.S.I.T)                            //      B.P. 212
                                      //       Cite Mahrajene
                                     //        1082 Tunis
Internet : zouari@spiky.rsinet.tn   //         TUNISIA
Bitnet : zouari@TNEARN.bitnet      //
--------------------------------------------------------------------
 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jallard@microsoft.com (James 'J' Allard)
Subject: Re: Winsock available?
Date: 18 Dec 92 18:02:26 GMT
Organization: Microsoft Corporation

In article <VuoXVB1w165w@cybernet.cse.fau.edu> tbenham@cybernet.cse.fau.edu (Tom Benham) writes:
>jallard@microsoft.com (James 'J' Allard) writes:
>
>> 
>> Windows Sockets is an API specification. A TCP/IP vendor implements the API
>> support via a DLL named "winsock.dll" with characteristics specified in the
>> document. Many vendors are planning support of the Windows Sockets API with
>> their TCP/IP implementations. Since I have seen postings from most of these
>> 
>
>How is Windows Sockets different than Berkeley Sockets and why do
>we need it?  How can one obtain doc?

Windows Sockets is based on Berkeley sockets, but includes "Windows
friendly" extensions. There were 3 major motivating factors behind
the effort:
 - Windows-based TCP/IP applications vendors were sick of writing to 
   n different sockets interfaces and shipping "shims" for their 
   software to run over them all.
 - Stack vendors were sick of getting applications vendors to write
   to their particular API
 - Microsoft was developing Windows NT and thinking about what 
   transport interface to use for TCP/IP.

That said, about 20-30 companies got together at Interop and hammered out
the details of a "Windows friendly", Berkeley-based API set for accessing
TCP/IP stacks. At Interop this year, many of the companies were offering
technology demonstrations showing their wares interoperating with multiple
stacks. Since the API is offered as a DLL (as opposed to a staticly linked
library), the API offers binary compatibility for applications developers.
Each vendor writes a DLL that talks with their stack, and an application
vendor writes to the single API. It's a big win for everyone involved.

Pick up the specification on either microdyne.com or vax.ftp.com. The
current (published) version is 1.0c, the current (draft) version is 1.1.
We anticipate that 1.1 will be published in either January or February.
Comments should go to winsockapi@microdyne.com, mailing list additions to
winsockapi-request@microdyne.com. I think the specs live in /winsockapi
directories on both systems.

-- 
_______________________________________________________________
J. Allard                                 jallard@microsoft.com
Program Manager of TCP/IP Technologies    work: (206)882-8080
Microsoft Corporation                     home: (206)860-8862
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jsbus@netcom.com (JSB Corp)
Subject: Winsock
Summary: commercial product supports berkeley sockets and winsock
Keywords: vsl winsock jsb
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Wed, 23 Dec 1992 23:49:19 GMT

>trier@slc6.ins.cwru.edu (Stephen C. Trier) writes:                         
                                                                            
Tom Wallace                                                                 
>trier@slc6.ins.cwru.edu (Stephen C. Trier) writes:                         
                                                                            
>> Windows Sockets is for Windows while Berkeley Sockets is for BSD Unix.   
>> There are some significant differences caused by the different OS archi- 
>> tectures, but the spirit is meant to be the same.                        
(12 lines removed)                                                          
                                                                            
At the risk of treading into the grey area of commercial posting,           
Windows developers should note that there is a product called               
Virtual Socket Library (VSL) that uses Berkeley Sockets calls               
to talk, not only to Windows Sockets                                        
compliant TCP/IP's, but most of today's popular networks as well ...        
with one common API. Rather then use newsgroup space to let you             
know the details, you can contact:                                          
                                                                            
Tom Wallace                                                                 
tomwa@jsbus.com
JSB Corporation - 408-438-8300 ext 209
From: tom@wcc.oz.au (Tom Evans)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA Telnet flooding problem
Date: 30 Dec 92 07:29:41 GMT
Organization: Webster Computer Corp, Melbourne, Australia

Apologies if this is an old question that has been beaten to death
previously - this is my first time in c.p.tcp-ip.ibmpc (and I did
look back in all prior postings I could find before sending this).

I'm running NCSA Telnet 2.3.05 on a 50MHz 486 running MSDOS 5.0 and
Windows 3.1 (same problem under either), with the Packet Driver "method" 
on an NE2000 clone.

The problem. I'm seeing this when I FTP data FROM the PC TO the other
computer (Sun 3/50). Nomatter what I set "retrans" to, the
retransmit time (as shown using a packet-monitor) seems to be about
TEN milliseconds or less, even when I set it to really large numbers
(like 500 * 18ms). This is overloading the poor machine I'm trying
to send data to.

Suspiciously, nomatter what I set rwin and maxseg to, the advertised
window is always 512 - is this a related problem?

FTP FROM the Sun 3/50 TO the PC blisters along at about 74k/second .
FTP from the PC to a faster Sun (a 3/60) works too, so people with
fast hosts may not be noticing this problem.

Please mail any responses, including where the FAQ is if there is one.
Thanks.

========================
Tom Evans  tom@wcc.oz.au
Webster Computer Corp P/L, 1270 Ferntree Gully Rd Scoresby, Melbourne 3179
Victoria, Australia 61-3-764-1100  FAX ...764-1179  A.C.N. 004 818 455
From: system@SPIKY.RSINET.TN (SYSTEM)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: signoff
Date: 28 Dec 92 14:14:43 GMT
Distribution: world
Organization: The Internet

please can you tell me how to unsubcribe from this list PCIP.
Newsgroups: comp.protocols.tcp-ip.ibmpc,ucs.networks
From: hughes@logos.ucs.indiana.edu (larry hughes)
Subject: networking or politics?
Organization: University Computing Services News
Date: Wed, 23 Dec 1992 21:01:45 GMT

For a good time, those of you who use NCSA or Clarkson Telnet,
try using the telpass program to add a user with a password
of "quayle96" (minus the quotes, must be in lower case).

This string checksums to 0 (modulo 256), and encrypts to the 
string "quayle96 !". 

Disclaimer:  I'm sure the encryption bug was an honest mistake. I 
don't believe it adds credence to the oft-heard statement that 
"politics is the 8th network layer."  

Regarding the checksum value itself, well, draw your own conclusions.

A very sharp person at our Support Center, Dawn Hewitt, discovered
this anomoly.  Knowing Dawn and her sense of humor, I don't belive
it's possible to deduce her political affiliations from her choice 
of passwords.  :-)

 //==================================================================\\
||      Larry J. Hughes, Jr.       |        hughes@indiana.edu        || 
||       Indiana University        | "The person who knows everything ||
||  University Computing Services  |        has a lot to learn."      ||
 \\===================================================================//

Newsgroups: comp.protocols.tcp-ip
From: erick@sunee.uwaterloo.ca (Erick Engelke)
Subject: Re: PCS WITH DUPLICATE TCP ADDRESSES
Organization: University of Waterloo
Date: Tue, 22 Dec 1992 21:15:02 GMT

> ccg@tcdsp1.mmm.com ("Charles Ganzhorn") writes:
>BOOTP is major bad idea.  You have to configure your routers to pass the
>silly stuff 'cuz you won't necessarily have a load host in all subnets.

Yes, like that silly DNS idea where we had to add nameservers just
to support names.  Here we have to add one configuration parameter
to a router for each network.  What a large price to pay for 
automatic configuration of all the machines on that subnet.

>Also, if your BOOTP logs all requests, a station whose download doesn't
>get satisfied typically requests every five seconds and ends up filling
>up the logs on systems.

So your error logs, if turned on, will show a broken system.  That is
a problem because it makes it so much harder to ignore a system 
which is unable to boot up.

Get with the program, and Merry Christmas.

Erick

-- 
----------------------------------------------------------------------------
Erick Engelke				 	            WATTCP Architect
erick@development.uwaterloo.ca     TCP/IP was easy but i still can't work VI
From: apollo@buengc.bu.edu (Doug A. Chan)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: PC-NFS SLIP and telnet problem
Date: 30 Dec 92 18:59:01 GMT
Reply-To: apollo@buengc.bu.edu (Doug A. Chan)
Followup-To: comp.protocols.tcp-ip
Organization: College of Engineering, Boston University, Boston, MA, USA

In article <1992Dec23.043717.1680@colorado.edu> garnett@refuge.Colorado.EDU (Santiago de la Paz) writes:
>In article <105528@bu.edu> apollo@buengc.bu.edu (Doug A. Chan) writes:
>>Whenever I try to telnet to a host, it just hangs there...
>>What is wrong with telnet?
>One of the primary reasons why a telnet attempt like this will hang is if
>the remote host cannot reverse-lookup the IP address of the host you're 
>coming from.  Make sure that both hosts are forward and reverse-mapped
>(just for thoroughness, doncha know) if you're using DNS, or that they're
>both in your machine's hosts files.

It wasn't any host/IP address problem (FTP, ping, nfsping, NFS, finger all
work fine!)  The host table is okay... just telnet was broken.
I turned on all of PC-NFS' telnet debugging and it got stuck during
the initial negotiation (after it has established a connection with
the host).  Sending a break or 'are you there' from the telnet prompt
sometimes forces the host's login messages to appear but that's about
it... (I still can't type anything to log in)
I bought Advance Telnet (an add-on product to PC-NFS) and it solved the
problem.  I don't know why the standard telnet program that comes with
PC-NFS doesn't work correctly over SLIP (it works fine over ethernet...).

-Doug
apollo@buengc.bu.edu

Newsgroups: comp.protocols.tcp-ip