Discussion Locked

Netware 5.0 Licensing problems - at wit'

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running one Netware 5.0 server with one Windows 98 workstation and one laptop.

I initially installed the licensing containers in the same context as the server and eventually began receiving NLSLSP error: Unable to obtain a connection..."
I found out that the license container will perform more reliably in the next higher context than the server i.e., LSP in GEELOVE/HOMEOFFICE and server in GEELOVE/HOMEOFFICE/OFFICE.

I uninstalled all licenses (BTW: I am using a 1 server/3 user training license) and tried removing all license containers but was unable to remove one, of the two I unexplainably had.

Now I am unable to reinstall the licenses because DS says (only when I try to install) they are already installed. However when I want to make a connection to the server DS says "No! You need licenses" or something to that effect :).

Do I have to remove DS, I don't want to do that, but will if it is the cleanest and smoothest way to resolve this problem. I wish I hadknown where to insta

7 replies

by pallan

Most common licensing problems are fixed in NW5SP5. Since these errors tend to happen at inconsistent intervals, the relief you got from moving the licenses was probably a coincidence.

As for the container, assuming all subordinate objects are gone, check the health of your DS and have another go at deleting it.

by sergey_vk

NW stores licenses in file located at DOS partition. If you used command like [remove dos] in your autoexec.ncf file in some cases NW will lose licenses ;) Have a nice work

P.S. At server console you can run install programm and load licenses from disk (in condition that you not removed dos )

by pschmied

A 3 node training network is great for making mistakes and learning where you aren't risking your company or your career.

NWAdmin is convenient, but for basic server operations, if you can get to the physical server console easily, use the bluescreen utilities. There is also no question of your being able to get a "connection" when you are at the console.

Starting just like NW Support - you must have all the service packs loaded. Run the DS Repair utility and also check the schema with the nds manager.

Remember that with no licenses installed, the basic system will accept 2 logged connections. Some older server-side programs will use a connection, even though they are now supposed to.

If the license is shown as still installed, and you can't remove the associated container, try looking at the Licence Server manager through the console.

You may also be able to use nwsetup to remove the undesired licence.

Only if everything else fails, should you remove NDS. This is practice for the r

by geelove

Thanks, I know that is why I have one. I ran DSRepair and every other utility, including NLSadmin, DSadmin, NWadmin.

This discussion is closed to new replies.