Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!nic.csu.net!beach.csulb.edu!csus.edu!wuarchive!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!saddison
From: saddison@ca.excelan.com (Skip Addison)
Newsgroups: comp.sys.novell
Subject: Re: Upgrade problem
Message-ID: <1991Mar21.162607.6536@novell.com>
Date: 22 Mar 91 13:21:25 GMT
Sender: news@novell.com (
Lines: 35

The News Manager)
Nntp-Posting-Host: ca
Reply-To: saddison@Novell.com (Skip Addison)
Organization: Novell, Sunnyvale, CA
References: <1991Mar20.021719.27003@magnus.acs.ohio-state.edu>
Date: Thu, 21 Mar 1991 16:26:07 GMT

In article <1991Mar20.021719.27003@magnus.acs.ohio-state.edu> salter@magnus.ircc.ohio-state.edu (John E Salter) writes:
>I have a problem upgrading from Netware v2.15a to Netware 386 v3.1
>using the transfer method.  The installation and transfer of files
>worked OK.   However, when I try to login to the new server I get the message:
> 
>SERVER2/JOHN: Unknown error returned by attach.  (89fb)
>You are attached to server SERVER2.
> 
>No, I have not updated my workstation shell software.  How important
>is it that I do?  I am using the packet driver on all workstations on the
>LAN.   
> ...

The old shells will still work.  You need to "SET ALLOW UNENCRYPTED
PASSWORDS = ON" before you can login with the old shell, however.

You DO need to use the new LOGIN, ATTACH, etc programs.  I suspect that
this is the problem.

In response to another's note on the ability to keep the users, groups, etc
across the upgrade process, you certainly can.  You must use the UPGRADE
program as documented, however, since the bindery file format does change.
A simple backup and restore won't cut it.  The bindery should be restored
before the rest of the data to preserve the most amount of information.

Note that there are significant differences between NetWare 3.11 security
and NetWare 2.1x security.

-- Skip
   saddison@novell.com