HDTenEightyP/NetNews huggingface dataset:
From: bob@comlab.gatech.edu (Bob Baggerman)
Newsgroups: comp.os.os2.networking
Subject: Re: lan manager
Keywords: does any version work under 2.0?!!
Date: 14 Oct 92 19:24:18 GMT
Organization: Georgia Institute of Technology

sip1@midway.uchicago.edu writes:
>LAN Manager server apparently will not work under OS/2 2.0.  It comes
>with its own version of OS/2 1.3 which you'll have to use.

Not entirely true.  The LAN Manager server indeed has not been ported to
OS/2 2.0.  The version of OS/2 that comes with LAN Manager 2.1 is a
version of OS/2 1.3 that has been optimized for use in a server role.
I think that primarily means a high speed, 386 specific file system.
But it is my understanding (haven't tried it yet!) that LanMan server 
will work with OS/2 1.2, and IBM and other OEM versions of OS/2.  In fact,
LanMan 2.0 did not include OS/2.  You had to purchase it seperately.  We 
used IBM OS/2 1.2.

Bob


--
Bob Baggerman                         !  bob.baggerman@gtri.gatech.edu
Communications Laboratory             !  bob@comlab.gatech.edu
Georgia Tech Research Institute       !  qseclrb@prism.gatech.edu
Atlanta, GA  30332  USA               !  404-894-3525
Newsgroups: comp.os.os2.networking
From: backman@vaxeline.ftp.com  (Larry Backman)
Subject: Re: FTP's TCP/IP for OS2 - When?
Nntp-Software: PC/TCP NNTP
Organization: FTP Software, Inc., Wakefield, MA
Date: Mon, 12 Oct 1992 13:27:19

In article <1992Oct10.055145.13891@gmuvax2.gmu.edu> kbass@gmuvax2.gmu.edu (Ken Bass) writes:

 >> 
 >> Who do you contact for easy to read documentation and automated install
 >> programs?

 Slam accepted. You contact me; I wrote the install. I reviewed the doc.
 You were saying?


 Larry Backman
 FTP Software
From: hamish@waikato.ac.nz
Newsgroups: comp.os.os2.networking
Subject: Re: Socket Numbers
Date: 9 Oct 92 09:39:09 +1300
Organization: University of Waikato, Hamilton, New Zealand

In article <ignacij.718564871@meishan.animal.uiuc.edu>, ignacij@meishan.animal.uiuc.edu (Ignacy Misztal) writes:
> geurin@texasex.nosc.mil writes:
> 
> 
>>Howdy-
> 
>>By what method does IBM TCP/IP decide when to reset socket numbers?
>>Is there a way to manually reset the socket numbers?

> 
> I reported the first problem to the IBM service dept. On my PC, the number of
> open secokets, as reported by netstat -s, is growing. It was 120
> yesterday and it is 160 today. Most of the sockets are in the CLOSE-WAIT state, although some are CLOSED. My PC swaps despite having 16 M RAM.
> Could it be due to memory absorbed by the sockets?

I concur. I first found this problem several weeks ago when trying to use the
tcpip's LPQ and LPR multiple times to an LPD daemon a friend of mine was
writing for netware 386. At forst I though it was netware, not closing the
connection, but it actually seems to be ibm's tcpip that is holding the socket
open for a while, and then closing it. I don't know how long it stays open for,
The same thing has hit me doing multiple LPR's to a vax and a sun workstation,
and leaving it overnigh cleared the sockets.

Sounds like IBM needs to overhaul its tcpip a fair bit. Anybody have the source
and want to comment on the job they've done? It must be code they got from
somewhere, they use Berkley headers in the programming toolkit, and the tcpip
stack itself seems to have some of the same bugs that HPUX has in its tcpip.

> 
-- 
==============================================================================
|  Hamish Marson   <h.marson@waikato.ac.nz>                             OS/2 |
|  Programmer (n/5), School of Computing and Mathematical Sciences           | 
|  University of Waikato,                                                    |
|  Hamilton, New Zealand.                                                    |
|Disclaimer:  Anything said in this message is the personal opinion of the   |
|             finger hitting the keyboard & doesn't represent my employers   |
|             opinion in any way. (ie we probably don't agree)               |
==============================================================================
  Q. If Nuclear Tests are so safe, why don't the French do them under Paris?
Newsgroups: comp.os.os2.networking,comp.os.os2.misc
From: regy106@csc.canterbury.ac.nz (John, Registry)
Subject: Please, Driver for SMC card
Organization: University of Canterbury, Christchurch, New Zealand
Date: Mon, 12 Oct 1992 21:00:02 GMT

Hi,
	Again I ask, Please can anybody tell me where to get drivers
for the SMC ethernet card for th os/2 2.0 novell requestor?
Thanks John
Newsgroups: comp.os.os2.networking
From: rjberke@berke.itg.ti.com (Richard Berke)
Subject: Telnetd, terminal types
Organization: Electronic Communications
Date: Thu, 8 Oct 1992 22:58:14 GMT

Here's what I've found out....

IBM negotiates terminal type with the incoming session.  IFFFFF the type is 
one of exactly ANSI or VT100, then a usable DLL is invoked by OS/2 for the 
session.IF the incoming session negotiates any other type, then only DUMB is 
used.

The TERM-IS.EXE program in TCPIP\BIN  reports faithfully the string that was 
offered by the incoming session and was accepted by OS/2.  It does NOT 
indicate the DLL being used.

IBM OS/2 Telnetd does **NOT** apparently implement the RFC 1060 terminal 
type names.  VT100's are actually known there as DEC-VT100.  IBM uses the 
shortened colloquial name, with no additional aliasing (as would a UNIX /etc/
termcap file), as the name of a DLL file to be called. Period.   You can't 
even fake out the TELNETD.CMD program to force a VT100!  I've also tried 
renaming the DLL's to try to have VT100.DLL be used instead of DUMB.DLL.  No 
luck.  The incoming requested session blows up, rather than either establish 
as either of dumb or vt100.

A further problem with running, for example, an editor or custom program 
that expects function keys 1-12, is that a VT100 physical terminal only has 
PF1---PF4.  There seems to be zero effect caused by pressing other than f1-
f4, although those four do perform the PC analogous functions.

That's where I am so far.  It's frustrating.

Thanks for your interest.

Richard Berke   RBRK   Richard.Berke@lobby.ti.com  (214) 575-2828
Texas Instruments      Plano, Texas
-------------------------------------------------------------------------
Richard Berke   RBRK   Richard.Berke@lobby.ti.com  (214) 575-2828
Texas Instruments      Plano, Texas
-------------------------------------------------------------------------
From: dab6@po.CWRU.Edu (Douglas A. Bell)
Newsgroups: comp.os.os2.networking
Subject: Re: Cabletron OS/2 drivers
Date: 13 Oct 1992 17:54:09 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: dab6@po.CWRU.Edu (Douglas A. Bell)
NNTP-Posting-Host: thor.ins.cwru.edu


In a previous article, imj1@cunixa.cc.columbia.edu (Imad M Jureidini) says:

>
>Hi!
>I own a Cabletron Ethernet card, and I was wondering if it were possible to
>load the DOS packet driver I use somewhere in the config.sys, so that OS/2 and
>all my DOS boxes would be aware of it.  Or maybe I need a specific OS/2 driver
>to do that.  Does anyone have such a beast?
>Thanks for any info!


You can load the packet drivers in a single dos session, but os2 needs
ndis drivers, not packet drivers.  Once you load ndis dirvers, you can't
load packet drivers.  While it may be possible to write a virtual packet
driver interface, so that every dos session thinks it has a packet driver,
even though the actual requests are going through the ndis driver, this has
not been done yet.

The ndis drivers for cabletron cards are available via anonymous ftp 
from ctron.com.

You can get technical support by sending mail to support@ctron.com.
From: Jos.Vos@f1.n100.z60.wlink.nl (Jos Vos)
Newsgroups: comp.os.os2.networking
Subject: Kermit binary for OS/2 wanted
Date: Tue, 13 Oct 1992 09:54:46 -0100

Organization: Bull, P.O. Box 22859, NL-1100 DJ Amsterdam, The Netherlands

Can anyone tell me how to get a Kermit binary for OS/2, if possible
including documentation?
Any pointers are welcome: mail-servers, FTP-sites, etc.

Please MAIL responses to me, as I don't read *.os2.* groups frequently.
Thanks.

-- 
--    Jos Vos <jos@bull.nl>   (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos)
--    Bull Nederland NV, Product Support Unix, Amsterdam, The Netherlands

Newsgroups: comp.os.os2.networking
From: gao@watson.ibm.com
Subject: Re: NFS from OS/2 to UNIX? What syntax?
Date: Thu, 08 Oct 1992 14:52:06 GMT
News-Software: IBM OS/2 PM RN (NR/2) v0.14 by O. Vishnepolsky and R. Rogers
Reply-To: gao@watson.ibm.com
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM T.J. Watson Research Center

In  <cntz30@rpi.edu>  assela@aix.rpi.edu (A. Andre Asselin) writes:
> naughton@chinet.chi.il.us (Thomas Naughton) writes:
> >   I ahve TCP/ip and NFS 1.2.1 (with CSD patches).  I want to
> >NFS mount my F: drive (cdrom) from my OS/2 box to my UNIX box.
> >I have exported the F:\ directory, but I can't seem to get
> >my UNIX box to mount it.  I am trying the mount command with the
> >syntax like:
> >   mount -F nfs -ro os2:F:\ /cdrom
> >but it doesn't seem to like the "os2:F:\" part very much.  Is
> >anyone else doing anything similar?  What should I try next?
> 
> Tom,
>    You can try using a forward slash (/) instead of the backward slash.
> That should help calm UNIX a bit, and the OS/2 NFS server will interpret
> it correctly.  You may also want to try moving the /cdrom to in front
> of the os2:f:/ part-- that part of the command line may be getting ignored.
> If you still have trouble, please post a followup note or email me.
> Good luck...
>        -- Andre Asselin  (assela@rpi.edu)

Or you can do the following way

    mount [......]  f:   /cdrom

if you export the entire F drive on your OS/2 system.

KeJia.
IBM, Watson
gao@watson.ibm.com
Newsgroups: comp.os.os2.networking
From: stein@sionext.uio.no (Stein Onsrud)
Subject: 3C527 NDIS Driver ?
Reply-To: Stein_Onsrud@siodata.uio.no
Organization: University of Oslo
Date: Thu, 15 Oct 1992 17:22:39 GMT

I would be happy to know that such driver exists !
From: jost@jake.prz.tu-berlin.de (Jost Weinmiller)
Newsgroups: comp.os.os2.networking
Subject: packet driver interface
Date: 15 Oct 92 15:29:58 GMT
Organization: TU-Berlin TUBKOM, Germany



hi, 
flame me, if this is the wrong group, 

i am looking for a source code, building an addressable interface
to a packet driver. 

i want to hand over packets from a higher layer to the
packet driver (got the driver already), have the driver
send the packets, grab the packets on the other end 
and hand them over to the receiving higher layer again.

sounds quite simple, but i just cant find the interface.

any pointers welcome. 

cheers
jost
-- 
jost weinmiller                
markelstrasse 41              
1000 berlin 41               
030/7933164
From: gkm@cbnewsh.cb.att.com (gary.k.mc nees)
Newsgroups: comp.os.os2.networking
Subject: Re: NFS Security (or lack thereof)
Date: 13 Oct 92 02:54:37 GMT
Distribution: usa
Organization: AT&T

In article <921012133407@minimillian.ftp.com> backman@vaxeline.ftp.com (Larry Backman) writes:
>In article <1992Oct11.090253.21863@netcom.com> badboy@netcom.com (Jay Keller) writes:
>
> >> has to do is set the UID and GID to anything he or she wants it to be, and 
> >> then mount anywhere in the Unix file system with read and write privileges.
> >> The DOS users, who now run the UID/GID flavor of FTP, Inc.'s IDRIVE, can
> >> (at least that is what it seems like to me, please tell me I'm wrong!).
> >> network..
> >> to blame the OS/2 and DOS clients?  Are these dumb questions?
> >> 
>NFS stands for No File Security :-).  It was really designed with Unix
>workstations in mind; and the with the concept that a person with access
>to NFS commands & files (mount, /etc/passwd, etc.) had already passed
>some sort of authentication, i.e. had logged into a UNIX host.  With this
>security paradigm, NFS RPC's typically contain a clear-text hostname &
>a UID/GID combination of the user who wishes access to something from that 
>host.  The server loosely authenticates access based on the hostname
>having access to the appropriately exported filesystem, and the UID/GID
>of that user having access to the file in question.
>
>This paradigm clearly falls apart with PC's which don't have either a
>concept of login, or a UID/GID.  There is a loose sort of authentication
>provided by PCNFSD, a server which runs in parallel with the NFSD server
>and provides a cheap mapping of a PC user's username password to a UID/GID
>which the PC user can then use in future NFS RPC's.  Most PC NFS vendors
>support PCNFSD security; IBM does not at this point in time.
>
>Larry Backman
>FTP Software

Doesn't the same security hole really exist in the UNIX world?
The only difference is that the UNIX machines are supposed
to be operated by a trusted person? Can't The person at a UNIX
box do the same thing he has super-user id? 

Gary McNees
From: Richard.Kooijman@dnpap.et.tudelft.nl (Richard Kooijman)
Newsgroups: comp.os.os2.networking
Subject: Beholder II announcement
Keywords: RMON, network monitoring
Date: 14 Oct 92 09:53:07 GMT
Organization: Delft University of Technology, Dept. of Electrical Engineering



                    __                __   
                   |  \              |  \  
                   |  |   .          |  |  
                   |__|       __     |__|  
                   |   \  |  /  \    |   \ 
                   |   |  |  |  |    |   | 
                   |___/  |  \__|    |___/    
                                |
                                |
                              _/


                Beholder - The Next Generation
                
                BOF session at Interop Fall '92
                 October 28th, 7:30pm - 9:30pm
              Moscone Convention Center, room 114
                         San Francisco
                  
                  
                  
The  Data  Network  Performance Analysis Project (DNPAP) group
likes  to  invite  you  to  our  Birds Of a Feather session at
Interop  Fall  '92,  October  28th,  from  7:30pm  till  9:30,
Moscone Convention Center, room 114, San Francisco.

We will present the successor of the 'old' Beholder:

Beholder - The Next Generation or Beholder II for short.


Features of Beholder TNG:

  - runs under OS/2
  - SNMP-able over UDP/IP or OS/2 named pipes
  - RMON compliant
  - modular design: collectors and viewers are 
    completely separated


Three short talks will be held on:

  - the history of the Beholder project
  - the RMON implementation in the Beholder
  - the technical details of capturing network packets 
    under OS/2
  
Also, some near future enhancements will be discussed.


We hope to meet you there,


The DNPAP group

  Jan van Oorschot
  Dirk Wisse
  Alfred Kayser
  Marc de Greeve
  Richard Kooijman

Beholder TNG mailing list: btng@dnpap.et.tudelft.nl


--
-- ir. Richard Kooijman ------------------ Email: R.Kooijman@ET.TUDelft.NL --
-- Intelligent Network Management Project (INEMA) ---------------------------
-- CARDIT, Delft University of Technology ------------ Tel: (31)-15-786209 --
-- P.O.Box 5031, 2600 GA Delft, The Netherlands ------ Fax: (31)-15-784898 --
Newsgroups: comp.os.os2.networking
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Peer-to-Peer
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Sat, 10 Oct 1992 02:32:42 GMT

In article <92281.172126MICHAELB@UCF1VM.BITNET> Michael Brunetti <MICHAELB@UCF1VM.BITNET> writes:
>What is the best method for Peer-to-Peer between:
>                      OS/2 v2 machine --- OS/2 v2 machine
>                      os/2 v2 machine --- DOS machine
>using NE2000 compatible NIC's.  Netware Lite? Lantastic? OS/2?
>Thanks.........

Right now, TCP/IP.  IBM's package is $130 for base services, academic
pricing.  For details, ftp over to ftp-os2.nmsu.edu, and grab the
announcement letter in /pub/os2/all/info.  FTP Software also has an
OS/2 version, as do other vendors.  (On the DOS side you can use just
about any TCP/IP package with NFS, like PC-NFS.  I'm less familiar
with driver support, though.)

On the OS/2 side you'll also need an NDIS driver.  These, too, are
available both with TCP/IP and, in the case of the NE2000, via
anonymous ftp from ftp-os2.nmsu.edu.

Artisoft is working on an OS/2 version of LANtastic.  Contact them to
see if you can participate in the beta program.

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
Dept. of Econ., Univ.   | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637       | Family Values Means a Job
Newsgroups: comp.os.os2.networking
From: ccewch@nuscc.nus.sg (Wong Chee Heng)
Subject: OS2 developer's CDs have no TCP/IP 1.2.1 ?
Organization: National University of Singapore
Date: Sat, 10 Oct 1992 06:20:22 GMT

Sometimes ago, I saw an announcement of the IBM's developer CDs. It said that
a copy of the TCP/IP 1.2.1 is included, I got them, but could find it,
can anyone tell me is it in the CD and where is it?

Thank you.

--
Wong Chee Heng
Systems Programmer
Newsgroups: comp.os.os2.networking
From: add@philabs.philips.com (Aninda V. Dasgupta)
Subject: 2 station Token-ring - problems with setting up
Summary: I don't want to buy a MAU!!!! How about a DTAU?
Keywords: Token-Ring, MAU, DTAU, Onan box, 9pin-to-9pin
Organization: Philips Laboratories, Briarcliff, New York
Date: Thu, 8 Oct 1992 13:50:50 GMT

I am trying to setup my own little token-ring with just two stations
on it.  Every vendor I talk to, wants to sell me a MAU. I have
just two stations and I know that I will never expand this
network, why should I have to buy a MAU? Even two port MAUs are
so expensive I don't want to touch them....

My question to Token-ring gurus is, can I use/get any one of the 
following?

- A Dual Terminal Access Unit or DTAU (People within IBM call it an Onan Box
  because it is made by Onan, Inc., but nobody seems to know how to
  buy one.) A DTAU serves two purposes.  One can connect it to a Token-ring
  wall outlet and then hook up two computers to its two ports, thus essentially
  expanding a single-port wall outlet to two ports.  But by flipping a
  switch one can use the DTAU to simply connect two stations and not hook the
  DTAU to any wall-outlet, thus having a two-station ring.  Does anyone know
  what I am taking about, know where I can buy one of these boxes, or have part
  numbers?

- A 9-pin to 9-pin cable that allows me to connect the two adapters on
  the two computers together?  Will such a cable work if I don't care
  about the fault detecting relays in a MAU?  (What else is a passive MAU
  good for other than the bypass-relays in it?)
  Any recommended vendors for such 9-pin to 9-pin (male to male) cables?
  I have tried BlackBox and Cabletron, didn't work.

- A Cheap 2-port MAU (within $250).  All the ones I have seen are way over
  my meager budget.

It's so hard to believe that setting up a simple two-station ring requires
the purchase of so much extra junk that I don't need (read: an 8-port MAU.)

Any help will be greatly appreciated.  Thanks in advance.
-- 
Aninda DasGupta   (add@philabs.philips.com)
Ph : (914) 945-6071    Fax : (914) 945-6552
Philips Labs\n 345 Scarborough Rd\n  Briarcliff Manor\n NY 10510
(Gas from Phillips Petroleum, Antacid from Phillips Medical, Lightbulbs from us)
Newsgroups: comp.os.os2.networking
From: scastill@nmsu.edu (Steve Castillo)
Subject: pmx and Patran or AVS
Organization: NMSU Computer Science
Distribution: comp.os.os2.networking
Date: Fri, 9 Oct 1992 14:58:06 GMT


I am running IBM's tcpip package version 1.2.1 with patches for pmx
and nfs.  I have a 50 MHz 486 with an ATI graphics Ultra and 16 Mbytes
of memory.  I am trying to use my pc as a local display for both
Patran 2.5 or AVS 3.0 running on remote workstations.  Patran 2.5 is
running on an HP 730 and AVS 3.0 is running on a Stardent GS1000.
Patran gives me an "unable to allocate enough colors" message even
though I am only using an terminal option with 16 colors on Patran.
AVS comes up on my display.  However, the x display boxes are black.
Anybody else trying these kinds of things?  Any ideas?  Any advice
would be greatly appreciated.  Thanks in advance.
--
*****************************************************************
Steve Castillo
New Mexico State University
Las Cruces, NM

scastill@nmsu.edu
(505)646-3214
Newsgroups: comp.os.os2.networking
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: NetWare Requester for OS/2 2.0 downloadable?
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Sat, 10 Oct 1992 02:34:33 GMT

In article <1992Oct8.011450.5783@nwnexus.WA.COM> markmc@halcyon.com (Mark McWiggins) writes:
>I need NetWare Requester for OS/2 2.0. Is there some BBS or archive
>site where Novell puts such things, or do I have to order it on disk?

Unfortunately it is not being made available from online services.
However, you can order it for $30 from Novell by calling 800-UPDATE1.
That number is good in the U.S.

Ask about the NetWare Workstation Kit Version 3.0 for OS/2 2.0.  It
should be out by now.

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
Dept. of Econ., Univ.   | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637       | Family Values Means a Job
From: assela@aix.rpi.edu (A. Andre Asselin)
Newsgroups: comp.os.os2.networking
Subject: Re: very poor ftp and nfs performance
Date: 9 Oct 92 04:53:23 GMT

backman@vaxeline.ftp.com  (Larry Backman) writes:
>In article <Oct06.232526.22220@engr.washington.edu> eliot@engr.washington.edu (eliot) writes:
[ problem description deleted... ]

>MY guess is that you are losing because of either of 2 things; potentially 
>your NFS is doing 8K RPC writes and the server is not receiving all 6
>IP fragments of the 8K RPC, causing you to retransmit over and over and
>over...

>Does a network trace show the same RPC (look at the XID field) being sent
>again & again?  Are you going through a router to the file server?

>Second possibility; you are doing 1K writes as opposed to 8K writes and
>running into an inhenrent NFS performance limitation, that writes must
>be synchronous; i.e. that data *must* be on disk before the RPC is completed.
>Due to the joys of Unix disk IO, writes take time; a 10K bytes/sec. number
>is consistant with what a RS6000 will do on 1K writes.  In this case; you
>should reconfigure your write size up to 8K and watch your performance
>increase..

>Good luck.  Maybe someone from IBM can shed further light on this..

Well, I'm not from IBM anymore, but I'll give it a shot...  

First, If you could post your configuration, it would really help track down
the problem.  Things to include are: your network configuration (i.e.
network type(s), # routers in between, etc.), the command you are using
to mount the RS6000, any options you pass to NFSCTL (or NFSSTART), and
anything else you think may be useful.  Also, is the performance bad
just between those two hosts?  If you go from OS/2 to a different server,
what happens?  How about from a different client to the RS6000?  How
about if you reverse them, and use the FTP client on the RS6000 and FTP
server on OS/2?  (The same questions apply to NFS as well).  Also, what is
the round trip time for packets (as reported by PING)?
   What Larry mentioned as the first possibility is probably unlikely unless
you changed the defaults of the NFS client (FYI, the NFS client defaults to
4K RPC packets and 4 BIODs that are used only to read; writes are inline).
   What you are describing sounds pretty strange, since it affects both
NFS and FTP-- it kind of seems like it's more of a network problem than
a specific protocol problem.  Does it affect any other programs, such as
Telnet for example?
   If you'd like to post the results of these tests, I'll give you a hand to
help track down the problem.  Good luck...
        - Andre Asselin         (assela@rpi.edu)