Solved

nwadmn32.exe will not load on XP workstation

Posted on 2006-06-27
24
2,939 Views
Last Modified: 2011-10-03
When attempting to run nwadmn32.exe on an XP workstation we receive the error:
“nwadmn32.exe – Entry Point Not Found”
“The procedure entry point SUnMapLS_IP_EBP_40 could not be located in the dynamic link library KERNEL32.DLL”

Novell Server running Netware 5
Novell 4.91 Client on the workstation.

We are only able to load nwadmn32 on a Win98 PC.  We are looking for a fix to allow us to run nwadmn32 on an XP workstation.
0
Comment
Question by:rollingrelic
  • 8
  • 6
  • 5
  • +3
24 Comments
 
LVL 30

Expert Comment

by:pgm554
ID: 16996943
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 16996958
OK.

First, so PsiCop doesn't have a conniption, it's not a Novell server, it's a NetWare server (as you said in the 2nd part of that statement.) Novell is a company, not a server OS.  They sell many products, including more than one OS, and the "Novell client" is appropriate because it's not just a client for NetWare, but for multiple Novell products.  Saying "the server is Novell NetWare 5" is OK, but it's not a "Novell server..."   Referring to a NetWare server as a "Novell server" perpetuates they myth that Novell IS NetWare, which makes it an uphill climb to get ANY Novell products approved even if they don't require NetWare (which most do not, being multiplatform products.)

That said, you're using the proper client, so that's not it.  Did you install NICI when you installed the client?  (You should, when using it for management of eDirectory/NDS.)

Are you running it from a local copy, or from a server?  If it's from a server, do you have a search mapping for that server's SYS:\PUBLIC?

What version of nwadmn32 are you trying to run?  The last version was 5.1.9f.  An older version may not have the right API calls.  If you're running it locally and not from the server, maybe running it from the server will work, because it'll look in its own directory first, for whatever DLLs it needs - maybe Windows XP isn't liking it run locally (I don't know, I rarely run it any more and only do it from the server when I have to.)
0
 

Author Comment

by:rollingrelic
ID: 17002837
Thanks for your help with my terminology.
We are using the NetWare Administrator version 5.1.9f.  NICI is installed. We going to the Z:\public\win32 directory and pasting a shortcut to nwadmn32.exe on the local desktop. This works on Win98se workstations. Following the same procedure on an XP SP2 workstation errors out. I don’t know if it is significant but there seems to be a difference it the way NetWare applies the default mappings on Win98se and XP. The nwadmn32 shortcut on the Win98se machines shows a path  of: Z:\public\win32\nwadmn32.exe on XP it is: Z:\win32\nwadmn32.exe. Does nwadmn32 need to seen “public”?
0
 
LVL 30

Expert Comment

by:pgm554
ID: 17002938
Why don't you copy the nwadmin32 to the XP WS and see what happens.
0
 
LVL 30

Expert Comment

by:pgm554
ID: 17002965
Looking at the path ,it looks as if the nwadmin you are using on the W98 machine is different than the one on you are trying to execute on the XP box.

Map to that public dir and try using it.
0
 

Author Comment

by:rollingrelic
ID: 17003092
I remapped a drive to: sys\public. The desktop shortcut shows a path of: W:\sys\public\win32\nwadmn32.exe.

Same error message.
0
 
LVL 30

Expert Comment

by:pgm554
ID: 17003464
Try copying it the local HD and see what happens.

Have you tried plain nwadmin?
0
 

Author Comment

by:rollingrelic
ID: 17003880
Nwadmin does not appear to be on sys\public.

Copied nwadmn32 to desktop. Get an error cw3220.dll cannot be found
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17003887
"default mappings?"  You mean you don't have no_default specified in your login script?

Just to clarify: Windows XP automatically root-maps everything, so if your mapping for Z is SYS:\Public, Z will be root-mapped to the public dir.  It's not "the way NetWare maps things" it's the way Windows NT/2K/XP maps things.  Blame Microsoft, not Novell.  Redmond chose to map everything root starting with WinNT.  They didn't care with prior versions 'cause they didn't "do" networking back then, and did the map rooting just to be difficult IMHO but probably "officially" in order to support their "share" concept.

If you want your drive mappings to work the same way on WinXP as they do on Win98, you need to add the "MAPROOTOFF=1" environment variable to your XP boxes.  That can be done from within a login script if you want, or do it manually on each PC.  If you want to know how to set it from a NetWare login script, either search E-E NetWare TA for the word MAPROOTOFF, or ask for assistance.

Alternatively, if your shortcut is pre-made, don't use it.  Create a new one, from WinXP Windoze Explorer.

Don't use "plain nwadmin" - that was deprecated a long time ago.  I seem to recall Novell saying not to use it even back as far as "IntranetWare" 4.11.  Sure, it may still be there in your public dir somewhere, but I don't think Novell supports it for NDS7 and up.  It just won't support the schema extensions, and there are no snapins/plugins.
0
 
LVL 34

Expert Comment

by:PsiCop
ID: 17004043
I do not have conniptions.
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17004507
Ok.  Not conniptions. ;)

Anyway, I think the problem may be confusion with the root-mapping behavior of WinXP, and how the shortcut ends up defined on the XP desktop.

My shortcut, using "x" as a "generic" drive mapping to the root of vol SYS:, is like this:

Target: x:\PUBLIC\win32\nwadmn32.exe
Start in: x:\PUBLIC\win32

It >should< work in your map-rooted situation as long as the "target" path matches the "start in" path.

Is your "z" mapped as a search drive?  It should be...
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 

Author Comment

by:rollingrelic
ID: 17004773
Desktop Icon

Target: Z:\PUBLIC\win32\nwadmn32.exe
Start in: Z:\PUBLIC\win32

Same error message
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17004790
Is Z: already map-rooted?  If so, then you want:

Target: Z:\win32\nwadmn32.exe
Start in: Z:\win32

See how that works...
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17004803
Sorry I wasn't clear on that.  When I said "it shoud work in your map-rooted environment" I didn't mean using the path as it works on a Win98 or from a mapping to the root of vol SYS:, I meant using the path as presented by Windows XP.
0
 
LVL 30

Expert Comment

by:pgm554
ID: 17005347
Do this :

Go out to support.novell.com and download the admn519f.exe file to your local hard disk and extract the contents to the local drive.(XP box)

Then try to run it from there.

0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17005907
Just curious, have you tried adding MAPROOTOFF=1 to the WinXP environment, rebooting, and then trying again, creating the shortcut fresh? (browse to file, right-click, copy, right-click on desktop, "paste shortcut")

I can't help wonder if it's how your search mapping is seen by the XP box, if you're using default mappings.

Also, if you create a new mapping using Windoze Explorer - don't.  Use the "Novell Map Network Drive" feature of the Novell Client32.  It's on the systray "N" context menu...
0
 

Author Comment

by:rollingrelic
ID: 17012369
Thanks for all your help and comments. We have tried all your suggestions with no success. We just plan to live with the limitation and keep a Win98 PC in our server room for NetWare admin until we either upgrade NetWare or move NetWare data store to our Windows servers.

0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17014672
This is quite  bizarre.  I have run NWADMN32 succesfully in NW5 networks on WinNT, Win2K and  WinXP.

Something is wrong with your setup that we haven't  covered yet.  It should work for you, as well.


What you mentioned earlier about default mapping bugs me a tad - how  are you mapping drives generally, if you're using the default mapping?  It  could be the root cause here.

Also, are you doing any tweaking  of WinXP or using it the way it comes  "out  of  the  box"?  You should be  disabling several useless, counterproductive and/or security-hole-waiting-to happen services and settings.  

Are you installing the Novell client32 custom or "typical?"  What protocol(s) are you using?
0
 
LVL 30

Expert Comment

by:pgm554
ID: 17014709
Same here,I just set up a 5 sp6 server on Vmware and it works fine.
Sounds like there is something amiss on the XP WS.
0
 
LVL 35

Expert Comment

by:ShineOn
ID: 17014980
Yeah.   I can't in good conscience just drop it, 'cause if something that works all over the world doesn't work for you, there's gotta be a reason, and I wouldn't advise letting that reason stay hidden because it may bite  you in the butt later.
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 17306273
PAQ / Refund
ee ai construct, community support moderator
0
 

Expert Comment

by:tamutech
ID: 27622830
I resolved this by first locating the DLL's required for the executable to operate:
   netwin32.dll
   ncpwin32.dll
   clnwin32.dll
   locwin32.dll

Then by copying them to the executable directory, avoiding system32 entirely.
If they exist in system32, you should delete them prior to executing application.
Where to copy them from you might ask? Definitely not from internet or otherwise.. get from a working Groupwise machine; one with ConsoleOne installed - it has these dll's in the following directory(your dir may differ):
   C:\Novell\consoleone\1.3.6f\bin

Kudos to google for providing random information on this error.
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

A procedure for exporting installed hotfix details of remote computers using powershell
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now