Technical Information Document
Novell client v4.83 for Windows NT/2000/XP - TID10067934 (last modified 31JAN2003)
printer friendly tell a friend
Click here if this does not solve your problem
10067934 10067934 10067934
goal

Novell client v4.83 for Windows NT/2000/XP

symptom

The Novell client v4.83 can be installed on the following Platforms using one single Installation routine:

 - Microsoft Windows NT
 - Microsoft Windows 2000
 - Microsoft Windows XP

fix

The following Changes have been made for this Client:

Added as a permanent option, Policy Packages scheduled to "disable the action after completion" will run at next boot up and login.

Added IP Address Costing parameter and Name Resolution group.

Bad Server Name Cache Enabled and Bad Server Name Cache Timeout parameters added to the Novell Client Properties, Advanced Settings.

Server Cache Timeout (Number of days before an entry is cleared out of the cache) will now be cleared at every reboot.

Added a check box to the Novell Client DHCP property page in the "Use server" area that specifies whether the data sent by the DHCP server is binary or string. The default is string (check box disabled). If the option is selected we treat the data sent by the server as binary.

Corrected the Properties for EOJ, FORCE FIRST NETWORK DRIVE and SEARCH DIRS FIRST, which were being set to "YES" in the registry if any change is made in client advanced client settings.

Fixed Disable "Save profile after successful login".

Corrected Problems with the GUI NetWare Copy program. When you say "Not to All" during the file overwrite prompt then it acts strange. It copies some files and then just seems to quit.

Fixed Blue screen when logging into NetWare from NT and the cable is unplugged.

Fixed NT4 Blue Screen if disconnected workstation does not check workstation only box.

Corrected BSOD during the login process.

Fix for IP address change and hibernating.

Added ability to recognize new DNS Suffix for VPN connections.

Able to create printer objects with the HP gateway using NWAdmin on Windows NT, 2K.

Corrected file attributes. Files on the source volume do not have any file attributes, but when they were copied to the NSS volume via ZENworks (NAL) the Hidden, System, Read-Only, and Shareable file attributes were added to the file.

Corrected an issue where EXE files restored from backup would not run.

Resolved Error: "Unable to detect network card, check documentation for a list of supported cards."

Resolved Error: "DOS Error 5 encountered during network startup. Timeout and access denied to tsinst.ovr”.

Able to rename/create a directory at the root of a volume.

Able to save MS Office XP Word and Excel documents to Novell NetWare directory. MS Word displays a message box stating, "Word cannot complete the save due to a file permission error. (H:\test.doc)".

Changed Client to rename or move a file without decompressing the file.

Fixed the Client to not add any file attributes during a copy. When you perform a file copy with a DOS utility to a NetWare volume, the Shareable flag is added to all files. This occurs from any DOS copy utility such as, copy, xcopy, and robocopy. It does not occur when the copy is done from Windows Explorer.

Added ability to detect an IP address change automatically and mark all devices as auto-reconnect. This process is detected after a user attempts to access a network resource.

The default setting for IP costing is ON.

Fixed an issue where moving a directory structure within a mapped drive would append the directory rather than merging it.

Fixed a Blue Screen, which occurred when using the Novell Client and Norton AntiVirus.

Corrected slow opening of MS Word files that were holding references to Servers in different networks.

Corrected NT Terminal Server blue screens, which occurred when a session is shadowed.

Corrected issue where leaf objects are displayed instead of the (O) and the (OU) from the Login window, when browsing to select a container.

Fix for shareable flag.

Allow the client to RIP for IPX network server if found through bindery call on Windows 2000.

Connecting to NWSAA via EXTRA, LAN traces indicate the client versions that fail are switching part way through to IP when talking to the NWSAA boxes. Working clients always communicate IPX//SPX.

NT Client will create ServerCache registry keys to persistently cache server names.

The workstation will shu.tdown after unlocking the screen when the locked SAS screen is active and the machine is brought into hibernation mode and back up.

Client will set Temp and TMP environment Variables correctly on Windows 2000 Terminal Server and User Profiles.

Resolved intermittent issue where after successfully changing the NT password user is unable to login. The redirected NT4 server was running DHOST, but the replica had been removed incorrectly using NDSManager. DHOST was still running but after the password was changed successfully, the re-login failed, because samsrv tried to resolve the user on the non-existing local replica.

On Windows 2000 NWGINA will read the "Default User" registry key. The functionality is redirecting Windows 2000 to use a different profile than the default user profile.

If a user profile was created without the Novell Client being installed or with an older version of the Novell client, the user had only read access to the policies registry key.

Changed the default to allow shutdown & power off options.

Fixed a problem that caused a blue screen on NT 4.0 machines during boot and login.

Corrected when the NDS username was entered with a trailing blank, the local account created by DLU had a trailing blank, too.

Ability to tell the version of an NLM by doing Windows properties on the file. The values of more than just 0-9 must be valid to work with NDS build numbering scheme. Alphanumeric values must also be valid.

Able to load printer drivers from the workstation; No longer prompted to use a CD for the drivers.

Corrected a problem where applications would hang when printing on Windows XP.

Printers are correctly displayed in start/settings/printers. Error displayed when printing was "Operation could not be completed The RPC server is unavailable". From start/settings/printers, right click on a printer and select properties the error "Printer properties cannot be displayed, the filename, directory name, or volume label syntax is incorrect" is displayed.

Fixed a memory leak that appeared when the workstation object could not be authenticated.

Updating the Novell Clients and Remote Management with a UNATTEND.TXT file using SETUPNW.EXE /ACU /U caused the workstation to go into a reboot loop.

Changed the Novell Client to remove the MS Client for NetWare at the end of the install rather than having NWGina do it after the reboot.

The Client will now detect the protocol selection chosen by the user and make the necessary registry adjustments on Windows 2000/XP. On an IPX only install, the preferred protocol will get set correctly to IPX.

Fixed Multicast problem from occurring when the IP address is unavailable.

Added new registry setting to allow the user to set the default port number.

When using a Windows XP workstation, ConsoleOne v1.3.2 and attempt to edit the Windows 2000 Group Policies properties, you are unable to set the security settings for the Group Policies.

During a workstation printer policy update, the user settings were lost even though the printers were unchanged.

Fixed an Explorer page fault when building property sheet for NetWare volume information.

The statistical Information of NetWare volume was not correct.

Fixed the following three distinctive errors: 1) the start/settings/printers does not show any printers. 2) when printing receive the error "Operation could not be completed the RPC server is unavailable" 3) under start/settings/printers, right click on a printer and select properties. Receive an error "Printer properties cannot be displayed, the filename, directory name, or volume label syntax is incorrect".

Added code to speed things up in disconnected case. The Client will now get the status of the printer and connection in a background thread. Also the installed list in updated on a background thread.

SPOOLSV access violation when canceling print job from Microsoft Office 2000 application.

When the installed NDPS Printer configuration has values that are out of bounds with the locks or limits in the NDPS default printer configuration the application that is printing appears hung.

NDPS public access printers fail to install.

Running Windows Terminal Server with Novell Client and enabled AutoAdminLogon to Windows but the system is setup to manually login to NDS. The Logon Setting's in the RDP-TCP Properties are set to 'Always use the following Logon Information'. When this setting is enabled, the Terminal Server session will automatically logon to Windows using the pre-defined NT user credentials for all Terminal Server sessions with the same user account. The user should be able to enter the NetWare user credentials and perform an individual logon to NetWare.

When AutoAdminQueryNDS is enabled; the NT/2000 tab fields are disabled wherever the NT/2000 tab gets displayed. This is appropriate when an automatic NT login is actually going to occur and we can't support those credentials being changed mid-stream. One place where this is not appropriate is when editing the location profile from the Novell client properties; the NT/2000 tab is being disabled in this display as well, which prevents editing the defaults for that portion of the tabs. Another scenario under which this may be inappropriate is from Terminal Server, when AutoAdminLogon has /not/ been configured but a terminal server set of automatic credentials has been passed in. For that scenario the user wants to set AutoAdminQueryNDS so that the terminal sessions are prompted for NDS credentials, but there is no AutoAdminLogon occurring from the terminal server console session. But, because the AutoAdminQueryNDS flag is set, the NT/2000 tab is grayed out even on the terminal server console (not just in the terminal server sessions that actually have automatic credentials).

When the first server in the preferred server list is unavailable, the Client will try the next one in the list by having the DHCP option 85 configured with a list of IP addresses of preferred servers that the client can use.

If the keys for Tree or Context are a binary type (like set by DHCP), there are garbage characters at the end of the tree or context name.

Fixed when NAL is in disconnected mode and launch scripts are run, the Client would try to connect to the network.

Able to view or browse for the Alias Container to set the context by browsing the directory via the Context radio button under the Advanced section of the Novell Logon window.  Previously only able to authenticate via the Alias Container by manually typing in the context in the context field under advanced section.

Allow shutdown and power off option to indicate cancel of login attempt.

Corrected random unlock failures when using NDS.

Unable to reboot workstations with a reboot utility run by an administrator on the NT domain which allows a reboot of Win NT and Win 2000 workstations logged into the domain. If Novell NWGINA is the primary GINADLL and the workstation is locked the reboot utility it says it will reboot the workstation but does not until the user actually unlocks the workstation by typing the username and password.
        
Login writing temporary files to non-terminal-safe location.

Login creates a temporary file called "WINNT~lgnw32.tmp" in the root of the Windows NT boot drive. Login is in fact reading the Windows directory, but when building the filename there was no back slash put between the path and the file name.

No advisory was being provided when the password is expiring.

Fixed Explorer page fault when getting NetWare volume information.
.

Document Title: Novell client v4.83 for Windows NT/2000/XP
Document ID: 10067934
Solution ID: NOVL70351
Creation Date: 29JAN2002
Modified Date: 31JAN2003
Novell Product Class: NetWare

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.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.