HDTenEightyP/NetNews huggingface dataset:
X-Vers: Weeg cc:Mail/SMTP translation (originally by A. Marshall)
Newsgroups: bit.listserv.novell
Date:         Tue, 18 Aug 1992 14:47:00 CST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Netman@PHYSLOG-PO.PHYSLOG.UIOWA.EDU
Subject:      mac password problems
X-To:         Novell LAN Interest Group <NOVELL@suvm.acs.syr.EDU>

From: COURTNEY@MCCADA.MAUICC.HAWAII.EDU
Sender:NOVELERR@SUVM.SYR.EDU
X-To:novell@suvm.acs.syr.edu
--------------------------------------------------------------------------------

             I posted this msg a week ago. Between then and now (unknown
to me, my node address changed. As a result, any responses I received
probably went into never-never land. So I am trying again.

             From time to time, I have seen msgs posted re: macs
forgetting their passwords. We are also experiencing this. I don't ever
recall seeing a resolution to this problem. If there is one, I would
REALLY appreciate hearing about it.


      _ _ _ _ _

      Yo Bill!

      I've determined two problems with Mac passwords here:

      ONE:  If the user's password expires (we originally had ours set
      to force a new password every 60 days) the Mac software does not
      notify or prompt the Mac user.  They are quietly allowed their
      grace logins and then are locked out of the system.  The
      solution: don't force periodic password changes for the
      Mac-heads.  (Check under User Info in SYSCON...)

      TWO:  If a user has mistyped their password at the login screen,
      they need to be careful to highlight the entire password field
      before deleting the wrong attempt.  We have found the situation
      where a user mistypes their password, tries to correct their
      mistake, and then, without knowing it, submits a new password
      that has an invisible "space" either before or after their typed
      text.  The net effect is that the new password doesn't work
      either and they eventually get locked out of the server for too
      many wrong login attempts.  The users swear that the network is
      screwy (and they're not far off) while I and my assistants
      assume that the users have biscuits for brains.

      Good luck!

      -- Cliff
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Organization: Penn State University / University Libraries
X-Envelope-to: novell@suvm.BITNET
X-VMS-To: NOVELL_L
X-VMS-Cc: in%"ROSS@ETSUADMN"
Newsgroups: bit.listserv.novell
Date:         Wed, 12 Aug 1992 08:58:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "J.Lance Wilkinson, (814) 865-1818" <JLW@PSULIAS.BITNET>
Subject:      Re: Keeping workstations out of a file server
X-To:         NOVELL-L@PSULIAS.BITNET
X-cc:         ROSS@ETSUADMN.BITNET

On 11-AUG-1992 13:12, <ROSS@ETSUADMN.BITNET> asked
Re: Keeping workstations out of a file server

>                            One way that I can think of is specifying a
>preferred server for each workstation, however there is still a chance of
>someone signing on without the preference.

        I haven't noticed anybody mention this one yet in replies, probably
        since you hint at it in your posting.  But why wouldn't it work for
        you?

                NETX /PS=preferred_server

        We use this here since we have 4 file servers with different user
        communities on each one, and occasionally we'd get your situation
        of somebody associating themselves with the wrong server (where their
        ID wasn't defined, by the way).  Since this invocation of NETX is
        in a .BAT job invoked by AUTOEXEC.BAT, and not typed by the user,
        it eliminates the chance of someone failing to use it.

        An alternative, for the case of users who are invoking NETX
        interactively (somehow I can't imagine a production shop doing
        it that way, too many fingers on the keyboard type errors and all),
        if you're running DOS 5.0 you can use the DOSKEY macro utility to
        define the command NETX to be "NETX/PS=preferred_server", putting
        that macro definition in your user's AUTOEXEC so whenever they type
        NETX they get NETX/PS=preferred_server.

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services             AT&T:      (814) 865-1818          |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 12 Aug 1992 16:20:01 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Andreas Pflug <100015.3552@COMPUSERVE.COM>
Subject:      Re:Netware and Unix
X-To:         novell@suvm.acs.syr.EDU

Vince,

> A) execute/access files from Unix servers and Netware sumultaneously
> ...

NetWare volumes may be shared with Unix using NetWare NFS. Haven't heard of
a way using Unix as NetWare Volume (as possible with MVS or VM mainframes).
With PC-NFS DOS can use Unix file systems, OS/2 2.0 could be possible with
TCP/IP package.

> B) print to printers on BOTH Unix and Netware from any PC simultaneously
> ...
NetWare NFS supports printing in both directions, Charon V3.5 will do so,
too. No experiences with that.


> C) backup Netware servers on UNIX tape system

Don't know anything like that, but how about the other way round? Cheyenne's
Arcserve is probably much more comfortable than any Unix tar or backup or
cpio or whatever you're using. You can easily backup NetWare NFS volumes.


> D) email to amy user on WAN using native OS (Windows/Unix/DOS)

One way for Mail I know: Pegasus Mail (currently V2.32) on NetWare with DOS
or Windows (freeware), connection to Unix with Charon (Brad Clements
bkc@omnigate.clarkson.edu says V3.5 will be released within the next two
weeks, free too). Charon interconnects NetWare and Unix with SMTP. It needs
packet drivers and a simple dedicated DOS workstation as gateway. Runs
great! (using a one year old version, don't have a newer one, waiting for
Brad.. :-) )

Other major packages (CC:mail, daVinci, ...) probably have gateways to SMTP.

> E) news for any user on WAN using native OS (Windows/Unix/DOS)
???? I just introduced NETNEWSU on NetWare, don't know if anything other
than mail exists on Unix.


Andreas Pflug 10015.3552@Compuserve.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Tue, 18 Aug 1992 15:34:21 CDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Mayfield <MHARRIS@RICEVM1.RICE.EDU>
Subject:      Re: Adding directory entries to a volume...
              18 Aug 1992 13:45:05 EDT from <rob@UMBC3.UMBC.EDU>

You didn't say which version of Netware you were using.
If you are using 3.11 you dont have to increase it, this happens automatically.
However, if you are using 2.15 or 2.2 you will have to load Netgen back up
again and make the change to the Net$os file.


======================================================================
Mayfield Harris              Phone: 713-527-4642
LAN Specialist                 Fax: 713-527-6099
Rice University           Internet: mharris@ricevm1.rice.edu

"He who ask a question may be a fool, but he who never ask"
                    "remains a fool forever"
======================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 12 Aug 1992 10:07:00 LCL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         DANB <DANB.BRANTON2@MHSGW.HARVARD.EDU>
Subject:      <None>
X-To:         - <NOVELL@SUVM.ACS.SYR.EDU>

To: NOVELL
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Thu, 13 Aug 1992 11:14:19 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         mike fanara <MIKEF@YALEVM.BITNET>
Subject:      pserver

Fellow netters,

I'm using Pserver 1.2.1 on a small 7 node ethernet network and I'm having the
damndest (sp?) time trying to get it to work.  Here's what I have:

    PS/2 model 80 - server 8mb Ram  SYS: 60MB
    3.11 Netware  - OS 10 user
    HP LaserJet III - printer \  Serial
    Epson FX 1050  - printer  /  Parallel, both attached to the server

    Capture in Sys login  l=1 - dot_matrix, l=2 - Hp III
    The HP III is the default

    Everything is configured in Pconsole with the Print Server, i.e. Printer
    definitions, who to notify, what queues to service, etc.

Now my problems: sometimes when I issue the capture to print to the dot matrix,
the file goes to the Hp III. Other times I'm getting "maybe not enough space on
Sys: volume" (there's almost 50MB). One time when I tried to unload Pserver and
then load again, the console hung for awhile, then when I got it back and re-
loaded it all of my printer definitions in Pconsole were lost.  I'm confused
as what to do. I tried rebooting the server, but that did not do a thing to
change the problems.  At the present time, print jobs enter the queue, but
stay in the ADDING stage. Nothing gets processed.  Can anyone help? Should I
upgrade to 1.2.2 of Pserver?  Any advice would be very appreciated.

Of course, TIA!

: Michael Fanara
: Computer Support Specialist III
: Yale School of Management
: Mikef@YaleVM.Bitnet
: Mikef@YaleVM.Ycc.Yale.Edu (Internet)
: Mikef@homey.som.yale.edu (Internet)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Thu, 13 Aug 1992 18:18:00 LCL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Dave Kearns <DKEARNS.TCC@KLAVEN.TCI.COM>
Subject:      Re: testing for a file server
X-To:         NOVELL <NOVELL@suvm.acs.syr.edu>

>I'm looking for a way to test for the availablity of a particular file
>server from a workstation.  I want to run an AUTOEXEC.BAT file which
>automatically logs on to the server if it is available, but otherwise
>branches to some other point, tells the (fairly dumb) user that the file
>server is unavailable and then provides some local software.

If you put a preferred server option in your NET.CFG, and that server
isn't available, NETX will connect you to any available server. You'd
then need a LOGIN servername/ line which would return an errorlevel of 1
if the server wasn't available. This works for me with both NETX and BNETX.

-dave
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Mon, 17 Aug 1992 10:08:00 LCL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Dave Kearns <DKEARNS.TCC@KLAVEN.TCI.COM>
Subject:      Re: free nlm wanted
X-To:         NOVELL <NOVELL@suvm.acs.syr.edu>

>I know this is asking a lot, and I am willing to bet there is no such
>animal, but is there an NLM that will best a Novell drive while it is
>up an operational.  We need to test a drive without taking the
>network down.


What sort of 'testing' did you want to do?


-dave
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Original_To:  jnet%"novell@suvm"
Original_cc:  BSMITH
Newsgroups: bit.listserv.novell
Date:         Fri, 14 Aug 1992 09:42:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Bob Smith,
              Kent State - East Liverpool Campus" <BSMITH@KENTELIV.BITNET>
Subject:      RE: Updating Network Drivers

Joe Doupnik <JRD@USU.BITNET> says:

>Cathrine,
>        My opinion, and it is just an opinion, is automatic updating
>across the net is not a swift idea. Machines differ so memory managment
>layouts differ, and shell components change size from issue to issue.
>Older shells can continue to work effectively for several years, or
>equivalently til the next release of Windows, and then folks need to
>upgrade. Since the goal of support organizations is user support then
>the least disruption and intrusion is wanted until a problem arises.
>Poking about someone's local hard disk is an intrusion with a capital I
>and the consequences might be unpleasant. An out of date shell is not
>causing harm to the net nor to other users, though it might generate
>extra Tech Support calls from the particular user.
>        What we do here is make jolly noises, urge folks to update, and
>in a few cases offer to do the job personally. Naturally that leaves a
>segment of the population untouched, because they want it that way. Shells
>are made available across the network so the effort is minimal.
>        On support calls it is easy to ask the person to type IPX I and
>NETX I to get version numbers. There are some commercial programs around
>which, I believe, can provide those numbers across the net.
>        Joe D.

I say - HERE!  HERE!

   Bob

**************************************************************************
Bob Smith, Computer Center Coordinator    JNET/BITNET - BSMITH@KENTELIV
Kent State - East Liverpool               DECNET      - KSUVXL::BSMITH
E. Liverpool, OH  43920  (216)385-3805    Internet    - BSMITH@KSUVXL.KENT.EDU
**************************************************************************
                       **************************
                       * You want it WHEN?!?!?! *
                       **************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
Newsgroups: bit.listserv.novell
Date:         Thu, 20 Aug 1992 08:11:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "SHEL SAX (802)388-3711X5323" <SAX@MIDD.BITNET>
Subject:      volume transfer

After completing an upgrade from a 286 server running 2.15 to a 386 server
running 3.11, I ran into some problems getting the print queues to work.
Consequently, I left the 286 server up and running while I tweaked the new
one.  Now that the 386 server is ready to go, I need to re-transfer one
entire volume from the 286 server which contains more recent data and some
applications.  What is the best way to accomplish this when both servers
could be up and running.  Should I delete the volume on the new server and
use the upgrade utility to transfer  the volume from the 286 server to the
386?  Any suggestions would be appreciated. TIA.
From: medici@dorm.rutgers.edu (Mark Medici)
Newsgroups: bit.listserv.novell
Subject: Re: Charon and smc card
Date: 14 Aug 92 16:03:36 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

SYSGWV@GRANITE.ALBANY.EDU (Gerd W. Voss) writes:
>Mark Medici <medici@dorm.rutgers.edu> writes:
>> Do NOT attempt to run Charon via ODI with SMC NICs.  After much trial
>> and terror troubleshooting, I'm convinced it cannot work.  However,
>> Charon hums happily along using 8003PKDR, as long as it it loaded
>> AFTER IPX.COM.
>
>Marc, do you mean all SMC nics, historicly ?, WD's ? I have charon up
>with wd 8bit's, wd16's , using ODI. I thought the SMC boards are WD's.
>Is there a Differance ? TIA.

Apparently, the problems I'm having getting Charon 3.4 to run over ODI
is particular to our site.  I've received three replies by mail that
indicate other sites have no trouble using Charon over ODI on SMC
Ethercard Elites.

This does strike me as strange, though.  I tried two different PCs (a
12MHz '286 clone and an IBM PS/2-50), both WD and SMC labeled
Ethercard Elites, the older WD supplied MLID as well as two version of
the SMC MLID, and two revs of Novell's ODI stack.  In all cases, the
machine running Charon would lock-up after 2min to 10 hours of use
(usually closer to 2 min) with nothing special happening.

However, using an econfiged, dedicated IPX.COM with 8003PKDR.EXE
results in a very stable and reliable Charon gateway.  Unless a server
drops off the network, our gateway has 100% uptime using this config.

Someone is mailing me copies of his ODI config, so I'll take another
look at this in the near future.

-- 
_________________________________________________________________________
RUCS     | Mark A. Medici, Systems Programmer III, User Services Division
User     | Rutgers University Computing Services, New Brunswick, NJ 08903
Services | [medici@gandalf.rutgers.edu]                    [908-932-2412]
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University of B.C. Computing Services
Newsgroups: bit.listserv.novell
Date:         Wed, 19 Aug 1992 22:52:14 PDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Jonn Martell <martell@UCS.UBC.CA>
Subject:      Re: Remote Software
X-To:         NOVELL%suvm.BITNET@cunyvm.cuny.edu

In article <NOVELL%92081913002338@SUVM.SYR.EDU> you write:
>Does anyone out there use any remote software?  I intend on making a purchase
>but dont want to use Carbon Copy.  I have used PCanyWhere and like it, but I
>understand that there is another software out by the name of Snap Shot, I
>think.
>
>If you know of any or have used something that is fast, please let me know.
>I want to be able to access my network from home using remote software.
>
>
>======================================================================
>Mayfield Harris              Phone: 713-527-4642
>LAN Specialist                 Fax: 713-527-6099
>Rice University           Internet: mharris@ricevm1.rice.edu

The last Network Computing mag as a good article from a LAN person at
Syracuse.  It involves using ODI/PKTDRV/SLIP for Netware connectivity
over dial up IP.  Unlike remote program that only send screens,
keyboards and possibly critter mouvements, these types of "remote
nodes" send the full IPX (over 9600 bps or 14.4 kbps $400 modems).

The "system" uses two unsupported drivers (aka shims) (ETHERSLIP and
PDETHER) to provide SLIP connectivity.  The nice thing is that is uses
plain modems, works and can easily be replaced by IPX on PPP *when*
it is implemented.  The bad thing is that it's not "plug and play"
and the shims add to the level of complexity, performance problems
and support problems. Even the batch file is not for the novice!
(It really makes me appreciate Appletalk Remote! and I'm not a Mac
guy!)

One point on remote IPX/IP/Atalk:

I suppose that the smart software developers are already working of
efficient ways to send IPX over a multi-protocol dial-up/serial line.
I just hope that they can have products ready when people start asking
for remote Netware/Mac/Unix capabilities (NOW!;-)  The guys at Novell
(Keith, Don etc.) are great - I'm sure they they are hard at work
(tonight!).  It's hard to predict but I would expect it to be available
within a year (if not, Microsoft might put something out!).

One last point regarding the gateway list to the bit.listserv.novell:

Please fix the "reply" field so that private email will go to the
originator rather that appearing as a "follow-up" post to the
newsgroup.  Please email me if you have questions; our "news"
guru explained why the Novell List Newsgroup was "broken".

I would hate to have my mailbox filled with posts that were
intended to be sent as private mail! ;-) This list is probably
one of the busiest as it is! Glad I can just "graze" it as
a newsgroup!

From: Jonn Martell
email: martell@ucs.ubc.ca
Organisation: UBC - Computing Services, MicroLAN
Newsgroup: bit.listserv.novell
"Netware Lite vs Windows NT: yeah right!, Novell! Go high end and fast!"
From: imhw400@indyvax.iupui.edu
Newsgroups: bit.listserv.novell
Subject: Re: Keeping workstations out of a file server
Date: 12 Aug 92 12:23:20 -0500

What happened when you tried using the Preferred Server mechanism?  (That is,
add "Preferred Server = thebigserver" to NET.CFG for everybody but the VP's
office.)

Come to think of it, Preferred Server would also help out when combined with
the earlier suggestion to disable GetNearestServer replies on the VP machine. 
If you do that *and* declare the VP server as Preferred Server on the VP
stations, they shouldn't have to change the way they login, right?
-- 
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Celebrate freedom:  read a banned newsgroup.
Newsgroups: bit.listserv.novell
Subject: Emerald backup breaking MAC connections?
From: paul@ccu1.aukuni.ac.nz (Mr. Paul R Gray)
Date: Tue, 18 Aug 1992 04:56:00 GMT
Organization: University of Auckland, New Zealand.

Hey there, one and all in net.world!

I have a Novell backup system using Emerald Systems DAT tapes and have
noticed some phenomenon:

When starting the backup on my server any MAC's connected lose their
connection to the SYS: volume. Has anyone else had this problem? If so,
how did they fix it or get around it. Any advise would be greatly appreciated.
Sorry if I'm dredging up an old subject, but I'm just a new fella to this 
group.

Thanx in advance.


-- 
Paul Gray                         Email:   pr.gray@aukuni.ac.nz
Network Programmer,
Computer Centre,                  Phone:   +64  9  737-999 ext 8949
Auckland University,
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Original_To:  JNET%"novell@suvm"
Original_cc:  MANAGER
Newsgroups: bit.listserv.novell
Date:         Thu, 20 Aug 1992 10:52:00 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Tom Moran <MANAGER@WVNCOE.BITNET>
Subject:      Zenith+EXABYTE+SBACKUP=HELP

Hello,

        I'm trying to get a Zenith 386/33E and an Exabyte 8200 to work with
SBACKUP. The 386 has a builtin SCSI. I've tried everything I could think of
...even reading the manuals. I called Zenith, but haven't gotten a response
(yet). If anyone is doing backups through the builtin port, please (kind
soul) send your configuration. PS I'm running NW3.11. Thanks so much.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <KASPER@PENNDRLS.UPENN.EDU>
Newsgroups: bit.listserv.novell
Date:         Wed, 19 Aug 1992 18:57:18 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         KASPER@PENNDRLS.UPENN.EDU
Subject:      Using NOVELL WAIS Server
X-To:         novell%suvm.bitnet@NOC2.DCCS.UPENN.EDU

I have tried to use the NOVELL WAIS server using the PC client version
of WAIS obtained at Syracuse.  It cannot connect.  It does connect to
other WAIS servers.  Is WAIS still available their?  If someone has
successfully used it, could you send me the 'NOVELL.SRC' file?  Thanks.

-Stan
kasper@penndrls.upenn.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Pmrqc:  1
X-Mailer: Pegasus Mail v2.3 (R1).
Newsgroups: bit.listserv.novell
Date:         Wed, 19 Aug 1992 10:19:30 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Cathy Erdly" <ERDLY_C@MSB.FLINT.UMICH.EDU>
Subject:      Merging Binderies

Hello All!

We are, as we type, building a new server for our student
microcomputer lab. Prior to this new server we had one server for
macintoshes and one server for DOS machines. Now we want to bring the
two together as one. We have restored our MAC_SERVER to our new
STUDENT server (bindery included). We have also already restored the
applications from the DOS_SERVER to the new STUDENT server.

Here's the big question.... Is it at all possible to merge the
bindery from the DOS_SERVER with the already restored MAC bindery on
the new STUDENT server?

BTW... All three servers are running NetWare ver. 3.11.

A speedy reply would be most appreciated. TIA.


=====================================================================
Catherine A. Erdly                              Phone: (313) 762-3123
Computer Systems Specialist II                         (313) 766-6629
Information Technology Services                   Fax: (313) 762-3687
University of Michigan - Flint
207 Murchie Science Building      E-mail: Cathy.Erdly@um.cc.umich.edu
303 East Kearsley Street            or    erdly_c@msb.flint.umich.edu
Flint, Michigan 48502
=====================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU