Readme for Novell Client v3.2 for Windows 95/98
(Last modified: 11Oct2002)
This document (10024888) is provided subject to the disclaimer at the end of this document.
goal
Readme for Novell Client v3.2 for Windows 95/98
fact
Novell Client 3.2 for Windows 95/98
fix
These notes describe new features and some issues that have
not been resolved for this release of the Novell* Client* for
Windows** 95/98 software. Most of these issues will be resolved
in future releases.
This release supports workstations running the following versions
of Windows:
* Windows 95a
* Windows 95b
* Windows 95c
* Windows 98
* Windows 98 SE
This release does not support the original release of Windows 95.
----------------------------------------------------------------
Contents
----------------------------------------------------------------
1.0 Installing
2.0 Logging In
3.0 General
4.0 Printing
5.0 Primary Documentation Is HTML
6.0 Trademarks
7.0 Disclaimer, Copyright, Export Notice, Patents
----------------------------------------------------------------
1.0 Installing
----------------------------------------------------------------
----------------------------------------------------------------
1.1 Installing from Diskettes
----------------------------------------------------------------
An option to install from diskettes is not available for
this release.
----------------------------------------------------------------
1.2 ODI Drivers Not Installed
----------------------------------------------------------------
ODI drivers are not installed in the latest version of the Client.
If you are upgrading an older version of the Client and you have
ODI drivers currently installed, these ODI drivers may still work.
If you are installing the Client for the first time,
NDIS drivers will be installed. If you do not already have the
necessary NDIS driver, you might need to obtain it from the
Windows CD-ROM or from the network card manufacturer.
----------------------------------------------------------------
1.3 "The DeviceIDDeleteOrder section in NWSETUP.INI is
either incomplete, or incorrect."
----------------------------------------------------------------
During installation on Windows 95a, an error occurs if the network
interface card is not configured properly (the IRQ and Port Numbers
are not correct or they conflict with another device).
To solve this problem, configure the network adapter manually or
apply the OSR2 patch from the Microsoft Web site.
----------------------------------------------------------------
1.4 Restore Defaults Option Sets Novell Defaults
----------------------------------------------------------------
If you click Restore Defaults during a custom installation,
the installation may not restore the same options selected during
a previous custom installation.
If you have selected fewer options than Novell's default modules
(NDPS and Workstation Manager), the Restore Defaults option
restores Novell's default options instead.
If you have selected options in addition to the Novell default
options, the Restore Defaults option restores the additional
options as well as the Novell default options.
----------------------------------------------------------------
1.5 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\win95\ibm_enu\mfc42.dll
Copy the DLL to the following directory on your workstation:
c:\windows\system
----------------------------------------------------------------
1.6 Drag-and-Drop Might Not Work Immediately
----------------------------------------------------------------
Drag-and-drop operations between applications or the desktop
might not work immediately after the client is installed and
the workstation is rebooted.
To solve this problem, reboot again to ensure proper registration
of the ActiveX controls included in the client.
----------------------------------------------------------------
1.7 Using ACU to Upgrade from the Microsoft Client for NetWare
----------------------------------------------------------------
If you are upgrading from the Microsoft client for NetWare to any
version of the Novell Client for Windows 95/98 using the setup.exe /acu
method in a login script, you must use the # sign in the login script
and the user must manually restart the workstation after the Novell
client installation has finished.
----------------------------------------------------------------
1.8 Incompatibility with Built-in Audio and Video Drivers on
Hewlett-Packard Vectra and Compaq Presario Computers
----------------------------------------------------------------
Some Hewlett-Packard Vectra and Compaq Presario computers use drivers
for their built-in audio and video features that are incompatible
with Novell Client for Windows 95. This incompatibility can cause a
General Protection Fault on the workstation.
If you use a Hewlett-Packard Vectra or a Compaq Presario and
experience a GPF after installing Novell Client for Windows 95/98,
use one of the following methods to avoid a GPF:
1. Update your audio and video drivers. Current drivers
can be obtained from your workstation's manufacturer.
2. Install generic audio and video drivers.
3. After installing the client, do not restart the
workstation. Return to Windows and shut down
the workstation using the Start > Shut Down option.
Finally, restart the workstation.
----------------------------------------------------------------
1.9 MSBATCH Installation Not Supported
----------------------------------------------------------------
Novell Client for Windows 95/98 does not support MSBATCH installation.
----------------------------------------------------------------
1.10 "IP with IPX Compatibility" Dependency
----------------------------------------------------------------
When using the client configuration "IP with IPX Compatibility"
make sure the TCP/IP stack has been configured with a TCP/IP
Gateway. This can be configured through DHCP or locally defined.
The IPX Compatibility driver and IP routing will not work properly
without a TCP/IP Gateway configured. Under Windows 95/98
the Gateway can be configured by opening the TCP/IP Properties page,
from the Network Properties page. If your network is configured to
use DHCP you do not need to configure the Gateway locally.
----------------------------------------------------------------
1.11 "IP with IPX Compatibility" needs Migration Agent
----------------------------------------------------------------
If you are using "IP with IPX Compatibility" on the client and are
trying to see IPX only servers, you need to make sure that you've
configured a Migration Agent (MA) on the network.
See the NetWare 5 documentation for more information on setting up
a Migration Agent on the network.
To troubleshoot a NetWare client's MA visibility or configuration,
run the CMDINFO command from an MS-DOS Prompt. The command should
list all configured or discovered MAs, depending on the IPX
Compatibility configuration.
----------------------------------------------------------------
1.12 Unable to find NWUSE.HLP During Installation
----------------------------------------------------------------
If you are upgrading Novell Client on a workstation running
Windows 95b, you might be prompted for the file NWUSE.HLP during
installation. This message occurs due to certain hardware
configurations.
If you receive this message, you must abort the current installation
and uninstall your existing client software using the version of
UNC32.EXE that shipped with the Novell Client software that you
already have on your workstation. Then, delete the Client32
directory on your hard drive.
You can now install the latest version of Novell Client.
----------------------------------------------------------------
2.0 Logging In
----------------------------------------------------------------
----------------------------------------------------------------
2.1 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.
----------------------------------------------------------------
2.2 Associating Login Restrictions with Workstation Objects
----------------------------------------------------------------
SYMPTOM: Workstation policy doesn't work correctly.
CAUSE: Login restrictions can be associated with Workstation objects
and OUs, but not to groups of Workstation objects. If a policy is
associated with a group of Workstation objects, it is not effective.
SOLUTION: Do not associate login restrictions with a group of
Workstation objects. Associate login restrictions only with a single
Workstation object or OU.
----------------------------------------------------------------
3.0 General
----------------------------------------------------------------
----------------------------------------------------------------
3.1 Dial-Up Networking With LAN Connections
----------------------------------------------------------------
Using Dial-Up Networking concurrently with a LAN connection might
cause name resolution problems. Servers on the LAN or the Dial-Up
connection might not be found. To solve this problem, disable the
LAN adapter by doing the following:
1. Click Start > Settings > Control Panel.
2. Double-click System, and then click the Device Manager tab.
3. Double-click the network adapter you want to disable.
4. In the Device Usage field, check Disable in this Configuration,
and then click OK.
----------------------------------------------------------------
3.2 SLP Configuration Over IP
----------------------------------------------------------------
In order to use SLP name resolution with Dial-Up Networking, you must
add the directory agent's IP address to the directory agent list on
the Novell NetWare Client Properties Service Location tab. To do this:
1. Click Start > Settings > Control Panel.
2. Double-click Network, and then double-click the Novell NetWare
Client.
3. Click the Service Location tab.
4. Add the directory agent IP address to the directory agent
list, and then click OK.
----------------------------------------------------------------
3.3 Dial-Up Networking over IP, Unable to see Network
----------------------------------------------------------------
If you are trying to use Dial-Up Networking on the client and
are unable to login or browse the Network, try the following
troubleshooting suggestions.
1. Make sure that you can resolve NetWare 5 IP server names.
a. For dynamic discovery of server make sure that your
client can see an SLP Directory Agent. The agent can be
statically configured, (see previous section), or if your
Dial-Up host supports DHCP and is configured with the
proper DA, then that should also work.
Note: By default, the client uses DHCP to discover a DA.
(This assumes that there is a DA configured on the Dial-Up
host network.)
b. The client will use an NWHOST file, if present, which
contains server names and their addresses. This might be
a preferred way to run your client. (The file is created
in the "\NOVELL\CLIENT32" directory on the workstation.)
c. The client also supports DNS names. After connecting to
the Dial-Up host make sure your DNS server is working
properly by trying to PING your server using its DNS name.
If the ping was successful, then use that same DNS name as
your server name in the login dialog.
d. Isolate the problem down to name resolution by using an IP
address instead of the server name. If the login works,
the problem is in name resolution.
2. Make sure that the IP stack is still functioning properly by
pinging known active IP nodes that are on the Dial-Up host
network.
3. If you are using IP with Compatibility mode on the client and
cannot see any IPX servers, make sure that the client has an
MA configured properly. See section 3.4.
----------------------------------------------------------------
3.4 Dial-Up Networking with Compatibility Mode
----------------------------------------------------------------
In order to use Compatibility mode to see IPX services over a Dial-Up
connection, you should statically configure the Migration Agent on
the Compatibility Mode Driver property page.
Note: If your Dial-Up host supports DHCP Inform requests, and it's
configured to hand out Migration Agents, you shouldn't need to
statically set the MA.
To statically set the MA address:
1. Click Start > Settings > Control Panel.
2. Double-click Network > Compatibility Mode Driver (CMD)
3. Uncheck Use DHCP and then add a Migration Agent, using an IP
address in dotted format (for example: 137.65.1.5). You can
also use a DNS name, keeping in mind the dial-up environment
you are trying to use.
4. Press OK to save the changes.
----------------------------------------------------------------
3.5 Winsock2 not Set Up Correctly on Windows 95 with Early
Versions of DCOM'95
----------------------------------------------------------------
Winsock2 is not set up correctly if the client workstation has
DCOM'95 installed and the version is not 812 or later. WS2Setup.exe
closes but there is no feedback given to the user about the problem.
The following is from the Microsoft Web page:
http://www.microsoft.com/Windows95/downloads/contents/WUAdminTools/
S_WUNetworkingTools/W95Sockets2/ReleaseNotes/ReleaseNotes.asp
WS2SETUP.EXE AND DCOM'95
WS2SETUP.EXE will only install on machines that have DCOM'95
build 812 or higher, or no version of DCOM'95 at all. If a
version of DCOM'95 prior to build 812 is detected, WS2SETUP.EXE
will abort without installing Winsock2 for Windows 95 and an
error message will be written to WS2SETUP.LOG. To obtain an updated
version of DCOM'95, see:
http://www.microsoft.com/com/dcom95/download-f.htm for
availability, download instructions and release notes.
----------------------------------------------------------------
3.6 IPX Compatibility and Server Versions
----------------------------------------------------------------
This client version requires that the servers hosting Migration
Agents be installed with the SP1 (or above) version of NetWare 5.
You can also configure CMD servers as Migration Agents to force
the client to obtain routing/service information about the IPX
network from those servers.
----------------------------------------------------------------
4.0 Printing
----------------------------------------------------------------
----------------------------------------------------------------
4.1 Printing to a Volume with Insufficient Space
----------------------------------------------------------------
When you print a large file to a volume with insufficient space,
the Novell Client returns an error which might hang the computer.
This occurs because the Novell Client cannot retry printing
because the volume is out of disk space, and it cannot delete
the print job because it thinks that important data will be lost.
To resolve this problem, make sure that you have sufficient disk
space before you start printing a large file.
----------------------------------------------------------------
4.2 Do Not Configure a Local NPRINTER with Interrupts
----------------------------------------------------------------
You should not configure a local NPRINTER with interrupts. Use
the default "polled mode" instead.
----------------------------------------------------------------
4.3 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 a .inf file or driver is located. If
you are setting up drivers for an NT package while running Windows
95/98, you are asked to enter the path where the ntprint.inf file
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 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 Windows 95/98 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/98 is installed. The easiest thing to do is to copy all of
the .cab files from the win95 or win98 directory of your Windows
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/98 package on Windows 95/98,
you will not be asked for the .inf files. However, you must still
point the install to where the drivers are located, usually the
Windows installation CD.
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 attempt 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.
----------------------------------------------------------------
4.4 "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.
----------------------------------------------------------------
5.0 Primary Administrative Documentation is HTML
----------------------------------------------------------------
The HTML documentation for Novell Client for Windows 95/98 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.
----------------------------------------------------------------
6.0 Trademarks
----------------------------------------------------------------
----------------------------------------------------------------
6.1 Novell Trademarks
----------------------------------------------------------------
Novell and NetWare are registered trademarks of Novell, Inc. in
the United States and other countries.
Client 32, Internetwork Packet Exchange and IPX, NDS, NetWare/IP,
Novell Client, and Open Data-Link Interface and ODI are trademarks
of Novell, Inc.
----------------------------------------------------------------
6.2 Third-Party Trademarks
----------------------------------------------------------------
(** Third-party trademark.)
All third-party trademarks are the property of their respective owners.
----------------------------------------------------------------
7.0 Disclaimer, Copyright, Export Notice, Patents
----------------------------------------------------------------
Novell, Inc., makes no representations or warranties with respect
to any Novell software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose. Distribution of any NetWare software is
forbidden without the express written consent of Novell, Inc.
Further, Novell reserves the right to discontinue distribution
of any Novell software.
Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of recreating lost data, the
cost of any substitute equipment or program, or claims by any
party other than you.
Novell strongly recommends a backup be made before any software
is installed. Technical support for this software may be provided
at the discretion of Novell.
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.
This product may not be exported outside the U.S. or Canada without
prior authorization from the U.S. Department of Commerce.
U.S Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129.
U.S. and International Patents Pending.
.
document
| Document Title: | Readme for Novell Client v3.2 for Windows 95/98 |
| Document ID: | 10024888 |
| Solution ID: | 1.0.49743082.2494055 |
| Creation Date: | 12Jan2000 |
| Modified Date: | 11Oct2002 |
| Novell Product Class: | Management Products NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.