Solstice(tm) NFS(tm) Client(tm) Release Notes for Windows 95 and Windows NT 4.0 June, 1997 (C) 1997 by Sun Microsystems, Inc. All rights and restrictions that apply to the Solstice Network Client documentation apply to this supplement. ----------------------------------------------------------------- **Contents** 1. What's New in Solstice Network Client 3.1 2. Installation and Configuration 3. File Services 4. Print Services 5. PC-CacheFS 6. User Profiles and System Policies ------------------------------------------------------------------ 1. WHAT'S NEW in SOLSTICE NETWORK CLIENT 3.1 ============================================ New Features in Solstice Network Client 3.1: -- NFS Client file and print services are supported for Windows NT. -- Winsock2 is supported in Windows NT. For updates to release notes, workarounds, frequently asked questions, and similar technical information, please check the News and Updates link on the Solstice Network Client page at the www.sun.com Web site (www.sun.com/solstice/net_client_html.) 2. INSTALLATION AND CONFIGURATION ================================= Notes on Upgrading PC-NFSpro to Solstice Network Client on Windows 95 -- After upgrading from PC-NFSpro 2.0, you will not be able to run the old Telnet application (although it will remain) over the Microsoft TCP/IP stack, unless you apply Sun patch #103091-03. Otherwise, Telnet will give you an error about the protocol driver not being installed. You can install the patch before or after doing the upgrade from PC-NFSpro 2.0. Installing Applications from Remote Solaris CD-ROM Drives -- Some Windows applications can be installed from a remote CD-ROM drive connected to a Solaris system only if the CD-ROM is mounted manually instead of through Solaris Volume Management. Lotus SmartSuite 97 is one application known to require this. To mount the CD-ROM manually on the Solaris computer: 1. Log in as root or become superuser. 2. Edit the file /etc/vold.conf and comment out the line beginning with "use cdrom drive" by inserting the # character in front of it. 3. Stop and restart Volume Management with the following commands: /etc/init.d/volmgt stop /etc/init.d/volmgt start 4. Insert the CD-ROM into the CD-ROM drive. 5. Mount the CD-ROM with the following command: mount -F hsfs -o notraildot,ro /dev/dsk/ /cdrom where is the proper device name for your CD drive, usually c0t6d0s2 for SPARC machines. 6. Share the /cdrom directory with the following command: share -o ro /cdrom You can then mount the CD-ROM on your Windows machine. To return your system to its original state: 1. Unmount the drive that maps the server's CD-ROM on your PC. net use /d : 2. Unshare the /cdrom directory on the server with the following command: unshare /cdrom 3. Unmount the manual mount: umount /cdrom 4. Edit the file /etc/vold.conf and remove the # character from the line beginning with "use cdrom drive ..." 5. Eject the CD-ROM from the CD-ROM drive: eject 6. Stop and restart Volume Management with the following commands: /etc/init.d/volmgt stop /etc/init.d/volmgt start 7. Check if /cdrom directory is clear: ls /cdrom 8. If it is not empty, you may have to reboot your server to clear it. Installing Corel Professional Office 7 - Corel Professional Office 7 must be installed from a local CD-ROM drive or a network CD-ROM drive mounted on a Windows NT server. It cannot be installed from a drive mounted on a Solaris system. Cannot Find 'sunclean.exe' File -- When you start Solstice Network Client, you may see the error message, "Cannot find the file 'sunclean.exe' (or one of its components)." To prevent this message from reappearing, open the windows.ini file and remove the reference to sunclean.exe on the run= line. If the directories ~suntemp.ns and ~suntemp.tmp are present on your C drive, remove them. Dual-boot Configurations -- In a Windows system configured for dual boot (with Windows NT and Windows 95 in separate target directories) you can install the Solstice NFS file and print sharing component under both Windows 95 and Windows NT, by installing into two different target directories. System Hangs on Reboot -- If you are running one of the system tools (for example, low space notification, disk defrag, or scandisk) at startup time on a network drive, then your system may hang as it attempts to start the system tool before the network drive is actually connected. To avoid this problem, do not run system tools from a network drive at startup. Install Microsoft NetWare Client First in Windows 95 -- On Windows 95 systems, if you want to access NetWare servers as well as NFS servers, you must add the Microsoft Client for NetWare before the Solstice client. Do this through the Configuration tab in the Network dialog box. Printing Problem When Running Novell 32Bit Client - If you are running Novell 32Bit Client and you have a problem with printing to an NFS server, you have two options: 1. Uninstall the Novell 32Bit Client, install the Solstice Client first, then reinstall the Novell 32Bit Client second. Do this through the Configuration tab in the Network dialog box. If both clients are already installed, remove both clients, add the Solstice NFS client and then add the NetWare 32Bit Client. 2. Use the Microsoft Client for NetWare Networks instead of the Novell 32Bit Client. NetWare Coexistence -- On Windows 95, if you use Solstice Network Client with NetWare as the primary network provider, you may have a problem with authentication. When you log into the network, NetWare changes the login name to all uppercase. There is no problem when you log in as a Novell user. However, when you log in to Solstice network, the login name is not recognized, and you will see an error stating that authentication failed. When the Solstice login screen appears, be sure that your login name is entered correctly. Silent Installation -- When performing a silent installation, the user will be presented with a final screen offering to restart the computer. 3. FILE SERVICES ================ NFS Server Browsing Problem with Internet Explorer 4.0 -- If you have installed Microsoft Internet Explorer 4.0 Suite with Integrated Shell, you cannot browse the exports of NFS servers in Network Neighborhood. You can, however, map a drive to an NFS file system using the Map Network Drive dialog. Extended Characters and Authentication -- Solstice Network Client does not support authenticating a username/password pair containing extended characters. NFS Automount Map Browsing Problems -- On Windows 95, if you experience problems when browsing NFS Automount Maps, check to see if your computer uses 16-bit drivers for paging. Use the Control Panel->System->Performance tab to determine if paging drivers are a problem. Look for the message, "Compatibility mode paging reduces overall system performance." If this message appears, avoid browsing NFS Automount Maps. NET USE Command Requires Client for Microsoft Windows -- On Windows 95, when you attempt to use the NET USE command without the Client for Microsoft Windows installed, the following error message appears: "Error 3545: You cannot start or stop the network from within an MS-DOS window." Install the Client for Microsoft Windows from the Windows 95 CD-ROM. Broadcast Problem When Dial-up Adapter Configured -- This problem may appear if you have both a dial-up adapter and an ethernet adapter configured on the same PC, and if the dialup adapter is "bound" to TCP/IP. When the PC is using the LAN connection and broadcasts for an authentication server (or NFS servers), the broadcast may fail. The workaround, when you first use the PC on a local area network, is to view the properties of the dialup adapter and uncheck the TCP/IP binding from the Binding tab. Once the PC has successfully broadcast for a server, you can bind the dialup adapter to TCP/IP and the PC should continue to work correctly. Incorrect Space Requirement Returned from Application Installation -- When you attempt to install an application from a mounted CD drive (with the server running Solaris 2.5.1), you might see a message that an obviously excessive amount of disk space is required to install the application, perhaps 10 times what the product literature describes as needed. This will prevent you from installing the application. To fix this problem, change the mount option in Solstice Network Client to NFS V2, instead of V3, and reboot to have the change take effect. Then the remote drive will provide the correct disk space requirement. To change the mount option, choose Settings->Control Panel->Networks. Then select Solstice Network Client and view the Properties, Advanced tab. Be sure to revert to NFS V3 after installing the application. Security Issue with NFS Server on Windows NT -- If you run NFS Server on a Windows NT server, exported file systems could be at risk from unauthorized access. NFS Server uses the permissions of the user who started NFS Server, rather than those of the user attempting to gain access, to authorize access to files on exported file systems. If NFS Server is started by a privileged user such as the Windows NT Administrator, anyone accessing the exported file systems has the same access rights as the privileged user. To minimize security problems, you should not export an entire disk. You should export only the directories you need to share, and treat those directories as public. Note that this is also a problem if NFS Server is configured to start automatically at Windows startup. Starting NFS Server -- NFS shared files become available to other systems when the NFS Server is started. Any user can manually start NFS server. NFS Server may also be started automatically--regardless of which user is logged in-- if an administrative user previously sets the Enable Solstice NFS Server option in the property page for the Solstice File Sharing service in the Network Control Panel. On Windows NT, a user must be logged in for NFS Server to start, either automatically or manually. This is not true on Windows 95. On Windows 95, if NFS Server is configured to start automatically, it will start if a user logs in or if a user successfully cancels out of login. Performance Enhancements -- * Enable Asynchronous Readahead By default, asynchronous readahead is disabled on Solstice Network Client. You can enable it to increase performance, but you risk experiencing some instabilities. For example, your PC might hang when you attempt to install an application from a network CD-ROM drive to another network drive. To enable asynchronous readahead: 1. Right-click the Network Neighborhood icon and click Properties. 2. On Windows 95, select Solstice NFS Client in the Configuration tab. On Windows NT, select Solstice NFS Client in the Services tab. 3. Click the Properties button. 4. Click the Tuning tab. 5. Under Asynchronous Transmissions, check Enable Asynchronous Readahead. 6. Click OK. 7. Click OK in the Network dialog box, then reboot to put this change into effect. * If you access network drives frequently, it is better to mount these drives rather than browse them in Network Neighborhood. * To improve performance, remove from the Network any clients or services that you do not use. Mount Options are Stored According to NT User Login Name -- Mount options are stored according to your NT login name. If you log in as a different NT user, you can establish your own persistent mounts and mount options. Persistent Mounts -- Mounted printers and file systems are stored using a fully-qualified domain name. If you change your naming service to a different domain or if your primary name service fails and your backup name service is in a different domain, your existing mounts will not automatically remount. You will have to remount the printers and file systems manually. Solstice Network Client Hangs When Browsing NFS Servers -- Solstice Network Client hangs when browsing NFS servers if DNS is not configured to resolve IP addresses to host names. This happens if DNS is set up for unidirectional resolution: host names to IP addresses. In this situation, create a local hosts file as a work-around, or fix the DNS configuration. Internationalization Limitation -- When browsing NFS servers, you may have a problem mapping a drive to a resource whose name contains 8-bit characters. You can, however, map the drive using the Map Network Drive dialog box in the Toolbar of Explorer, My Computer, or Network Neighborhood. 4. PRINT SERVICES ================= Adding Network Printer with Add Printer Wizard -- On Windows 95 and Windows NT, when adding a network printer with the Add Printer Wizard, be sure to answer No to the question "Do you print from MS-DOS-based programs?" Solstice Network Client does not support printing from DOS. If you answer Yes, you will get an error when you try to capture the LPT printer port. Syntax for Mounting Printers -- On Windows 95, do not use the double back-slash when mounting printers, either with PCNFSD or LPR printing. Use the forward-slash, as in: lpr://servername/queuename or pcnfs://servername/queuename 5. PC-CacheFS ============= Do not install Solstice Network Client on a system if PC-CacheFS is enabled, especially over a network connection to a cached, mounted drive when diskspace is low. To disable PC-CacheFS, from Solstice Utilities, choose the PC-CacheFS Monitor. In Cache Configuration, click Delete Cache. PC-CacheFS is not available for Windows NT. 6. USER PROFILES AND SYSTEM POLICIES ===================================== User Profiles Work Inconsistently on Windows NT -- We recommend that you do not store User Profiles on an NFS server, since they are not updated consistently. When a user logs in, the more recent user profile stored on the server is not always copied to the local computer for use during the current session. Windows NT uses the local user profile instead, even though it may be older than the version stored on the server. When a user logs out, the user profile is not always updated with the current settings. System Policies and Logon Scripts stored on an NFS server do work consistently. Note: You can use names, instead of numbers, for user policy names. Windows NT Group Policies Not Supported -- Group policies are not supported in Solstice Network Client on Windows NT.