Novell 4.11

-You can have an NDS problem. Run LOAD DSREPAIR|Unattended full repair
-With some luck you have some account that has been made equivalent to Admin, or has been given similar right. Use that.
-With some luck you remember the password for Admin you used when you set up the original server. You can log in in bindery mode, as SUPERVISOR, with that password. With netadmin.exe you can then correct whatever has been done to .admin.xxx.
-And if none of this helps, maybe some tool on www.netwarefiles.com can help you, but that is not a guarantee at all. And maybe Novell's support can enter the database directly, but that is going to cost quite a lot since NW411 is no longer supported since last year.

If anyone else reads this: this happens more than some people realise. Make an additional user, don't make him "equivalent" to Admin.xxx, but give that user the same rights. Some work in the beginning, but it prevents a lot of trouble.

Jim

As well as the points raised in answer 1, provided you have access to a server with the [root] partition, and that server also holds a partition where you have supervisory rights, you don't have to remember the bindery supervisor password. )I have personally tried this to recover an inherited tree and succeeded.
Set the bindery context on this server as "your" partition AND the organization partition.
Login as yourself, and run syscon. If you don't have a NW3 server still around, there is a download on the Novell site at http://www.novell.com/coolsolutions/tools/1235.html (remove any spaces).
Usingg syscon, reset the Supervisor account (the [root] admin account won't work).
Now login to the server in bindery mode as the supervisor. You can now reset the Admin account.

Login to NDS as the Admin account.
Now you are in, create another account with full NDS & File system rights (as said before, not just equivalent to).

HTH
Roger

This question was closed by the author