Novell Client for Windows NT/2000 Release Notes
12/8/99
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 12.0.  

----------------------------------------------------------------
Contents
----------------------------------------------------------------

    1.0   Client Installation
    2.0   Login and Shutdown
    3.0   Drive Mappings
    4.0   Profile Storage
    5.0   RAS Issues
    6.0   DHCP Issues
    7.0   Print Issues
    8.0   Driver Issues 
    9.0   Software Compatibility
   10.0   Win2NCS Compatibility Issues
   11.0   Miscellaneous
   12.0   Windows 2000 Issues
   13.0   Primary Documentation is HTML
   14.0   How Customers Can Get Support
   15.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 or 
Windows 2000 Release Candidate 3 with 24 MB of RAM. If a minimum 
of 24 MB is not installed, a blue screen occurs during reboot 
or right after login because NDS needs more memory.  Because NDS 
needs more memory, logging in as "workstation only" does not 
cause a blue screen, However, if you try to map a drive, a blue 
screen occurs.

Service Pack 3 or later is required. Service Pack 5 is recommended.

NOTE: At shipping, Novell Client was tested with Windows 2000 
Release Candidate 3.  Because this is not the final shipping 
version of Windows 2000, you should check for future updates to
Novell Client once the final version of Windows 2000 is shipped. 


----------------------------------------------------------------
1.2 Errors Resulting From a Custom Installation of Novell
    Client for Windows NT
----------------------------------------------------------------


Novell recommends the Typical Installation option to most customers
installing the Novell Clients.

If you are installing the Novell Client for Windows NT and you 
choose Custom Installation, do not check all of the components listed 
under custom installation.

A Custom Installation for the NT Client will work if you do not 
select all of the components listed for installation.

----------------------------------------------------------------
1.3 Installing Remote Management with ZENworks Full
----------------------------------------------------------------

Remote Management in ZENworks Full depends on Workstation Manager. 
If you plan to use Remote Management, make sure that Workstation 
Manager is installed on all workstations that will be managed 
remotely. Remote Management is not compatible with IP Gateway.


----------------------------------------------------------------
1.4 New Unattended Install Parameter
----------------------------------------------------------------

The following parameter has been added to the unattended 
install. This parameter is not included in Novell Client 
Install Manager and must manually added to the unattend.txt 
file if it is to be used.

!TCPIP_SOURCE_PATH = (path)
Used when using Automatic Client Upgrade (ACU) to upgrade an 
IP client. Specify the full path to the source files for the 
Microsoft TCP/IP installation files. If this parameter is not 
specified, the location where the ACU was run from (setupnw.exe)
will be used as the default.  Additionally, all parameters to 
configure TCP/IP are available as well.  These are the same 
parameter names that are specified by Microsoft for use during 
an unattended operating system install.  They should be added 
under the Novell client section of the unattended file.

To set this parameter:

1. Use Novell Client Install Manager (NCIMAN) to create an 
   unattend.txt file.

2. Open the unattend.txt file.

3. Manually add the desired parameters to the unattend.txt file.

4. Save the unattend.txt file.

5. Perform an unattended network install as instructed in the 
   product documentation.


----------------------------------------------------------------
2.0  Login and Shutdown
----------------------------------------------------------------

----------------------------------------------------------------
2.1 Login Utilities
----------------------------------------------------------------

Novell recommends that you do not use the command line Login 
utility.

There are several ways to initiate a Novell Client Login once 
you have already logged in to NetWare or the local workstation:

* Right-click the red N icon in the System Tray and click NetWare
  Login.

* Right-click Network Neighborhood and click NetWare Login.

* Click Start > Programs > Novell (Common) > Novell Login.

* In Network Neighborhood, double-click the tree or server you 
  want to log in to, and the Novell Login automatically loads. 

* In Network Neighborhood, right-click on the desired tree or 
  server and choose either Authenticate or Login. 

* Run loginw32.exe from the DOS command prompt.

----------------------------------------------------------------
2.2 Logout Utility
----------------------------------------------------------------

The logout.exe command is also not recommended for use. If you 
use this command, you should use it with a server name specified
(for example: LOGOUT <server name>).  

If you want to log in to new NetWare services while logging out 
of or clearing your current connections, use the NetWare Client 
Login (use any of the methods described in section 2.1 above to 
start the login) and click the Clear Current Connections check 
box.

If you want to log out of both the Windows NT workstation and 
NetWare, press Ctrl+Alt+Del and click the Logout button. 

Alternatively, another way to log out of a specific server is 
to right-click Network Neighborhood, click NetWare Connections, 
select the server or tree, and then click Detach.

----------------------------------------------------------------
2.3 CAPTURE Execution in a Login Script
----------------------------------------------------------------

If you use a login script that contains an external CAPTURE 
command using capture.exe, the screen might go blank with a 
blinking cursor in the upper-lefthand corner.  

Eventually, the capture executes and everything returns to 
normal.  

This happens if Windows NT is set to "full screen" when the 
CAPTURE command is executed from the login script. Although 
things are working correctly, a slow server performing the 
capture with a blank screen makes it appear as though it is 
not working.

Follow these steps:

1. Double-click My Computer > Control Panel > MS-DOS Console.

2. In the Console Windows Properties dialog box, make sure 
   the Options tab is selected.

3. From the Display Options group, click Window.

----------------------------------------------------------------
2.4 MFC42.DLL Error
----------------------------------------------------------------

The 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 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.5 Login script command SET_TIME ON/OFF behaves differently 
    on NT
----------------------------------------------------------------

Novell Client for Windows NT Properties > Advanced Settings 
contains a "Set Station Time" property. 

When this setting is On, the workstation time is always 
synchronized with the network during GINA Login. The Login 
script SET_TIME command has no effect on time synchronization. 
This is due to the time being synchronized before the script 
command is processed. 

When the setting is Off, the "SET_TIME ON" script command will 
have an effect when scripts are run and the workstation time 
will be synchronized with the network.

----------------------------------------------------------------
2.6 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 workstation and all of the other workstations that 
are placed in the restriction list as being able to login 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 IP.  The allowed addresses 
assigned in NDS are IPX.  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 and so 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
----------------------------------------------------------------

The map.exe utility might function improperly if the computer's 
DOS environment size is small. If you encounter problems while 
running map.exe, increase the DOS environment size by adding or 
editing the "SHELL=" line in the winnt\system32\config.nt file. 
For example:

  SHELL=%SYSTEMROOT%\SYSTEM32\COMMAND.COM /E:2048

Map.exe was not designed as a Windows NT executable and, 
therefore, does not recognize drives mapped to NT servers as 
network drives. Consequently, MAP will not list NT network 
drives. The Windows NT NET USE command can be used to correctly 
connect and list network drives for both NetWare and NT servers.

----------------------------------------------------------------
3.2  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.3  Drive Mappings
----------------------------------------------------------------

All drive mappings made using the NetWare Login are root mapped.
Programs cannot access directories above the directory that the 
drive is mapped to.

This release includes a feature that allows you to turn off map 
root from a login script by doing the following:

1. Right-click My Computer.

2. Click Properties > Environment.

3. Enter MAPROOTOFF (all one word) as a variable.

   Note: Because this is an environment variable, you could also 
   specify

   SET MAPROOTOFF="1"

   as the first line in the login script. This would globally 
   force all NT workstations using the login script to not map 
   root drives.
    
4. Set the value of the MAPROOTOFF variable to 1.

5. Click Select.

This feature only affects MAP commands performed in a login 
script. Once Windows NT has been started, NT allows you only 
to map to the root.

----------------------------------------------------------------
3.4 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, and then clicking Properties > Services > Novell 
Client for Windows NT > Properties.

----------------------------------------------------------------
3.5 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 if the existing mapping is the same path
as the permanent connection.


----------------------------------------------------------------
4.0 Profile Storage
----------------------------------------------------------------

----------------------------------------------------------------
4.1 Using the Same Profile for Multiple Users
----------------------------------------------------------------

When storing your profile through an NDS login, you can use a 
File System Pointer. This allows multiple users to use the same 
profile, provided they all use the same path as the file system 
pointer.

----------------------------------------------------------------
4.2 Long Filenames
----------------------------------------------------------------

When storing your profile from a Windows NT 4.0 workstation on a
NetWare server, that server volume must support long filenames. 
In versions of NetWare earlier than NetWare 4.11, the OS/2** 
name space was required for long filename support. In NetWare 5*
and NetWare 4.11, the long.nam name space is required. Have your
network supervisor install the os2.nam or long.nam name space on
the server.


----------------------------------------------------------------
5.0 RAS Issues
----------------------------------------------------------------

----------------------------------------------------------------
5.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 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.2 Supporting a Large Number of Remote Access Users
----------------------------------------------------------------

If you support a large number of RAS users in your network and 
you experience problems with users not being able to log in 
because of insufficient NetWare connections, try setting the 
Watchdog Configuration parameters so that connections time out 
quickly when RAS connections abnormally terminate.

----------------------------------------------------------------
5.3 SLP Requirements for Server Name Resolution from RAS Clients
----------------------------------------------------------------

If you rely on SLP to provide the resolution of server names 
to IP addresses in your network and your RAS server does not 
forward IP multicast packets between the client and the network,
then you must set up and configure SLP Directory Agents.

SLP Directory Agents are configured through the Novell Client 
property pages or through DHCP.

----------------------------------------------------------------
5.4 IPX Compatibility Requirements for RAS Client
----------------------------------------------------------------

IPX Compatibility requires the services of SLP. See Section 5.3, 
above, for more information.

If you have a RAS Client or RAS Server installed on your Windows NT
workstation then you must make sure that it is configured to only 
perform IP Networking over the RAS connections before installing 
the Novell IP Client with IPX Compatibility support.

----------------------------------------------------------------
5.5 Restoring RAS Connections and IPX Compatibility
----------------------------------------------------------------

You will have to restart your workstation before re-establishing
a RAS connection if the RAS server assigns your client a 
different IP address during each RAS connection and if you are 
using IPX Compatibility to run IPX applications or to connect to
IPX servers from your Novell IP Client.

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.


----------------------------------------------------------------
6.0 DHCP Issues
----------------------------------------------------------------

----------------------------------------------------------------
6.1 Using DHCP as an NDS Server Name Service Provider
----------------------------------------------------------------

You can set up a DHCP server to inform the Novell IP Clients 
about an NDS Tree Name and the IP Addresses of servers that are 
on that tree.  When using this feature, it is best to specify 
the IP addresses of the closest NDS servers containing 
partitions with the necessary user information.

Clients can obtain this configuration information from DHCP even
when you statically configure the client's IP address or even 
when the DHCP server used to supply the information is different
from the DHCP server supplying an IP address to the client.

You can easily configure Novell's DHCP Servers (NetWare 5 and 
above) to distribute this information to the clients.

----------------------------------------------------------------
6.2 Using DHCP to distribute SLP Configuration Information
----------------------------------------------------------------

You can configure the following SLP parameters through DHCP:

  - IP Address of SLP Directory Agents
  - SLP Scopes

Clients can obtain this configuration information from DHCP even
when you statically configure the client's IP address or even 
when the DHCP server used to supply this information is not the 
DHCP server supplying an IP address to the client.

You can easily configure Novell's DHCP Servers (NetWare 5 and 
above) to distribute this information to the clients.

----------------------------------------------------------------
6.3 Using DHCP to distribute IPX Compatibility Information
----------------------------------------------------------------

You can configure the following IPX Compatibility parameters 
through DHCP:

  - IP Address of Migration Agents
  - CMD Network Number
  - Migration Agent List Stale Time

Clients can obtain this configuration information from DHCP 
even when you statically configure the client's IP address or 
even when the DHCP server used to supply this information is 
different from the DHCP server supplying an IP address to the 
client.

You can easily configure Novell's DHCP Servers (NetWare 5 and 
above) to distribute this information to the clients.

----------------------------------------------------------------
7.0 Print Issues
----------------------------------------------------------------

----------------------------------------------------------------
7.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.inf is 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.


----------------------------------------------------------------
7.2 Printing DBCS Characters from DOS
----------------------------------------------------------------

Under Windows NT, the default command window runs as a 32-bit 
process. In order to use the existing DOS printer driver for 
DOS-intrinsic commands, a 16-bit command window must be used.  

This allows DOS-intrinsic commands such as COPY, TYPE, etc., 
to use the print driver.  

The following instructions explain how to set up NT to support 
this.  These instructions also set up the NT system to support 
the printer driver for DOS applications.
  
1. Edit the autoexec.nt file, found in the %SystemRoot%\system32
   directory, and add the DOS printer driver for your specific 
   printer. 

   Add the printer driver after the:
  
   %SystemRoot%\system32\vlmsup.exe

   line. Make sure you copy the printer driver to the path you 
   specify in the autoexec.nt file.

2. Copy the <winnt directory>\system32\config.nt file to another
   name such as config.prt.

3. Edit the new config file and add the DOSONLY command to the 
   file.

4. Continue the setup process using the instructions for your 
   specific version of Windows NT:

   4a. Create a shortcut to the command.com program, found in 
       the <winnt directory>\system32 directory.

   4b. Right-click the shortcut icon and then click Properties.
        
   4c. On the Program property page, click Windows NT and enter 
       the paths for the config and autoexec files that you 
       created in Steps 1 and 2.

   4d. Double-click the shortcut icon and a DOS window opens. 

       Only DOS applications can be run from this window, but 
       anything that is printed will be rendered by the printer 
       driver you installed. Any DOS commands that affect the 
       print driver must be entered in this window. DOS 
       applications can be started by any method.


----------------------------------------------------------------
7.3  "Error writing to <printer>: 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 the 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.  


----------------------------------------------------------------
8.0 Driver Issues
----------------------------------------------------------------

----------------------------------------------------------------
8.1 Network Board Driver Issues
----------------------------------------------------------------

There have been some problems 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.

----------------------------------------------------------------
8.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's
filter drivers and those used by Quarterdeck CleanSweep can cause 
the NT workstation to blue screen. Other filter drivers can cause 
similar behavior. Novell recommends that you do not use programs 
that have filter drivers with this release.


----------------------------------------------------------------
9.0 Software Compatibility
----------------------------------------------------------------

----------------------------------------------------------------
9.1 Microsoft SMB Client Support over IPX
----------------------------------------------------------------

The Novell Client for Windows NT coexists with the Microsoft 
SMB Client over IPX networks. The Microsoft SMB Client utilizes 
NetBIOS when communicating over IPX, which increases the 
utilization of your network.

If you want to, you can prevent the Microsoft SMB Client 
from communicating over NetBIOS by modifying your workstation
configuration. Unbind the workstation and server from NWLink 
NetBIOS in the Network Properties page.

----------------------------------------------------------------
9.2 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, it hangs and requires you to reboot. 

If you experience this problem, go to the Novell Services 
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.

----------------------------------------------------------------
9.3 Microsoft File and Print Services
----------------------------------------------------------------

The Novell Client for Windows NT software does not work with 
Microsoft's File and Print Services for NetWare (FPNW). This is 
because FPNW advertises itself as a NetWare 3.12 server but does
not emulate a 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 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.

----------------------------------------------------------------
9.4 NVER
----------------------------------------------------------------

The NVER command does not work with Windows NT. Attempting to 
use this command might cause the command window to hang.

----------------------------------------------------------------
9.5 Attachmate Irma
----------------------------------------------------------------

Attachmate** Irma v3.02 does not work with the Novell Client for
Windows NT at this time. 

Attachmate recommends that customers use the 32-bit version of 
this application under Windows NT.

----------------------------------------------------------------
9.6 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.

----------------------------------------------------------------
9.7 Novell's 3270 LAN Workstation v1.2x (WSLANWIN.EXE)
----------------------------------------------------------------

Novell cannot support this application on the v4.0 NT Client. 
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 v2.21 to run.  

Novell no longer owns the rights to this application. It is now 
property of Attachmate.

----------------------------------------------------------------
9.8 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, they 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.

----------------------------------------------------------------
9.9 Files Marked Execute-only Do Not Execute
----------------------------------------------------------------

Only Win32 files can be marked Execute-only and work, 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.

----------------------------------------------------------------
9.10 DiscView Software for a DISCPORT CD-Tower by Microtest
----------------------------------------------------------------

When you attempt to access one of these CDs, the current process
might crash. This is apparently a bug in the Microtest software.
When using this 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.

----------------------------------------------------------------
9.11 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.

----------------------------------------------------------------
9.12 SFLOGIN
----------------------------------------------------------------

SFLOGIN 32 v2.01 and all prior releases are incompatible with 
this client.

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.

----------------------------------------------------------------
9.13 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.

----------------------------------------------------------------
9.14 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 Connect Web site. Refer to Novell Support Connect for 
possible workarounds to new problems and to the problems listed 
in these release notes.


----------------------------------------------------------------
10.0 Win2NCS Compatibility Issues
----------------------------------------------------------------

----------------------------------------------------------------
10.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 by both companies and will be resolved
in a future release.

----------------------------------------------------------------
10.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.  

----------------------------------------------------------------
10.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 by both companies and will be resolved in a 
future release.


----------------------------------------------------------------
11.0 Miscellaneous
----------------------------------------------------------------

----------------------------------------------------------------
11.1 Password Restrictions
----------------------------------------------------------------

It is best if administrators configure NT workstations to not 
use any of the Microsoft password restrictions available in User
Manager. Novell Client for Windows NT works best if password 
restrictions are left up to NetWare.


----------------------------------------------------------------
11.2 IPX Compatibility and the IPX Internal Network Number
----------------------------------------------------------------

Workstations using IPX Compatibility cannot have an IPX Internal
Network Number configured.  If you have configured an IPX 
Internal Network Number on your workstation and you are planning
to install the Novell IP Client with IPX Compatibility then 
remove the IPX Internal Network Number before installing the 
client.

----------------------------------------------------------------
11.3 IPX Compatibility and Multiple Network Attachments
----------------------------------------------------------------

You should be aware that limitations of the IPX stack present 
in Windows NT and limitations of 16bit 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 wish 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.

----------------------------------------------------------------
11.4 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 (like 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.

----------------------------------------------------------------
11.5 DOS Utilities Supported Only When Used with IPX or IP
     Compatibility Mode
----------------------------------------------------------------

The 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.

----------------------------------------------------------------
12.0 Windows 2000 Issues
----------------------------------------------------------------

----------------------------------------------------------------
12.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 the Novell Client is 4.6 or lower, Windows 
     2000 installs the Novell Client version 4.51 from the Windows 
     2000 CD-ROM.
  *  If the version of the Novell Client is 4.7 or higher, Windows 
     2000 leaves it in tact 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.


----------------------------------------------------------------
12.2 Installing Novell Client on Windows 2000
----------------------------------------------------------------

To install Novell Client from a NetWare server, install the 
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 
loose 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.


----------------------------------------------------------------
12.3 Close Local Area Connection Properties Page During Install
----------------------------------------------------------------

The Novell Client cannot be installed on Windows 2000 if the Local 
Area Connection Properties page is open.  Please close the Local 
Area Connection Properties page before running the Novell Client install.


----------------------------------------------------------------
12.4 Login Options not Available on Windows 2000
----------------------------------------------------------------

Novell recommends that you do not use the command line Login 
utility.  There are several ways to initiate a Novell Client Login 
once you have already logged in to NetWare or the local workstation. 

The Start > Programs > NetWare (Common) > NetWare Login option is 
not available in Windows 2000.  

The following methods are available in Windows 2000: 

* Right-click the red N icon in the System Tray and click NetWare
  Login.

* Right-click My Network Places and click NetWare Login.

* In My Network Places, double-click the tree or server you 
  want to log in to, and the NetWare Login automatically loads. 

* In My Network Places, right-click on the desired tree or 
  server and choose either Authenticate or Login. 

* Run loginw32.exe from the DOS command prompt.


----------------------------------------------------------------
12.5 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. 



----------------------------------------------------------------
12.6 Using DHCP as an NDS Server Name Service Provider
----------------------------------------------------------------

In this Beta, you cannot use a DHCP server to inform clients 
about a NDS tree name. However, you can set up a DHCP server to 
inform the Novell IP Clients about the IP Addresses of servers 
that are on that tree.  When using this feature, it is best to 
specify the IP addresses of the closest NDS servers containing 
partitions with the necessary user information.

Clients can obtain this configuration information from DHCP even
when you statically configure the client's IP address or even 
when the DHCP server used to supply the information is different
from the DHCP server supplying an IP address to the client.

You can easily configure Novell's DHCP Servers (NetWare 5 and 
above) to distribute this information to the clients.


----------------------------------------------------------------
12.7 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.


----------------------------------------------------------------
12.8 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, the 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 have to remove
the components and then reinstall them. 

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, and 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, and 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.


----------------------------------------------------------------
13.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, end-user documentation can 
be found in Novell Client User Guide located on the red N in the 
toolbar. 


----------------------------------------------------------------
14.0 How Customers Can Get Support
----------------------------------------------------------------

The Novell Support Connection* provides access to Novell's 
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 Connection Web 
site. Searches are based on geographical location, product 
expertise, or both.

Visit the Novell Support Connection 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
                                               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 Connection Web site for a complete list of 
     languages and support telephone numbers.

To order the Novell Connection CD, call 1-800-377-4136 or
1-303-297-2725, or visit the Novell Support Connection Web site.


----------------------------------------------------------------
15.0 Copyright, Patents, Disclaimer, and Trademarks
----------------------------------------------------------------

----------------------------------------------------------------
15.1 Copyright, Patents, and Disclaimer
----------------------------------------------------------------

Copyright (c) 1996-1999 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.

U.S. Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129.
U.S. and International Patents Pending.

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.

----------------------------------------------------------------
15.2 Novell Trademarks
----------------------------------------------------------------

(* Novell trademark.)

Envoy is a registered trademark of Novell, Inc. in the United 
States and other countries.

Internet Packet Exchange and IPX are trademarks of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

LANalyzer is a registered trademark of Novell, Inc. in the 
United States and other countries.

NDS is a trademark of Novell, Inc.

NE2000 is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United 
States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare 4 is a trademark of Novell, Inc.

NetWare 5 is a trademark of Novell, Inc.

NetWare/IP is a trademark of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United 
States and other countries.

Novell Client is a trademark of Novell, Inc.

Novell Support Connection is a trademark of Novell, Inc.

Open Data-Link Interface and ODI are trademarks of Novell, Inc.

Packet Burst is a trademark of Novell, Inc.

PartnerNet is a trademark and a service mark of Novell, Inc.

Premium Service is a service mark of Novell, Inc.

Sequenced Packet Exchange and SPX are trademarks of Novell, Inc.

----------------------------------------------------------------
14.3 Third-Party Trademarks
----------------------------------------------------------------


(** Third-party trademark.)

All third-party trademarks are the property of their respective owners.

