Return to nwtips.htm
For WinNT/2k/XP clients, see http://www.ithowto.com/novell/clientspeed.htm
for info on optimizing bindings, name resolution, etc. Below are my own recommended settings in
addition to the settings from the link above.
DOS with VLM 1.21 (add these to NET.CFG): lock delay=0 lock retries=1 ;load FIO.VLM into conventional memory for faster performance. load low FIO = ON ;load these VLMs into conventional memory for faster performance. load low REDIR = ON load low NETX = ON load low CONN = ON load low IPXNCP = ONYou can download my DOS ODI Boot disk with NETX/VLM support: nwbtdos.htm
Novell Clients for Win9x/ME:Novell Client properties -> Advanced -> Cache Writes = off Close Behind Ticks = 0 Delay Writes = off File Write Thru = off Lock Delay = 0 (1 is minimum on some versions) Lock Retries = 1 Opportunistic Locking = OFF (not present on some versions) True Commit = off (unless server is unstable) Novell Clients for WinNT/2k/XP (see section below also):Novell Client properties -> Advanced Settings -> Burst Mode = on, in some rare cases, off may be faster for 2K/XP/2003. File Caching = off File Commit = off (unless server is unstable) Disabling file caching (Op-locks) on the server: Set client file caching enabled = off (NW 5.0 and later) set Level 2 oplocks enabled=off (NW6.x only)
For
maximum compatibility and performance, I recommend installing the client for
IPX only or at least make IPX the preferred protocol. If you must use IP, install the client for IP only if you don’t
require IPX/SPX compatibility.
Installing with both IP and IPX will be somewhat slower.
1. Make
sure you have IPX bound to a specific frame type (i.e. 802.2) on each
workstation.
2. Make
sure only the Novell client is bound to IPX, that the MS Client uses only IP or
NetBEUI.
3. Make
sure all IP name resolutions methods are disabled in the Novell Client.
You can
use IP instead of IPX, make the appropriate changes to steps 1-3.
4. Set the
"Name Resolution Timeout" = 2 seconds (or 1 second) in the properties
of the Novell Client.
5.
Minimize (and standardize) the IPX frame type(s) used on the servers. I recommend 802.2 only if possible.
6. See the
client tuning tips at http://www.ithowto.com/novell/clientspeed.htm
If those
don't make a significant difference, try an older client. The following work well.
Do a
“custom” install, IPX only (or IP only), no NMAS, no NICI. Only install NMAS or NICI if you are running
a NW 6.5 server AND you need those features (most installations do not need
these).
Client
version recommendations:
Most
testing was done with NT4sp6a and W2ksp3/sp4 workstations using IPX to NW 4.2sp7
and NW5.0sp6a servers with traditional NW volumes. I’ve only done sporadic testing with NSS and no testing with NW
6.x. Therefore, your results may vary. Here’s a test program that I wrote for
testing file sharing and locking capabilities of the clients, OpenTest
Do Not
reboot after installing each patch, apply all patches, then all registry
settings, then reboot.
All
patches can be applied by right clicking on the .INF file and selecting
"Install".
The
Microsoft Client/Gateway Service for NetWare (CSNW/GSNW) works well for basic
file and print services, however, it has these issues:
1. You
can't do any administration of the NetWare server.
2. It is
restricted to IPX connections only. q222059
3. You
don't get the 'right click' context menu options for 'salvage' or 'purge'
4. It
doesn’t support long file names on NSS volumes. q216361
5. You
don't get the 'send' message to user/group functionality.
6. The
user name and password on Windows and NetWare must match.
7. Each
user must configure the NDS Tree name and Context the first time they log into
a given workstation. They must also
click the check box to enable login scripts on that first login. According to q163979,
you can set defaults for these options.
8. Once
step 6 is completed, there is no easy way to login to Windows without logging
in to NetWare.
9. It
doesn’t support NCP packet signing. q216489
10. It
doesn’t support contextless login. q216821
11. If the
NetWare server is unavailable (or the network cable is disconnected, etc.),
there may be a long delay on login as it tries to find the NetWare server.
12. If you
have a user in multiple contexts, he/she must have multiple Windows usernames
to login to the different contexts.
13. Mobile
(i.e. Laptop) users may have difficulty logging in at different locations.
W2k (sp3/sp4) and XP
(sp1/sp2) clients:
The MS
Client Service for NetWare generally works well, as long as you don’t need the
features of the Novell client and can live with the limitations listed
above. WinXP prior to sp2 has a bug
that keeps it from releasing the NDS connection on logout, see q823189
for details. There are some potentially
significant issues with CSNW/GSNW prior to W2ksp3 and WinNTsp5 and minor issues
with WinNT sp5/sp6, W2k sp3/sp4, and WinXP sp2. Search the MS knowledgebase for ‘CSNW’ to find these.
4.91sp2 +
491psp2_pkb works very well for Win2ksp4 and XPsp2 (I haven’t tested other OS
service packs, but haven’t heard of any issues either). I haven’t tested 491psp2_pkc, but it will
likely work well also. I have been
testing it IPX only without NMAS because I’m using it with a 4.2 server that
won’t use IPX and I have nothing that would benefit from NMAS.
4.9sp2 +
49psp2_pkc (+ optional post pkc patches).
Preliminary testing (very preliminary) indicates this version works well
on W2ksp4.
Client 4.83 with sp2 - 4.83 patches
4.83sp3. Optionally install 483psp3_pka (I haven’t personally tested 4.83sp3. It’s reported to work well, but I suspect it
has the same file closing issues seen in 4.9sp1 above since I’ve seen those
issues with the NWFS.SYS included in 483psp3_pka)
4.83sp2 + 483psp2e (This is the combination I use for W2k with the settings in this document. It has minor file locking issues, but it’s the best Novell Client I’ve found for W2k.) Moderate testing indicates this combination works well with XPsp1 (XPsp2 not tested).
On 4.83
(sp2 + 483psp2e), you may want to disable NWFILTER by running NWFINST -d (in
%systemroot%\system32\netware\ directory).
You can also disable it in later versions, but it hasn’t been as much of
an issue with 4.83sp3 and later.
Clients
prior to 4.81 should not be used on W2k, nor should clients prior to 4.83 be
used on XP.
Client 4.71 has potentially dangerous file locking issues
on W2k. I
recommend that you do NOT use it.
NT4 (sp4/sp5/sp6a) Clients:
The MS
Client Service for NetWare works well, as long as you don’t need the features
of the Novell client.
Client
4.51 is the fastest client for NT4, it works well in IPX environments.
Client
4.71 works well with NT4, but it has potentially dangerous file locking issues
on W2k.
4.83sp2+patches
(or 4.83sp3?) works well on NT4, but you should back-rev NWFS.SYS to the one in
4.83sp2 if using IPX only.
Win9x:
Microsoft's included Client for NetWare
Networks has some issues, I don't recommend it. The one that ships with W95 supports bindery login only, one with
some NDS support is available for W98.
Client 3.10sp2
Client 3.32 is reported to work well, but I
have not tested it.
NT4/2k/XP client registry settings:
Here are
some registry settings that may prevent problems (not all of these affect all
client versions, but they shouldn’t hurt either):
All
Registry settings can be applied by double clicking the .reg file, or you can
manually apply the changes using REGEDT32.
You can download the .reg files here
rem Use
same username (NDS) for Windows logon
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login\Tab
Settings\NT Credentials]
"Sync
NDS Username"=dword:00000001
-----------
rem enable
'Simple Unlock' feature
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login]
"Simple
Unlock"=dword:00000002
------------
rem
Disable 'cache exclusive' feature.
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters]
"Cache
Exclusive Open"=dword:00000000
-------------
rem
preload Bad Server Cache with local drive letters (A-Z).
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters]
"BadServer"=hex(7):41,00,42,00,43,00,44,00,45,00,\
46,00,47,00,48,00,49,00,4a,00,4b,00,4c,00,4d,00,\
4e,00,4f,00,50,00,51,00,52,00,53,00,54,00,55,00,\
56,00,57,00,58,00,59,00,5a,00
------------
rem enable
DFS (prevents BSOD on W2ksp4)
Windows
Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MUP]
"DisableDFS"=dword:00000000