Re: Cannot run NWadmin32 ordinal not found
Peter Kuo
> The ordinal 1001 could not be located in the dynamic link library
> CLNWIN32.DLL.
Typically that means a referenced function is not found in the named DLL,
which means you may have outdated Client32. What version are you running?
--
Peter
eDirectory Rules!
http://www.DreamLAN.com
Edward van der Maas
>
> Hello all,
>
> After applying SP6a it seems that my one user name that everyone uses
> now only allows one connection. In setup from awhile back I allowed
> concurrent user logins which worked fine for me.
>
> I have tried to run NWadmin32 to adminishter the users only to receive
> the following message:
>
> nwadmin32.exe - Ordinal Not Found
> The ordinal 1001 could not be located in the dynamic link library
> CLNWIN32.DLL.
>
> I have this file in my \Novell\Client32\libs32 directory.
Maybe try ConsoleONe ?
--
Cheers,
Edward
Marcel Cox
we need information about your environment:
- What NetWare version are you using? As you talk about SP6a, this seems
to suggest you are using NetWare 5.0, but we need to be sure. Also, more
important (especially regarding your one connection issue) is to know
whether this is a normal NetWare version or a small business version.
- what client OS are you using and what Novell client version?
Now as for the 2 problems you mention, let me take a first stab at them:
1) The one connection issue. There might be 2 possible reasons for such a
behaviour: a concurrent connection restriction, or a licensing problem.
Given support packs don't change user properties or access restrictions,
my bets are on a licensing issue. In other words, licensing is no longer
working and the server just gives a "grace login" connection to the first
user allowing him to work correctly. However further users will be limited
in their access because the lack of licensing. To further debug possible
licensing issues, we first need the detailed information about your
environment that I asked at the beginning of this message
2) The ordinal 1001 error. Tecnically, this means a problem with the
library CLNWIN32.DLL, but the root cause could be different things:
- on outdated Novell client. While this is technically possible, you must
be running a really very old client to hit such an error for an outdated
client
- you could have a rogue version of CLNWIN32.DLL somewhere. In a "clean"
configuration, you should only have one copy of that file, and fir example
for a Windows 2000/XP workstations, this is in WINDOWS\SYSTEM32.
Unfortunately, Novell themselves had the bad habit of sometimes bundling
the xxx32.DLL files with some other products and a wrong incompatible or
outdated version might get loaded from a wrong location
- it is also possible that you are not using a Novell client at all, but
just the Microsoft client services for NetWare. In this case, you can't
use any programs that require the Novell client libraries. You need to
install a Novell client first.
Once again, the detailed information on your environment is needed to
further debug this problem. Without detailed information on your setup,
the only answer I can give is just these vague suggestions.
PS. Using ConsoleOne instead of NWADMN32 is probably of no help in your
situation. First of all, on Windows, ConsoleOne uses the samle client
library DLLs as NWADMN32 and so you might hit similar problems. Secondly,
if your root problem for the one connection limitation is a licensing
issue, then ConsoleOne is of no help because ConsoleOne does not have any
licensing snapins and therefore can't give you any information on licensing.
--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8