OK:
Check your password retention settings within NWadmin.

also I have seen very strange ADSM/NetWare scenarios, when the NetWare user
ID is not located in the same container as the NEtware server being backed
up.
You did not mention if this was NetWare 4.X servers or not, I assume they
are.
you may want to also try remarking out the NWPfile  variable in the dsm.opt
file and deleting the *.pwd file. then start the ADSM client .  Close the
ADSM client session and then remove the remarking variable for NWPfile and
start up the ADSM client ( so the PWD file is created)
I have also experienced, this process to create a GOOD *.PWD file and begin
to work like it should.

John Stephens
Storage Solutions Specialists, Inc.


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Julie Phinney
> Sent: Thursday, March 25, 1999 12:38 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ADSM - Novell client
>
>
> Hi John,,
> Nope, we're not.  But the ID/Password that I'm having trouble with is not
> the ADSM client id and password, it's the Novell Supervisor-Equivalent id
> and password that are requested the first time you access a file system,
> and are encrypted in the .PWD file and stored in the ADSM subdirectory.
> Thanks,
> Julie
>
>
>
>
> John Stephens <Stephens AT STORSOL DOT COM> on 03/25/99 11:15:19 AM
>
> Please respond to Stephens AT Storsol DOT com
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:    (bcc: Julie Phinney/Green Bay/Humana)
> Subject:  Re: ADSM - Novell client
>
>
>
>
>
> Julie:
> Are you using PasswordAccess    Generate in the dsm.opt file?
>
> John Stephens
> Storage Solutions Specialists, Inc.
> WWW.Storsol.com
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
> > Of
> > Julie Phinney
> > Sent: Thursday, March 25, 1999 11:50 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: ADSM - Novell client
> >
> >
> > 3 times in the last month,   we come in to find most of our Novell
> servers
> > in one location have not backed up, and the ADSM scheduler sessions  are
> > asking for the Novell ID to be entered.
> > We re-enter the id and password on each that is asking,   and
> > everything is
> > fine.
> > Now it just happened again, this time in 2 different locations at once.
> > The error is seen on many, but not all, of the Novell servers.
> >
> > Anyone seen anything like this before?
> >
> > Thanks,
> > Julie
> >
>