Novell Client for Windows NT/2000 Release Notes 3/10/00 These notes describe new features and some issues that have not been resolved for this release of the Novell* Client* for Windows** NT/2000 software. Important: Issues specific to Windows 2000 are located in Section 10.0. Note: Additional issues associated with this release are located in TID #2955975 at www.support.novell.com. ---------------------------------------------------------------- Contents ---------------------------------------------------------------- 1.0 Client Installation 2.0 Login and Shutdown 3.0 Drive Mappings 4.0 RAS Issues 5.0 Print Issues 6.0 Driver Issues 7.0 Software Compatibility 8.0 WIN2NCS Compatibility Issues 9.0 Miscellaneous 10.0 Windows 2000 Issues 11.0 Primary Documentation is HTML 12.0 How Customers Can Get Support 13.0 Trademarks, Copyright, Disclaimer, and Patents ---------------------------------------------------------------- 1.0 Client Installation ---------------------------------------------------------------- ---------------------------------------------------------------- 1.1 Windows NT and Windows 2000 Installation Requirements ---------------------------------------------------------------- Novell Client for Windows NT/2000 requires Windows NT** 4.0 with SP3, SP4, or SP5 with at least 24 MB of RAM or Windows 2000. ---------------------------------------------------------------- 1.2 Update Required on NetWare 4.11 and NetWare 4.2 Servers ---------------------------------------------------------------- NetWare 4.11 and NetWare 4.2 servers require an update on the server prior to the installation of this Client. The server update information is located in TID 295244 in the Novell Technical Support database at www.support.novell.com. ---------------------------------------------------------------- 2.0 Login and Shutdown ---------------------------------------------------------------- ---------------------------------------------------------------- 2.1 MFC42.DLL Error ---------------------------------------------------------------- Novell Client runs with MFC42.DLL version 4.21.7022 or later. MFC42.DLL version 6.00.8267.0 is installed when you install Novell Client. If an older version is installed over the version installed by Novell Client, the client login fails with an error message similar to the following: "The ordinal 6453 could not be located in the dynamic link library MFC42.DLL." The actual message might vary, depending on the version of mfc42.dll that you are using. To recover from this error, reinstall the correct version of MFC42.DLL. You can find the correct file on the ZENworks* CD at: D:\PRODUCTS\WINNT\I386\LIBS32\MFC42.DLL Copy the DLL to the following directory on your workstation: %SystemRoot%\system32 Copying MFC42.DLL will fail if some component is using the file. If the copy fails, try renaming %SYSTEMROOT%\SYSTEM32\MFC42.DLL to %SYSTEMROOT%\SYSTEM32\MFC42.OLD and then try copying the new version again. ---------------------------------------------------------------- 2.2 Login Restrictions Set for IPX/SPX Prevent User From Logging In ---------------------------------------------------------------- Symptom: Login restrictions are set for IPX/SPX* and the node address. When the administrative workstation is reset, the new client files are automatically updated and the reboot prompt is displayed. After restarting, the workstations that are placed in the restriction list as being able to log in as admin and which now have the new client cannot log in and no administration of the server can be done. Cause: This is a problem with preferring the IP protocol. The allowed addresses assigned in NDS* are IPX* address. If the server is bound to IP, the clients are designed to prefer this protocol by default. The result is that the client is attempting to log in to the server using IP but the address is restricted to only allow IPX addresses, causing an authentication failure. This is due ultimately to the IP address not being stored in NDS. Solution: Do not bind IP to the server until static IP addresses have been assigned. Or, change your protocol preference to IPX. ---------------------------------------------------------------- 3.0 Drive Mappings ---------------------------------------------------------------- ---------------------------------------------------------------- 3.1 MAP.EXE Might Fail When Mapping a Drive to an NDS Object ---------------------------------------------------------------- MAP.EXE is not IP-aware for NDS objects. As a result, MAP.EXE might fail if you try to use it to map a drive to an NDS object, for example with a command like the following: MAP N .mydir.organization.company The failure will result in a message such as: MAP-4.13-195: Directory [N .mydir.organization.company] cannot be located This error can be avoided by using one of the following solutions: * Use "MAP N SERVER\VOL:\DIRECTORY" instead of "MAP N .mydir.organization.company". * Unbind IP from the server that the NDS object points to. * Configure the Protocol Preferences of Novell Client property page to use IPX only. ---------------------------------------------------------------- 3.2 Errors When Reconnecting Permanent Drive Mappings to Servers in Different Directory Trees ---------------------------------------------------------------- In Windows NT 4.0, users might encounter an error when restoring permanent drive mappings to NetWare servers in different trees. These mappings will be authenticated through NDS. The user might get an "Invalid Password" prompt when restoring these drives. This is not because the password is invalid, but because the client does not have a valid context for the secondary tree. If this problem is encountered, enter the default context for all Directory trees on the Client tab of the Novell Client Configuration page. This is accessed by right-clicking Network Neighborhood, then clicking Properties > Services > Novell Client for Windows NT > Properties. ---------------------------------------------------------------- 3.3 Permanent Connections ---------------------------------------------------------------- If you have a permanent drive mapping that conflicts with a drive mapping made in your login script, a dialog box appears indicating that an error occurred while reconnecting the drive and that the local device name is already in use. One of the options in this dialog box has some confusing results. If you check Do Not Try to Restore the Connection in the Future and then click Yes or OK, the drive mapping made from your login script is removed. If you do not check this check box, the drive mapping from your login script is preserved. This is a bug in Windows NT itself. By default, Windows NT removes any mappings on that drive letter without checking to see whether existing mapping is the same path as the permanent connection. ---------------------------------------------------------------- 4.0 RAS Issues ---------------------------------------------------------------- ---------------------------------------------------------------- 4.1 TCP/IP Networking Issues Using LAN and Dial-Up Adapters Together ---------------------------------------------------------------- There are TCP/IP networking issues when you establish a RAS connection from a workstation with a LAN adapter. These issues might alter the state of the connections that were active at the time when the RAS connection was established, or they might keep you from establishing new connections. Please see the Routing TCP/IP Packets On a Multihomed RAS Computer article (ID Q138878) in the technical support section of the Microsoft* Web site. ---------------------------------------------------------------- 5.0 Print Issues ---------------------------------------------------------------- ---------------------------------------------------------------- 5.1 Printer Driver Setup ---------------------------------------------------------------- Associating a printer driver with a printer or queue in the printer policy packages requires driver files to be copied to a server. The path that these files are copied to is displayed in the Path box in the Setup Printer Driver dialog box (which is displayed when you select New Driver in the Printer Policy dialog box). Users or workstations must have read file/scan rights to this path (SYS:PUBLIC on the server where the queue resides) if the workstation or user package is to be able to download these drivers to the workstation. The printers associated with a package will not be installed if the drivers are not downloaded. When you select a driver to be associated with a printer, you might be asked to enter a path where an .INF file or driver is located. If you are setting up drivers for an NT package while running Windows 95, you are asked to enter the path where the NTPRINT.INFis located. This file is located in the WINDOWS\INF directory, the windows directory being the directory where NT 4.0 is installed. The easiest thing to do is to copy all of the files from the I386 directory of your NT installation CD to an area on a server or the workstation, and then copy the NTPRINT.INF file to that same directory. Once you have given the path to the .INF file, a list of drivers displays. Select the driver you want. You might then be asked where the driver files are located. (If you have put the drivers and the .INF file in the same directory, you might not be prompted for the location.) If the drivers are somewhere else (usually on the NT install CD if you have not copied them to a different path), then browse to the path or type it in. The files are then copied to the path on the server. If you are setting up drivers for a Windows 95 package while running Windows NT, you are prompted to enter the path to the MSPRINT.INF file location. This file is located in the WINDOWS\INF directory, the WINDOWS directory being the directory where Windows 95 is installed. The easiest thing to do is to copy all of the .cab files from the win95 directory of your Windows 95 installation CD to an area on a server or the workstation, and then copy the MSPRINT.INF, MSPRINT2.INF, and LAYOUT.INF files to that same directory. If you are installing drivers for a Windows NT package on Windows NT or a Windows 95 package on Windows 95, you will not be asked for the .INF files. However, you must still point the install to where the drivers are located, usually the installation CD for Windows NT or Windows 95. If you attempt to copy drivers that are set as READ ONLY, then the Microsoft API will copy the files as .TMP files. This will cause problems when users go to download the driver because the driver will not be found. Make sure the files in the area you copy from are not read only. This usually will not be a problem if you follow the above directions. ---------------------------------------------------------------- 5.2 "Error writing to : Space to store the file waiting to be printed is not available on the server" or "A write fault occurred while printing" ---------------------------------------------------------------- You may experience difficulties printing through NDPS if your network connection is dropped and later auto-reconnects. To resolve this problem, you must download and install NetWare 5 Support Pack 2 (NW5SP2.EXE) from www.novell.com/download. Instructions for downloading and installing the Support Pack are included with the download. After installing NetWare 5 Support Pack 2 1. At the server console, load NDPSM.NLM to load NDPS Manager on the server. 2. From the NDPS Manager main menu, select Printer Agent List. 3. Select a Printer Agent. 4. Once the Printer Agent information is displayed, select Configuration: (See Form). 5. From the configuration screen, change the Security Level from High to Medium. ---------------------------------------------------------------- 6.0 Driver Issues ---------------------------------------------------------------- ---------------------------------------------------------------- 6.1 Network Board Driver Issues ---------------------------------------------------------------- Some problems have been found in the drivers for the following network boards (adapter cards): --Intel** EtherExpress** 100 (drivers dated earlier than May 7, 1996) --HP** J2573A ISA (drivers dated earlier than April 10, 1996) --HP J2577A EISA (drivers dated earlier than April 10, 1996) For a driver that will work with one of these boards, contact the board manufacturer. ---------------------------------------------------------------- 6.2 Possible Problems When Using Filter Drivers ---------------------------------------------------------------- Using filter drivers with the Novell Client for Windows NT might cause problems. For example, it has been determined that Inoculan** filter drivers and those used by Quarterdeck CleanSweep can cause the NT workstation to go to a blue screen. Other filter drivers can cause similar behavior. Novell recommends that you do not use programs that have filter drivers with this Novell Client release. ---------------------------------------------------------------- 7.0 Software Compatibility ---------------------------------------------------------------- ---------------------------------------------------------------- 7.1 Envoy for Windows ---------------------------------------------------------------- Currently, Envoy* for Windows (both version 1.0 and 1.0a) opens and allows you to view documents, but as soon as you try to exit the application, Envoy hangs and requires you to reboot. If you experience this problem, go to the Novell Technical Support area on the World Wide Web (http://support.novell.com/) and search for the file EVYNT.EXE. When you run this self- extracting executable file, it produces two files--one .EXE file and one .DLL file. Copy these files to your Envoy directory. ---------------------------------------------------------------- 7.2 Microsoft File and Print Services ---------------------------------------------------------------- Novell Client for Windows NT software does not work with Microsoft File and Print Services for NetWare (FPNW). This is because FPNW advertises itself as a NetWare 3.12 server but does not emulate a NetWare 3.12 server. It more closely emulates a NetWare 2.2 server. When the client attaches, it attempts to use features that are available on NetWare 3.12 servers. Since FPNW does not support these features, the client is unable to use FPNW. A fix is available from Microsoft, but Novell testing indicates that the fix still does not provide a complete solution. ---------------------------------------------------------------- 7.3 NVER ---------------------------------------------------------------- The NVER command does not work with Windows NT. Attempting to use this command might cause the command window to hang. ---------------------------------------------------------------- 7.4 Attachmate IRMA ---------------------------------------------------------------- Attachmate** IRMA** v3.02 does not work with Novell Client for Windows NT at this time. Attachmate recommends that customers use the 32-bit version of IRMA in Windows NT. ---------------------------------------------------------------- 7.5 RCONSOLE and the Japanese Version of Windows NT ---------------------------------------------------------------- RCONSOLE.EXE currently does not work on NEC** PC98 systems using the Japanese version of Windows NT. ---------------------------------------------------------------- 7.6 Novell 3270 LAN Workstation v1.2x (WSLANWIN.EXE) ---------------------------------------------------------------- Novell cannot support 3270 LAN Workstation v1.2x on Windows NT. This application cannot handle SPX* Sends that complete in true asynchronous fashion. If the SPX Sends are made synchronous, then the application works fine. Unfortunately, this would cause a negative impact on the API. Some customers have been successful in getting WSLANWIN.EXE v2.21 to run. Novell no longer owns the rights to WSLANWIN.EXE. It is now the property of Attachmate. ---------------------------------------------------------------- 7.7 VIPX and VLMSUP Commands in Autoexec.nt ---------------------------------------------------------------- When you run SETUPNW /A /ACU, SETUPNW places the VIPX and VLMSUP commands at the end of your AUTOEXEC.NT file. This is normally not a problem. However, if you load a DOS TSR such as BREQUEST for Btrieve** applications, these applications require that VIPX and VLMSUP be loaded first. To fix this problem, edit the AUTOEXEC.NT file so that these commands are before the command to load the TSR. ---------------------------------------------------------------- 7.8 Files Marked Execute-only Do Not Execute ---------------------------------------------------------------- Only Windows 32-bit files will work if marked Execute-only, due to a problem with the way 16-bit subsystems process executables. Microsoft is aware of the problem, but will not fix it because it breaches security in that subsystem. There is no workaround. ---------------------------------------------------------------- 7.9 DiscView Software for a DiscPort CD-Tower by Microtest ---------------------------------------------------------------- When you attempt to access a CD in a Microtest** DiscPort** CD-Tower, the current process might crash. This is apparently a bug in the Microtest software. When using the Microtest software and a NetWare 4.1 or later server, the client might crash. To resolve this problem, the Microtest software needs to be updated on the server. ---------------------------------------------------------------- 7.10 Microsoft Word 7 ---------------------------------------------------------------- If you remove any NetWare volume while using Word 7, a Dr. Watson error occurs. Do not remove any volumes while using Word 7. ---------------------------------------------------------------- 7.11 SFLOGIN ---------------------------------------------------------------- SFLOGIN 32 v2.01 and all earlier releases are incompatible with this Novell Client version. For more information see the Netoria web site at: http://www.netoria.com. If an incompatible SFLOGIN version is detected during installation, then it will be disabled to avoid serious workstation problems. ---------------------------------------------------------------- 7.12 McAfee NetShield 3.1.4 ---------------------------------------------------------------- McAfee** NetShield 3.1.4 causes a blue screen when you try to access a NetWare file. The blue screen appears to be caused by NWFS.SYS, but it is actually a compatibility problem with that version of NetShield. If this problem occurs, upgrade to a later version of NetShield. ---------------------------------------------------------------- 7.13 Additional Software Incompatibilities ---------------------------------------------------------------- When a new product is released, it is inevitable that software incompatibilities will be found. As Novell becomes aware of these problems, more information will be posted on the Novell Support Connection Web site. Refer to Novell Support Connection for possible workarounds to new problems and to the problems listed in these release notes. ---------------------------------------------------------------- 8.0 WIN2NCS Compatibility Issues ---------------------------------------------------------------- ---------------------------------------------------------------- 8.1 WIN2NCS and pcANYWHERE 7.5 for Windows NT ---------------------------------------------------------------- When using WIN2NCS and pcANYWHERE** 7.5 to set up a host session on a network client, the workstation displays the message "Modem Initialization Error." This problem appears to be a timing issue between WIN2NCS and pcANYWHERE 7.5 for NT. The problem is currently being addressed and will be resolved in a future release. ---------------------------------------------------------------- 8.2 ReachOut 7.0 for Windows NT Does Not Reliably Switch COM Ports Assigned to WIN2NCS ---------------------------------------------------------------- When using WIN2NCS and ReachOut** 7.0, ReachOut 7.0 for NT does not reliably switch COM ports on an existing ReachOut configuration for those COM ports assigned to WIN2NCS. ---------------------------------------------------------------- 8.3 Windows NT Experiences System Faults after Using ReachOut 7.0 for Windows NT and WIN2NCS ---------------------------------------------------------------- System faults (blue screens) have been noted in NT after using ReachOut 7.0 and WIN2NCS on NT. These problems are currently being addressed and will be resolved in a future release. ---------------------------------------------------------------- 9.0 Miscellaneous ---------------------------------------------------------------- ---------------------------------------------------------------- 9.1 IPX Compatibility and Multiple Network Attachments ---------------------------------------------------------------- You should be aware that limitations of the IPX stack present in Windows NT and limitations of 16-bit IPX/SPX applications complicate operations of multihomed workstations. These limitations impose additional configuration requirements to make use of the services of IPX Compatibility from your multihomed Novell IP Client. Workstations connected to the network through more than one network attachment are considered to be multihomed workstations. LAN connections and RAS connections qualify as network attachments. On Windows NT, the IPX stack does not allow IPX applications to detect more than one network attachment to segments with the same network number. This limitation forces you to configure different IPX Compatibility Network Numbers (also known as CMD Network Numbers) for each adapter used by your workstation to access the network if you want to allow your Novell IP Client to simultaneously access IPX Servers through each one of the adapters. For example, you could allow IPX Compatibility to use the default IPX Compatibility Network Number over the LAN adapter but configure a different network number for IPX Compatibility to use over the RAS connection (WAN adapter). You should be aware that nodes utilizing IPX Compatibility on the same network should be configured to use the same network number in order to directly communicate when using Client/Server IPX applications. The IPX stack arbitrarily selects a network attachment for 16-bit IPX/SPX applications because those applications expect to operate on workstations with only one network attachment. For this reason, you may find that your 16-bit IPX/SPX applications are only capable of communicating over your LAN adapter when you also have a RAS connection over a WAN adapter. If you have a multihomed Novell IP Client and you only want to use the service of IPX Compatibility over one of the network attachments and you are getting unwanted results, then you can disable IPX Compatibility over the other network attachments. For example, if you have a workstation connected to the corporate network through LAN adapter A and connected to a lab network through LAN adapter B, and IPX Compatibility only seems to work over LAN adapter B, you can force IPX Compatibility to work over LAN adapter A by opening the IPX Compatibility property page, selecting LAN adapter B, and unchecking the Enabled check box. ---------------------------------------------------------------- 9.2 IPX Compatibility and Changing IP Addresses ---------------------------------------------------------------- When the IP address of a given interface changes, you might not be able to restore the connections that you had to IPX servers from your Novell IP Client, or your IPX/SPX applications might stop working. If this occurs, you will have to restart your workstation to recover. IP interface addresses can change because of TCP/IP manual configuration changes, because a DHCP lease expires and is renewed with a different address, or because your network connection goes down and up (such as when you reestablish a RAS connection). You can avoid the changing address problem over RAS connections if you statically configure the IP address that your workstation uses over the dial-up adapter. ---------------------------------------------------------------- 9.3 DOS Utilities Supported Only When Used with IPX or IP Compatibility Mode ---------------------------------------------------------------- DOS utilities (CX, MAP, CAPTURE, etc.) are supported only when used with IPX or IP Compatibility Mode. Use the equivalent GUI-based utilities when accessing resources that are only available from IP servers. ---------------------------------------------------------------- 10.0 Windows 2000 Issues ---------------------------------------------------------------- ---------------------------------------------------------------- 10.1 Upgrading a Workstation with Novell Client ---------------------------------------------------------------- You can upgrade a Windows NT 4 workstation with Novell Client software to Windows 2000 without uninstalling the client software. The software detects the version of the Novell Client installed and does one of the following: * If the version of Novell Client is 4.6 or earlier, Windows 2000 installs Novell Client version 4.51 from the Windows 2000 CD-ROM. * If the version of Novell Client is 4.7 or later, Windows 2000 leaves it intact but removes all installed components and changes the protocol selection. After the migration to Windows 2000 is complete, Novell Client will reinstall the previously installed components and restore the previously selected protocols. Warning: In order to complete the reinstallation of the components and protocols, the user who logs in to the workstation after the migration must have Administrator rights. ---------------------------------------------------------------- 10.2 Installing Novell Client on Windows 2000 ---------------------------------------------------------------- To install Novell Client from a NetWare server, install Novell Client version 4.51 from the Windows 2000 CD and then login to the NetWare server and install the latest Novell Client from the network. Novell Client version 4.51 is located on the Windows 2000 Professional and Windows 2000 Server CDs in the I386\WINNTUPG\OEM\NOVELL directory. Warning: If you install Novell client from a NetWare server using the Microsoft Client Service for NetWare, the workstation will lose its connection to the server during the install and the install will fail. Note: Novell Client version 4.51 client does not support NWIP, CMD, NDPS, NAL NT Service Agent, IP Gateway, or 16-bit support. ---------------------------------------------------------------- 10.3 Close Local Area Connection Properties Page During Install ---------------------------------------------------------------- Novell Client cannot be installed on Windows 2000 if the Local Area Connection Properties page is open. Close the Local Area Connection Properties page before running the Novell Client install. ---------------------------------------------------------------- 10.4 Some Windows NT 4.0 Printer Drivers Incompatible with Windows 2000 Build 2131 or Later ---------------------------------------------------------------- Some Windows NT 4.0 printer drivers are incompatible with Windows 2000 Build 2131 or later and will not install. Contact Microsoft for more information. ---------------------------------------------------------------- 10.5 Components Not Upgraded from Windows NT to Windows 2000 ---------------------------------------------------------------- The following components will not be upgraded from Windows NT to Windows 2000: IPX Compatibility and Novell NetWare/IP Adapter. ---------------------------------------------------------------- 10.6 Configuration using IPX Compatibility or Novell NetWare/IP Adapter ---------------------------------------------------------------- If either IPX Compatibility or Novell NetWare/IP Adapter are installed, the Local Area Connection Properties page should not be accessed or used for configuration. Doing so will remove the bindings between IPX and all Clients, rendering the machine unusable. If this happens, Novell Client will try to restore the bindings to IPX after a reboot. If, the bindings are still invalid once you reboot the workstation, you will need to remove the components and then reinstall them. Note: This issue will be fixed by Microsoft in Support Pack1 for Windows 2000. To remove IPX Compatibility Mode: 1. Run SETUPNW.EXE. 2. On the Protocol Selection page, select a different protocol. 3. Run SETUPNW.EXE again. 4. On the Protocol Selection page, select IPX Compatibility Mode. To remove NetWare/IP: 1. Run NCIMAN.EXE. 2. Double-click the Installation Option. 3. Click the NetWare/IP tab, then click Install This Component and Remove This Component. 4. Click OK and save the unattended file in the install directory. 5. Reinstall Novell Client using this unattended file. 6. Run NCIMAN.EXE again. 2. Double-click the Installation Option. 3. Click the NetWare/IP tab, then click Install This Component. 4. Click OK and save the unattended file in the install directory. 5. Reinstall Novell Client using this unattended file. ---------------------------------------------------------------- 10.7 Installing NWIP on Windows 2000 ---------------------------------------------------------------- NWIP can only be installed on a Windows 2000 workstation through a network installation method using the Automatic Client Upgrade utility (ACU.EXE). However, if you are installing to an IPX-only workstation, you will lose your connection and the installation will abort. To resolve this: 1. Set up a network installation. Detailed instructions about installing Novell Clients across the network are available at http://www.novell.com/documentation/lg/noclienu/docui/ index.html#../noclienu/data/h2tp1v4b.html. 2. As a part of the network installation, modify the ACU.INI file and set the following parameters: [ClientLocalInstall] LocalInstall=Yes LocalDirectory=C:\Novell\ClientLocalInstall DeleteLocalInstall=No 3. Complete the network installation as indicated in the documentation. ---------------------------------------------------------------- 10.8 ZENworks 2 Support Pack 1 Requires Novell Client for Windows NT/2000 version 4.71 to Run on Windows 2000 ---------------------------------------------------------------- ZENworks 2 Support Pack 1 includes support for the Windows 2000 operating system. Windows NT-2000 User policy packages and Workstation policy packages can be created and used just as the Windows NT policy packages are. For full Windows 2000 support, you must download and install Novell Client for Windows NT/2000 version 4.71 that also includes the ZENworks Starter Pack. This version of the Novell client supersedes all previous Windows NT/2000 client releases and contains all of the functionality included in previous clients. IMPORTANT: Do not install the ZENworks Starter Pack when you install the Windows NT/2000 client. Doing so will disable the possibility of installing ZENworks Support Pack 1. You can download this client version from the Novell Software Downloads Web site at http://www.novell.com/download/ ---------------------------------------------------------------- 10.9 ZENworks 2 Remote Control and Workstation Inventory Not Installed ---------------------------------------------------------------- Only the full version of ZENworks 2 includes the Novell Client software that installs Remote Control and Workstation Inventory capabilities to desktops. ZENworks 2 (full) ships on a product CD. If you download a version of the Novell Client from the Novell Web site or if you update to a version of the client that is later than those that shipped with ZENworks 2, you may not have the option to install Remote Control and Workstation Inventory components. ---------------------------------------------------------------- 11.0 Primary Administrator Documentation is HTML ---------------------------------------------------------------- The HTML documentation for Novell Client for Windows NT/2000 contains information on installing, configuring, using, understanding, and troubleshooting this client. The HTML documentation is available on the Novell Web site at http://www.novell.com/documentation. In addition to the HTML documentation, user documentation can be found in Novell Client User Guide located on the red N in the toolbar. ---------------------------------------------------------------- 12.0 How Customers Can Get Support ---------------------------------------------------------------- Novell Support Connection provides access to Novell networking expertise through the Novell Support Connection Web site, the Novell Support Connection CD, and support programs for customers and partners. By using the Novell Support Connection Web site or CD, you can connect to the same networking knowledge used by Novell technical support engineers. For additional support, Novell encourages customers to contact a Novell partner. Customers can locate qualified partners using the Novell Support Connection Web site. Searches are based on geographical location, product expertise, or both. Visit the Novell Support Connection Web site at: support.novell.com (Americas) support.novell.de (Europe, Middle East, Africa) support.novell.com.au (Asia Pacific) Or call: Americas English 1-800-858-4000 1-801-861-4000 Europe, Middle East, Africa English (49) 211 5632 744 French (49) 211 5632 733 German (49) 211 5632 777 Asia Pacific English (61) 2 9925 3133 See the Novell Support Connection Web site for a complete list of languages and support telephone numbers. To order the Novell Support Connection CD, call 1-800-377-4136 or 1-303-297-2725, or visit the Novell Support Connection Web site. ---------------------------------------------------------------- 13.0 Legal Information ---------------------------------------------------------------- ---------------------------------------------------------------- 13.1 Disclaimer, Patents, and Copyright ---------------------------------------------------------------- Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. U.S Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129. U.S. and International Patents Pending. Copyright (C) 1996, 1998-2000 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. ---------------------------------------------------------------- 13.2 Trademarks ---------------------------------------------------------------- Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. Client 32, Envoy, Internetwork Packet Exchange and IPX, NDS, NetWare/IP, Novell Client, Novell Support Connection, Open Data-Link Interface, ODI, PartnerNet, Premium Service, Sequenced Packet Exchange, SPX, and ZENworks are trademarks of Novell, Inc. All third-party trademarks are the property of their respective owners.