HDTenEightyP/NetNews huggingface dataset:
Via:      UK.AC.HW.CLUST; 14 APR 92 12:40:51 BST
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 12:40:00 BST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         CHRIS GRAY <CENCTG@VAXB.HERIOT-WATT.AC.UK>
Subject:      Running Windows 3.0 over ODI

I am installing Windows 3.0 and ODI (latest version, ie. from ODIUP5.ZIP) and I
was wondering if there are any problems or tricks that I should know about
running Windows over IPXODI/NETX rather than over standard SHGENned IPX/NETX.

 ============================================================================
| *  CHRIS GRAY  *  Network Services Programmer  *  CENCTG@UK.AC.HW.CLUST  * |
|----------------------------------------------------------------------------|
| *  Computer Centre, Heriot Watt University, Edinburgh, UK *                |
 ============================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 10 Apr 1992 15:26:40 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Jim O'Brien <JOBRIEN@UMES.BITNET>
Subject:      Weird Problem Cont'd

Yesterday, Thursday 4/10 I posted a fairly long msg about our NW server
crashing when I brought up PCBridge which got us on the internet.

I got one reply, suggesting that I off load Pserver and use set minimum
packet recieve buffers = 200.  Well I unloaded pserver set min pkt rec buf =
200 and set max pkt rec = 500.  The server still crashed in about 35 minutes.

I did notice in Monitor that I was getting No ECB available errors.  Not many,
last count before crash was 5, but at the same time as this,  the following
were incremented also:

RxShortPktErrorCount
BusReadErrorCount
E16ODIFResetCount
UnsupportedFramePacketCount

Each of the above mirrored the No ECB error count.  When I brought the
server back up,  and PCBridge was still up, I quickly received a No ECB
error.  I had users on thhe net show I shut down the bridge.  That was
an 1.5 hours ago and it has crept up since.

I was also using netwatch to see what was happening,  I didn't see anything
that seemed wrong, but who knows.  One of the WS displayed an error:
UMESCSNW1: error finding router

The server is an EISA server and the manual say that it may need more than
default min pkt rec buffers, but I think I've covered that one.

I'd appreciate any suggestions. Thanks.

----------------------------------------------------------------------
Jim O'Brien  -  Network Manager     | BITNET:    jobrien@umes
University of Maryland Eastern Shore| INTERNET:  jobrien@umes.umd.edu
----------------------- Safe Diving !! -------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:         UK.AC.LUT;  8 APR 92 13:42:18 BST
X-Mailer:    ELM [version 2.3 PL0 (LUT)]
Newsgroups: bit.listserv.novell
Date:         Wed, 8 Apr 1992 13:41:57 BST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         OBSchou <O.B.Schou@LUT.AC.UK>
Subject:      Re: Problem with RARPSERV.NLM - kills TCPIP

(Pat on the Back time)
Brian Meek writes:

> Sorry to have to acknowledge that the RARPSERV.NLM available on
> sjf-lwp.novell.com simply doesn't work properly when IP forwarding
> is enabled.
>
> About all I can do at this point in time is update the readme.txt
> with a warning about the anomaly.
>
> This NLM was built quickly and was not intended for commercial
> distribution.  I made it available in a rather clandestine fashion
> because it is known to be useful in some circumstances.
...

So we fell into a small hole with RARPSERV.   I for one am very glad of
the interaction of Novell to/from "users".  Clandestine release, maybe,
but it helped us in our eventual decision to dive headlong into (!?)
providing LWP tied closely with Netware as a campus service.

Keep it up Novell.  Special praise to Brian Meek and Janet Perry for
all the help they have (indirectly) given this site.

Bertil.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 10 Apr 1992 15:27:33 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Jeff <jeff@IUS.INDIANA.EDU>
Subject:      Unsubscribe.
X-To:         novell%suvm.bitnet@uga.cc.uga.edu

         What is the address I send to for
         subscribing/unsubscribing/getting info on this list server?

         Thanks,
         Jeff
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 10 Apr 1992 10:23:46 +0000
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Comments:     Warning -- original Sender: tag was ALIEN@ENAPSTG1
From:         SMANDAKO@ENAPSTG1.BITNET
Subject:      Re: Sitelock security and station restrictions

On  Thu, 9 Apr 1992 10:15:30 GMT+1000 Chris Owen <CHRIS@CBE.QUT.EDU.AU>
Write:
>
>Sitelock v. 3.20 and earlier may a security problem due to creating a
>SUPERVISOR equivalent bindery object with no password.  Anyone with
>the right tools can log in as the object and gain full access to the
>server.  The security hole shows up when running Novell's
>SECURITY.EXE.
>
>Station restrictions can be used to limit logins to the fileserver
>running the NLM.  Because the supervisor equivalent object is not a
>user object, SYSCON and NETCON cannot be used to do this.
>
>To remedy the situation, I wrote a simple program, STATREST, which can
>be found on risc.ua.edu in pub/network/misc/statrest.zip.  STATREST is
>used from the command line to add station restrictions to an object
>of any type (not just a user object), and prevent it from logging in
>from anywhere other than defined station addresses, so it will be
>useful for other applications too.  Note that although it can be used
>to add restrictions

Hello Chris:
I'm interested in the program that you wrote, please can you send it to me?

Thanks
Sergio Mandakovic
Newsgroups: bit.listserv.novell
From: barleben@sun1.ruf.uni-freiburg.de (Friedrich Barleben)
Subject: Castelle Fax-Server and Novell net
Organization: Rechenzentrum der Universitaet Freiburg, Deutschland
Date: Mon, 13 Apr 92 16:54:24 GMT

The Castelle fax server looks like a nice solution if you are
working in a Netware enviroment with PCs only. We have
a mixed network with Pcs, Macs and Suns and I would really
like to know if Mac and Sun users can send/receive faxes 
as well. Anyone out there who has done this successfully?

Hoping,

Friedrich Barleben

-- 
Internet:    barleben@sun1.ruf.uni-freiburg.de  | Fiete Barleben        
CompuServe:  100020,2345                        | Zasiusstrasse 35
phone/fax:   +49-761-73751                      | W 7800 Freiburg
BTX:         *0761702503#                       | Germany   
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 06:58:36 -0500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Charles Finney <cfinney@UMAXC.WEEG.UIOWA.EDU>
Subject:      Re: How Much memory per unit diskspace?
X-To:         NOVELL%SUVM.BITNET@uga.cc.uga.edu

The most obvious usage shows up in the allocation of directory blocks and
their usage of directory slots.  If DOS is the only name space in use on
a volume, creation of a directory cause a directory block to be allocated
with 32 file entries available, of which one is in use by the directory
name.  This operation consumes one directory block worth of memory (4k).

Presuming four name spaces are defined for a volume, DOS, Mac, Unix, and
HPFS.  Creation of a directory/folder will again consume one directory block
with 32 file entries, however, now the directory name uses 4 of the available
directory slots leaving 28 available for files.  Creation of files will
consume 4 directory slots at a whack, meanint that only 8 files per directory
block are available.  Netware v3.11 has a maximum allocation of 65535
directory blocks giving about 2 million file slots with 1 name space or
500,000 with 4 name spaces.  The memory requirements to cache the directory
structure is simply the number of directorys as given in VOLINFO/32*4096.

The above implies that the maximum number of directories per volume is
65535 at which time only 31, 9, or 7 files per directory could be created
depending on the number of name spaces being supported.

     Charles E. Finney                    charles-finney@uiowa.edu
     Network Services Group               (319) 335-5399
     University of Iowa

           "Safety!  Where is that to be found?  I am obliged to fight
            for my own life everyday."       Ras Michael
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: UNIVERSIDAD DEL NORTE
Newsgroups: bit.listserv.novell
Date:         Sat, 4 Apr 1992 11:55:54 COL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         JPEREZ@UNORTEVM.BITNET
Subject:      9370-80 in a netware token-ring network

Hi Friends,

I have a 9370 model 80 with a token-ring card (6134) and I need to connect
it to a netware token-ring network.

Where can I find information about it ?. Any list,document,book ?


Thanks in advance.

Julio Cesar.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Original_To:  JNET%"novell@suvm"
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 06:28:00 PST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         BRUCEA@UCRVMS.BITNET
Subject:      RE: MS-DOS 5.0 Dosgen Problem

We could never get this to work on a diskless (or dos-less) workstation
using IBM's RPL chips and netware 3.11.  RPLFIX didn't help any.  The problem
seems to be that DOS5 expects to reload its command interpreter from drive A:,
and it tries to do that right after loading netx, before control gets
transferred to the server.  So, immediately after loading netx, it hangs
with an "invalid command.com" and "system halted" message.  If anyone has
actually got this to work, I would be interested in hearing about it, too.

Brucea@ucrac1.ucr.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 8 Apr 1992 16:19:54 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Glen Jula <julag@TACOM-EMH165.ARMY.MIL>
Subject:      I think the military is lost.
X-To:         RAY@SAFETY.NWSCC.SEA06.NAVY.MIL,
              NOVELL%SUVM.BITNET@uga.cc.uga.edu

In response to my previous message, replies have been pouring in.


THANKS THANKS THANKS.

I have gotten messages from the edu, com, bitnet, uk, and ca world.  I
have not yet seen one message from the millitary world.

Ray Todd Stevens
Safety Dept NWSC Crane
Ray@safety.nwscc.sea06.navy.mil

No, we just don't have enough resources, you of all should know
of the budget situation.

                            GLEN P. JULA
                            US ARMY TACOM
                       WARREN, MI 48397-5000
                    julag@tacom-emh165.army.mil

           DSN:       786-5185/5488
          COMM: (313) 574-XXXX
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Organization: Indiana University - Purdue University at Indianapolis
X-VMS-To: IN%NOVELL
X-VMS-Cc: IMHW400
Newsgroups: bit.listserv.novell
Date:         Mon, 6 Apr 1992 09:22:00 -0500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Mark H. Wood" <IMHW400@INDYVAX.IUPUI.EDU>
Subject: Re: Load Remote /?
X-To:         NOVELL@SUVM.ACS.SYR.EDU

    Will somebody please tell me how it is that you all have gotten
    AUTOEXEC.NCF to echo at all?  It doesn't do that on any of our 3.11
    servers!

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL6]
Newsgroups: bit.listserv.novell
Date:         Thu, 9 Apr 1992 09:53:50 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Bill Swartz <bill@PICASSO.OCIS.TEMPLE.EDU>
Subject:      Re: BEACONING
X-To:         NOVELL%SUVM.BITNET@uga.cc.uga.edu
              "VALLEYD%SIMSC.BITNET@uga.cc.uga.edu" at Apr 8, 92 5:28 pm

>
> What causes Beaconing,  How does one diagnos which card is sending the beacon
> around the Ring,  how can I prevent/eliminate this problem and not have the
> Network come tumbling down???
> Need all the help I can get on this one.  I have had this problem for 2 wks.
> Thanks in advance,
> Dave Valley
> LAN Admin.  O.P.M. - I.A.D.I.A.D.
>
  Typically, beaconing is caused by cards running at different speeds on the
  network (this may not be the actual definition of beaconing but...).  The
  easiest way to see who the culprit is - is to turn everything off and bring
  them back on the network one at a time.  When you start to get the
  beaconing TADA.  HTH!

--
   -------------------------------------------------------------------------
   Bill Swartz
   Lan Technical Consultant                 bill@picasso.ocis.temple.edu
   Temple University                        bill@templevm
   -------------------------------------------------------------------------
   There have been hundreds of horrible events in my life, few have ever
   actually happened. ---  Unknown
   -------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 17 Apr 1992 10:49:38 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Orlando Vanegas <ORLANDO@UMDC.BITNET>
Subject:      GetOriginalNameSpace Error.

Steve  writes  can load v_repair without V_mac and viceversa.

Load v_repair,
hit alt+esc, switch to system
loac v_mac,
hit alt+esc, switch to v_repair and keep on working.

hope the above helps,
Orlando Vanegas, Networks Administrator, Information Resources Group,
Maryland Biotechnology Institute, University of Maryland, Orlando@umdc.umd.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-VMS-To: IN%"novell%suvm.bitnet@brownvm.brown.edu"
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 12:02:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         KMALLORY@RCNVMS.RCN.MASS.EDU
Subject:      Thanks ;)
X-To:         novell%suvm.bitnet@brownvm.brown.edu

Thanks to all that helped with the survey, it is greatly appreciated.  The data
collected will fit well in my paper.  As some of you mentioned I will only get
Novell responses, it's okay because I plan to break it down into all the
different operating systems.  For those of you who requested a summary, it will
be emailed to you next week or the week after.

Once again, thanks for your help,
Karen Mallory
Salem State College
Computer Services
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Mon, 6 Apr 1992 12:32:44 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         GAUHC@CUNYVM.BITNET
Subject:      TCPIP File Transfers
X-cc:         lemhc@CUNYVM.BITNET

Novellers,
I am familiar with using FTP as a means of file transfer but it appears
that certain systems have trouble with FTP {e.g E-Mail, VM/VMS etc}.

Would anyone know how to use Kermit or other file transfer protocols with
TCPIP.  Thanks in Advance for any and all assistance.`

Please post to the NET


Gauhc@cunyvm.cuny.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 08:34:27 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Mark Hunter / University Placement Services
              <HUNTERM@VTVM2.BITNET>
Subject:      Gateway 486 as Server

We're considering a Gateway 33 MHz 386 EISA machine as a file server
on a busy 25-node ethernet LAN.    Probably will use a Mylex LNE390A card.
What are the implications of this machine having a "custom-manufactured"
motherboard and of its using "Award" BIOS?   Any cause for concern
on these two items?   Has anyone experienced difficulties with this
machine?

+-----------------------------------------------------------------------+
Mark Hunter                                        HUNTERM@VTVM2 (BITNET)
Systems Manager                        HUNTERM@VTVM2.CC.VT.EDU (INTERNET)
University Placement Services                              (703) 231-6241
Virginia Tech                                         FAX: (703) 231-8018
Blacksburg, VA  24061-0128
+-----------------------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 15 Apr 1992 13:54:21 CDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         wittmann@ENGR.WISC.EDU
Subject:      Re: The Mylex binding Multiple protocols
X-To:         boyles@NeXTwork.Rose-Hulman.Edu, novell@suvm.acs.syr.edu

In article <1992Apr15.175007.6338@cs.rose-hulman.edu> you write:
|>
|>
|> Has any one using the Mylex LNE390A had any problems binding multiple
|> protocols (IPX/SPX, Appletalk).  Mylex admits they have some problems but
|> says it will work.
|>
|> Please respond to,
|>
|> Ernie Boyles
|> Ernie.Boyles@Rose-Hulman.Edu

Nope, it won't work.  The LNE390 driver does not handle macintosh multicasts
correctly.  You can bind multiple protocols, but Appletalk won't work
correctly.

Art

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Art Wittmann                                  Phone: (608) 263-1748
Network Manager                               Email: wittmann@engr.wisc.edu
Computer Aided Engineering Center                or: wittmann@cae.wisc.edu
University of Wisconsin, Madison
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 14:13:19 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Lewis Maximin II <LEMHC@CUNYVM.BITNET>
Subject: Telnet accepting addressses

Hi Novellists/TCPers,

Is there a way to get TELNET to accept alpha characters as an address??
Most people give addresses in terms of letters not #s therefore when I
give an alpha ftp address, it bombs.  Suggestions??


very big TIA!
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 14 Apr 1992 14:04:17 PDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Jim Wilson <A2JW@PSUORVM.BITNET>
Subject:      2.15c: Pap Socket

I'm running Netware 2.15C together with the Apple VAPS on a mixed
network of DOS and MAC machines.

Frequently I'm getting the message "Unable to kill pap socket" and the
associated MAC printer queue is unpublished.  To correct the problem,
all I've had to do so far is to publish the affecte queue.

What's going on?  And how can I stop it from happening?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:        UK.AC.ED.CASTLE;  6 APR 92  9:53:14 BST
Newsgroups: bit.listserv.novell
Date:         Mon, 6 Apr 1992 09:52:22 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         G J Scobie <gscobie@CASTLE.ED.AC.UK>
Subject:      New Updates

Is there an upto date list of all patches/fixes and upgrades for Netware
3.11? I'd like to be able to compare directory listings of the PUBLIC
and SYSTEM areas in order to see what needs to be downloaded.

Thanks in advance

Garry Scobie
LAN Support
Computing Service
Edinburgh University
Scotland
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-mailer: Pegasus Mail v2.2 (R3).
X-Envelope-to: novell@suvm.acs.syr.edu
Newsgroups: bit.listserv.novell
Date:         Thu, 9 Apr 1992 10:15:30 GMT+1000
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Chris Owen <CHRIS@CBE.QUT.EDU.AU>
Subject:      Sitelock security and station restrictions
X-To:         novell@suvm.acs.syr.edu

Sitelock v. 3.20 and earlier may a security problem due to creating a
SUPERVISOR equivalent bindery object with no password.  Anyone with
the right tools can log in as the object and gain full access to the
server.  The security hole shows up when running Novell's
SECURITY.EXE.

Station restrictions can be used to limit logins to the fileserver
running the NLM.  Because the supervisor equivalent object is not a
user object, SYSCON and NETCON cannot be used to do this.

To remedy the situation, I wrote a simple program, STATREST, which can
be found on risc.ua.edu in pub/network/misc/statrest.zip.  STATREST is
used from the command line to add station restrictions to an object
of any type (not just a user object), and prevent it from logging in
from anywhere other than defined station addresses, so it will be
useful for other applications too.  Note that although it can be used
to add restrictions

In the case of Sitelock, we want to restrict the object to the file
server.

Usage is:

STATREST object_name net:node [object_type]

This will set station restrictions for object_name of type
object_type.
object_type defaults to 1 (user), but supplying -1 here acts as a wild
card.  Wildcards can also be supplied for object_name.

Eg, for SITELOCK, run

STATREST object net:node -1

where net:node is the network address of the fileserver, and object
is the name of the offending object as reported by SECURITY.  If you
are running NetWare 3.x, net is the internal network number, and node
is 1.  If you are running NetWare 2.x, net:node is the address of LAN
card A.

I have not mentioned the name of the object in order to prevent
non-supervisors from breaking in to Sitelock'd networks.  You will
need to run SECURITY.EXE to find out.  You need to be SUPERVISOR or
equivalent to run SECURITY, or modify station restrictions.

In the interest of safe computing,

Chris Owen                            |     c.owen@qut.edu.au
Computer Based Education              |     phone +61 7 864 2912
Queensland University of Technology
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU