NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Novell Client 4.9 Post-SP1 Update "B" TID #: 2968980 README FOR: 49psp1a_pkb.exe SUPERSEDES: 49psp1a_loginw32.exe 49psp1a_nwfs6.exe 49psp1a_nwgina_b.exe 49psp1a_nwsrvloc.exe 49psp1a_pka.exe NOVELL PRODUCTS and VERSIONS: Novell Client v4.9 for Windows NT/2000/XP ABSTRACT: 49PSP1A_PKB.EXE is a collection of client patches for Novell Client 4.9 SP1a. These files are NOT a support pack, but are fixes to problems found after the 4.9 SP1a client was released. In addition to including all the files in 49PSP1A_PKA.EXE, 49PSP1A_PKB.EXE is the public release of the following files previously released for beta test: 49PSP1A_LOGINW32.EXE 49PSP1A_NWFS6.EXE 49PSP1A_NWGINA_B.EXE 49PSP1A_NWSRVLOC.EXE Patch release history: 27May2004 - Original Beta Release of 49psp1a_pkb.exe 09Jun2004 - Re-released with correction to file location for loginw32.dll. No program files were changed. 22Jun2004 - Re-released, documenting a problem relating to ZENworks 3.2 Remote Control. No program files were changed. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: == PRE-INSTALLATION == 1. This patch kit is designed to update the Novell Client v4.9 SP1a for Windows NT/2000/XP. Be sure to install only on this version of the client. == PATCH INSTALLATION == 1. Expand the self-extracting file 49PSP1A_PKB.EXE (this file) to a temporary folder. 2. Open the folder. 3. (recommended, but optional) Rename the existing files (with a .old extension, for example) which will be replaced with this patch kit in the following locations. \System32\netware NWDHCP.SYS NWFILTER.SYS NWFS.SYS NWSLP.SYS SRVLOC.SYS \System32 LOGINW32.DLL NETWIN32.DLL NWGINA.DLL NWSPOOL.DLL NWSRVLOC.DLL SLPINFO.EXE Do not reboot before proceeding! 4. Right-Click on _49PSP1A_PKB.INF and then click on INSTALL. 5. You will be prompted to reboot. A reboot is required to complete the installation. Note: Installation of the registry settings described in the "Issues" section of this readme can be automated by uncommenting the respective lines in _49PSP1A_PKB.INF. == OVERLAYING THE 49SP1aCLTe.exe INSTALLATION SET == The files in this package can also be overlaid on top of a Novell Client 4.9 SP1a installation set so that when SETUPNW.EXE is run to install the Novell client you will be installing the core 4.9 SP1a client and the updates contained in this package in one operation. To update the installation set with all the files in this patch set, extract this package to a temporary location, then copy the resultant directory structure to over the top of the i386 folder in your "Novell Client 4.9 SP1a" installation. Note that the updated OEMNPRNW.INF file in this package applies only to English versions of the Novell Client 4.9 SP1a for Windows NT/2000/XP installation set. 22Jun2004 - After overlaying these files on the 4.9 SP1a installation set, a custom install of the Client and ZENworks 3.2 Remote Management will result in Remote Management not being installed properly. After importing the machine, an attempt to remote control it from ConsoleOne will result in the error "Remote Management not found." This problem is resolved in the 4.9 SP2 package. ISSUE: This collection of Post-4.9 SP1a patches fixes multiple issues, including the following. New items since 49PSP1A_PKA.EXE are marked with an asterisk. Fixes to LOGINW32.DLL: *1. The client can use a previously set server IP address instead of waiting for DHCP option 85 data. This problem can result in the workstation connecting to the wrong server when the "preferred server" information is delivered through DHCP option 85. This happens because the workstation goes to a new location (and therefore a different DHCP server giving a different IP address for the "preferred server" option 85), it then connects to the *previous* server and not to the new server given via DHCP. Typically, the observed behavior is the workstation will try connect to the IP address delivered by the first DHCP server. See TID 10092123. (355489) *2. eDir Admin user is unable to unlock locked workstation using smart card. See TID 10089561. (100352346) *3. Windows Explorer intermittently will not load. See TID 10090679. (358887) *4. Microsoft Encrypted File System (EFS) has problems when passwords are being changed. See TID 10090015. (354361) *5. Enhanced GINA to detect the status of the LAN connection. (347029) *6. Unable to unlock the workstation to logout current user. See TID 10090862. (357620) *7. "Unlock Workstation" dialog says nothing about the new "Force Logoff" feature. This build contains the fix for English only; other languages will be included in SP2. See TID 10089354. (100351812) *8. Unexpected results logging in to MetaFrame XP through ICA session. (360366) Fixes to NETWIN32.DLL: 1. -601 errors when administering BM or changing passwords. See TID 10092091. (363180) Fixes to NWDHCP.SYS: 1. Intermittent login issues - problem with using dhcp options 78 and 79. (358433) 2. Workstation connects to the wrong server when the "preferred server" information is delivered through DHCP option 85. When the workstation goes to a new location (and therefore a different DHCP server giving a different IP address for the "preferred server" option 85), it then connects to the *previous* server and not to the new server given via DHCP. The problem is caused by NWDHCP.SYS loading late, and was resolved by removing NWDHCP dependencies on the resource manager.(360121, 355489) Fixes to NWFILTER.SYS: 1. NetWare 4.90 client Can't Login (map CIFS shares) to a Linux Samba Server. See TID 10091617. (355747) Fixes to NWFS.SYS: 1. Fixed random Blue Screen. (358838) 2. Blue screen on Return from Hibernation. (100352632) 3. Client drops connection to server while browsing volume. See TID 10089964. (357723) 4. Properties on 4GB+ file are incorrectly reported. For example, a 7.25 Gig file opened in Windows Explorer displays the file size as 7.25 GB, but if you right click on it and go to Properties, it says the file size is 4.00 GB on disk and from that point on, Explorer also reads the wrong file size. (346580) 5. Blue screen on Windows 2000 when coming out of suspend mode. See TID 10088501. (355605) 6. Windows paged kernel memory increases every time an automated XCOPY command is run against a NetWare server. (357720) 7. Excel files incorrectly locked when using 4.9sp1 client. See TID 10089899. (357714) 8. Read-Only error message opening "Word" document when resuming from "Stand by mode". See TID 10085578. (353149) 9. Opening files fails in various read/write modes with various lock modes specified. See TID 10089765. (357611) 10. 4.91a client with IPX enabled conflicts with AT&T Dialer / VPN. See TID 10091739. (361574) *11. Novell Client not requesting "Last Accessed Time" from NetWare 5.x+ servers. See TID 10081957. (345195) *12. Remove NWDHCP dependencies on the resource manager. (360121) *13. Read-Only error message opening "Word" document when resuming from "Stand by mode". See TID 10085578. (353149) *14. Latest client frequently dropping connections on XP. (362117) *15. When resetting pwd, date gets set to 1/1/92. See TID 10090680. (355285) *16. Cookies redirected to a NetWare server no longer work after applying 4.9 client. See TID 10090929. (359790) *17. Stop Error KMODE_EXCEPTION_NOT_HANDLED. See TID 10092155. (359121) *18. No error message when a user attempts to delete a file without rights. See TID 10092271. (363524) *19. Premise application licensing fails. See TID 10069268. (364815) *20. Blue screen when copying files. (363927) *21 XP blue screen upon login. Error is: "Stop: C000021a {fatal system error}. (363888) *22 On a Citrix terminal server with Zen 4 and Workstation Manager, there is an accumulation of invalid entries in the scope table; entries that apparently belong to a system process that made some reference to a NetWare resource and then exited without cleaning up. (365000) Fixes to NWGINA.DLL: 1. "Local Profile Newer" message with volatile Dynamic Local User See TID 10087202. (100349051) 2. Every terminal and console session except for the one first logged-in on to hangs, including being hung at a point where the Novell login dialog isn't displayed (just a blank desktop, prior to the Novell login even being offered). See TID 10090828. (359598) 3. Error: "The system cannot find the file specified" See TID 10088438. (100350183) *4. Wrong user can show up in the "NetWare Security" screen. See TID 10090140. (358018) *5. Microsoft Encrypted File System (EFS) has problems when passwords are being changed. See TID 10090015. (354361) *6. Unable to logon to NT domain with the 4.9 client running on Win 2003 Terminal Services. See TID 10087706. (100354077) *7. Roaming Profile doesn't read GP Exclude Dirs first time when profile is copied. See TID 10092087. (362104) *8. Unable to map Microsoft shares after upgrading domain controller to Windows 2003 Server. (363333) *9. Roaming profiles are not being applied. See TID 10092430. (365681) Fixes to NWSPOOL.DLL 1. Print queues fail to connect on bootup from the printers folder on WinXP. See TID 10091524. (350548) Fixes to NWSRVLOC.DLL 1. Lotus notes hangs on shut down after installing the 4.9 client on systems running Windows 2000 and higher. See TID 10091085. (360243) SRVLOC.SYS, NWSLP.SYS, and SLPINFO.EXE Support for SLP v2 has been added. With these files installed, the client will be able to communicate with any SLP Directory Agent which supports SLP v1 or v2. Note that Novell's SLPDA.SYS running with eDirectory 8.7.1 does not support SLP v2. The client modules included in this patch can support SLP v1 and/or SLP v2. Support for both version is the default. The next release of the client support pack will include an interface allowing you to configure SLP to interoperate with SLP v1, v2, or both. A new version of slpinfo.exe which displays the version of SLP is also included in this patch. Fixes to SRVLOC.SYS 1. Fixes a problem with send error handling. This resulted in the client resending an SLP packet after receiving a send error. This fix can be augmented by the DependOnService registry setting. If the Client loads before the SLP service is running, resources which cannot be found as a result of this condition may be added to the bad server cache, resulting in "tree or server cannot be found" type errors. This setting ensures that the SLP service is loaded and running before the Novell Client attempts to load. Nwfsxp.reg (or Nwfsnt4.reg for Windows NT4), a .reg file which will install the registry key, is included in this patch. It installs this registry key: For Windows 2000, XP: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation] "DependOnService"=hex(7):53,00,52,00,56,00,4c,00,4f,00,43,00,00,00,00,00 For Windows NT4: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation] "DependOnService"=hex(7):53,52,56,4c,4f,43,00,00 See TID 10092086. (360525) 2. Active Directory domain controller blue screen in srvloc.sys See TID 10091108. (353431) Fixes to NWSLP.SYS 1. The way the client forms SLP requests is inefficient. SLP requests are formed such that every DA holding partitions that include any component of xxx.root.tree respond. This version of NWSLP.DLL changes this behavior, introduced 11Jun2003, such that we now search only on the last component of the name. Occassionally, this change can cause the client to intermittently fail to login. The error "Tree or server name cannot be found - would you like to log into NT?" may be displayed. See TID 10080035. (338563). This change reverses the fix described in this TID, but a new registry value allows the client to behave either way. WildCardLastLevelOnly.reg, a .reg file which will install the registry key controlling this behavior, is included in this patch. NOTE: The registry entry is not needed if you want to use the default. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NWSLP\parameters] "Wild Card Last Level Only"=dword:00000001 Options for this value include: dword:00000001 = search only on the last component in a name. This is faster but can result in the "Tree of server cannot be found" error. (This is the default.) dword:00000000 = search on every component in a name. This is slower, but more robust. NWSETUP.DLL, NCIMAN.EXE and OEMNPRNW.INF These files are used before and during a client install. They are intended to be overlaid on top of a Novell Client 4.9 installation set, and are not installed when _49PSP1A_PKA.INF is executed. Fixes to NCIMAN.EXE and NWSETUP.DLL 1. "DHCP Settings" tab hangs when selected. See TID 10091109. (100353274) 2. DHCP location profile setting gets lost when opening property page through network control panel. See TID 10091319. (100304148) Fixes to OEMNPRNW.INF Note that only the English version of this file is included in the patch kit. Builds for other languages will be included with the 4.9 SP2 client. 1. SETUPNW /ACU does not write Major/MinorInternalVersion values to registry on NT. See TID 10090890. (358122) Self-Extracting File Name: 49psp1a_pkb.exe Files Included Size Date Time ..\ 49PSP1A_PKB.TXT (This file) NWFSNT4.REG 137 2-20-2004 8:41:30 am NWFSXP.REG 380 2-20-2004 8:10:56 am NWSETUP.DLL 620032 2-17-2004 2:08:12 pm WILDCARDLASTLEVELONLY.REG 320 4-1-2004 2:45:10 pm _49PSP1A_PKB.INF 1886 6-9-2004 12:47:00 pm ..\ADMIN\ NCIMAN.EXE 777216 2-17-2004 2:01:02 pm ..\LIBS32\ LOGINW32.DLL 393299 3-31-2004 10:06:08 am NETWIN32.DLL 272384 3-12-2004 4:22:16 pm ..\NLS\ ..\NLS\ENGLISH\ OEMNPRNW.INF 526187 1-16-2004 11:54:02 am ..\REDIR\ NWDHCP.SYS 16176 2-23-2004 10:52:38 am NWFILTER.SYS 15762 1-12-2004 9:17:10 am NWFS.SYS 475118 4-19-2004 1:50:04 pm NWGINA.DLL 352336 4-12-2004 4:22:12 pm NWSLP.SYS 19375 3-5-2004 8:46:32 am NWSPOOL.DLL 229445 2-23-2004 7:32:46 pm NWSRVLOC.DLL 29632 4-22-2004 6:50:18 am SLPINFO.EXE 24928 3-5-2004 8:48:16 am SRVLOC.SYS 152976 3-5-2004 8:47:36 am ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------