INTRANETWARE CLIENT FOR WINDOWS 95 ENGLISH-ONLY RELEASE RELEASE NOTES 7/16/97 CONTENTS 1.0 Installing 2.0 Logging In 3.0 Configuring 4.0 Printing 5.0 Remote Access Dialer 6.0 LAN Adapter 7.0 NetWare /IP and IP Gateway 8.0 International Issues 9.0 Primary Documentation Is Help 10.0 Trademarks 11.0 Disclaimer 1.0 Installing 1.1 INSTALL.BAT Might Not Run on Some Dell Machines WINSETUP.EXE replaces INSTALL.BAT. However, you can still run INSTALL.BAT. If you run INSTALL.BAT on a Dell machine and encounter problems, you can install IntranetWare Client for Windows 95 by running SETUP.EXE. SETUP.EXE is located in PRODUCTS\WIN95\IBM_ENU. 1.2 Installing from Diskettes To install from diskette you must first create the Client installation disks using the MAKEDISK.BAT utility on the second IntranetWare Client CD. To make disks, type MAKEDISK at a DOS prompt from the root of the second Client CD. 1.3 Uninstalling with UNC32.EXE If TSA (Target Services Agent) is installed and running, and UNC32.EXE is run, it will cause an illegal operation. 2.0 Logging In 2.1 No Login With 3COM 3C589C PCMCIA Adapter After installing IntranetWare Client for Windows 95, if you are using a 3COM 3C589C PCMCIA Ethernet board, you may no longer receive the NOVELL NETWARE LOGIN screen during Windows 95 boot. To solve this problem: a. Go to DOS. b. Change to the client folder (for example, NOVELL\CLIENT32). c. Enter "LOAD 3C589.LAN" d. Execute the NOVELL NETWARE LOGIN by clicking Start>Programs>Novell> IntranetWare Login. 2.2 Login Script Displays "Dropping Last Line" Error In limited cases, the login script displays an error indicating that the last line of the script has been dropped. This occurs because the last letter of the last line is not read. If the login script does not have a blank line at the end, the last command might fail. To solve this problem: a. Open the login script in NetWare Administrator. b. Add a blank line to the end of the login script. c. Save the script. 3.0 Configuring 3.1 Toshiba laptops running Windows 95 might hang when using some ODI LAN drivers. Toshiba laptops with built-in infrared come with a product called Tranxit preinstalled. Tranxit installs three devices in the SYSTEM.INI file: PCOMM2.386, PUMAFIR.386, and PUMAIR.386 (with the last device loaded being PUMAFIR.386). Commenting out the three devices from Tranxit allows the machine to come up and function correctly with the ODI driver. 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 IntranetWare Client gives an error which might hang the computer. This occurs because the IntranetWare Client cannot retry printing because the volume is out of the 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. 5.0 Remote Access Dialer 5.1 Use Custom Install to Upgrade Remote Access Dialer The Beta version of the Remote Access Dialer will not be automatically updated by the final shipping release of the SETUP program unless Custom install is used and Remote Access Dialer is chosen as a custom feature. 5.2 Wait While Explorer Retries Request to Server Error If, while attempting to connect to a NetWare server using Remote Access Dialer, you receive the error message "NETWORK STATUS - CLIENT32 PLEASE WAIT WHILE EXPLORER RETRIES REQUEST TO [SERVER]. TO STOP WAITING, PRESS ENTER. NETWARE WILL THEN RETURN AN ERROR AND TRY TO RECONNECT IN THE BACKGROUND" verify the following: 1. In the Network Control Panel Advanced Settings tab Under IntranetWare Client, change "Minimum time to net" parameter to 3000. 2. CLIENT32.NLM - Install the latest version of IntranetWare client for Windows 95. Verify that the CLIENT32.NLM is equal to or greater than 466,399 and dated on or after 10-30-96. 6.0 LAN Adapter 6.1 Using LAN Adapter and Dial-up Adapter Together If you configure the client with LAN Adapter and Dial-up Adapter together, TCP/IP will not function properly. This occurs in both Windows 95 and Windows NT 4.0 Workstation. To resolve this issue try one of two options: 1. Remove LAN Adapter. 2. Keep the LAN Adapter, remove Dial-up Networking and install Novell's Mobile Dialer released in NIAS 4.1 or supported 3rd Party PPP Dialer. 7.0 NetWare/IP and IP Gateway 7.1 Using DHCP In the LAN environment, NetWare/IP clients can be automatically configured by DHCP. This only works if your DHCP host can be configured for NetWare/IP client configuration records. In a Dial-Up environment, the NetWare/IP client usually depends on a DHCP host located in the dial-up server itself. Once again, this will only work if the DHCP host in the dial-up server can be configured for NetWare/IP client configuration records. If you are using a dial-up server that cannot be so configured, then you must fall-back to manual configuration on the client. 7.2 NetWare/IP Won't Run Over IP Gateway NetWare/IP requires a TCP/IP protocol stack on the client and an IP connection to the network. Although NetWare/IP coexists with the IP Gateway, NetWare/IP cannot be run over the gateway. This is because the gateway does not supply an IP connection to the network for low-level services such as NetWare/IP. For instance, if you want to run a NetWare/IP client over a dial-up connection, you must enable IP for that connection. 7.3 IP Gateway: IPX/IP or IP/IP The Novell IP Gateway can operate as an IPX/IP Gateway or an IP/IP Gateway. IPX/IP is appropriate when the client is attached to an IPX network or to a network supporting both IPX and IP. We recommend that NetWare/IP not be used when the client is operating as an IPX/IP Gateway. IP/IP Gateway is appropriate when the client is bound to the IP Protocols. Normally, NetWare/IP should be used in a configuration which supports user login and location of IntranetWare servers with the gateway through NDS. If the preferred gateway server is specified by IP address and access control is disabled for the server, then NetWare/IP is not required when using the gateway. In an IP/IP Gateway configuration, NetWare/IP is required for access to other IntranetWare servers on the LAN. 7.4 Setting a Preferred IP Gateway Server You will be prompted multiple times to enter preferred gateway server names during install if you have not already set a preferred gateway server. To avoid seeing screens prompting you for preferred gateway server names, you can manually set the preferred gateway server by editing ADMIN.CFG. To set the servers, add the following entries under the IP Gateway heading. IPX/IP Gateway Server = test1 IP Gateway Server = test2 It is recommended that you specify a preferred gateway server with its NDS context. Include a leading dot as in the following example: .mygwserver-gw.myorgunit.myorg .CN=mygwserver-gw.OU=myou1.O=myorg 7.5 Terminate Winsock Applications Before Mode Change All winsock applications must be terminated before using the switcher program to change between Native mode, IPX-to-IP mode, and IP-to-IP mode, and then restarted once the mode change has been made. Some winsock applications may not fully terminate, leaving winsock resident in memory. If this occurs, you will need to reboot your workstation to complete the mode change. 8.0 International Issues 8.1 English-only This CD-ROM is an English-only version of the IntranetWare Client. The IntranetWare Client software and help files, as well as DynaText and HTML documentation files, will be translated into Portuguese, French, Italian, German, and Spanish for the international release of the IntranetWare Client CD-ROM. 9.0 Primary Documentation Is Help 9.1 The help files for IntranetWare Client for Windows 95 contain information on installing, configuring, using, understanding, and troubleshooting this Client. They are the primary documentation. To see the Client help, open the SETUPNW.HLP file. (For example, on a Windows 95 workstation, click Start, then Run, and then enter: C:\NOVELL\CLIENT32\SETUPNW.HLP). 10.0 Trademarks 10.1 Novell Trademarks Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. Client 32, IntranetWare, IntranetWare Client, Internetwork Packet Exchange and IPX, Open Data-Link Interface and ODI are trademarks of Novell, Inc. 10.2 Third-Party Trademarks Microsoft is a registered trademark and Windows 95 is a trademark of Microsoft Corporation. 3Com is a registered trademark of 3Com Corporation. Dell is a trademark of Dell Computer Corporation. DynaText is a registered trademark of Electronic Book Technologies, Inc. Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP. 11.0 Disclaimer 11.1 Novell, Inc., makes no representations or warranties with respect to any NetWare 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 NetWare 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.