bei den vielen Bugs seit dem letzten Release.... Ich werde mal das Dingens ausprobieren.....

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Novell Client v4.83 Support Pack 1 for Windows NT/2000/XP Known Issues July 2002 [...] 3.0 Changes Since Last Support Pack - Resolved dialup connection issue when using the Border VPN Client does not work. Receive error Tree or Server not found . With changes made to SRVLOC.SYS and to the Border VPN client, the DA is brought up, but SLP responses are not properly formatted. - Workstation exploring server with 10 volumes will have each volume duplicated one additional time. If the server has 13 or more mounted volumes explorer will display each volume 25 times. - Using any WNetAddConnection interface to map a drive (Novell's Novell Map Network Drive , Microsoft's Map Network Drive , etc.), if a UNC in the format servervolume: is provided (the colon character : being what's in appropriate here), the Novell client will still successfully map this drive. When you try and bring up the properties of the drive, file or directory using that mapped drive, Windows Explorer will go into a non-responsive state. On the wire it can be seen that the workstation in requested the volume mount number of volume: (which is invalid, because the volume name is volume ), after which the workstation performs a bindery scan to see whether this is the name of a print queue. This sequence is repeated with all possible haste and without end, which causes high utilization on the NetWare server being queried (both from the NCP traffic and the bindery scan). For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10070345.htm - Problem occurred on Windows 2000 terminal server as well as Windows 2000 Professional. Trying to delete the Profile after logout via setting the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon subkey and set the DeleteRoamingCache value to 1. If the user has a manual drive mapping the profile will not be deleted. The USERENV.LOG reports a failure due to a registry key being held open. - The Nortel VPN changes the domain in the registry a few seconds after the new IP address event is given. The Novell Client does not recognize this change and uses the original domain. The original domain may have been configured via TCP or was set via DHCP. - NT blue screen by using the AutoAdminLogon. - Fixed problem where DHCP domains were not being used for Windows 2000. Could not login when only Tree name is specified over a dialup VPN connection - Password synchronization product change. - Improved exception handling. - Improved clustering reconnects on a hard failover. Only works on Windows 2000/XP. This change has no effect on NT 4. - DENY WRITE flag did not get set on Windows 2000. - Files held open indefinitely on network after installing 4.83 Client. - WestGroup's Premise application fails to allow more than one user to access the software, due to licensing problem. There is no problem on NT, only on Windows 2000 or XP. For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10069268.htm - The roaming profile, when created, seems to strip off attributes. If there is a hidden file stored locally after logout, that hidden file is copied up to the home directory as UN- hidden. No real problem until that user moves to another machine that does not have the user's profile. When the profile is copied from the Home directory, then the file appears on C: as NOT hidden. The file DESKTOP.INI, is a hidden file in the Startup group and is launched into notepad after the above process makes it UN-hidden on the 2nd computer system. After logging out of machine A, logging into machine B gives you the following message: Your roaming profile is not available. The operating system is attempting to log you on with your locally stored profile. - If the Minitab application (network version) is installed on a NetWare server volume, opening worksheets from the Minitab application (file - open) fails entirely, or the sheet is only partially read into the application. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10069268.htm. - The OnDemand install fails, showing Access Denied errors in its log file on both files. - When viewing the properties of a file on a NetWare volume (using Windows Explorer), the Creation and Accessed date is correct, but the time is always displayed as 12:00:00 AM. The Modified date and time are correct. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10067381.htm - Running the 4.8/4.8SP3 client on WinNT, when you create a directory on through a mapped drive and then CD to that directory, the name of the directory (as shown in the command prompt $p$g) is all uppercase. It only occurs when the directory name is 8.3 or less. This is a problem with Java apps which are case sensitive as to the directory name. For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10065315.htm - Client 4.83 with latest patch truncates Visio 2002 documents when attempting to open from server. If document is stored on local machine problem does not occur. - Unable to save Word files to a network drive. Error Word cannot complete the operation because too many files are open. - Fixed a Blue Screens on disconnect. - For clustering to reconnect on a hard failover set the TCP KeepAlive attribute on the connection. Only works on Windows 2000/XP, there is no effect on Windows NT 4. - Added code to handle invalid volume names. Now check for connection to the specified server if it is then return a success, otherwise will check for the bad volume name. - When remote controlling an XP workstation, access is not denied if the user does not have RemoteInteractiveLogon right or if DenyRemoteInteractiveLogon is set. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10071376.htm - _vb_script__ run from Active Directory Group Policy _object_ does not populate Logonserver variable. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10072045.htm - Group Policies do not get applied on XP workstations when logging into NT4 domain. - High utilization on Citrix Terminal Server with published applications. - Fixed problems where certain policies did not get applied because the user was not able to read the settings. - The TEMP and TMP variable are sometimes set to long directory names, which causes problems with 16-bit applications. Now enforce that the TEMP/TMP variable as a short directory. For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10069264.htm - If AutoAdminLogon is configured, we do not want to save the settings to the registry in case that AutoAdminLogon was bypassed by pressing the shift key or when logged off on Windows 2000 without ForceAutoLogon set. This would break a subsequent autologon, because the user name would be changed. For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10070755.htm - On Windows XP if a cached logon occurred, a warning message appeared on the wrong desktop. The machine appeared to be hung. After the timeout of 2 minutes it was closed and the logon process continued. - Configuring the DLU Restriction Policy to Exclude or Include certain workstations an error pops up when you try to login to a workstation that is excluded. Error: Your NDS user has been associated to a Dynamic Local User policy. The workstation has been restricted from using this feature. Contact your system administrator. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10070003.htm - Added feature to turn off the DLU functionality from the client side. - 4.8x NWIP clients can't RCONSOLE across subnets. - BSOD on NT4 w/NDS stopping NetMail Manager Service while connected to ModWeb. - Updated to correctly return byte count for enumerated data names, and to close the registry key in all return paths. - Workstations get very slow response from the network when trying to open files that check for printers. For more information, see
http://support.novell.com/cgi- bin/search/searchtid.cgi?/10061185.htm - The customer noted that if they pushed Novell print provider to the bottom of the Windows print provider order, or if they removed the Novell client entirely, their LanMan-_base_d remote printer connections would be enumerated successfully. With either Novell print provider installed & positioned ahead of LanMan in the print provider order, enumeration of the installed LanMan-_base_d printers would fail. For more information, see http://support.novell.com/cgi- bin/search/searchtid.cgi?/10070604.htm - If you try to PING specifying an abnormally large number of characters, a DRWATSON will occur. - Client is configured to use a BM VPN connection to
... read more »