Hi there

I have an interesting note I'd like to post and perhaps report as a bug so
the sysop can forward it to the client development team.

• I am using Windows XP SP2 (Swedish version) and a default installation of
the Novell client v4.91 SP1
• Public on the server is root search mapped as S16 to Z:\, i.e. after all
the local Windows search paths.
• The NWLANGUAGE environment variable is set to “ENGLISH”.

With my test server prepared (NetWare 6.5 SP3) I logged in and started my
network analyzer (Ethereal). When I right-click on the red “N” on the
systray, and selected “Novell Client Properties”, I get the following
interesting packets in my trace.

Source Dest. Info
<Client> <Server> C Obtain info for: PUBLIC
<Server> <Client> R OK
<Client> <Server> C Obtain info for: PUBLIC/PROP.HLP
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/CONNSVCR.DLL
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/LOGINSVC.HLP
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/LOGINSVR.DLL
<Server> <Client> R No matching files or directories were found

Questions and potential bugs:

1.) The files PROP.HLP, CONNSVCR.DLL and LOGINSVR.DLL exist on my local
workstation in the directory C:\WINDOWS\System32\NLS\ENGLISH which is in
the search path before Z:\. Why doesn’t the client find them there? Instead
it goes through all the search drives and ends up looking for the files in
PUBLIC on the server.

2.) The file LOGINSVC.HLP does NOT exist on my local workstation at all. In
the directory C:\WINDOWS\System32 there is a LOGINSVC.DLL, but no *.hlp
file. Why is the client searching for a file that exists neither on the
workstation nor in the unpacked NW Client source installation directory?

The second test I made was during right-clicking on the red “N” and
selecting “NetWare Login” on the popup menu. I captured the following
packets. (Note I did not login, I only opened up the login window)

Source Dest. Info
<Client> <Server> C Obtain info for: PUBLIC
<Server> <Client> R OK
<Client> <Server> C Obtain info for: PUBLIC/nls/Swedish/ldapsdkmsg.dll
<Server> <Client> R Invalid path
<Client> <Server> C Obtain info for: PUBLIC/nls/Swedish/ldapsdkmsg.dll (Twice!)
<Server> <Client> R Invalid path
<Client> <Server> C Obtain info for: PUBLIC/WMNotify.dll
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC
<Server> <Client> R OK
<Client> <Server> C Obtain info for: PUBLIC/LoginW32.rll
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/LOGIN.MSG
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/AxPrf.HLP
<Server> <Client> R No matching files or directories were found
<Client> <Server> C Obtain info for: PUBLIC/AxPrf.rll
<Server> <Client> R No matching files or directories were found

Questions and potential bugs:

1.) The files LDAPSDKMSG.DLL, LoginW32.rll, LOGIN.MSG and AxPrf.rll all
exist on my local workstation in the directory
C:\WINDOWS\System32\NLS\ENGLISH, which is in the search path before Z:\.
Why doesn’t the client find them there? Instead it goes through all the
search drives and ends up looking for the files in PUBLIC on the server.
Why is the client searching for the LDAPSDKMSG.DLL file twice? Why is it
trying to locate the file in a “Swedish” subdirectory even though the
NWLANGUAGE variable is set to “ENGLISH”.

2.) The file WMNotify.DLL is an old ZENworks 3.2 file (Workstation Manager)
that was made obsolete and removed from the Novell client v4.91. ZENworks
components have never been installed on this PC, why is the client
searching for this file?

3.) The file AxPrf.HLP does NOT exist on my local workstation at all. In
the directory C:\WINDOWS\System32 there is an AxPrf.OCX, but no *.hlp file.
Why is the client searching for a file that exists neither on the
workstation nor in the unpacked NW Client source installation directory?


Does anyone have any ideas why the Novell client behaves like this? It both
slows down the performance and causes unnecessary traffic on the network.


Regards,

Peter Englund
Senior Consultant
IT Infrastructure & Security
(CNE, CCNA&CCSA)