Copyright: Copyright 1990-1998 Citrix Systems, Inc.


New in This Edition of the Readme (02/98)

The following sections are new in this edition:

Load Balancing and Application Publishing

ICA Browsing and Error Handling Overview

Frequently Asked Questions About Load Balancing

Configuring a Load-Balanced Windows NT Desktop (Single Server Image)

Replicating Gateway Services for NetWare Settings Between WinFrame Servers in a Load-Balanced Server Farm

Load Balancing and Application Publishing Across a Firewall

Load Balancing and Application Publishing Across Domain Trusts with WinFrame 1.7

Load Balancing Registry Entries

ICA File Syntax

Creating Customized WinFrame Client Diskettes

The following topics have changed in this edition:

Adjusting Keyboard and Mouse Responsiveness

Frequently Asked Questions on Administration and Configuration

Publications Errata

Examining a System Crash Dump

WinFrame-Specific Environment Variables


IMPORTANT! READ ME FIRST!
READ THIS FIRST

The following topics contain important information for system administrators, and should be read first.

New in this Edition of the Readme (02/98)

Load Balancing and Application Publishing

Creating User Accounts on WinFrame

Frequently Asked Questions About Administration and Configuration

Drive Mapping

General Installation of Applications on WinFrame

Application Performance Tuning

 NetBIOS WinStations

 IPX/SPX WinStations

 Configuring a Firewall for TCP/IP WinStations

 NASI WinStations

 Configuring WinFrame for Dialin Clients

 System and Client Printing

Note

Refer to the latest WinFrame Solutions Guide for the most up-to-date product application notes.


Welcome to WinFrame

This Readme file is designed to answer some of the most common questions regarding administration of a WinFrame server. Instead of repeating information that is already in the printed documentation, links have been made to their online versions. This file should not be used as a replacement for the printed documentation. For the latest information, refer to the WinFrame Solutions Guide, the Citrix web site at http://www.citrix.com, or your Citrix support representative.

Conventions

The following conventional terms, text formats, and symbols are used throughout the documentation.

Convention	Meaning
Bold	Indicates the actual commands, words, or characters that you type in a dialog box or at the command prompt.
Italic	Indicates a placeholder for information or parameters that you must provide. For example, if the procedure asks you to type filename, you must type the actual name of a file. Italic also indicates new terms and the titles of other books in the documentation set.
ALL UPPERCASE	Indicates a directory, filename, or acronym. You can use lowercase letters when you type directory names or filenames in a dialog box or at the command prompt, unless otherwise indicated for a specific application or utility.
Monospace	Represents examples of screen text or entries that you might type at the command line or in initialization files.
	Indicates a procedure.
\WINNT, \WINFRAME, or %SYSTEMROOT%	Refers to the WinFrame system tree. This can be %SYSTEMROOT%, \WINNT, \WINNT35, \WINDOWS, or whatever other directory name you specified when installing WinFrame.


Publications Errata

This section contains updates and additions to the WinFrame Manuals.

Installing WinFrame and Using WINNT.EXE in Chapter 2 of the Installation Guide - The correct command for creating new boot disks for WinFrame should be:

winnt /ox

Using System Recovery in Control Panel in Chapter 2 of the Installation Guide - The correct introduction for the section should be:

When a severe error (called a STOP error, or fatal system error) occurs on WinFrame, by default the system writes an event to the system log, alerts administrators, dumps system memory to a file you can use for debugging, and automatically reboots the server. Because WinFrame automatically reboots rather than waiting for administrator intervention, fatal system errors cause less server down time than they would otherwise.

The dump of system memory to a log file can be valuable for debugging the cause of the STOP error. If you contact your technical support representatives about the error, they may ask for the log file. The log file will not be created unless the paging file is on the same drive letter as the WinFrame system and there is free drive space equal to the size of the paging file plus  between 1 and 20 megabytes. Notice that WinFrame writes the log file to the same file name (MEMORY.DMP, by default) each time a STOP error occurs; to preserve log files, you should copy them to a new filename each time a STOP error occurs.

To perform these actions, drivers (totaling a few kilobytes of memory) must be kept in memory at all times. If desired, you can disable these actions to make more memory available. This is not recommended. To change how WinFrame reacts to a STOP error, use the System option in Control Panel.

Installing the Client-Based network Administration Tools in Chapter 9 of the Installation Guide - The version of User Manager for Domains installed with the Client-Based Network Administration Tools does not display WinFrame-specific configuration options. These options are only available when running User Manager for Domains on a WinFrame server.

Feature Summary and System Requirements in Welcome and Planning for Installation in Chapter 10 of the Installation Guide, and Feature Summary and System Requirements in Chapter 1 of the Concepts and Planning Guide - A personal computer using a 386 or higher microprocessor is the minimum requirement for the WinFrame Win16 Client. To use the SecureICA DOS client, a 386 or higher microprocessor is required.

Making Sure You Have Enough Memory in Chapter 10 of the Concepts and Planning Guide and Changing the Virtual-Memory Paging File in Chapter 5 of the System Guide - The recommended size given for the paging file is incorrect. The recommended size is 1.5 times the amount of RAM available on the server.

Finding More Information in Before You Begin and Starting and Quitting WinFrame in Chapter 1 of the System Guide - The "Introducing Windows NT" online demonstration program is not included with WinFrame.

Using Windows NT Applications in Chapter 1 of the System Guide - The icons for WinStation Configuration, WinStation Administration, and Product Licensing are not in the online version of the System Guide. Refer to the printed version of the System Guide for illustrations of these icons.

Adding ICA Hotlinks to Web Pages in Chapter 24 of the System Guide - The correct CODEBASE parameter should be:

CODEBASE="http://www.citrix.com/bin/cab/wfica.cab"

QUERY SERVER in Appendix A of the System Guide - On a server with two network cards, the query server command will only enumerate servers on one card's subnet at a time. To enumerate the servers on the other card's subnet, specify the address of any server on the subnet with the /tcpserver:x, /ipxserver:x, or /netbiosserver:x parameter.

How Security Works at Connection Time in Chapter 4 of the Remote Access Service manual - This page is missing. It has been reproduced here

Configuring User Rights and User Profiles in Chapters 4 and 5 of the Security Guide - The correct description for Step 11 should be:

11.	The For Unlocked Groups, Allow User To options are not relevant if application security is enabled using the Application Security Registration utility. The default option Make Any Change allows a user to create a new group and then create icons within the new unlocked group. To prevent users from creating new groups, select one of the other options.

Option	Description
Create/Delete/Change Program Items	Users can create, delete, and change program items but cannot create, delete, or change program groups.
Change All Program Item Properties	Users can modify existing program items but cannot create or delete them, nor can they create, delete, or change program groups.
Change Program Item Properties Except Command Line	Users can change all properties of a program item except the entry in the command line of the Program Item Properties dialog box. Users cannot create or delete program items, nor can they create, delete, or change program groups.


New/Changed/Removed Commands

CLTPRINT

This utility sets the number of printer pipes to the client print spooler. Printer pipes are used to send data from applications to client print spoolers. The number of pipes specifies the number of print jobs that can be sent to the spooler simultaneously. The default number of printer pipes is 10. See the topic CLTPRINT for more information.

ALTADDR

This utility is used to query and set the alternate (external) address that a WinFrame server will return to clients who request it. The alternate address is used by WinFrame clients outside a firewall. This utility is included in Hotfix SE170016. See the topic Load Balancing and Application Publishing Across a Firewall for more information.

CNVRTUC

This utility allows WinFrame user configuration data to be replicated to backup domain controllers (BDCs) from the primary domain controller (PDC) by migrating the accounts from the Registry of the PDC to the Security Accounts Manager (SAM) database. This is necessary for both Windows NT and WinFrame PDCs. Once the migration is accomplished, the replication of the WinFrame user configurations will be performed using the normal policies governing the replication of the user account database from the PDC to one or more BDCs. This program must be run from a WinFrame server while logged in as a domain administrator. It does not need to be run from the PDC.

SETBUILD

Some hardware manufacturers' update programs check the Windows NT build and version number prior to installing updated HALs and drivers. Previous versions of WinFrame used a different build number than Windows NT to prevent accidental overwriting of WinFrame-specific system files. The SETBUILD command was used to change the build level of WinFrame to match Windows NT 3.51. WinFrame Version 1.7 now reports the same build level as Windows NT, build level 1057, so the SETBUILD command is not required.

Caution

DO NOT apply Microsoft Windows NT 3.5 Service Packs to your system. These will corrupt your system setup. Only use WinFrame Service Packs provided by your Citrix support representative. WinFrame Service Packs incorporate the same updates contained in Microsoft Windows NT Service Packs after they have been tested for compatibility with WinFrame.

WFICONS

When a Windows NT 3.51 server is upgraded to WinFrame Version 1.7, the additional WinFrame icons are not added to the Program Manager groups of existing users. To add these icons to an existing user's Program Manager groups, run wficons from the command line while logged on as that user. All user accounts created after WinFrame is installed will automatically have these icons.

Ten icons are added to the Administrative Tools group: Application Configuration, Application Security Registration, C2 Security Manager, Dial-In Setup Wizard, NetWare User Access for WinFrame, WinFrame Activation, WinFrame Client Disk Creator, WinFrame Licensing, WinStation Administration, and WinStation Configuration. Two icons are added to the Main group: Hardware Compatibility List and Solutions Guide. The Application Configuration and Application Security Registration icons are new to WinFrame 1.7.

HOTFIX

Hotfixes are interim WinFrame system patches which are tested and verified to fix specific problems. They should be applied only on the advice of your support representative. The HOTFIX command is used to install, remove, and verify these patches. See WinFrame Hotfixes and Service Packs in the Solutions Guide for more information on using this command.


CLTPRINT

Description

Sets the number of printer pipes to the client print spooler.

Syntax

CLTPRINT [/Q] [/PIPES:nn] [/?]

Options

/PIPES:nn

Sets the specified number of printer pipes. This number must be between 10 and 63.

/Q

Displays the current number of printer pipes.

/? (help)

Displays the syntax for the utility and information about the utility's options.

Remarks

Printer pipes are used to send data from applications to client print spoolers. The number of pipes specifies the number of print jobs that can be sent to the spooler simultaneously.

The default number of printer pipes is 10.

The Spooler service must be stopped and restarted after changing the number of pipes. Print jobs already spooled will continue printing.

Print jobs sent to the spooler will get an error message. Make sure no users start printing during the time the spooler service is stopped.


Configuring WinFrame

This section contains instructions on configuring your WinFrame server.


Frequently Asked Questions on Administration and Configuration
Frequently Asked Questions About Administration and Configuration

Note

Refer to the latest WinFrame Solutions Guide for the most up-to-date product application notes.

You can use the following links to go directly to a topic or scroll down to browse them all:

When users logon using the WinFrame Client, their local AUTOEXEC.BAT path data is appended to their default WinFrame path. How can I keep this from happening?

When I add a second SCSI drive to my WinFrame system, it fails to boot properly.

What actually happens when I shut down the system, and why does it take so long?

I had to restore my system using the Emergency Repair diskette, and now all the users and WinStations added since I installed WinFrame are gone.

How can I prevent users from logging on to a WinFrame server while I perform system maintenance?

I am concerned about system security. How can I proactively monitor unsuccessful logon attempts?

How can I shadow remote users from the WinFrame system console?

What happens if a WinFrame Client PC is accidentally disconnected during remote printing or a file transfer?

I am having trouble with SNA connections.

How can I change the video resolution for my WinFrame Client sessions?

The modem list contains modems that have a "CTX" at the end of their description. What does this mean?

If WinFrame is installed over an existing copy of Microsoft Windows NT 3.5, what icons does WinFrame Setup add?

How do I configure my multiport serial adapter?

How can I map my local drive C when connected to the WinFrame server?

How do I set up WinFrame to run over an ISDN connection?

Does WinFrame support Windows applications that require VxDs?

When connecting to a NetWare 2.2x server from a WinFrame session, I cannot change to a directory in which I have rights if I have no rights in the parent directory. Why?

While logged in to WinFrame and running an application stored on another server, a network error caused my application to crash and display a Dr. Watson error of type (0xC0000005). None of the WinFrame users were then able to access the application. Why?

How can I prevent users from accessing their client computer from the WinFrame session?

How can I control client drive mapping?

When connecting to network drives in File Manager, how can I make the "Reconnect at Login" box unchecked as the default setting?

I can't seem to run programs stored on a mapped drive when configured as Initial Applications in Remote Application Manager.

I can't seem to run batch files as Initial Applications in Remote Application Manager.

How can I remotely administer my WinFrame server?

Why are print jobs larger when sent through a client print queue (compared with going directory to a network printer)?

Can WinStation Administration display information about WinFrame servers in other domains?

Why are the CLIENTNAME or WINSTATIONNAME environment variables different from what is reported in WinStation Administration?

Can users reconnect to published applications?

When users logon using the WinFrame Client, their local AUTOEXEC.BAT path data is appended to their default WinFrame path. How can I keep this from happening?

By default, WinFrame appends any path data from C:\AUTOEXEC.BAT to the default path. To keep this from happening, follow these steps:

To prevent client AUTOEXEC.BAT path data from being appended to the default path

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions.

1.	Logon as the user you want to change this setting for.

2.	Run the Registry Editor by choosing Run from the File menu in the Program Manager and typing REGEDT32.EXE.

3.	In the Registry Editor, find the Registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ParseAutoexec.

4.	The associated data type and value will be REG_SZ and 1. Change the value to 0 and save the change. This will prevent Winlogon (the logon process) from appending the local path the next time the user logs on.

To apply this change to multiple users, use the User Profile Editor to copy the profile to another user or make it the default. Refer to Chapter 14, "User Profile Editor", in the System Guide for more information on using the User Profile Editor.

When I add a second SCSI drive to my WinFrame system, it fails to boot properly.

Verify that the second SCSI drive has a different, unique SCSI ID. If the second drive has the same SCSI ID as the boot drive (which should be SCSI ID 0), the system will not boot properly. Also make sure that the terminating resistors are properly installed (one at each end of the SCSI device chain) and that the terminators have power. Watch the power-on self-test (POST) to verify that every SCSI device is properly detected and that the boot drive is SCSI ID 0.

What actually happens when I shut down the system, and why does it take so long?

A system shutdown terminates all users and active programs. The following steps occur during shutdown:

1.	An exit command is issued to all active user applications.

2.	If the application does not exit within a specific interval, the application is terminated.

3.	After all the applications for a user terminate, the user is logged out.

4.	After all users are logged out, an exit command is issued to all system services.

5.	If the system service does not terminate within a specific interval, the service is terminated.

6.	The file system cache is written to disk.

7.	The disks are marked Read Only.

8.	The "System can be turned off" message is displayed, or the system is rebooted if the Shutdown and Reboot option was selected.

Warning

The command-line form of the SHUTDOWN command supports the /NOW option. SHUTDOWN /NOW forces an immediate shutdown, skipping Steps 1 through 5 above. DO NOT use SHUTDOWN /NOW unless it is absolutely necessary, as there is a possibility of severe data loss or file corruption.

Because there can be many users and processes in a large multi-user configuration, large system configurations may take some time to shut down in an orderly fashion. It is important to allow the system to shut down completely. You may need to make sure that your UPS can sustain the system for the amount of time it takes to complete a worst-case shutdown.

I had to restore my system using the Emergency Repair diskette, and now all the users and WinStations added since I installed WinFrame are gone.

The Emergency Repair diskette only contains the Administrator and Guest userids. If you had a large number of users and WinStations, the additional information could overflow the Emergency Repair diskette, making it unusable. The proper procedure is to use the Emergency Repair diskette to repair the system, and then to restore user and WinStation data from a backup tape.

How can I prevent users from logging on to a WinFrame server while I perform system maintenance?

Use CHANGE WINSTATION /DISABLE to disable user logons at WinStations other than the system console. Since CHANGE WINSTATION does not log off users currently logged on, notify those users to log off. Once the users have logged off, perform your required maintenance at the system console or your current WinStation.

When you are done, you can either shutdown and reboot the system or use CHANGE WINSTATION /ENABLE to re-enable user logons.

I am concerned about system security. How can I proactively monitor unsuccessful logon attempts?

Enable logon/logoff event logging, and use the AUDITLOG utility to generate reports of unsuccessful logon attempts. AUDITLOG can also display logon and logoff times and logon duration by user for usage accounting. Refer to Appendix A, "WinFrame Command Reference" of the System Guide for more information.

How can I shadow remote users from the WinFrame system console. How can I do this?

Run the WinFrame Win32 client at the console. Create a remote application that logs on to the WinFrame server using a network protocol you have WinStations configured for. Logon at the console using that remote application. You can now shadow user sessions from the WinFrame Client connection at the WinFrame console.

What happens if a WinFrame Client PC is accidentally disconnected during remote printing or a file transfer?

If a remote print job is interrupted, the currently printing job is restarted from the beginning the next time a WinFrame Client PC with that clientname connects to the WinFrame server. (This is why it is important to make sure that each WinFrame Client PC has a unique clientname.) The print job can be deleted while it is waiting for a reconnect.

For file transfers, the application doing the transfer gets a network disconnected error. The application must then close the file and reopen it after reconnecting to the WinFrame server.

I am having trouble with SNA connections.

Microsoft SNA 2.11 works. Refer to Chapter 7, "AS/400 Minicomputer Connectivity and WinFrame" in the Solutions Guide for more information.

How do I change the video resolution for my WinFrame Client sessions?

Use the WinFrame Client to change video resolution. Make sure you do not have any active connections to the WinFrame server when you change the resolution settings. Choose Settings from the Options pull-down menu. Select Preferences. The current screen resolution and colors are shown. Select Change to change the displayed values. Make sure the settings you choose are compatible with your video adapter and monitor.

The modem list contains modems that have a "CTX" at the end of their description. What does this mean?

These modems are definitions from our WinView product. If the standard NT modem list does not contain your modem, select from these modems.

If WinFrame is installed over an existing copy of Microsoft Windows NT 3.5, what icons does WinFrame Setup add?

Ten icons are added to the Administrative Tools group: Application Configuration, Application Security Registration, C2 Security Manager, Dial-In Setup Wizard, NetWare User Access for WinFrame, WinFrame Activation, WinFrame Client Disk Creator, WinFrame Licensing, WinStation Administration, and WinStation Configuration. Two icons are added to the Main group: Hardware Compatibility List and Solutions Guide. These icons are added only for new users. Existing NT users are not automatically upgraded. To add these icons to an existing user's Program Manager groups, run wficons from the command line while logged on as that user.

How do I configure my multiport serial adapter?

WinFrame (and Windows NT) treat multiport serial adapters as network adapters. To add a multiport serial adapter to the configuration, you must double-click on the Control Panel icon in the Main group, then click on the Network icon. Click on the Add Adapter button and choose the correct multiport adapter from the network adapters list. The rest of the setup is straightforward.

How can I map my local drive C when connected to the WinFrame server?

By default, WinFrame maps your client drives for you automatically when you connect, unless a system administrator has disabled this feature. To see which drive letters your local drives are mapped to, start the Windows File Manager and examine your mapped drive letters, or type net use at a command prompt. One drive should be mapped to \\Client\C:. This is your local disk. The drive mapping utility first tries to map client drives to their actual drive letter, if the client drive's actual drive letter is not free, drive mapping looks for a free drive letter starting backwards from V. You can manually map your client drives to different drive letters using the Windows File Manager. Select Connect Network Drive from the Disk menu and choose the local drive you wish to map from the Client Network in the Shared Directories window. The Client Network is used by the WinFrame client to map client drives and printers.

How do I set up WinFrame to run over an ISDN connection?

This depends on the ISDN solution you are using. There are two types of ISDN solutions. The first type is an ISDN-to-Ethernet (or other network style) bridge. This kind connects into your network and pipes network packets over the ISDN line to a remote site. ISDN bridges are transparent to WinFrame servers and clients because they emulate a standard network. The second type of ISDN solution uses ISDN adapter cards placed in the WinFrame server and the remote WinFrame client. The ISDN card is used as a RAS port by WinFrame RAS. Refer to Chapter 6 of the Remote Access Services manual and Chapter 8 of the Solutions Guide for specifics on particular ISDN solutions.

Does WinFrame support Windows applications that require VxDs?

No, nor does Windows NT. VxDs directly access hardware resources. It is very easy for a corrupt VxD to bring down an entire system; therefore VxDs are not allowed on WinFrame or Windows NT. Applications that require the use of VxDs must be rewritten to function properly with WinFrame and Windows NT. As more 32-bit applications are developed, this will become less of a consideration.

When connecting to a NetWare 2.2x server from a WinFrame session, I cannot change to a directory in which I have rights if I have no rights in the parent directory. Why?

To fix this problem, grant "Read" and "File Scan" rights to the parent directory. This should not cause any security problems as no changes can be made, and the user is still not able to view any other subdirectories they do not have access to.

While logged in to WinFrame and running an application stored on another server, a network error caused my application to crash and display a Dr. Watson error of type (0xC0000005). None of the WinFrame users were then able to access the application. Why?

In order to keep system resources low, all users reference a single virtual-memory image of any 32-bit applications that are run. If the actual application file is unavailable when requested by the virtual-memory manager, the link between the virtual-memory image and the file on the disk is severed. To solve the problem, every process that is using the virtual-memory image must be terminated. The virtual-memory image will be discarded and a new functional image will be created the next time a process accesses the file. If you encounter this problem, have all users who were using the application log off the system. Then reset all disconnected WinStations using WinStation Administration. A preventative measure is keeping all applications stored on the WinFrame server, which will minimize the possibility of network errors.

How can I prevent users from accessing their client computer from the WinFrame session?

While there is no specific way to disable this feature, a system administrator can remove a Registry value to make WinFrame Client users unable to use their local client drives and printers from the File Manager, Print Manager, and the NET USE command line utility.

Note

It is still technically possible for application software to access client drives using Windows API calls.

To Disable Browsing and connecting client drives

1.	Run Control Panel from Program Manager on the WinFrame server.

2.	Double-click on the Services icon.

3.	Select the Client Network service and click the Stop button.

4.	When the service is stopped, click on the Startup button.

5.	Change the Startup Type to Disabled and click OK.

6.	Click the Close button in the Services window.

7.	Close the Control Panel.

This change will not affect users until they log off and back on.

How can I control client drive mapping?

See the topic Controlling Drive Mapping Assignments for information about the two new Registry values InitialClientDrive and InitialNetWareDrive, which will allow you to better control how drives are mapped during logon.

When connecting to network drives in File Manager, how can I make the "Reconnect at Login" box unchecked as the default setting?

The Registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\Current Version\Network\Persistent Connections contains a value called "SaveConnections" of type REG_SZ. If the "Reconnect at logon" box is unchecked when a user logs off this is set to "no". Otherwise the default is "yes".

To make the "Reconnect at Login" box unchecked as the default:

1.	Logon as the user you want to change this setting for.

2.	Run the Registry Editor by choosing Run from the File menu in the Program Manager and typing REGEDT32.EXE.

3.	Highlight the key HKEY_USERS.

4.	Choose "Load Hive" from the "Registry" menu.

5.	Open the file %SystemRoot\System32\config\UserDef.

6.	When prompted for the key name enter "UserDef".

7.	Change the value "SaveConnections" to no" under the key HKEY_USERS\UserDef\Software\Microsoft\Windows NT\Current Version\Network\Persistent Connections

8.	Highlight the key HKEY_USERS\UserDef and choose the "Unload Hive" option from the Registry menu.

9.	Reboot

New users will now find the box unchecked by default. Existing users will have to uncheck the box and then logout. If they are using a mandatory profile, uncheck the box then re-save the profile.

I can't seem to run programs stored on a mapped drive when configured as Initial Applications in Remote Application Manager.

This problem occurs when the login process attempts to run the specified application before the persistent drive mappings have been restored. One solution to this problem is to make the Initial Application a Command (.CMD) file or Batch (.BAT) file that waits for a few seconds before running the application. Here is an example using the SLEEP.EXE program included in the Microsoft Windows NT Resource Kit:

Sleep 10

start /MAX t:\app.exe

The Sleep program simply waits the specified amount of time (in this case 10 seconds), which should give the logon process enough time to complete. The next statement launches the specified program in maximized view.

A better method is to map the drive in the login script and use a profile with the "Wait for logon script to complete before starting Program Manager" option checked. This will ensure the drive is mapped without any unnecessary waiting.

I can't seem to run batch files as Initial Applications in Remote Application Manager.

You must specify the BAT or CMD extension in Remote Application Manager.

How can I remotely administer my WinFrame server?

Installing the Client-Based Network Administration Tools will allow you to manage users, shared directories, printers, and file permissions on WinFrame and Windows NT servers. It will install the following programs: User Manager for Domains, Server Manager, Event Viewer, Print Manager. It also adds a Security menu to the File Manager for viewing and setting file permissions on remote servers.

The version of User Manager for Domains installed with the Client-Based Network Administration Tools does not display WinFrame-specific configuration options. These options are only available when running User Manager for Domains on a WinFrame server.

Why are print jobs larger when sent through a client print queue (compared with going directory to a network printer)?

Normally, when a file is printed to a local queue it will contain references to fonts already available. Because the WinFrame Print Manager is not aware of the fonts present on the client PC, it embeds all of the necessary font information into the file that is sent to the client.

Can WinStation Administration display information about WinFrame servers in other domains?

Yes, but only from domains that have a trust relationship with the domain you are in when WinStation Administration is run. WinStation Administration does not indicate which domain a server is in.

Why are the CLIENTNAME or WINSTATIONNAME environment variables different from what is reported in WinStation Administration?

These environment variables are set during logon. Therefore, when you reconnect to a disconnected session the environment variables are not changed. See WinFrame-Specific Environment Variables for more information about the CLIENTNAME and WINSTATIONNAME environment variables.

Can users reconnect to published applications?

Yes. The WinFrame 1.7 ICA Browser allows sessions disconnected from published applications to reconnect. The ICA Browser contains a list of disconnected sessions and associates a client name and published application name with a specific server so if the same client computer attempts to reconnect to the same published application, it will be directed to the server it was disconnected from.

The user must disconnect the session 'gracefully.' To do so, press Shift+F3 (or another hotkey assigned to close a remote application) and then click OK in the dialog box that is displayed. The user must then logon with the same username and the same CLIENTNAME (the name for the client computer specified in WFNAME.INI) to get reconnected to the same session. If the user tries running the published application from a different client computer, they will be connected to the least busy application server, which may or may not be the server with the disconnected session.

If this is not working property, verify that the session was disconnected properly by typing
query server /disc at a command prompt to display a list of the currently disconnected sessions. If the disconnected session is not listed, the user did not disconnect properly.


Drive Mapping

When a user logs in to a WinFrame server, the hard drives on the client system are mapped to drive letters in the WinFrame session. The server first tries to match the client drives to the actual drive letters; for example: A to the first diskette, B to the client system's second diskette, C to the first hard drive partition, etc. This allows the user access to client drive letters in the same way from local or remote sessions. However, these drive letters are often used by the drives on the WinFrame server. In this case, client drives are mapped to other drive letters. The server starts at V and searches backward looking for free drive letters to map the client drives to. This way, the user can still access local drives, even though they have been assigned other drive letters (not necessarily in sequence). You can specify the drive letter mapping method during installation of WinFrame, or use the following procedure to change the drive letter mappings after installation.

If you want to change drive letter assignments and did not do it during Setup, you should change the drive letters for the WinFrame server immediately after installation. No users should be logged into the system during this procedure and all programs must be closed. Drive letter reassignment should be done before installing any applications on the WinFrame server. If you have already installed applications, their INI files and Registry settings may point to the wrong drive letters and cause the applications to operate incorrectly.

To change drive letter assignments

1.	Logon as an administrator onto the WinFrame server console.

2.	Start the Disk Administrator.

3.	Select the first drive partition, usually C, and click the Drive Letter option under the Tools menu. Set the drive letter for C to the drive letter where you want the WinFrame server to start. Most small client systems have one or two hard drives. Therefore, starting at drive E or F should leave enough drive letters free for client systems to use. Click OK to make the change. If you change your boot drive, you will get an error message that the drive is being used. Just continue and set the drive to change when the WinFrame server next boots.

4.	Select the second drive partition, usually D, and follow the procedure in step 3. to change the drive letters. Continue to do this for each partition until all the drive letters are remapped. Try to assign the drive letters sequentially so that they will be in the same order they were before.

5.	If a CD-ROM drive exists on the system, select the CD-ROM Drive Letters under the Tools menu and remap its drive letter. Usually this is sequentially last in the drive list.

6.	When done, click Commit Changes Now under the Partition menu. This saves the changes and reboots the system.

When the system reboots, the drive letters are changed to the new drive letters. The system administrator can now install applications, set up users, and configure WinStations as normal. When WinStations connect to the WinFrame server, they are able to map their drives to their default drive letters, making use of the client system easier for the remote user. Users can then access and use their local drives as they normally would.

Controlling Drive Mapping Assignments

In WinFrame, client drive mapping and NetWare login script execution occur in parallel. Therefore, it is very important for the WinFrame administrator to ensure that there are no drive mapping conflicts between the client drives and NetWare drives. It is possible that a user could find V mapped to his client drive C during one WinFrame session but have it mapped to SYS:PUBLIC during another session. This undesirable situation can be avoided by setting two new Registry values stored in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix:

InitialClientDrive

Defines the first drive letter to use for client drive mapping. The system works backward through the alphabet from this letter to map client drives that could not be mapped to their "native" drive letters.

InitialNetwareDrive

Defines the drive letter to be used for the NetWare SYS:LOGIN directory that is mapped to the preferred server during the initial NetWare attachment. This setting is the equivalent of the DOS VLM NET.CFG setting "First Network Drive". If this value is not set, the first available drive letter starting with C and working up to Z will be used for this mapping.

Because the login process is multi-threaded, it is impossible to know for sure what order the various drive mappings will take. This was done to speed the login process. The following steps take place concurrently during login:

A.	If the "Disable Client Drive Mapping" option in WinStation Configuration is not checked and home directory mapping is configured in User Manager for Domains the client drives are mapped using steps A and B below. If client drive mapping is disabled, the client drives can still be mapped manually by the login script, or by the user after loggin in.

1.	Any available drive letters that match the client's native drive letters are used. Available drive letters are drives not in use as local WinFrame server drives or network connections. For example, if drive C is not in use on the server it is mapped to the client's C drive (\\Client\C:).

2.	For those client drives left unmapped by Step 1, the system starts at drive V and work backward through the alphabet, using available drive letters sequentially for the remainder of the client drives. Drive letters that are already in use as WinFrame server drives, mapped to persistent network connections, or mapped by NetWare login script processing are skipped. For example, drive V is mapped to \\Client\C: when drive C is in use as the WinFrame server's local drive C.

B.	Any drive mappings configured in NetWare login scripts are performed. If a drive letter is already in use, the mapping fails and the existing drive mapping remains.

C.	Any persistent drive mappings manually configured by the user are performed. If a drive letter is already in use, the mapping fails and the existing drive mapping remains.

Consider the following examples:

Example 1

WinFrame server local drives:  C:, D:, T:

Client has drives C:, D:, E:

InitialClientDrive is set to: V: (the new default)

In this particular example, drive V is mapped to the client's drive C, drive U is mapped to the client's drive D, and drive S is mapped to the client's drive E because drive T is already in use on the WinFrame server.

Example 2

WinFrame server local drives:  E:, F:

NetWare login script mappings:  X:, Y:, Z:

Client has drives:  C:, D:, E:

InitialClientDrive is set to: V: (the new default)

InitialNetwareDrive is set to: G: (not set by default)

In this example, drive C is mapped to the client's drive C, drive D is mapped to the client's drive D, and drive V is mapped to the client's drive E.

Example 3

WinFrame server local drives:  E:, F:

NetWare login script mappings:  V:, W:, X:, Y:, Z:

Client has drives:  C:, D:, E:

InitialClientDrive is set to: V: (the new default)

InitialNetwareDrive is not set (the default)

This configuration can be very confusing. Because the InitialNetwareDrive Registry value is not set, it's possible that drive C could be mapped to SYS:LOGIN on the NetWare server or to the client's drive C. It is also possible that drive V could be mapped to the NetWare server or to the client's drive E or C. It depends upon whether the NetWare script execution completes before the client drive mapping or vice-versa.

The last configuration (Example 3) should be avoided if at all possible. It is recommended that both the InitialNetwareDrive and InitialClientDrive values be set to avoid this problem. Follow these guidelines when setting these values:

Set InitialNetwareDrive one drive letter higher than the last physical WinFrame server local drive.

Set InitialClientDrive so that client drive mappings won't conflict with NetWare mappings. If your login script maps drives F though L and T through Z, set InitialClientDrive to S.

To add the Registry values

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions.

1.	Run REGEDT32.EXE.

2.	Locate the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

3.	With this key highlighted, select Add Value from the Edit menu.

4.	Type InitialClientDrive in the Value Name field.

5.	Select REG_SZ from the Data Type pull-down list, then click OK.

6.	In the String field, type the drive letter that you want to use. Include the colon; for example S:.

7.	Click OK.

8.	Select Add Value from the Edit menu.

9.	Type InitialNetwareDrive in the Value Name field.

10.	Select REG_SZ from the Data Type pull-down list, then click OK.

11.	In the String field, type the drive letter that you want to use. Include the colon; for example F:.

12.	Click OK.

13.	To finish, exit the Registry Editor.


System and Client Printing

Printing Overview

WinFrame supports three different types of printers: local printers, network printers, and client printers.

Local printers are printers connected to parallel or serial ports on the WinFrame server or "port monitor" ports such as HP network printers and UNIX LPD printers. Local printers are generally local to the WinFrame server, and are connected to using the Create Printer selection in Print Manager. Additional local printers can be added by installing additional ports in the Other selection under Print to.

Network printers are printers connected to remote print servers that are available as network resources. The remote print servers run Novell NetWare or Windows NT Server. These are under the control of the remote print server. Connect to these printers using the Connect Printer selection in Print Manager. Access network printers by installing the appropriate network support software.

Client printers are printers connected to a WinFrame Client PC. Client printers are a cross between a local printer and a network printer. They represent printers that exist on the client PC. These are under the control of both the client PC and the WinFrame server. Connect to a client printer using the Connect Printer or Create Printer selections in Print Manager, or use the default printer mapping facility of the WinFrame Windows Clients. Client printers are associated with the Client Network under network types.

Client Printing and Clientname

Each WinFrame client PC has a clientname, which is specified when the WinFrame Client is installed. The clientname is very important in client printing, and is how the WinFrame print spooler identifies a given client when dealing with client printers. Each client PC should have a unique clientname. The WinStation a client is currently logged onto does not identify the client printer, since a given client could logon from a local IPX connection, and then reconnect later over a dial-in connection. By having a unique clientname, the WinFrame print spooler can always properly identify the client.

The clientname is stored in the file WFCNAME.INI. This can be overridden by the /clientname command-line switch for Remote Application Manager. If the clientname does not exist in WFCNAME.INI and is not specified with the command-line option, the Windows GetComputerName API call is used to generate the clientname.

The WinFrame Windows Clients supplied with WinFrame Version 1.7 now support a new remote printing protocol designed to work with remote spoolers, such as Windows. This allows a user to browse their client printers in the same manner they browse for remote NetWare or Windows NT Server printers. When the user selects a specific client printer, the printer device driver information in automatically retrieved from the client computer, and used to create the local WinFrame client printer. The client printer name is made up of the clientname and the Windows printer name. For example, a Windows client with a clientname of "Warehouse" and a printer name of "Shipping Labels" would generate a client printer name of "Warehouse#Shipping Labels". This name cannot be changed, and is used to locate the specific printer on the specific client PC. Since the Windows printer name is used and not the port name, multiple printers can share an LPT port without conflict.

When connecting to a client printer, the user is not required to enter any information unless the system cannot find a driver match, in which case the user is prompted with a simple dialog to select the printer driver.

To Manually Connect to a Client Printer

Start Print Manager, then select Connect To Printer from the Printer pull-down menu. A list of available networks such as Client Network, NetWare Network, and Microsoft Windows Network is displayed. Double-click on Client Network, and it will show a single entry with a computer icon called Client. This refers to the client currently connected to the WinFrame server. Double-clicking on Client displays a list of printers available on the Windows Client PC. Double-clicking on one of the printers creates a client printer automatically. You may be prompted to specify a driver and paper tray information. Once the printer is connected, it is available for printing from any Windows application.

Automatic Client Printers

Client printers can be automatically connected when a user logs on from a client PC and automatically deleted at logoff if the print queues do not contain any print jobs. Automatic client printing is configured by the Connect Client Printers at Logon check box in the Client Devices dialog for a WinStation or a user. If Connect Client Printers at Logon is checked, client printers are automatically created and deleted. This feature is only available with the Windows clients. The WinFrame DOS Client does not support automatic client printers, although printers can be defined manually.

If you do not want the automatically created printers deleted on logoff, run Print Manager. Open the Printer, Properties, dialog. This dialog contains a Description field, which contains the string "Auto Created Client Printer". If this description is modified or deleted, the printer will not be deleted at logoff. Future logons will find the printer already present, and will not modify it. Changes to your Windows printer settings will not be automatically set. This can be useful if you use custom print settings.

If Connect Client Queues at Logon is not checked, the user can still use Print Manager to manually connect a client printer which is not deleted at logoff.

Use Connect Printer instead of Create Printer when configuring client printers on Windows clients. Connect Printer is much less error prone.

To Setup Client Printers for the WinFrame Client for DOS

Make sure the printer is connected to a LTP or COM port on the DOS client system. From the client system, run WinFrame Client and connect to the WinFrame server. Once connected, logon and start the Print Manager in the Main group. On the Printer menu, select Create Printer. In the Create Printer dialog box, select the correct printer driver from the drop-down box of printer drivers. Select the correct portID for the Print To field. This should be in the form:

CLIENT\LPT1:	For the client system's local LPT1 port

CLIENT\LPT2:	For the client system's local LPT2 port

CLIENT\COMx:	For the client system's local COM ports (where x is the COM port number)

Make sure you DO NOT change the default Printer Name. This is of the form Clientname#LPTx and is used to associate a client printer with a client system. If this is changed, the printer will not install correctly and will not work. If Share This Printer On The Network is checked, the printer is accessible to other users on the network. Obviously, the printer will only print for network users when the WinFrame Client is connected to that particular WinFrame host. When the information is correct, click the OK button and enter the Printer Setup information for the printer; the printer queue is created. Use the Permissions option under the Security menu to grant other users access to their client printer. This printer is used as any other standard print queue.

Note

Make sure that the DOS client system does not already have a network printer captured or net used to the LPT or COM port, otherwise the print job is routed to the network printer rather than the local printer.

To Setup Client Printers for Windows 3.1x, Windows 95, or Windows NT WinFrame Clients

On a Windows client, the WinFrame client printer queue prints to the local Windows printer queue on your client. You must, therefore, make sure the printer driver loaded on WinFrame matches the printer driver loaded on your local Windows client. To do so, compare the name displayed in the Print Manager on the client computer with the name stored in the PRINTER.INF file on the WinFrame server--they must be exactly the same.

The WinFrame Windows Clients directly communicate with the WinFrame Print Manager. You do not have to manually configure your printers unless you want to. The procedure for manually configuring client printers is presented below if you want to customize your printer configuration.

Make sure the printer is connected to the Windows 3.1x, Windows 95, or Windows NT client system via an LPT or COM port or that your Windows client has captured the correct network printer to the correct port. Next, on your Windows client, install the Windows 3.1x, Windows 95, or Windows NT 3.5 printer driver for the client system. This sets up and installs a printer queue on your Windows client with the correct printer driver. This printer queue maps to the port to which the printer is connected. Now run the Remote Application Manager and connect to the WinFrame server. Logon and start the Print Manager in the Main group. From the Printer menu, click Create Printer. In the Create Printer dialog box, select the correct printer driver from the drop-down box of printer drivers for the client printer, then select the portID for the Print To field. This port should match the portID that the printer queue on your Windows client is connected to. This is in the form:

CLIENT\LPT1:	For the Windows queue mapped to the client system's local LPT1 port

CLIENT\LPT2:	For the Windows queue mapped to the client system's local LPT2 port

CLIENT\COM1:	For the Windows queue mapped to the client system's local COM1 port

For example if you have an Epson Stylus 300 mapped printer driver installed on your Windows client and it is mapped to the LPT1 port on your Windows client, select CLIENT\LPT1. Once you select the port, the mapped name of the port automatically appears in the Printer Name field. Do NOT change this default Printer Name. This is in the form Clientname#LPTx and is the way WinFrame associates a client printer to a client system. If this is changed, the printer will not install correctly and will not work. If the Share this printer on the network box is checked, the printer will be accessible to other users on the network. Note that the printer will only print for network users when the WinFrame Client is connected to that particular WinFrame host. When the information is correct, click the OK button and enter the Printer Setup information for the printer; the printer queue is created. Use the Permissions option under the Security menu to grant other users access to their client printer. This printer is used as any other standard print queue.

Note

If you are trying to use a local printer, make sure that the client system does not already have a network printer captured or net used to the LPT or COM port, otherwise the print job is routed to the network printer rather than the local printer being used.

If at some point you want to move a printer to a different port on your system or change the printer on that port, you must not only change the port on your Windows client system, you must also recreate the client printer queue on WinFrame. This is because the WinFrame printer queue is associated with the portID on your client system. If you change the printer on it or move the printer driver to another port, you will have to delete the old WinFrame client printer queue and create a new one to match the new printer portID on your client system.

To Setup Client Printers for WinFrame Web Clients

The WinFrame Web Clients allow users to print from their published windows apps back to a Windows client printer. This is achieved by the Autocreation of the Client Windows printer. The web Client does not support printing from dos based applications back to the Windows client printer.

How the Web Client Print Queue is Created

Unlike the regular network client, the web client does not create a Wfcname.ini file on the client workstation. This file is what contains the 'ClientName' which is the Network name that was assigned when the client OS was installed. This name is used in the UNIQUE creation of the client Print Queue name at the Server. For NT and windows 95 and WFW 3.11 workstations, this name will be the network computer name of that machine. For Windows 3.1 there is no computer name because this OS does not have Networking built in. In the latter case or if there is a problem reading the 'ClientName', the username is used instead. The clientname is also set as environment variable in the users' session. For this reason it is equally important to make sure that the Web Client Usernames are unique. The first step to Autocreating the Client printer is to make sure that the check box in User Manager/Config or WinStation Advanced Configuration is checked for 'Connect Client Printers at logon. The next step in the Autocreation of the client printer is identifying the windows printer installed on the client. For the Win32 platform the registry is referenced for the local windows printer name, for the Win16 platform, the Win.ini file. The name(s) of the local Windows printers must match to one in the Server's Printer.inf file. If one is not found then you can update the printer.inf file at the host by following the instructions outlined in the Citrix KB document titled, "Adding Printers to Autocreation List".

Troubleshooting

Check if the Windows application makes use of the Windows GDI to create a print job. If the application uses its own driver to print to an LPTx device, then it may fail because DOS Printing is not a function of the Web Client.

Verify that the application is able to print through the Network client.

Pause the client print queue and make sure a job enters the queue, if it does not, check that printer is the default printer, also check that the application is configured to print to that printer.

Verify the print properties of the client printer.

If multiple users are simultaneously logging into a single WinFrame server with the same username using a web client, printing to client printers will behave erratically. To solve this problem, either print to network printers, or assign an unique username to each user.

Printing is not supported when using the web client to make multiple simultaneous connections from a single client to a single WinFrame server using the same username.

Where to Find Printer Drivers in WinFrame

When installing local, network, and client printers, all the default printer drivers are available on the hard disk. The path for the printer drivers is %SYSTEMROOT% \SYSTEM32\SPOOL\DRIVERS\W32X86. Specify this path when installing a new printer. This is needed only for local and network installations. Client printer installations automatically locate the printer drivers and install themselves. This is done for the remote user who cannot physically place the CD-ROM into the system but needs to access printer drivers for his local client printer installation.

WinFrame uses Windows NT (32-bit) printer drivers, not 16-bit Windows printer drivers. This is because WinFrame is based on Windows NT, which is a protected, secure 32-bit system that only operates with Windows NT printer device drivers. Windows 16-bit printer drivers could compromise system stability and security.

When an application (16-bit or 32-bit) prints under Windows NT, it first creates a GDI Device Surface, selecting the Windows NT 32-bit device driver. The application's drawing commands are translated into the unique data for that printer. This data is then sent to the printer. If the printer is a client printer, the data is sent as raw printer data to the remote Windows printer and no additional translation is done.

If a customer has a new or special printer that only has a 16-bit Windows printer driver, they can not print to this client printer unless it is compatible with a printer that has a driver for Windows NT. This is because, as mentioned before, the 16-bit printer driver can not be loaded for a Windows NT GDI surface.

This is also true for Windows 95. Even though Windows 95 is marketed as a 32-bit system, for compatibility and memory size reasons it uses the Windows 3.11 16-bit GDI device drivers. Windows 95 GDI printer device drivers are not 32-bit Windows NT compatible drivers and will not work.

The end result of this story is that even though we try hard to make it appear that the application is printing to the remote Windows printer, it really has to print locally on the WinFrame host through the Windows NT graphics interfaces, and we then ship the resulting low level printer data to the client to have it appear on the remote printer.

To Setup Network Printers as WinFrame System-Wide Printers

Logon to the WinFrame server as an administrator and start the Print Manager in the Main group. From the Printer menu click Connect to Printer. In the Connect to Printer dialog box, select the network server and the printer to which the WinFrame server should connect and click the OK button.

Note

A network server can be Windows NT Server, another WinFrame server, an OS/2 LAN Manager server, or a Novell NetWare server.

Select the printer driver from the pull-down list and click the OK button. Enter the driver path as shown above and click Continue. In the Printer Setup dialog box, enter the correct information for the printer and click the OK button. This will create the print queue for the printer and make it available to all users on the WinFrame server.

To Change the Default Printer

Start the Printer Manager from the Main group. At the top of the window in the Print Manager's toolbar is a default drop-down box. Select the printer queue that you want to use as your default printer. This becomes the default print queue for all Windows programs that are run by that user and becomes the default for any DOS programs that print to LPT1. (This assumes that no other NET USE has been established for DOS LPT1 for a network printer.)


Migrating WinFrame Client Remote Applications

The new WinFrame Clients use a slightly different format for their remote application list files than the WinFrame Clients that shipped with WinFrame Version 1.5. When you install the WinFrame Clients supplied with WinFrame 1.7 into the same directory as a 1.5 version of the client, the install program automatically converts the remote application list to the new format, preserving your remote applications. The new remote application list format is not backwards compatible with the 1.5 version of the WinFrame Client.

The 1.5 version WinFrame Clients supported serial remote control connections (also called Dial-In connections) for the WinFrame DOS Client only. Windows clients also support Dial-In remote control connections, you may want to use the WinFrame Win16 or Win32 Client in place of the WinFrame DOS Client.

The best method to use to ensure full compatibility is to first install the WinFrame 1.7 DOS Client over the WinFrame 1.5 DOS Client, and then install the WinFrame 1.7 Windows Client over the DOS Client. This ensures that both the DOS client and the Windows client will function properly. If you do not update the DOS client, the DOS client will no longer be able to read the remote application list.

WinFrame Client .INI Files

There are four .INI files used by the WinFrame Client: MODULE.INI, APPSRV.INI, WFCLIENT.INI, and MODEM.INI.

The MODULE.INI and MODEM.INI files contain fixed modem and module information, and should not be modified unless specifically instructed to do so.

The WFCLIENT.INI contains setup defaults; for example, default video color depth and screen resolutions and the default application profile.

The APPSRV.INI file contains the remote application list, and is maintained by the Entry menu of the Remote Application Manager.

In the WinFrame 1.5 version of the WinFrame Client, the active .INI files resided in the WINDOWS directory. In the WinFrame 1.7 version of the WinFrame Client, the active .INI files reside in the directory containing the WinFrame Client. If you install the 1.7 version of the WinFrame Client over a 1.5 version, the 1.7 version of the WinFrame Client continues to use the .INI files in the WINDOWS directory unless you delete those files. The Remote Application Manager will always search the WINDOWS directory first for each .INI file. It is not required that all of the .INI files be in the same directory.

If you want to have several separate WinFrame Client configurations (for example, for different users of the same client PC), you can create user-specific .INI files (APPSRV.INI or WFCLIENT.INI) in the user's WINDOWS directory.


NetBIOS WinStations

NetBIOS WinStations can be configured to use NetBIOS running over Microsoft NetBEUI only. If you are configuring NetBIOS WinStations for use on a network, you must make sure that the network is configured to use NetBIOS over NetBEUI on both the client and the WinFrame server, or remote users trying to connect to the WinFrame host via NetBIOS will get an error message.

The names of all the WinFrame servers configured for NetBIOS WinStations are listed in the WinFrame Server pull-down box when you configure a NetBIOS connection on a WinFrame client.

A special situation occurs in the DOS NetBEUI environment of LAN Manager when using the WinFrame Client over a NetBIOS connection. Because the majority of the data flows in one direction, NetBEUI inserts a 100 millisecond delay after every packet transmitted. This can be disabled by inserting the following line under the [NETBEUI_XIF] heading in the LAN Manager PROTOCOL.INI file:

PIGGYBACKACKS=0

When this parameter is used, no performance degradation between the workstation and server should be noticed.


IPX/SPX WinStations

IPX/SPX WinStations, once configured on a WinFrame server, can be accessed by any of the WinFrame Remote Application Manager clients. The names of all the WinFrame servers configured for IPX/SPX WinStations are listed in the WinFrame Server pull-down box when you configure an IPX/SPX connection on a WinFrame client. You can also address the WinFrame host by its NIC address. Obtain the NIC address by starting a command prompt on the WinFrame host console and typing NET CONFIG SERVER, or with the QUERY SERVER servername utility.

The NET CONFIG SERVER command displays information similar to the following:

Server Name                       \\ZAPHOD

Server Comment

Software version                  Windows NT 3.51

Server is active on               NwlnkNb (00aa0068940f) NwlnkIpx (00aa0068940f) NetBT_E1001 (00aa0068940f) Nbf_E1001 (00aa0068940f)

Server hidden                     No

Maximum Logged On Users           Unlimited

Maximum open files per session    2048

Idle session time (min)           15

The command completed successfully.

The NIC address can be found in the NwlnkIpx(xxxxxxxxxxxx) entry on the Server is active on line. Use this address in the WinFrame client's WinFrame Server box to attach to the WinFrame host.

The QUERY SERVER servername output is more concise, and also gives the network number as well as the NIC address.

If the name of the server or the NIC address of the WinFrame host is correct but you still cannot connect, verify that the frame type being used is the same on both the WinFrame host and WinFrame client. You can set the frame type on the WinFrame client in the client system's NET.CFG file. The WinFrame host's frame type can be set from the Network Control Panel. If you are using Windows for Workgroups on the client side, you may have to manually specify the frame type in the Network Setup program in the Network group for your ODI device driver.


WinFrame in the Enterprise

This section contains instructions on configuring your WinFrame server in an enterprise environment with multiple servers and software platforms.


Configuring a Windows NT 4.0 PDC To Work With WinFrame (FIX40PDC)
Configuring a Windows NT 4.0 PDC To Work With WinFrame

Use the FIX40PDC utility on your WinFrame server if your Primary Domain Controller is a Windows NT 4.0 machine. Windows NT 4.0 has greater security on the Registry, preventing users from reading and corrupting it. One Registry key users need access to is the Citrix-defined Registry key that stores user configuration data. When logged on to the WinFrame machine as a domain administrator, run the FIX40PDC.EXE program with no arguments and the utility will determine whether your PDC is a Windows NT 4.0 machine. If it is, the utility will fix the Registry entry that gives access to the Citrix WinFrame user settings. It will report a message as to what action (if any) it took.

Loading User Configuration Data From a Trusted Domain With a Windows NT 4.0 Primary Domain Controller on a Trusted Domain

If your WinFrame machine is on one domain and loads user configuration from a trusted domain whose Primary Domain Controller is a Windows NT 4.0 machine, you will need to do the following:

In this example, the domain the WinFrame machine is on is PRODUCTION and the trusted domain that the user accounts are on is ACCOUNTS. The WinFrame machine is called WINFRAME1 and the NT 4.0 PDC on the trusted domain is called NT40PDC.

1.	Copy the FIX40PDC.EXE utility from the %SYSTEMROOT%\SYSTEM32 directory of  WINFRAME1 to the WINNT\SYSTEM32 directory on NT40PDC.

2.	From a command prompt on NT40PDC, type FIX40PDC. The utility should print a message stating that WinFrame user settings will now be updated properly on the Windows NT 4.0 Primary Domain Controller.

3.	Reboot NT40PDC for the changes to take effect.


NASI WinStations

The NetWare Asynchronous Services Interface (NASI) provides access to the NASI Connection Service (NCS) offered with NetWare Connect. NetWare Connect uses the server COM ports or third-party multiport serial adapters that provide multiple connections to asynchronous services.

A WinFrame WinStation can be connected to one of these NCS ports. This is done by creating a NASI WinStation. The NASI protocol is built on top of the Internetwork Packet Exchange / Sequenced Packet Exchange (IPX/SPX) protocol.

NCS servers advertise their presence with the NetWare Service Advertising Protocol (SAP). To configure a WinFrame NASI WinStation, both the NWLink IPX/SPX Compatible Transport and the Gateway Service for NetWare must be installed and running on the WinFrame server.

NCS Configuration

NetWare Connect supports enhanced security and modem pooling, and supports many modem types. The security, port, and modem configurations are all handled by NetWare Connect. NCS dial-back is not supported. Refer to the NetWare Connect documentation for more information.

It is recommended that the NCS port be marked as dial-in only. Dial-in ports may use modem pooling and NetWare security, and can be shared by several WinFrame servers. A port that is marked as dial out must be dedicated to a single WinStation and bypasses the NetWare Connect security.

Using a NASI WinStation

Use the WinFrame client to dial in to NetWare Connect. This is a Dial In remote control connection, not a remote node connection. NetWare Connect (depending on the NCS port configuration) prompts you for a username and password and presents a list of WinFrame (or other) servers to connect to.

If you are using the Win16 or Win32 WinFrame clients, make sure you check the "Display Terminal Window When Making Dial-In Connections" check box. This allows the NetWare Connect logon to take place interactively.

NASI WinStation Configuration

Each NASI WinStation may be configured to connect to different NCS ports. Alternatively, multiple WinStations may be connected to one NCS port. This is done to make use of NCS modem pooling, where each NCS port name may map to several physical ports. A WinStation may be configured so that only one NetWare user (or all users) can connect via NCS.

Each WinStation may specify a unique combination of configuration parameters. The administrator may configure the NASI Port Name, Username, Password, Session Type, Session Name, and NetWare File Server (for NetWare bindery access). See Chapter 20, "WinStation Configuration", in the System Guide for information on configuring NASI WinStations.

Diagnostics

A utility called QUERY NACS is provided to assist administrators. This utility shows all NCS ports available on the network along with status information on each port. The username and password used to query the NCS servers may be specified to the utility. The syntax of the command is:

QUERY NACS [/USER:username] [/PASSWORD:password] [/SERVER:fileserver] [/?]

Refer to Appendix A, "WinFrame Command Reference" of the System Guide for more information about the QUERY NACS command.


Configuring WinFrame for Dialin Clients

This section contains the following topics:

Asynchronous Connections

Modems Supported by WinFrame

Modem Definitions for RAS and ICA Dial-In on WinFrame

Configuring RAS Clients

Configuring RAS Clients

Domain Accounts vs. Local Accounts and WinFrame RAS

DOS/LAN Manager RAS Client

Microsoft Windows for Workgroups 3.11 RAS Client

Microsoft Windows 95 Dial-Up Networking

Microsoft Windows NT 3.5 Remote Access Client

Funk SoftWare WanderLink PPP

Shiva PPP 3.5

Stampede Remote Office PPP

Trumpet Winsock

See Also:

Adding Support for New Modems in the WinFrame Solutions Guide


Asynchronous Connections

PCs use serial ports for asynchronous connections. Most PCs contain two serial ports, COM1 and COM2. Using a multiport asynchronous adapter, a PC can be configured with as many as 256 serial ports. These ports are most often used for modems, but can also be used for serial printer connections, null modems, and mice. A null modem is a special cable used to connect two computers across a distance of 50 feet or less. Internal modems contain their own high-speed serial port circuitry and essentially add another serial port to the computer.

Note

The most common problem with serial connections is using the wrong type of cable. See Appendix D, "Cabling", in the Remote Access Services manual for proper pin connection diagrams.

To use a modem connection between your WinFrame server and client PCs, both will need serial ports capable of handling high baud rates (in excess of 9600 baud). If you plan on having multiple PCs dial-in to your WinFrame server, you should use a multiport serial adapter. You should also use high-speed communications ports on your client PCs if they will be using external modems.

The burden placed on a PC's processor by an adapter is often inversely proportional to the maximum data rate of the adapter. Most high-speed interfaces, such as LAN cards, use hardware that moves large blocks of data with virtually no CPU intervention. Because the interfaces are so fast, high-speed hardware on the LAN card is a requirement for the PC to handle the data rate without errors.

Serial interfaces, on the other hand, operate at relatively slow speeds and often can be serviced directly by the PC's CPU, eliminating the need for high-speed hardware on the adapter. Until recently, most PCs were built with simple 8250 or 16450 serial controller chips (or UARTs). With these chips, CPU interrupts are generated each time a character of data is sent or received, reducing the amount of time the CPU could devote to other tasks. The overhead incurred is acceptable at low baud rates (9600 baud or less); however, higher baud rates impose an unacceptable burden on the system.

When the CPU cannot keep up with the serial port, a PC experiences data overruns, where a new character arrives before the CPU has processed the previous one. The WinFrame client transmits data in blocks known as frames. If a character is lost from a frame due to a data overrun, the entire packet is resent, usually not until a lengthy timeout interval has expired. If the processor is much too slow, overruns occur in almost every packet and the remote access connection fails. If the processor speed falls short, complex interactions between the serial port, the CPU, memory managers, and other system software may cause intermittent overruns. In this case, the remote access connection may seem to work but have intermittent problems such as sudden drops in speed, spurious loss of connections, and so on.

Such inconsistent behavior is one of the most annoying problems faced by both end users and support personnel. In addition to the differences in performance between serial controller chips, serial performance may also vary by operating system. For example, Microsoft Windows and Windows for Workgroups adds an extra layer of software for handling CPU interrupts, forcing the processor to execute extra instructions each time it is interrupted.

On the other hand, DOS, as the simplest operating system, requires the least extra processing by the CPU each time it is interrupted. Therefore, maximum serial port throughput for a given hardware configuration usually occurs when running DOS. However, the simplicity of DOS may also lead to less consistency because it provides no context for handling CPU interrupts. Some low-level DOS programs, particularly memory managers, may disable interrupts for extended periods of time. During the intervals when interrupts are disabled, characters may be lost because the CPU is not aware that it must service them. The need to support higher and higher serial port speeds has led to the use of more sophisticated serial controller chips. Three such solutions are listed below, in order of their data rate capabilities.

1.	The first solution is to install a serial communications board with a 16550A Universal Asynchronous Receiver/Transmitter (UART) chip. A 16550A UART can receive or transmit up to 16 characters without processor intervention; therefore, the processor is interrupted less frequently and moves more data with less effort. Adapters utilizing a 16550A UART represent a good solution for PC clients utilizing a 14,400 bps modem. Most PCMCIA modem cards contain 16550A UARTs. These adapters use the standard COM port drivers supplied with the operating system (DOS, Windows, Windows for Workgroups, Windows 95, or Windows NT).

2.	The next solution is to install a Hayes ESP Communications Accelerator, or similar product, that allows you to send and receive data at speeds up to 115,200 bps. The ESP Communications Accelerator is a non-intelligent adapter that provides automatic flow control and two 1024-byte buffers versus the 16550A's 16-byte buffer. In addition, it is fully backward compatible with conventional 16450 and 16550A serial ports. The Hayes ESP Communications Accelerator is a good choice for connecting modems running above 14,400 bps, such as the Hayes 28,800 Optima modem, that has a maximum data rate with compression of up to 115,200 bps. The adapter must support either a standard COM port interface or an INT14 interface to be compatible with WinFrame DOS and Win16 Client, or have a Windows 95 or Windows NT device driver to be compatible with the WinFrame Win32 client.

3.	The last, and most expensive, solution is to install an intelligent serial port card such as the Digi AccelePort 8r. This card has its own on-board processor (an 32-bit 16MHz IDT 3041 RISC processor) and 128KB of dual-ported RAM, which relieves the processor of the burden of managing the serial ports. The Digi intelligent adapter or an equivalent intelligent adapter will provide the highest remote access performance. The adapter must support either a standard COM port interface or an INT14 interface to be compatible with the WinFrame DOS and Win16 clients, or have a Windows 95 or Windows NT device driver to be compatible with the WinFrame Win32 client.


Modems Supported by WinFrame

The WinFrame server supports all modems supported by Windows NT 3.51 Remote Access Services. The Hardware Compatibility List contains a listing of these modems. Additionally, WinFrame supports the following modems as async WinStations through definitions in the CTXMODEM.INF file. These modems have CTX at the end of the name.

See Adding Support for New Modems in the WinFrame Solutions Guide for information on adding support for new modems.

Apex Data PCMCIA Data/Fax - CTX

AT&T Comsphere 3800 Serie - CTX

AT&T DataPort 14.4/FAX Mo - CTX

ATI 14400 ETC-Express PCM - CTX

ATI 14400 ETC-I/E Fax-Mod - CTX

ATI 2400etc/e - CTX

Black Box 325 Modem/Modem - CTX

Boca Research M1440 14.4K - CTX

Boca Research V.FAST 28.8 - CTX

Bullet E9696m V.32 - CTX

Cardinal 9600 V.42bis Ext - CTX

Compaq 14.4 PCMCIA Data + - CTX

Compaq Enhanced 9600 Data - CTX

Compaq PCMCIA 14.4 Data+F - CTX

Compaq PCMCIA SPEEDPAQ 14 - CTX

Compaq SPEEDPAQ 144/P PCM - CTX

Compaq SPEEDPAQ 192 PCMCI - CTX

Dallas Fax Modem - CTX

Encore 1200 HB Integral M - CTX

Entre 2400X - CTX

Evercom 96 Modem - CTX

Generic 2400 Baud Modem - CTX

Generic 9600 Baud Modem - CTX

GVC 14400bps V.42 Modem - CTX

GVC 28800bps V.42 Fax Mod - CTX

GVC 9600bps V.42 Modem - CTX

Hayes ACCURA 144 + FAX144 - CTX

Hayes ACCURA 288 V.FC + F - CTX

Hayes Smartmodem 1200 - CTX

Hayes Smartmodem 2400 - CTX

Hayes Smartmodem OPTIMA 2 - CTX

Hayes Smartmodem OPTIMA 9 - CTX

Hayes V-series Smartmodem - CTX

Hayes V-Series ULTRA Smar - CTX

IBM High Speed Internal/P - CTX

Intel 14.4ex Modem - CTX

Intel PCMCIA Faxmodem - CTX

Maxwell Modem 2400V from  - CTX

Megahertz 14.4 PCMCIA Dat - CTX

Megahertz 14.4/14.4 FAX/M - CTX

Megahertz XJACK 28.8 PCMC - CTX

Microcom DeskPort FAST 28 - CTX

Microcom DeskPort FAST ES - CTX

Microcom QX/4232hs Modem - CTX

Microcom TravelCard FAST  - CTX

Microdyne Access Modem (N - CTX

Motorola Codex 3220 Modem - CTX

Motorola Codex 326X Modem - CTX

Motorola Life Style V.34  - CTX

Motorola Power Series V.3 - CTX

Motorola UDS CELLect PCMC - CTX

MultiTech LT PCMCIA MT143 - CTX

MultiTech LT PCMCIA MT283 - CTX

MultiTech MT1432BR/MT932B - CTX

MultiTech MT1432MR/MRI/MR - CTX

MultiTech MT1432MU - CTX

MultiTech MT1932BL/ZDX - CTX

MultiTech MT2834BA - CTX

MultiTech MT2834ZDX 28.8  - CTX

MultiTech MultiModem224 - CTX

MultiTech MultiModemV32 - CTX

Octocom OSI 8596 and 8596 - CTX

Okidata Okitel 2400 - CTX

PIICEON PCMCIA Dispatcher - CTX

Practical Modem 2400 SA - CTX

Practical Peripherals 144 - CTX

Practical Peripherals 960 - CTX

Practical PractiCARD 144  - CTX

QuikKomm Modem 2400 - CTX

Racal-Datacom ALM 3223 - CTX

Racal-Datacom ALM 3226 Ce - CTX

Racal-Datacom ALM 3239 - CTX

Racal-Datacom RMD 3232 Mo - CTX

Scout PCMCIA V.32 14,400  - CTX

Scout ScoutPlus V.32bis 1 - CTX

Spartan 9600 MNP5/V.42 - CTX

Supra 14.4 Data/Fax Modem - CTX

Supra 28.8 Data/Fax Modem - CTX

Telebit QBlazer Plus - CTX

Telebit T1600 - CTX

Telebit T2000 and TrailBl - CTX

Telenetics TC 1442L/1442  - CTX

Toshiba Noteworthy T144NW - CTX

TWINCOM 144/DF Modem - CTX

UDS Fast Talk V.32/42B - CTX

UDS FasTalk II  14.4 V.32 - CTX

UDS FastTalk 32bx - CTX

UDS V.3229/V.3229L Modem - CTX

Universal Data Systems V. - CTX

USRobotics COURIER 2400 - CTX

USRobotics COURIER Dual S - CTX

USRobotics COURIER HST - CTX

USRobotics COURIER HST Du - CTX

USRobotics Dual Analog Mo - CTX

USRobotics Sportster 14.4 - CTX

USRobotics Sportster 28.8 - CTX

USRobotics Sportster 9600 - CTX

USRobotics WorldPort 14.4 - CTX

ViVa Modem 24 - CTX

ZOOM 14400 V.32bis FaxMod - CTX

ZOOM 28800 V.34X FaxModem - CTX

Zypcom Z32b-SX Series Dat - CTX

Zypcom Z32t-SX Series Dat - CTX

Zoltrix288 RC288Dpi Rev 04BC

Pract Per PC288LCD V.34

Pract Perf PM288MT II V.34


Modem Definitions for RAS and Async Dialin on WinFrame

See Also:

RAS Troubleshooting

Modems Supported by WinFrame

Adding Support for New Modems in the WinFrame Solutions Guide

Appendix E of the Remote Access Service manual

The %SYSTEMROOT%\SYSTEM32\RAS directory contains three modem configuration files: MODEM.INF, CTXMODEM.INF, and USRMODEM.INF. These files contain modem definitions containing the command and response strings each modem needs for correct operation. Modems defined in MODEM.INF are used by RAS and async WinStations. Modems defined in CTXMODEM.INF and USRMODEM.INF can only be used by async WinStations.

To add or modify a modem definition for RAS connections, edit MODEM.INF. To modify the definition for a modem with CTX at the end of the name, edit CTXMODEM.INF. To add a new modem for async WinStations only, add the definition to USRMODEM.INF. This makes it easier to diagnose problems with the INF file.

The following is an excerpt from the Microsoft Knowledge Base from the Developer's Network CD-ROM regarding editing the MODEM.INF file.

SUMMARY

This article contains information to help you modify sections in MODEMS.INF to accommodate modems not handled by standard means. MODEMS.INF lists the expected responses for each modem type in a section using the form seen in this example:

[CODEX_2264.INIT.RESPONSE]

OK=*cr*lfOK*cr*lf

ERROR=*cr*lfERROR*cr*lf

Defaults are listed at the beginning of the file and exceptions are listed in each modem's section, with .RESPONSE in the section header. Modem commands depend on the modem (not all are 100 percent Hayes command set compatible) but RAS does not understand BUSY, etc., so you must modify MODEMS.INF. The COMDEV.INI file contains the name of the modem selected and points RAS to the MODEMS.INF file for the appropriate strings.

E1 normally indicates echo validated but in some instances it means enable command state character echo, which is not the same thing as validating the echo. (This can be done in the script file but the modem performs no validation, it simply echoes the command.)

The setting S3=13 (CR) is a default. Some modems forget to echo the (CR) character. To find out if a program is waiting for the complete echo of the string sent to the modem, check the section of the MODEMS.INF file detailing your modem. See what the program is waiting for, then edit the MODEMS.INF file (use any text editor) to make it compatible with your modem.

When you enter a Dial command (ATDT), some modems send a crlf or crlfOKcrlf message before dialing and sending the expected answer. Here is how to deal with these modems:

If you use ATQ0V1 (return result codes and return result codes in verbose form), you get the message CONNECT. If you use ATX3 or ATX4 you also get BUSY. Wait until you get these results and don't be concerned if you get something else before. CONNECT or BUSY are always the last results before you can enter a new command. If this does not work, you might have a timing problem. Check to see if you have to dial BLIND or increase the value of S7. The best testing technique is to set S7 to the highest possible value listed in your modem handbook.

Copyright Microsoft Corporation 1994.


Configuring RAS Clients

See Also:

Domain Accounts vs. Local Accounts and WinFrame RAS

DOS/LAN Manager RAS Client

Microsoft Windows 95 Dial-Up Networking

Microsoft Windows for Workgroups 3.11 RAS Client

Microsoft Windows NT 3.5 Remote Access Client

Funk SoftWare WanderLink PPP

Shiva PPP 3.5

Stampede Remote Office PPP

Trumpet Winsock

Introduction

This is a quick start guide to setting up remote node support on the WinFrame server. It is intended to help an administrator configure the WinFrame server. The Remote Access Service (RAS) provides the remote node connectivity service on WinFrame for remote computers. This allows remote users who are connected over an async connection to appear as nodes on the network. Users can run applications installed on their local hard disk that make use of the network. They can also run the WinFrame Remote Application Manager to gain access to WinFrame servers on the network. With access to a WinFrame server, they can use a WinFrame remote control session where they can run any application over the network async connection by establishing a network remote control session. If you have not already determined whether you want RAS users to use domain accounts or local accounts, read Domain Accounts vs. Local Accounts and WinFrame RAS before continuing.

Note

For information on how to configure and setup remote control services, see Chapter 20, "WinStation Configuration," in the System Administrator's Guide.

RAS Quick Setup on WinFrame

WinFrame's Remote Access Service (RAS) supports a wide variety of remote node clients. Supported remote node clients come in two types. The first is a client that supports Microsoft's RAS protocol running with NetBEUI. This includes Microsoft's LAN Manager RAS client and Microsoft's Windows for Workgroups 3.11 RAS client. These clients support only the NetBEUI protocol and, therefore, only have NetBIOS access. The WinFrame server, however, can be set up as an IPX or IP gateway to provide these clients with some IPX and IP access. For example, with the NetWare Gateway Service, they can net use drives from a Novell file server as they would a WinFrame or Windows NT system. These clients do not have true access to IPX and IP, however, and are therefore limited.

The second type of remote node client supported is Point-to-Point Protocol (PPP) clients. These are now the standard in remote node connectivity. Examples of clients like these are Microsoft Windows 95 Dial-Up Networking and Microsoft Windows NT Remote Access client. Because PPP is a standard, a wide variety of third party PPP clients are also available for use with WinFrame Remote Access Service. These clients can support NetBEUI, IPX, IP, and NetBIOS on any of these network protocols (depending on the particular protocols supported by the PPP client). Microsoft Windows 95 Dial-Up Networking and NT Remote Access clients support NetBEUI, IPX, IP, and NetBIOS on any of these protocols. Third-party PPP clients typically support IPX and/or IP access. PPP remote node connectivity allows the remote client PC the freedom to use any standard network protocol, allowing any type of network application to run on the remote client.

Remote node connectivity gives the client system access to a remote network and allows the system to access the network as it would if it were local. The remote client can logon to the network, make use of available of file and print servers, and run network applications. This kind of remote node connectivity is perfect for providing remote access to WinFrame, Novell, and Microsoft NT network file servers as well as remote access to network WinFrame remote control services and UNIX. Applications that use the network to communicate can exist on the remote user's hard disk and can communicate as normal over the remote node connection. The following section is a quick setup for installing RAS on WinFrame. It sets up RAS for the most common situations for the widest variety of remote node clients. For more specific information on WinFrame Remote Access Service and how to configure it, see the Remote Access Service manual.

To install RAS on WinFrame

Note

RAS supports up to 256 remote node connections. This requires the use of a multiport serial adapter to provide the COM ports to which RAS configured modems are connected. Without a multiport serial adapter, RAS is restricted to only two remote node connections: COM1 and COM2, assuming that one of these is not being used by a mouse. Even so, the COM1 and COM2 ports must have a 16550 UART installed in order to use baud rates above 19200 or use modems above 9600 baud. Intelligent multiport async adapters not only provide more async connections but are far faster and support baud rates of 115200 and above, as well as freeing up the system CPU from unwanted async interrupts. These are recommended for use with RAS over common serial ports. The multiport adapter should be installed and the modems connected before installing RAS because RAS must access these ports and modems when it is being configured.

1.	Load the WinFrame CD-ROM into your system's CD-ROM drive.

2.	Logon as an administrator at the WinFrame console. From the Main program group, start the Control Panel and select the Network icon to open up the network settings dialog box. Select Add Software and Remote Access Service from the list, then click the Continue button.

3.	The installation script prompts for the path of the distribution files. Enter the system's CD-ROM drive letter followed by the \I386 path and click on the Continue button. The RAS files are installed onto the WinFrame system.

4.	After the file copy is completed, the Remote Access Setup dialog box is displayed. Select the port to be used and the modem type or null modem (direct connection) for each connection to be created. At least one connection must be created.

5.	Click the Add button to add more connections or the Remove button to delete them. If you have multiple connections that are using the same type of modem, create the first one, select it, and then use the Clone button to make the rest. Click the Network button when done.

6.	In the network configuration panel, set the Encryption settings to either Allow any Authentication Including Clear Text (PAP) or Require Encrypted Authentication (CHAP). Do not set it to Microsoft Encryption unless you know you are only going to use Microsoft RAS clients. If using a third party PPP client, you must select one of the first two encryption settings. Select the network protocols you want the remote node clients to use and then click the Configure button next to each protocol. The following steps explain how to configure each of the network protocol configuration panels.

7.	RAS setup asks if you want NetBEUI clients to have access to the entire network or just that WinFrame system. Make your selection and click the OK button.

8.	At the TCP/IP Configuration dialog box choose whether or not to allow users access to the entire network or just this WinFrame server. Next, choose between using a DHCP server or using a static address pool. If you use a static address pool, enter the range of addresses to use and any address ranges within it that should be excluded. Make sure Allow Remote Clients to Request a Predetermined IP Address is selected and click the OK button.

9.	At the IPX Configuration dialog choose whether or not to allow remote users to have IPX access only to this WinFrame server or to the entire network. Make sure Allow remote clients to request IPX node number is selected and then click OK to continue.

10. When done, click the OK button on the Network Configuration dialog and then click the Continue button on the Remote Access Setup dialog. You are asked for the path of the RAS files again. Enter the path of the CD-ROM \I386 directory or the diskette drive and allow the installation to finish. Click OK to return to the Network Settings dialog. Click OK in the Network Settings dialog to finish the install. See below for instructions on assigning RAS permissions.

11. The system must be rebooted. Click the Restart Now button to reboot the system and load RAS.

Granting RAS Permissions to WinFrame Users

After rebooting, logon as an administrator and start the Remote Access Administrator in the RAS program group. The RAS server starts and lists your connections. Select Permissions from the Users menu and grant RAS access to all the users who are allowed to use RAS. You can grant RAS access to local users and to network domain users. There are two ways to set up usernames for RAS access authentication: one profile per user or one master profile for all users.

The first method involves creating a user profile for each remote user on each WinFrame server accessed by remote users using RAS. This is the more secure method but requires the system administrator to maintain many user profiles.

The second method requires you to define one master profile that is used by all remote clients to establish a remote node session. Once the remote node connection is made, users can start a remote control session on the WinFrame server using their own usernames, which can be local or domain usernames. This method is less secure because all remote node users logon with the same remote node username.

RAS permissions can be granted to local users or domain users. Microsoft remote access clients such as Windows 95 Dial-Up Networking, Windows NT Remote Access client, Windows for Workgroups 3.11 RAS client, or LAN Manager RAS client can use either type just by entering the username, password, and domain in the usual manner. Third-party PPP clients can use local users as normal but domain usernames must be prefixed with domain/ where domain is the domain name. For example, if the PPP client is using a locally configured user, you just enter the username and password. If the PPP client is using a domain user, you need to enter the domain\username and password for the user.

To configure a domain user for RAS access, start the Remote Access Administrator. Choose Select Domain or Server from the Server pull-down menu. Type the name of the network domain the users will logon from into the Domain text box. Select OK when done. Select the Permissions option from the Users menu. The list of network users on that domain appears. Grant the users RAS access as required.

To configure a local user on a WinFrame server for RAS access, start the Remote Access Administrator. Choose Select Domain or Server from the Server pull-down menu. Type \\computername, where computername is the name of the WinFrame RAS server, into the Domain text box. Select OK when done. Select the Permissions option from the Users menu. The list of local users configured on that WinFrame server appears. Grant the users RAS access as required.

Note

The above clients can be restricted to use local user names for RAS access and are not required to use domain users. Domain user RAS access simply allows for easier configuration if multiple WinFrame RAS servers exist on the network. If local users are used, they must be configured on every WinFrame RAS server that the remote users may access.

Troubleshooting

Modem Troubleshooting on RAS

If you are having problems with modems on RAS and want to turn on RAS logging, you may start REGEDT32 and set the following subkey to 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rasman\parameters

If the value does not exist, choose Add Value from the Edit menu and enter these values for the following fields.

Value Name: logging

Data Type: REG_DWORD

String: 1

At this point you must stop and start the RAS server to activate the change and start the logging to the %SYSTEMROOT%\SYSTEM32\RAS \DEVICE.LOG file. You can stop and start the RAS server from the RAS Admin program in the RAS group that was created when you installed the RAS server in steps 1 through 11 above. Once this is done, you can inspect DEVICE.LOG to help diagnose problems. To disable RAS logging, set the value for the subkey back to zero.

PPP Troubleshooting on RAS

If you are having problems getting a PPP client to connect to the RAS service on the WinFrame host, you can turn on PPP logging by starting REGEDT32 and setting the following subkey to 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rasman\PPP\Logging

If the value does not exist, choose Add Value from the Edit menu and enter these values for the following fields.

Value Name: Logging

Data Type: REG_DWORD

String: 1

At this point you must stop and start the RAS server to activate the change and start the logging to the %SYSTEMROOT%\SYSTEM32\RAS\PPP.LOG file. You can stop and start the RAS server from the RAS Admin program in the RAS group that was created when you installed the RAS server in steps 1 through 11 above. Once this is done, you can inspect PPP.LOG to help diagnose problems with establishing PPP connections. To disable PPP logging, set the value for the subkey back to zero.

Why do the RAS modems constantly recycle themselves and refuse to stay on-line?

First turn on RAS logging. Let the modem cycle a few times and then examine the DEVICE.LOG file. You may find that the initialization string being used is causing the modem to return an error that causes RAS to try to reset the modem forever. RAS is not smart enough to recognize error codes from the modem and stop or send a popup to the console. If the initialization string is the problem, verify that you selected the correct modem when installing the RAS server software on the WinFrame server. If this is correct, modify the %SYSTEMROOT%\SYSTEM32\RAS\MODEM.INF file that RAS uses and change the initialization string to remove the invalid command. Make sure you make a backup copy of the MODEM.INF file before altering it. You can stop the RAS server and use the Windows Terminal program to echo out the AT commands the MODEM.INF file is using to see which command is causing the error. You can then remove the command from the string or replace the string with a more appropriate one (see the modem's documentation for appropriate commands).

If the error is not due to the initialization string, try stopping and restarting the RAS server on the WinFrame server. If that does not work, power off the modem, wait at least one minute, and then power it back on. You can also try sending an AT&F command and then an ATW command to write the factory defaults back to the modem. If all else fails, power down the entire system and do a cold boot.

When I logon at the console, I can see the network and logon to Novell file servers with no problem. When a RAS user connects remotely, the user gets an IPX and IP address but cannot see any Novell file servers. Why is this?

The problem may be that you have your WinFrame server connected to an intelligent 10 Base-T hub. Some 10 Base-T hubs allow only one network address per port. With WinFrame, the server itself is the first network address and every user thereafter has a unique address. In this case, the WinFrame server gets the port and any RAS connections get ignored on the network. To fix this, you can either use a 10 Base-T hub that allows multiple network addresses per port or change the WinFrame server network connection to 10 Base-2 (coax) Ethernet cable. Another solution is to set the RAS IPX settings to assign the same network IPX address to all clients. Then set your clients to use server assigned IPX addresses rather than client assigned IPX addresses.

Note

The Microsoft Developer Network CD-ROMs provide various tips and hints for RAS that you may find useful.

See Also:

How do I configure my multiport serial adapter?

How do I set up WinFrame to run over an ISDN connection?


Domain Logons vs Local Logons to WinFrame RAS
Domain Accounts vs. Local Accounts and WinFrame RAS

Two types of logons can be used with remote node clients. The first type is local to the WinFrame server. This is a user logon that has been configured for a particular WinFrame server. Once configured, this logon can be used for either remote node logons or remote control logons, but only on that particular WinFrame server. The second type of logon is called a domain logon. This logon is configured on a network domain controller, where the domain server is either a WinFrame or Windows NT Server. Once a user is configured on a domain controller, the user can logon via remote node/remote control to any WinFrame server on the network. A domain logon is far more flexible and easier to administer. It also gives users a single user profile that can be used anywhere on the network, which makes it easier for users as well. If you want to restrict users from logging into a particular WinFrame server, you can deny them access from the User Manager for Domains utility. See Creating User Accounts on WinFrame for information on creating user accounts. See the Remote Access Services manual for more information on RAS.

Granting RAS/Remote Node access to local users

1.	When a local user logon is created for a WinFrame server, the user has remote control access across a network but does not yet have dial-in RAS/Remote Node access to that WinFrame server. Logon to the WinFrame console as an administrator and run the Remote Access Administrator.

2.	In the Remote Access Administrator, click on the Select Domain or Server option from the Server menu. When the Select Domain dialog box appears, type \\wfservername, where wfservername is the name of the WinFrame server the user will dial for remote node access. Click the OK button in the Select Domain dialog box to set the Remote Access Administrator to that WinFrame server.

3.	Select the Permissions option from the Users menu. This now shows the local user logons configured for that particular WinFrame server. From here users are granted RAS access. Grant RAS access to the users who will be dialing-in and then click the OK button to save the changes.

4.	Local users now have remote node access to the WinFrame server and can dial-in via RAS.

Dialing in to WinFrame RAS with a local user account

1.	Various remote node utilities may be used to connect to the WinFrame RAS server. These include Windows 95 Dial-Up Networking and Windows NT Remote Access clients, as well as all Microsoft RAS clients. For all of these, when creating an entry, type the user name and password of the local user logon created to logon to the WinFrame server via RAS.

2.	You may now dial in and connect. The local user logon will be authenticated and remote node access granted. The remote client will be connected to the remote network. The remote user can then run the Remote Application Manager to create a remote control session on the WinFrame server.

Granting RAS/Remote Node access to domain users

1.	Once a domain user logon is created for a network domain, the user has remote control access across a network but does not yet have dial in RAS/Remote Node access to any WinFrame servers on the network domain. To do this, logon to any WinFrame console and run the Remote Access Administrator.

2.	In the Remote Access Administrator, click on the Select Domain or Server option from the Server menu. When the Select Domain dialog box appears, select the name of the network domain to which you want to grant RAS access. Click the OK button in the Select Domain dialog to set the Remote Access Administrator to that network domain.

3.	Next select the Permissions option from the Users menu. This will show the domain user logons. From here you can grant the users RAS access. Grant RAS access to the users who will be dialing-in and then click the OK button to save the changes.

4.	Domain users now have remote node access to any WinFrame server on the network domain and can dial in using RAS.

Dialing in to WinFrame RAS with a domain user account

1.	Various remote node utilities may be used to connect to the WinFrame RAS server. These include Windows 95 Dial-Up Networking and Windows NT Remote Access clients, as well as all Microsoft RAS clients. If you are using a Microsoft client, such as any Microsoft RAS client, Windows 95 Dial-Up Networking, or the Windows NT Remote Access client, enter the user name, domain name, and user password for the user. If you are using a third party PPP client, you will not have a domain field to enter the domain name when creating your entry. You must, therefore, enter the domain name along with the user name in the username field. To do this, create your entry on your remote node client and type: domainname\username for the Username and type the password into the password field. Domainname is the name of the network domain, and username is the name of the domain user. These should be separated by a backward slash. When WinFrame RAS sees the domain name in front of the user name, it recognizes the user as a domain user and checks with the domain RAS access to determine whether or not the user is valid.

2.	You can now dial in to any WinFrame server on the remote network domain. The domain user logon is authenticated and remote node access granted. The remote client is connected to the remote network. The remote user can run the Remote Application Manager to create a remote control session on the WinFrame server.


DOS/LAN Manager RAS Client

See Also:

Configuring RAS Clients

Overview

The DOS/LAN Manager RAS Client provides DOS and Windows 3.1 with a connection to a RAS server running on a WinFrame server. It provides only the NetBEUI protocol and supports only NetBIOS. This allows the DOS or 16-bit Windows clients to connect via NetBIOS to the WinFrame server as well as allowing the remote Windows or DOS client to be another node on the WinFrame server's local network.

Requirements

Hardware Requirements:

286 (DOS) or 386 (Windows) or higher

2MB RAM for DOS, 8MB RAM for Windows 3.1 or higher

Hard Disk

Software Requirements:

DOS or Windows 3.1 or Windows for Workgroups 3.11 (for Windows access)

Installation

A RAS setup consists of two parts. The RAS server must first be installed on the WinFrame server and the RAS client must be installed on the user's client system. The following section describes how to install and set up the DOS RAS client and the supporting NetBIOS protocol stack on the user's client system. To set up and install RAS on a WinFrame server, see the WinFrame Remote Access Services manual or review Configuring RAS Clients.

To Install the DOS RAS client on a DOS system for DOS use only

1.	Create the DOS client RAS diskettes from the WinFrame CD-ROM:

A.	Load the WinFrame CD-ROM into the CD-ROM drive.

B.	Logon to the WinFrame console as an administrator and start a DOS session. Change to the CD-ROM drive. Change into the \CLIENTS\MSCLIENT\DISKS\DISK1 (CD \CLIENTS\MSCLIENT\DISKS\DISK1) directory. Copy the entire contents of that directory and any subdirectories onto a blank formatted 3.5 inch diskette (XCOPY /S *.* A:). Label the disk Network Client Disk1.

C.	Change into the \CLIENTS\MSCLIENT\DISKS\DISK2 directory. Copy the entire contents of that directory and any subdirectories onto a blank formatted 3.5-inch diskette, (XCOPY /S *.* A:). Label the disk as Network Client Disk2.

D.	 Change into the \CLIENTS\RAS\DISKS\DISK1 directory. Copy the entire contents of that directory and any subdirectories onto a third blank formatted 3.5-inch diskette (XCOPY /S *.* A:). Label this disk RAS.

2.	On a standard DOS client with no other network software installed, place the Network Client Disk1 into diskette drive A. Change to drive A, type SETUP, and select the following configuration options:

A.	Select the network adapter MS-DOS Remote Access MAC Driver.

B.	Change your username to a valid domain or local username.

C.	Set the Computer Name to whatever name you would like.

D.	Set the WorkGroup Name to the workgroup the user will use and the Domain Name to the Domain to be used. These correspond to the workgroup, domain, and users already configured on the local WinFrame system or on the workgroup and domain that the WinFrame system uses.

E.	Change the Setup Options to Full Redirector, Run Network Client, and Logon to Domain (if you want).

F.	Select The Listed Options are Correct to save your settings and complete the RAS client installation. At the end of the install press ENTER to reboot or F3 to exit to DOS. Change into the newly created Network Client directory on your hard drive.

3.	From the newly created Network Client directory on the hard disk, type RASCOPY. This will start a batch file that will ask you to insert the first RAS disk. Make sure the RAS disk is in drive A and then press ENTER. When the files are copied, the batch file will ask for the second RAS disk, which does not exist  a RAS installation oversight. All the needed files are on the one RAS disk, so just press ENTER a second time and the rest of the files will copy over.

4.	There will now be a \RAS directory under the Network Client directory. Change into that \RAS directory and run the SETUP program. This will allow you to set up your COM port and modem type for the DOS client. Save your settings and exit. Reboot your system for the settings to take effect.

Note

Connection speeds are limited to 9600 baud when using modem connections with the DOS RAS Client.

Proceed to the Usage section of this document.

To Install the LAN Manager RAS client on a DOS/Windows system

1.	Create the LAN Manager for DOS and RAS disks from the WinFrame CD-ROM.

A.	Load the WinFrame CD-ROM into the CD-ROM drive.

B.	Logon to the WinFrame console as an administrator and from the Run command in the File menu, type NCADMIN and click the OK button to start the Network Client Administrator. Once started, select Make Installation Disk Set and click Continue. In the next panel, select the Existing Path radio button, and in the text box above, enter the path x:\CLIENTS, where x is the drive letter of the CD-ROM, then click the OK button.

Note

Make sure you have five formatted floppies before continuing steps C and D.

C.	Once in the Make Installation Disk Set dialog, select the your diskette drive and the LAN Manager for DOS entry. Insert a diskette in your diskette drive and click OK to start creating the LAN Manager for DOS floppies. Continue to insert floppies until all four of the LAN Manager for DOS disks are created. Label the floppies LAN Manager Setup, Drivers 1, Drivers 2, and NetWare Connectivity.

D.	Next, select the RAS 1.1a Client entry and your diskette drive. Insert a diskette into your diskette drive and click OK to start creating the RAS diskette. When done, exit the Network Client Administrator. Label the diskette RAS 1.1a.

2.	On a standard DOS client, with no other network software installed, place the LAN Manager Setup disk into diskette drive A. Change to drive A, type SETUP, and select the following configuration options:

A.	Select LAN Manager Enhanced installation.

B.	Select the network adapter No Driver. On the Workstation Configuration panel, select OK and leave the configurations Empty.

C.	On the Workstation Settings panel, enter a name for your computer, a username on the domain or WinFrame server, and the domain name if needed. Select OK when done.

D.	If to be used with Windows, select Yes to run LAN Manager with Windows.

E.	When done, select Save to save your configuration and finish the LAN Manager install.

3.	When done installing LAN Manager, place the RAS 1.1a disk into drive A and type LMRSETUP for the LAN Manager RAS set up.

4.	There will now be a \RAS directory under the Network Client directory. Change into that \RAS directory and run the SETUP program. This allows you to set up your COM port and modem type for the DOS client. When done, save and exit. Reboot your system.

Note

Connection speeds are limited to 9600 baud when using modem connections with the LAN Manager RAS Client.

Usage

Verify that the system boots up and loads all the RAS drivers without error. When you reach the DOS command prompt, type RASPHONE. This will load the RAS dialing client. From the menu, create a new entry that contains the COM port and modem you created earlier and the phone number. Select the new entry and press ENTER to dial. The RAS client will ask you for your username and password. Enter a valid local or domain username and password and press ENTER. The RAS client will dial-out and connect to the RAS server on the WinFrame system. After connecting, the RAS server will validate the user and you will get a message that you are now connected to the RAS server. At this point you can exit RASPHONE.

At the DOS command prompt, type NET VIEW \\computername, where computername is the name of the WinFrame server. This should show you any network shares that the WinFrame server has (if any) and will verify that you are connected. At this point you can start Windows 3.1 if you want.

The user may now run the DOS WinFrame Client or the 16-bit Windows WinFrame Client ( for LAN Manager only) and connect to any WinFrame server via the NetBIOS protocol. Use the WinStation Configuration to create NetBIOS WinStations.

Note

RAS permissions must be given to the user(s) who will be dialing in from the RAS client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. At the first menu, click on Select Domain. In the domain dialog box, type: \\servername.

This brings up a list of the local users on the WinFrame server running RAS. If you want to grant access to domain-based users, type: \\domainname, where domainname is the name of the domain the users are logging in from. Select the Permissions menu item under the User menu. From here, you can grant RAS access to users who will be using the RAS connections. Verify that the users who will be dialing in to the RAS server have been granted RAS access.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions. Verify that you are not granting permissions to a domain user and then logging in as a local user, or vice versa.

The RAS client says that the workstation is not started.

This is caused by not selecting Run the Network Client during the RAS client install. To solve this problem, type NET START WORKSTATION at the DOS command prompt. You can add this statement to your AUTOEXEC.BAT so it will start automatically the next time the DOS system boots.

The RAS client will not recognize the modem or has a problem accessing the modem.

Power down the DOS system and then power it back on after ten seconds. The DOS client can affect the COM port UART to the point that only a cold boot will clear it. A warm boot (pressing CTRL+ALT+DEL) will not fix this problem. If the modem is still not working, make sure that you have the correct modem set in the RAS Setup or a Hayes compatible setting. Verify that the modem is Hayes compatible. If all else fails, try a different brand of modem.

Note

The Microsoft Developer Network CD-ROMs provide various tips and hints for RAS that you may find useful.


Windows for Workgroups 3.11 RAS Client
Microsoft Windows for Workgroups 3.11 RAS Client

See Also:

Configuring RAS Clients

Overview

The Windows for Workgroups 3.11 RAS Client provides the user's system with a connection to a RAS server running on a WinFrame server. It supports only the NetBEUI protocol and, therefore, supports only NetBIOS. This allows the DOS or 16-bit WinFrame Client to connect via NetBIOS to the WinFrame server and allows the remote Windows or DOS client to be another node on the WinFrame server's local network.

Requirements

Hardware Requirements:

386 or 486 or higher

8MB of RAM

Hard Disk

Installation

A RAS set up consists of two parts. The NT RAS server must first be installed on the WinFrame server and the RAS client must be installed on the user's client system. The following section describes how to install and set up the Windows for Workgroups 3.11 RAS client and the supporting NetBIOS protocol stack on the user's client system. To set up and install NT RAS on a WinFrame server, see the WinFrame Remote Access Services manual or review Configuring RAS Clients.

To Install or Upgrade to Windows for Workgroups 3.11

1.	If the client system has Windows 3.1 or an earlier version of Windows for Workgroups started, exit to DOS.

2.	If you already have a standard Windows for Workgroups 3.11 diskette disk install set, you should install them now. Follow the standard Windows for Workgroups 3.11 installation instructions and then proceed to the Installing the Windows for Workgroups 3.11 RAS Client section of this document. If you do not have a standard Windows for Workgroups 3.11 diskette disk install set you can install Windows for Workgroups 3.11 from the WinFrame Installation CD-ROM. To do this, the client system must either have a CD-ROM drive or be able to connect to the WinFrame server over the local network. If this is a remote system and is not on the WinFrame server's local network or does not have access to the CD-ROM drive, obtain a copy of the Windows for Workgroups 3.11 diskette disk install set and install Windows for Workgroups 3.11. After this, proceed to the Installing the Windows for Workgroups 3.11 RAS Client section.

3.	If the user's client system has a CD-ROM drive, place the WinFrame installation CD-ROM into the client system's CD-ROM and continue with step 5 of this procedure. Otherwise proceed to step 4.

4.	Because the user's client system does not have a CD-ROM drive, the WinFrame installation CD-ROM has to be accessed across the local network from the WinFrame server's CD-ROM drive or a NetWare CD-ROM drive. If the client already has network access and can access a server of some type with a CD-ROM drive, use this for the Windows for Workgroups 3.11 installation. Insert the CD-ROM into the server's CD-ROM and use the client to map across the network to the CD-ROM drive. The client system can now proceed to step 5. If the client system has access to the network but does not currently have networking software installed, the following procedure may be used to access the CD-ROM drive.

Sharing the CD-ROM drive from a WinFrame server on the network

A.	Insert the CD-ROM in the WinFrame server's CD-ROM drive.

B.	Logon as an administrator at the WinFrame console.

C.	At a DOS command prompt type: NET SHARE CDROM=x:\, where x is the CD-ROM's drive letter. This will share the CD-ROM on the network for the client system to access.

Create client for DOS disks (gives DOS client access to WinFrame server across the network)

Note

This assumes the WinFrame CD-ROM is still in the CD-ROM drive.

A.	Logon to the WinFrame console as an administrator and start a DOS session. Change to the CD-ROM drive. Change to the \CLIENTS\MSCLIENT\DISKS\DISK1 directory. Copy the entire contents of that directory and any subdirectories onto a blank formatted 3.5-inch diskette: XCOPY /S *.* A:. Label the disk Network Client Disk1.

B.	Change into the \CLIENTS\MSCLIENT\DISKS\DISK2 directory. Copy the entire contents of that directory and any subdirectories onto a blank formatted 3.5-inch diskette: XCOPY /S *.* A:. Label the disk Network Client Disk2.

Install the DOS Client on the client system

On a standard DOS client, with no other network software installed, place the Network Client Disk1 into diskette drive A. Change to drive A, type SETUP, and select the following configuration options:

A.	Select the network adapter DOS Remote Access MAC Driver.

B.	Change your username to a valid domain or local username.

C.	Set the computer name to whatever name you would like.

D.	Set the workgroup name to the workgroup the user will use and the domain name to the domain to be used. These correspond to the workgroup, domain, and users already configured on the local WinFrame system or on the workgroup and domain that the WinFrame system uses.

E.	Change the Setup Options to Full Redirector, Run Network Client, and Logon to Domain (if you want).

F.	Select The Listed Options are Correct to save your settings and complete the RAS client installation. At the end of the install, press ENTER to reboot.

Accessing the WinFrame CD-ROM drive from across the network

A.	After the client system boots up, logon to the network using a valid username and password.

B.	Once logged in, access the CD-ROM drive from the WinFrame server by typing: NET USE x: \\wfservername\CDROM, where x is any available network drive letter and wfservername is the name of the WinFrame server. Drive X should now be accessible and the user's client system should be able to see and access the WinFrame Installation CD-ROM.

5.	Once the WinFrame Installation CD-ROM is accessible, change to the CD-ROM's drive letter and change into the Windows for Workgroups 3.11 installation directory by typing CD \CLIENTS\WFW\NETSETUP from the DOS command prompt:

Once in this directory, type SETUP to start the Windows for Workgroups 3.11 installation. If you are upgrading from Windows 3.1 or an earlier version of Windows for Workgroups, you may install into your old \WINDOWS directory on your client's hard disk. Follow the standard installation procedure for Windows for Workgroups. When asked, select your network adapter if you have one and the protocols needed.

To Install the Windows for Workgroups 3.11 RAS Client

1.	To install the Windows for Workgroups 3.11 RAS Client, start Windows and double-click on the Remote Access icon in the Network group.

2.	Click the Install button to install the remote access software. Follow the dialogs and insert floppies as needed. If you installed from CD-ROM or over the network, enter the correct path for the CD-ROM. When asked, enter your modem type and the COM port the modem is attached to. If your specific modem is not on the list, select a compatible or Hayes type modem from the list. When the installation is completed, the system is rebooted.

Usage

To use the Windows for Workgroups 3.11 RAS Client to connect to WinFrame RAS:

1.	To use the Windows for Workgroups 3.11 RAS Client, start Windows and double-click on the remote access icon in the Network group. The first time the RAS client runs, you must add a phone book entry. Click on the OK button in this panel and create a new entry.

2.	Once in the Add Phone Book Entry dialog box, add the entry name, the phone number of the WinFrame RAS server's modem(s), and a description of the connection. If the username you are logged in as on the client is the same as the remote username, you can select the Authenticate using current username and password. If the username is different, deselect this option. Make sure the correct port and modem device are selected for use on your client. When finished click OK to save the entry. Check with the Windows for Workgroups 3.11 manuals for more information on the X.25, ISDN, Network, and Security options.

3.	More entries can be added by clicking the Add button on the toolbar. Existing entries can be edited or deleted by using the Edit or Remove buttons on the toolbar. To dial the WinFrame RAS server, select the correct entry and click the Dial button on the toolbar.

4.	At this point, the authentication panel will appear. Enter a valid username, password, and (if needed) the domain name, then click the OK button to dial the connection.

Note

This dialog will not appear if you selected the Authenticate using current user name and password option in the entry setup panel.

5.	The client calls the RAS server, connects, and authenticates your username. The client system is connected to the WinFrame server's RAS server and accesses the network to which the WinFrame server is connected.

6.	Once connected the Connection Complete dialog box appears. You can set the RAS dialer to Minimize on dial or to not display this dialog at all in the future. Once done, click the OK button. To disconnect from the RAS server, click on the Hang Up button on the Remote Access client's toolbar.

7.	The user may now run the WinFrame Win16 Client and connect to any WinFrame server using the NetBIOS over NetBEUI protocol. Use the WinStation Configuration utility on the WinFrame host to create NetBIOS WinStations if needed. Also be sure to set the WinStations to connect on NetBIOS over NetBEUI, not IPX/SPX or TCP/IP NetBIOS. The Windows for Workgroups 3.11 RAS Client supports only NetBIOS over NetBEUI. If you configure the WinStations on the WinFrame server to run NetBIOS on either IPX/SPX or TCP/IP, you will get an error when you try to connect.

Note

RAS permissions must be given to the user(s) who will be dialing-in from the RAS client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. From the first menu click on Select Domain. Once the dialog box for the domain comes up, type: \\wfservername.

This displays the local users on the WinFrame server running RAS. If you want to grant access to domain- based users type: \\domainname, where domainname is the name of the DOMAIN the user logons are from. From there, select the Permissions menu item under the User menu. The Administrator can grant RAS access to the users who will be using the RAS connections. Verify that this is done and that the users who will be dialing-in to the RAS server have been granted RAS access.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions. Verify that you are not granting permissions to a domain user and then logging in as a local user, or vice versa.

When I try to dial, the Remote Access program says it cannot find my COM port. Why?

Your COM port's UART is probably in an invalid state. To fix it, exit Windows and power off your client system and modem. Power them back on, restart Windows, and try to dial again.

After I connect to the RAS server, I get an error that says that the NetBIOS name for my system is already being used. What causes this?

Another system on the remote network is using the same name as your system or you are trying to make a RAS connection to a network you are connected to. If another system on the network is using the same name as your system, use Windows Control Panel to change the name of your computer. If the client system is trying to make a RAS connection to the same network that it is connected to, disable or disconnect the other network connection.

Note

The Microsoft Developer Network CD-ROMs provide various tips and hints for RAS that you may find useful.


Windows 95 Dial-Up Networking
Microsoft Windows 95 Dial-Up Networking

See Also:

Configuring RAS Clients

Overview

Windows 95 includes a Dial-Up Networking feature that supports a variety of PPP protocols. This Dial-Up Networking utility can be used to connect to a RAS server running on a WinFrame server as a PPP connection. This allows a remote Windows 95 client to become another node on the WinFrame server's local network. IPX, TCP, and NetBEUI are supported as protocols across this PPP connection.

Requirements

Hardware Requirements:

386 or 486

Windows 95 supported modem

8MB of RAM

Hard Disk

Software Requirements:

Windows 95 or higher

To install Windows 95 Dial-Up Networking

1.	Start Windows 95 and double-click on the Control Panel icon in the My Computer group. In the Control Panel, double-click on the Add/Remove Programs applet.

2.	In the Add/Remove Programs applet, select the Windows Setup folder tab and double-click on the Communications application option. This opens the Communications dialog box.

3.	In the Communications dialog box, select the Windows 95 Dial-Up Networking option and click the OK button to save.

4.	In the Add/Remove Programs applet, click the OK button to add the Windows 95 Dial-Up Networking. Follow the on-screen instructions to proceed with installation.

5.	When the software is installed on the client system, double-click on the Control Panel again in the My Computer group. In the Control Panel, double-click on the Network applet.

6.	In the Network applet, verify that the Dial-Up Adapter driver is loaded and that the correct protocols for your client system and network are loaded. A typical configuration would look like:

Client for Microsoft Networks (if WinFrame server is on Network Domain)

Client for NetWare Networks (if it will be used with a NetWare Network)

Dial-Up Adapter

IPX/SPX compatible protocol -> Dial-Up Adapter (for IPX, needed for NetWare)

NetBEUI -> Dial-Up Adapter (for NetBEUI)

TCP/IP -> Dial-Up Adapter (for TCP/IP)

Make sure the Properties settings for each of the above items are set according to your client and your network set up. Check with the Windows 95 documentation for greater detail and specifics on protocol and driver settings and properties for your network.

To use the Windows 95 Dial-Up Networking to connect to WinFrame RAS

Note

The following assumes that you have a modem connected to a COM port on your Windows 95 client. This also assumes that Windows 95 is aware of the modem and has run the modem set up for your modem. This is done by running the Modem Setup Wizard in the Windows 95 control panel. Refer to your Windows 95 documentation for more information on setting up and installing modems for use on your Windows 95 client.

1.	Boot up the client system running Windows 95 and open the My Computer group. In the group, open the Dial-Up Networking folder. The first time the folder is opened, the Dial-up Networking setup wizard will start automatically. Click the Next button to create your Dial-Up Networking connection to the WinFrame server.

2.	Enter a name for the connection icon and select the modem from the list of installed modems on the Windows 95 client. Click on the Configure button to change configuration settings, such as baud rate, for your modem. Click the Next button to continue.

3.	The next panel lets you enter the telephone number of the WinFrame server. Enter the telephone number to dial and select Next to continue.

4.	Click the Finish button to create your new Dial-Up Networking WinFrame connection icon.

5.	Once the icon is created, the Dial-Up Networking folder will open. This folder contains all the connection icons to remote network sites. To create new Dial-Up Networking icons to new sites, double-click the Make New Connection icon to restart the set up wizard. To edit old connection icons, click the right mouse button and select Properties from the menu. To connect to the WinFrame RAS server, double-click on the new Dial-Up Networking icon you just created.

6.	The Connect To dialog box appears. Enter the username and password of the user on the WinFrame server who has been granted RAS access. Verify that the phone number is correct for the connection and click the Connect button to dial.

7.	The status dialing box appears. This shows the current status of the connection, username authentication, and network validation of your client.

8.	You are prompted for a user logon to the remote network's domain, if your user belongs a domain setup. Enter the username, password, and domain name to logon to.

9.	The Windows 95 client is connected to the remote network to which the WinFrame server belongs. The connected dialog box appears as long as you are connected. Click on the Details button to see what protocols are being used over the Dial-Up Networking connection. Click on the Disconnect button to disconnect from the WinFrame server.

10. The user may now run the WinFrame Win32 Client and connect to any WinFrame server via the protocols were used: NetBEUI (NetBIOS), IPX, or TCP/IP. Be sure that WinStations have been configured on the WinFrame host corresponding to the network protocols being used.

Note

RAS permissions must be given to the user(s) who will be dialing-in from the Windows 95 client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. At the first menu, click on Select Domain. When the dialog box for the domain appears, type \\wfservername to display the local users on the WinFrame server running RAS. If you want to grant access to domain-based users, type: \\domainname, where domainname is the name of the domain the users logons are from. Select the Permissions menu item under the User menu. You can grant RAS access to any users who will be using the PPP to RAS connections. Verify that this is done and that the users who will be dialing-in to the RAS server have been granted RAS access.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions. Verify that you are not granting permissions to a domain user and then logging in as a local user, or vice versa.


Microsoft Windows NT 3.5 Remote Access Client

See Also:

Configuring RAS Clients

Overview

The Windows NT 3.5 Remote Access Client provides the user's remote system with a connection to a RAS server running on a WinFrame server. It provides PPP access and supports the NetBEUI (NetBIOS), IPX/SPX, and TCP/IP protocols. This allows the 32-bit WinFrame Client to connect over any of these protocols and start a remote control session on a remote WinFrame server as well as allowing the client to be another node on the remote network.

Requirements

Hardware Requirements:

486 or Pentium or higher

16MB of RAM

Hard Disk

Software Requirements:

Windows NT 3.5 Workstation or Server

WinFrame

Installation

A RAS set up consists of two parts: the RAS server must first be installed on the WinFrame server and the Windows NT 3.5 Remote Access client must be installed on the user's client system. The following section describes how to install and set up the Remote Access client on the user's client system. To set up and install RAS on a WinFrame server, see the WinFrame Remote Access Services manual or review Configuring RAS Clients.

To install the Windows NT 3.5 Remote Access Client

1.	Start Windows NT 3.5. Start the Network application in the Windows NT Control Panel.

2.	After the Network starts, select Add Software. The Add Network Software dialog box appears. Select Remote Access Service and then select Continue.

3.	Enter the path to the Windows NT 3.5 files. These may be on diskettes or on the Windows NT 3.5 CD-ROM. After you specify the path, Network copies the required files for the RAS Client.

4.	When installation is complete, the Remote Access Setup dialog will appear. Select the COM port used by the modem on your client PC and select OK. The Configure Port dialog appears. Specify your modem type and select the Dial-out only option under the Port Usage section of the dialog. When you are finished, select OK to save your settings.

5.	Select Continue from the Remote Access Setup dialog box to finish the set up. At this point, various network protocol set up dialogs will appear. Enter the settings that agree with your network set up. Refer to the Microsoft Remote Access Services manual for more information.

6.	You will again be asked for the path of your Windows NT 3.5 files. Enter the path you specified in Step 3 and select Continue. The install completes RAS setup. After setup is complete, you are returned to the Network Settings dialog box. Select OK to save your changes. The network bindings are reconfigured and the system restarts.

Using the Windows NT 3.51 Remote Access Client

1.	Start Windows and double-click on the Remote Access icon in the RAS group. The first time the RAS client runs, it will make the user add a phone book entry. Click on the OK button in this panel and create a new entry.

2.	In the Add Phone Book Entry dialog box, add the entry name, the phone number of the WinFrame RAS server's modem(s), and a description of the connection. If the username you are logged in as on the client is the same as the remote username, you can select Authenticate Using Current Username and Password. If the username is different, deselect this option. Make sure the correct port and modem device are selected for use on your client. When finished, click OK to save the entry. Refer to the Windows NT 3.5 manuals for more information on the X.25, ISDN, Network, and Security options.

3.	More entries can be added by clicking the Add button on the toolbar. Existing entries can be edited or deleted by using the Edit or Remove buttons on the toolbar. To dial the WinFrame RAS server, select the correct entry and click the Dial button on the toolbar.

4.	At this point the authentication panel appears. Enter a valid username, password, and (if needed) the domain name, then click the OK button to dial the connection.

Note

This dialog does not appear if you selected the Authenticate Using Current Username and Password option in the entry setup panel.

5.	The client calls the RAS server, connects, and authenticates your username. The client system is connected to the WinFrame RAS server and accesses the network to which the WinFrame server is connected.

6.	The Connection Complete dialog box appears. You can set the RAS dialer to Minimize on dial or to not display this dialog at all in the future. Click the OK button. To disconnect from the RAS server, click on the Hang Up button on the Remote Access client's toolbar.

7.	You may now run the WinFrame Win32 Client and connect to any WinFrame server via any of the supported protocols. Be sure to use the WinStation Configuration utility on the WinFrame host to create virtual terminals based on the network protocol to be used.

Note

RAS permissions must be given to the user(s) who will be dialing-in from the RAS client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. From the first menu, click on Select Domain. When the dialog box for the domain appears, type: \\wfservername.

This displays the local users on the WinFrame server running RAS. If you want to grant access to domain-based users, type: \\domainname, where domainname is the name of the domain the user logons are from. From there, select the Permissions menu item under the User menu. You can grant RAS access to any users who will be using the RAS connections. Verify that this is done and that the users who will be dialing-in to the RAS server have been granted RAS access.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions. Verify that you are not granting permissions to a domain user and then logging in as a local user, or vice versa.

After I connect to the RAS server, I get an error that says that the NetBIOS name for my system is already being used. What causes this?

Another system on the remote network is using the same name as your system or you are trying to make a RAS connection to a network you are connected to. If another system on the network is using the same name as your system, use Windows Control Panel to change the name of your computer. If the client system is trying to make a RAS connection to the same network that it is connected to, disable or disconnect the other network connection.

Note

The Microsoft Developer Network CD-ROMs provide various tips and hints for RAS that you may find useful.


Funk SoftWare WanderLink PPP

See Also:

Configuring RAS Clients

Overview

WanderLink 2.10 is a combination point-to-point protocol (PPP) remote client and remote control software for a DOS/Windows based system. While the remote control part of WanderLink, Proxy, is not useful for WinFrame servers, the PPP remote client can be used in conjunction with RAS to provide remote LAN node access to a remote DOS/Windows client system. The WanderLink 2.10 client provides IPX and IP protocols to a remote network.

Note

This package provides PPP connectivity for a client system, NOT a WinFrame server. Do not install this package on a WinFrame server because it will not work.

Requirements

Hardware Requirements:

386 or 486

WanderLink supported modem

4MB of RAM for DOS, 8MB of RAM for Windows 3.1 or higher

Hard Disk

Software Requirements:

Funk SoftWare WanderLink V2.1.0

Novell NetWare Client Software (included)

WanderLink supported TCP/IP Stack (if IP access is desired)

DOS or Windows 3.1 or Windows for Workgroups 3.11 (for Windows access)

Installation

A PPP to RAS configuration consists of two parts: the RAS server must first be installed on the WinFrame server and then the PPP client and any supporting protocol stacks must be installed on the user's client system. The following section describes how to install and set up the Funk SoftWare's WanderLink PPP client and supporting IPX and IP protocol stacks on the user's client system. To set up and install RAS on a WinFrame server, see the Remote Access Services manual or review Configuring RAS Clients. Once RAS is successfully installed, several RAS settings must be made for Stampede compatibility. The first of these is the Encryption Setting. This must be set to either Require any authentication including clear text or Require encrypted authentication. It cannot be set to Require Microsoft encrypted authentication. This change can be made by configuring the Remote Access Server software in the Network applet under the NT Windows Control Panel on the WinFrame server.

Before starting the WanderLink PPP installation, verify that there is no networking on the client system. If networking is currently installed on the system, remove or uninstall it from the client system before continuing with the installation. (Merging multiple networking stacks on the same client system is beyond the scope of this documentation. If interested in doing so, please refer to WanderLink's documentation and Novell's NetWare documentation. It is otherwise assumed that the WanderLink PPP installation is being done on a clean system; that is, DOS and Windows with no other networking.)

To install the WanderLink PPP client, insert the Wander Link Disk1 into drive A of the client system. If Windows exists on the client system, start Windows and at the Run command in the File menu type: A:\SETUP. If the system has DOS only, change to drive A and type: A:\WINSTALL. This will start the installation program. When the first panel appears, deselect the Master (take over the other PC) option under the Proxy section. This is the remote control host piece that cannot be used with WinFrame. Verify that the Dial-in client and NetWare Client (VLM) are selected under the WanderLink section. Click the Install button to continue. If a VLM is found on the system (because other networking was not removed beforehand), you will get a popup message asking if you want to use the current VLM or install the new one. Click the Install New VLM button to install WanderLink's VLM set up. The WanderLink install proceeds to copy the installation files to the client's hard disk. When done, you will be asked if you want to initialize the PPP settings. Click Yes to set the port and the modem. In the settings panel, select the modem being used on the client system, the port it is connected to, and the baud rate to use. Click the Save button to keep the modem and port settings. Click the Connections radio button and then click the Add button to add a new phone book entry. Enter the connection name, local username on the remote WinFrame server, the user's password, and the phone number(s) of the RAS server's modem(s).

Note

Make sure that the username and password are configured on the local WinFrame server. The user cannot be a domain user and must be configured locally. To configure a user locally, logon as an administrator on the WinFrame console and run the User Manager for Domains program in the Administrative Tools group. Click on Select Domain under the User menu. When the dialog box for the domain appears, type \\wfservername and press ENTER, where wfservername is the WinFrame server name that the RAS server is running on to which the PPP client will attach. This brings up a list of the local users for that system. New users can be added and passwords for them may be set. Refer to the WinFrame manuals for more information on configuring users and passwords. When done configuring the user(s), RAS permissions must be given to the user(s) who will be dialing-in from the PPP client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. Click on Select Domain. When the dialog box for the domain appears, type \\wfservername. This will bring up a list of the local users on the WinFrame server running RAS. Select the Permissions menu item under the User menu. You can grant RAS access to any users who will be using the PPP to RAS connections. Verify that this is done and that the users who will be dialing-in to the RAS server have been granted RAS access. Click the Save button to save your settings and then click the Exit button to finish the installation. Follow the on-line instructions and then reboot the client system.

You can install any of the WanderLink supported IP stacks. Refer to the WanderLink IP Stack Support help file for information on how to install IP stacks to function with the WanderLink PPP client.

Usage

To use WanderLink to connect to the RAS server, boot up the client system to DOS, change into the C:\WLINK directory, and at the DOS prompt, type: LOADVLM.

When the NetWare VLMs are loaded, start Windows as normal. When Windows has started, double-click on the WanderLink Client Icon in the WanderLink PPP Client group to start WanderLink. Select the Connection type and click the Connect button. WanderLink will connect to the RAS server, authenticate the user, and create the IPX and IP connections. You may then exit or minimize the WanderLink client and utilize the network via IPX and IP as normal. The client system will appear as another node on the network to which the WinFrame server is connected. You can run the DOS WinFrame Client or the 16-bit Windows WinFrame Client and connect to any WinFrame server on the remote network via IPX or IP. Be sure to configure the terminals on the appropriate WinFrame servers for the network protocol that will be used. To disconnect from the RAS server, start up the WanderLink Client again and click on the Disconnect button.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Installation section on setting up local users and granting them RAS access permissions.

Why does it take so long to logon to a NetWare server over a PPP connection?

Asynchronous serial PPP connections are much slower than normal network connections. Operations must be optimized and program executable files must be stored on the client's hard disk in order to achieve good performance. Use the Windows File Manager to logon to a NetWare server and map drives rather than using the standard DOS logon command. The Windows File Manager logon code is local to the client system. If you prefer to use the DOS logon commands, copy these commands to the local client system hard disk rather than trying to load them over the network. This will make access much faster.

As a general rule, only data should go across the PPP connection, not programs. If you load programs from the remote network, they must be moved across the PPP connection first before being loaded into memory on the client system. This slows down access significantly. If the program is installed on the client system's hard disk, the program can be loaded into memory directly from hard disk and only data packets traverse the PPP connection. In general, if an entire application must be run remotely, you should use a WinFrame remote control connection instead of a remote node connection.


Shiva PPP 3.5

See Also:

Configuring RAS Clients

Overview

Shiva PPP 3.5 is a remote LAN node connectivity package that allows a client system to become another node on a remote network. Shiva PPP 3.5 will connect to a variety of PPP servers, including a Windows NT or WinFrame RAS server. The protocols supported by Shiva PPP are NetBEUI, IPX, and IP. Shiva PPP comes with both ODI and NDIS interfaces and supports a variety of TCP/IP stacks. Shiva PPP can connect to a RAS server running on a WinFrame server to provide remote LAN node connectivity to a remote client system.

Note

This package provides PPP connectivity for a client system, NOT a WinFrame server. Do not install this package on a WinFrame server.

Requirements

Hardware Requirements:

386 or 486 (SX or DX)

Shiva PPP supported modem

4MB of RAM for DOS, 8MB of RAM for Windows 3.1 or higher

Hard Disk

Software Requirements:

Shiva PPP 3.5

Novell NetWare Client Software (included)

Shiva Supported TCP/IP Stack (if IP is desired)

DOS or Windows 3.1 or Windows 3.11 (for Windows access)

Installation

There are two parts to a successful PPP to RAS setup: the RAS server must be installed on the WinFrame server and then the PPP client and any supporting protocol stacks must be installed on the user's client system. The following section describes how to install and set up the PPP client and supporting protocol stacks on the user's client system. To set up and install RAS on a WinFrame server, see the Remote Access Services manual or refer to Configuring RAS Clients. When RAS is successfully installed, several RAS settings must be made for Shiva compatibility. The first of these is the Encryption Setting. This must be set to either Require Any Authentication Including Clear Text or Require Encrypted Authentication. It cannot be set to Require Microsoft encrypted authentication. The second setting change is under the IPX Configure button. At the bottom of this dialog box there is a check box that allows the PPP client to supply its own IPX address. Make sure this is checked so that Shiva can use its own IPX address. Shiva does not support dynamically changing the IPX address at the client system when given an address by the RAS server. Both of these changes are made by configuring the Remote Access Server software in the Network applet under the Windows Control Panel on the WinFrame server.

Before starting the Shiva PPP installation, verify that there is no networking on the client system. If networking is currently installed on the system, remove or uninstall it from the client system before continuing with the installation. (Merging multiple networking stacks on the same client system is beyond the scope of this documentation. If interested in doing so, refer to Shiva's PPP documentation, Windows for Workgroups documentation if using Windows for Workgroups, and Novell's NetWare documentation. It is otherwise assumed that the Shiva PPP installation is being done on a clean system; that is, DOS and Windows or Windows for Workgroups only.) The installation of the Shiva PPP 3.5 client is a three step process for DOS and Windows 3.1 and a four step process for Windows for Workgroups 3.11. These steps include:

1.	Installing the Novell NetWare Client

2.	Installing the Shiva PPP 3.5 package

3.	Installing the Shiva Windows for Workgroups 3.11 driver (for Windows for Workgroups only)

4.	Installing the TCP/IP protocol

To install the Novell NetWare Client, insert the first disk of the NetWare Client Install disks into drive A of the client system and from a DOS prompt type: A:\INSTALL.

When the install program starts, enter the destination directory, the Windows directory (if there is one), and the network driver. To select the network driver, press the ENTER key on Select the driver for your network board and select ShivaRemote Dial-In Driver as the network driver type. Press the ENTER key on the Install option to install the Novell NetWare client. This will install the NetWare client to the hard disk and add a few lines to the CONFIG.SYS and AUTOEXEC.BAT files on the client system. When the installation is completed, verify that the line: LASTDRIVE=Z exists in CONFIG.SYS and verify that the STARTNET.BAT command file is called from the AUTOEXEC.BAT file.

The next part of the installation is setting up the Shiva PPP 3.5 software. If the client system will be DOS only, you may install the Shiva PPP software from DOS. If, however, Windows 3.1 or Windows for Workgroups 3.11 are available, start them up first before executing the Shiva PPP install. Insert the Shiva PPP 3.5 Install disk into drive A, and from DOS type: A:\SETUP.

From inside Windows, type A:\SETUP at the Run option in the File menu of the Program Manager.

For DOS and Windows 3.1, click the OK button for the first information panel of the Shiva PPP 3.5 installation. For Windows for Workgroups 3.11, verify the check boxes are selected to install the Shiva PPP software and to update the Windows for Workgroups network drivers, then click OK. On the next panel enter the destination directory for the Shiva PPP software, usually C:\SHIVA, and click the OK button. The Shiva PPP software will install to the hard disk and changes to the Windows .INI files will be made to load Shiva's dial-in VxD. In Windows, a Shiva group is created with all the necessary icons needed to run the program. At the end of the installation, you are asked for the COM port and modem being used. Enter the modem type to be used, the baud rate to be used, and the COM port to which the modem is connected.

Note

The following paragraph refers ONLY to Windows for Workgroups 3.11 users. Skip this paragraph if the client system that Shiva PPP 3.5 is installed on is DOS or Windows 3.1 based.

If the system that Shiva PPP 3.5 is installed on is a Windows for Workgroups 3.11 client system, the Shiva Network driver has to be installed. To do this, open the Network group and double-click on the Network Setup applet. Click the Drivers button when the Network Setup applet appears. Remove any other drivers that are currently there. (Refer to the Shiva and Windows for Workgroups documentation on how to integrate multiple networks.) Click the Add Driver button, which will give you a list of all the Windows for Workgroups network drivers. Select Unlisted or Updated Driver from the list. The Network Setup applet provides a dialog box requesting the path of the new network driver. Enter the path for the Shiva PPP 3.5 client, usually C:\SHIVA. The Network Setup applet will find the Shiva PPP dial-in driver in the Shiva directory. Select the driver and continue with the install. When the driver has been added, the protocols must be updated. By default, Windows for Workgroups adds the NetBEUI protocol and the IPX/SPX with NetBIOS protocol. Remove the IPX/SPX with NetBIOS protocol by selecting it and clicking the Remove button. This protocol is not supported by Shiva PPP 3.5 at this time due to a timing incompatibility. To access IPX/SPX, Shiva must use the ODI driver to access the Novell NetWare client running in DOS under Windows. NetBEUI should be the only protocol. Save these settings by selecting the OK button. When install is completed, you will be asked if you want to install new drivers. Make sure you answer NO to preserve the Shiva PPP Windows for Workgroups drivers currently installed on the hard disk.

Note

You must select NO or Windows will hang the next time it is started.

The Network Setup applet will close and Windows will ask if it should restart the system or not. Select the Restart the System button to reboot the system.

You may now install a TCP/IP stack. See the Shiva help files or Shiva documentation for the installation of the various TCP/IP stacks that Shiva PPP supports. The Shiva help files are found in the Shiva PPP group that is created in Windows during the installation.

Usage

Make a connection from the client system to the RAS server as follows. When the client system boots up, make sure that the Novell NetWare client loads correctly and returns no errors. If running Shiva PPP from DOS, change into the Shiva installation directory and run the CONNECT.EXE program. If the client system has Windows 3.1 or Windows for Workgroups, start Windows. In Windows, double-click on the Shiva Connect icon in the Shiva group to start the Windows version of the connect program, WCONNECT.EXE. When the connect or Windows connect program starts, enter a name for the connection, the username and password on the RAS system, and the phone number of the RAS server's modem(s).

Note

Make sure that the username and password are configured on the local WinFrame server. The user cannot be a domain user and must be configured locally. To configure a user locally, logon as an administrator on the WinFrame console and run the User Manager for Domains program in the Administrative Tools group. In the Administrative Tools group, click on Select Domain under the User menu. When the dialog box for the domain appears, type: \\wfservername and press ENTER, where wfservername is the WinFrame server. This will bring up a list of the local users for that system. New users can be added and passwords for them may be set. When done configuring the user(s), RAS permissions must be given to the users who will be dialing-in from the PPP client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. From the first menu click on Select Domain. When the dialog box for the domain appears, type \\wfservername followed by the WinFrame server name. This displays a list of the local users on the WinFrame server running RAS. Select the Permissions menu item under the User menu. You can grant RAS access to any users who will be using the PPP to RAS connections. Verify that this is done and that the user who will be dialing-in to the RAS server has been granted RAS access. Select any other options desired and then close the Options dialog.

Note

The Dial-Back features of Shiva PPP 3.5 will not work with a RAS server. If these are selected and a phone number is entered, they will be ignored during the connection.

You are now ready to connect. Click the Connect button and Shiva PPP will take the modem off hook and dial the RAS server. When the connection is made, you are authenticated and the protocols will be connected and set up for use. Shiva will report the client system's IP address and notify you that you are connected. You may now make use of any networking connections and programs you would like. The client system can be seen and accessed as another network node on the WinFrame server's local network. The DOS WinFrame Client or 16-bit Windows WinFrame Client can be run to connect to any WinFrame server on the remote network via IPX, IP, or NetBIOS. Be sure to configure the terminals on the appropriate WinFrame servers for the network protocol that will be used. To disconnect from the RAS server, return to the connect program and click on the Disconnect button. This terminates the connection and hangs up the modem from the phone line.

Troubleshooting

When I start Windows for Workgroups, Windows just hangs and leaves nothing but the mouse cursor on the screen. What's wrong?

This is caused by answering Yes to update the drivers instead of answering No when adding the Windows for Workgroups 3.11 Shiva PPP dial-in driver. If this happens, reboot the system in DOS. Edit the AUTOEXEC.BAT file and REM out all the networking lines, such as STARTNET.BAT, etc.; then reboot the system and restart Windows. Windows will start but the network will fail. Place the Shiva PPP 3.5 Installation diskette into the client system's drive A. From the Run option in the File menu type: A:\SETUP.

You will see two options at the first install panel. Select the Update the Windows for Workgroups drivers but make sure to deselect the Install Shiva PPP option. Click the OK button to reinstall the Shiva PPP Windows for Workgroup drivers. Exit Windows and edit the AUTOEXEC.BAT again. Reenable the networking statements and save the AUTOEXEC.BAT file. Reboot the system and restart Windows. Windows will start and the network will load correctly.

Shiva PPP dials the RAS server and connects. When it does, the IPX and IP protocols install and work correctly but it gives me the error that the NetBEUI connection failed because another system was found on the domain with the same NetBIOS name even when there isn't. What happened?

This is usually caused by using an incorrect modem initialization string or by using a baud rate that is too high for the connection. Try lowering the baud rate. If that fixes the connection, determine how high the setting can be made before NetBEUI fails to connect. If higher baud rates such as 38400 and 57600 are desired, verify that the COM port to which the modem is connected has a 16550 UART. If not, upgrade the COM port. If changing the baud rates does not help, try a different modem on the client system or verify that the modem is set for the correct modem initialization string.

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions.

Why does it take so long to logon to a NetWare File Server over a PPP connection?

Asynchronous serial PPP connections are much slower than normal network connections. Operations must be optimized and program executable files must be stored on the client's hard disk in order to achieve good performance. Use the Windows File Manager to logon to a NetWare File Server and map drives rather than using the standard DOS logon command. The Windows File Manager logon code is local to the client system. If you prefer to use the DOS logon commands, copy these commands to the local client system hard disk rather than trying to load them over the network. This will make access much faster.

As a general rule, only data should go across the PPP connection, not programs. If you load programs from the remote network, they must be moved across the PPP connection first before being loaded into memory on the client system. This slows down access significantly. If the program is installed on the client system's hard disk, the program can be loaded into memory directly from hard disk and only data packets traverse the PPP connection. In general, if an entire application must be run remotely, you should use a WinFrame remote control connection instead of a remote node connection.


Stampede Remote Office PPP

See Also:

Configuring RAS Clients

Overview

Stampede Remote Office provides a Windows remote control and a client PPP package. While the remote control part of Remote Office is not needed, the client PPP package can be used in conjunction with a RAS server running on a WinFrame server. This allows a remote Windows or DOS client to be another node on the WinFrame server's local network. Protocols such as IPX and TCP/IP can be used across the PPP connection as a standard network or WinFrame Client can be run across the PPP connection to connect to a WinFrame server.

Note

This package provides PPP connectivity for a client system only, NOT a WinFrame server. Do not install this package on a WinFrame server.

Requirements

Hardware Requirements:

386 or 486

Stampede Remote Office supported modem

4MB of RAM for DOS, 8MB of RAM for Windows 3.1 or higher

Hard Disk

Software Requirements:

Stampede Remote Office Release 2.1.0

Novell NetWare Client Software (included)

FTP OnNet TCP/IP Stack (included)

DOS or Windows 3.1 or Windows for Workgroups 3.11 (for Windows access)

Installation

A PPP to RAS configuration consists of two parts: the RAS server must first be installed on the WinFrame server and then the PPP client and any supporting protocol stacks to be used must be installed on the user's client system. The following section describes how to install and set up the Stampede Remote Office PPP client and supporting IPX and IP protocol stacks on the user's client system. To setup and install NT RAS on a WinFrame server, see the Remote Access Services manual or refer to Configuring RAS Clients. Once RAS has been successfully installed, several RAS settings must be made for Stampede compatibility. The first of these is the Encryption Setting. This must be set to either Require any authentication including clear text or Require encrypted authentication. It cannot be set to Require Microsoft encrypted authentication. Make this change by configuring the Remote Access Server software in the Network applet under the NT Windows Control Panel on the WinFrame server.

Before starting the Stampede Remote Office PPP installation, verify that no networking is on the client system. If networking is currently installed on the system, remove or uninstall it from the client system before continuing with the installation. (Merging multiple networking stacks on the same client system is beyond the scope of this documentation. If interested in doing so, review Stampede's Remote Office PPP documentation, FTP's OnNet documentation, and Novell's NetWare documentation. It is otherwise assumed that the Stampede Remote Office PPP installation is being done on a clean system; that is, DOS and Windows only.)

To install the Stampede Remote Office PPP client, insert the Remote Office Gold Client Installation Disk into drive A of the client system. If Windows is started, exit Windows so that the system is at the DOS prompt. From the DOS prompt, type: A:\INSTALL.

When installation starts, enter the username, companyname, and destination directory for Stampede Remote Office, then press OK. On the next panel, select the COM port to which the client system's modem is connected and click on the OK button. In the next dialog box, you are presented with a list of Stampede supported modems. Select the modem to be used with the client system. If your modem is not on the list, select a 9600 V.32 or 14.4 V.32bis compatible modem, depending on your particular modem type.

The next panel asks you which stacks you want to use with Stampede Remote Office PPP. Select NetWare and OnNet TCP/IP Gold, unless other networks are being used. Click on the OK button. The dialogs will request the client system's IP address and the IP address of the Domain Name Server. Enter the addresses for both. Enter the username, password, and phone number of the RAS server's modem(s) in the next panel. Enter a local username and password on the WinFrame server to be used. In the phone number text box, enter the RAS server's phone number, then select the OK button.

In the final panel, the installation program asks if you want the Remote Office Windows programs to be installed. If the client system supports Windows, select Yes, otherwise select No. You are shown all the choices you made and given an opportunity to change them. If any are incorrect, change them at this point. When all the settings are as desired, click the OK button to continue with the installation. Follow on-line instructions to complete installation. When the installation is done, reboot the client system.

Usage

You can connect to a RAS server in one of two ways. The first way is connecting from DOS systems. Change into the Remote Office directory, C:\ROF, and edit the ROSTART.BAT file. The following line should be near the end of the file:

C:\ROF\ROCLIENT /S

Save the file and run the ROCLIENT.BAT file from the DOS command prompt. This will load the correct drivers and run the Remote Office Client program. From the Remote Office DOS Client, you can select Add Phonebook Record from the Setup menu to add a new entry if one was not entered before. Enter the name, phone number of the RAS server modem(s), and local username and password on the WinFrame server running RAS. Click the Add button to save and the Exit button to return to the main menu.

Note

The Callback Number field will not work with NT RAS. If a number is entered, it will be ignored.

Note

Make sure that the username and password are configured on the local WinFrame server. The user cannot be a domain user and must be configured locally. To configure a user locally, logon as an administrator on the WinFrame console and run the User Manager for Domains program in the Administrative Tools group. Click on Select Domain under the User menu. When the dialog box for the domain appears, type \\wfservername and press ENTER, where wfservername is the name of the WinFrame server. This brings up a list of the local users for that system. New users can be added and passwords for them may be set. See the WinFrame manuals on configuring users and passwords. When done configuring the user(s), RAS permissions must be given to the user(s) who will be dialing-in from the PPP client. To do this, logon as an administrator on the WinFrame server console and start the Remote Access Administrator program in the RAS group. Click on Select Domain. When the dialog box for the domain appears, type \\wfservername. This will bring up a list of the local users on the WinFrame server running RAS. Select the Permissions menu item under the User menu. You can grant RAS access to any users who will be using the PPP to RAS connections. Verify that this is done and that the users who will be dialing-in to the RAS server have been granted RAS access. Click the Save button to save your settings and then click the Exit button to finish the installation. Follow the on-line instructions and then reboot the client system.

If you need to make changes to the port or modem type, select the Ports and Modems item from the Setup menu. You can set the COM port and modem type being used for the connection on the client system. Select Logon to Host from the Connection menu. Verify that the information in this dialog box is correct and then select the OK button to connect to the RAS server. The Remote Office Client will connect to the RAS server, authenticate the user, and create the IPX and IP connections. This will set up the remote client system as another node on the WinFrame server's network. When connected, you may exit from the Remote Office Client and use DOS and any networking functions as normal. To disconnect from the RAS server, run the ROCLIENT.EXE program again and select Disconnect to end the connection.

Users connecting from Windows systems should change into the Remote Office directory, C:\ROF, and edit the ROSTART.BAT file. The following line should be near the end of the file:

WIN C:\ROF\WROCLNT /S

Once verified, save the file and run the ROCLIENT.BAT file from the DOS command prompt. This will load the correct drivers, run Windows, and run the Windows Remote Office Client program. When the client program loads, you can click on the Phonebook button to add new dial-in entries or click the Ports button to make modem and port setting changes. These settings are changed in the same way as with the DOS client.

When you want to connect to the RAS server, click the Connect button, verify that the entry information is correct, and then select the OK button to connect. When this is done, the client program will connect to the RAS server, authenticate the user, and create the IPX and IP connections. This will set up the remote client system as another node on the WinFrame server's network. When the connection is made, you can exit from the client program or just minimize it. The DOS WinFrame Client or the 16-bit Windows WinFrame Client can be run and connect to any WinFrame server on the remote network via IPX or IP. Be sure to configure the terminals on the appropriate WinFrame servers for the network protocol that will be used. To disconnect from the RAS server, select the Disconnect button in the Windows Remote Office client program.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused either by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. See the note in the Usage section on setting up local users and granting them RAS access permissions.

Why does it take so long to logon to a NetWare File Server over a PPP connection?

Asynchronous serial PPP connections are much slower than normal network connections. Operations must be optimized and program executable files must be stored on the client's hard disk in order to achieve good performance. Use the Windows File Manager to logon to a NetWare File Server and map drives rather than using the standard DOS logon command. The Windows File Manager logon code is local to the client system. If you prefer to use the DOS logon commands, copy these commands to the local client system hard disk rather than trying to load them over the network. This will make access much faster.

As a general rule, only data should go across the PPP connection, not programs. If you load programs from the remote network, they must be moved across the PPP connection first before being loaded into memory on the client system. This slows down access significantly. If the program is installed on the client system's hard disk, the program can be loaded into memory directly from hard disk and only data packets traverse the PPP connection. In general, if an entire application must be run remotely, you should use a WinFrame remote control connection instead of a remote node connection.


Trumpet Winsock

See Also:

Configuring RAS Clients

Overview

The Trumpet Winsock TCP/IP stack can be installed on both 16-bit and 32-bit versions of Windows. As Windows 95 and Windows NT include built-in Winsock stacks, Trumpet Winsock is primarily used on Windows 3.1 and Windows for Workgroups 3.11. Trumpet can be used for situations where you want easy access to both a local IPX network and a remote WinFrame RAS IP network through Windows without having to disable your local network. Trumpet also has scripting capabilities that may be useful for unusual situations. Trumpet Winsock can be used on a network over a packet driver or over a Trumpet PPP connection to WinFrame's RAS. Once a TCP/IP connection is established with the WinFrame server, the 16-bit Remote Application Manager for Windows can be run to establish a remote control session on the WinFrame server. The following information describes how to install Trumpet Winsock for use with the 16-bit Remote Application Manager and WinFrame.

Requirements

Hardware Requirements

See Windows 3.1 and Trumpet Winsock requirements

Software Requirements

WinFrame 1.5 or higher
Windows 3.1 or Windows for Workgroups 3.11
Trumpet Winsock 2.1 or higher (available from http://www.trumpet.com.au)
Packet driver (if using Trumpet on a network LAN)

Installation

Trumpet Winsock can be installed in one of two ways: it can be installed as a PPP client for use with WinFrame RAS or it can be used with a LAN adapter using a packet driver.

A PPP to RAS configuration consists of two parts. The NT RAS server must first be installed on the WinFrame server. Next the Trumpet Winsock PPP client must be installed on the user's client system. The following section describes how to install and set up Trumpet Winsock as a PPP client that supports the IP protocol on the user's client system. To set up and install NT RAS on a WinFrame server, see the WinFrame RAS manual or refer to Configuring RAS Clients. When RAS is successfully installed, the Encryption Setting must be made. This must be set to either Require Any Authentication Including Clear Text or Require Encrypted Authentication. It cannot be set to Require Microsoft encrypted authentication. Make this change by configuring the Remote Access Server software in the Network applet under the NT Windows Control Panel on the WinFrame server.

Make sure you have Windows 3.1 or Windows for Workgroups 3.11 installed. If networking is installed on these clients, make sure you remove it. Refer to the Windows manuals for Windows installation and set up and the removal of networking in Windows. The use of other stacks on Windows with the Trumpet Winsock stack is beyond the scope of this document. If you are interested in doing this, see the Windows manuals and the Trumpet Winsock manual for details.

To Install the Trumpet Winsock stack for a PPP connection to WinFrame

1.	Create a directory called \TRUMPET on the Windows client and copy the TWSK21F.ZIP file into this directory. Unzip this file using PKUNZIP. You should have at least the following files in the \TRUMPET directory:

tcpman.exe, winsock.dll, hosts, services, protocol, sendreg.exe, setup.cmd, logon.cmd, bye.cmd, and trumpwsk.hlp, as well as some Trumpet TCP utilities.

You can download this file from various sources including http://www.trumpet.com.au.

2.	Once you have unzipped the Trumpet files, edit your AUTOEXEC.BAT and add C:\TRUMPET to the end of your path statement. For example: PATH C:\WINDOWS;C:\DOS becomes PATH C:\WINDOWS;C:\DOS;C:\TRUMPET.

Save the AUTOEXEC.BAT file and reboot the client system.

3.	Start Windows on the client and create a new Windows program group; for example, TRUMPET. Click New from the Windows Program Manager File menu to add a new program item. Set this item to C:\TRUMPET\TCPMAN.EXE. This is the Trumpet TCP Manager utility used to create connections.

4.	Double-click the Trumpet TCP Manager icon to start the TCPMAN.EXE program. The first time it runs, Trumpet set up will start automatically. If you need to get into this panel in the future, just click the Setup option under the File menu. In the setup panel, enter the IP address of your DNS server and domain name, if you have one. Check the Internal PPP box and set the SLIP port to the COM port to which your modem is connected. Leave your IP address, net mask, and IP gateway at 0.0.0.0. These values are supplied by the WinFrame server. Click OK to save. At this point you will have to exit and restart TCPMAN.EXE for the new values to take effect.

5.	When TCPMAN.EXE restarts, select PPP Options from the File menu. Check the Use Password Authentication Protocol (PAP) box. Enter your username and password for the WinFrame server so that you can logon to RAS. If you are using a domain user name, you have to append the domain name, separated by a back slash for the username. For example:

For a local WinFrame user:

Username:	BOBW
Password:	eraser

For an NT/WinFrame domain user:

Username:	DOMAIN\BOBW
Password:	eraser

Remember that you will have to grant RAS access to your user from the Remote Access Administrator in order to allow the user to logon.

6.	The default logon script that comes with Trumpet Winsock is not suitable for Windows NT or WinFrame RAS. To change it, start a DOS prompt and change into the \TRUMPET directory. Create a backup copy of the original LOGON.CMD file to LOGON.BAK by typing COPY LOGON.CMD LOGON.BAK.

When the backup copy is created, edit LOGON.CMD file using DOS EDIT or Windows NotePad. Change the LOGON.CMD to match the following:

# Trumpet Winsock 2.1 Logon.cmd
# Copyright (C) 1994,1995 Peter R. Tattam &
# Trumpet Software International Pty Ltd (TSI)
# All rights reserved.
# Unless TSI has given prior written consent to such use,
# no permission is granted to distribute or otherwise make available
# to the public modified versions of this script for commercial purposes.
# Any permitted distribution of modified versions of the script must
# retain the copyright notice at the start of this file and must clearly
# identify those parts of the file that have been modified.
#trace on
# set up some strings for dialing up
query $number "Enter your dial up phone number"
$modemsetup = "&c1&k3"
$prompt = ">"
$userprompt = "Accepted:"
$passprompt = "assword:"
$slipcmd = "slip"
$addrtarg = "our address is"
$pppcmd = "ppp"
$pppready = "PPP."
%attempts = 10
###############################################
# timeouts for various sections of the script
###############################################
#
# timeout for busy tone... adjust this until the BUSY string is detected.
#
%busytimeout = 10
#
# time between successive busy attempts.
#
%busywait = 30
#
# time to wait for a CONNECT string to be received
#
%connecttimeout = 60
#
# time to wait until DCD is detected
#
%on-linetimeout = 60
#
# time to wait for username & password prompts
#
%logontimeout = 60
#
# time to wait for server prompt to appear
#
%prompttimeout = 30
#
# time to wait for a SLIP address to be parsed
#
%addresstimeout = 30
#
#
#
#
#----------------------------------------------------------
#
# initialize modem
#
status "Initializing modem..."
output "atz"\13
if ! [input 5 OK\n]
 message "Modem is not responding"
 abort
end
#
# setup our modem commands
#
output "at"$modemsetup\13
if ! [input 10 OK\n]
 message "Modem is not responding"
 abort
end
#
# send phone number
#
%n = 0
repeat
 %n = %n + 1
 if %n > %attempts
  message "Too many dial attempts"
  abort
 end
 status Dialling $number...(attempt %n)
 output "atdt"$number\13
 %busy = [input %busytimeout BUSY]
 if %busy
  status "The line is busy...pausing for a while"
  sleep %busywait
  %ok = 0
 else
  %ok = [input %connecttimeout CONNECT]
 end
until %ok
input 10 \n
#
# wait till it's safe to send because some modem's hang up
# if you transmit during the connection phase
#
wait %on-linetimeout dcd
#

See the Trumpet Winsock manual for more information on how to customize and change the script further. You can set the initialization string for your modem in the LOGON.CMD file as well as any other modem or line settings by using Trumpet's scripting language. When you change the LOGON.CMD file, save it and exit the DOS session to get back to Windows.

8.	From the Dialer menu of TCPMAN.EXE, click the Logon selection. You are prompted for the phone number of the WinFrame RAS server; enter the phone number and press ENTER. The modem dials and connects to the WinFrame RAS server and TCPMAN logs on and creates a TCP/IP connection. Run Trumpet Ping to ping the WinFrame server to verify a connection.

To Install the Trumpet Winsock stack for use with a LAN adapter

1.	Make sure you have Windows 3.1 or Windows for Workgroups 3.11 installed. If networking is installed on these clients, make sure you remove it. Refer to the Windows manuals for Windows installation and set up as well as the removal of networking in Windows. The use of other stacks on Windows with the Trumpet Winsock stack is beyond the scope of this document. If you are interested in doing this, see the Windows manuals and the Trumpet Winsock manual for details.

2.	Create a directory called \TRUMPET on the Windows client and copy the TWSK21F.ZIP and WINPKT.ZIP files into this directory. Unzip these files using PKUNZIP. You should have at least the following files in the \TRUMPET directory:

tcpman.exe, winsock.dll, hosts, services, protocol, sendreg.exe, setup.cmd, logon.cmd, bye.cmd, trumpwsk.hlp, and winpkt.com as well as some Trumpet TCP utilities.

You can download these file from various sources including http://www.trumpet.com.au.

3.	When you have unzipped the Trumpet files, edit your AUTOEXEC.BAT and add C:\TRUMPET to the end of your PATH statement. For example: PATH C:\WINDOWS;C:\DOS becomes PATH C:\WINDOWS;C:\DOS;C:\TRUMPET

Save the AUTOEXEC.BAT file and reboot the client system.

4.	Start Windows on the client and create a new Windows program group; for example, TRUMPET. Click New from the Windows Program Manager File menu to add a new program item. Set this item to C:\TRUMPET\TCPMAN.EXE. This is the Trumpet TCP Manager utility used to create connections.

5.	Double-click the Trumpet TCP Manager icon to start the TCPMAN.EXE program. The first time it runs, Trumpet set up will start automatically. If you need to get into this panel in the future, click the Setup option under the File menu. In the setup panel, make sure both Internal PPP and Internal SLIP are NOT checked. Enter the IP address for your Windows client as well as the net mask and the default IP gateway. Next, enter the IP address of your DNS server and domain name, if you have one. Click OK to save. Exit TCPMAN.EXE and load your IP packet driver to use with WINPKT.

6.	You can either use just IP alone with your LAN adapter using a packet driver or you can use the ODIPKT.COM driver to link into your NetWare IPX ODI driver. Using the ODIPKT.COM driver will give you both IP and IPX connectivity on your network. Using a packet driver alone will give you only IP connectivity on your network. If your LAN adapter came with a packet driver, you may use it. The ftp site, ftp.crynwr.com, has packet drivers for many different network cards in the /drivers directory. If you cannot find a packet driver for your network card or you would rather use the ODI driver for your network card to get IPX as well as IP, you can get the ODIPKT.COM driver from many places on the web, including hsdndev.harvard.edu in the /pub/odipkt directory. Once you have obtained the correct packet driver, copy it into the \TRUMPET directory.

7.	If you are installing a packet driver for your LAN adapter, you must add the packet driver command and the Trumpet Winsock WINPKT command to the end of your AUTOEXEC.BAT. The packet driver command line must have the vector, irq, and port being used for the LAN adapter. For example the following would be added to the AUTOEXEC.BAT for a NE2000 adapter running on IRQ 2 port 300:

NE2000 0x60 2 0x300
WINPKT 0x60

If you are installing the ODIPKT.COM driver for use with your standard ODI driver, you must first install the Novell NetWare client with your ODI driver. This will give you IPX support. When done, you can edit your network batch file, usually STARTNET.BAT, to load the drivers in this order:

C:\NWCLIENT\LSL
C:\NWCLIENT\NE2000
C:\NWCLIENT\IPXODI
C:\TRUMPET\ODIPKT
C:\TRUMPET\WINPKT 0x69
C:\NWCLIENT\VLM

Here VLMs are being loaded, but you can use NETX instead if you wish. Your NET.CFG should be edited to load the Frame types in the right order and to set the Buffers and MemPool settings correctly. For example:

Link Support
Buffers 8 1586
MemPool 16384

Link Driver NE2000
Port 300
Int 2
Frame Ethernet_II
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3

When STARTNET.BAT loads, it should load IPX and the ODIPKT.COM driver. You can then start Windows and start TCPMAN.EXE to load TCP/IP. Run Trumpet Ping to ping the WinFrame server and verify a connection.

Usage

Once the client has IP support, either by use of Trumpet Winsock as a PPP client or directly on a LAN using a packet driver, the 16-bit Windows Remote Application Manager can be run and connect to any WinFrame server on the remote network via IP. Be sure to configure the terminals on the appropriate WinFrame servers for the network protocol that will be used. If using PPP and you wish to disconnect from the RAS server, click Bye from the Dialer menu of TCPMAN.EXE.

Troubleshooting

Why does my user logon fail to authenticate on the RAS server when I dial in via PPP?

This is caused either by not using a valid username on the WinFrame server or by not granting the username RAS access permissions. Refer to the WinFrame manuals on setting up users and granting them RAS access permissions.

The packet driver loads, but when I run TCPMAN in Windows it gives an error and says "TCP unable to load". What's wrong?

This is usually caused by either not using the correct vector, interrupt, or I/O port address when loading the packet driver, not using the same vector when loading WINPKT, or by having something wrong in your NET.CFG. If using the ODIPKT driver, make sure the Frame Ethernet_II frame type loads before the Frame Ethernet_802.3 frame type.


Integrated NetWare Password Support

Integrated NetWare password support allows a user to use one password to logon to WinFrame, Windows NT, NetWare 3.x, and NetWare 4.1x servers. Integrated password support synchronizes the WinFrame passwords with the NetWare password. When a user logs on, he enters his NetWare password. If the NetWare password is valid but differs from his password on the WinFrame server, the password on the WinFrame server is updated to match the NetWare password.

Note

NetWare UserIDs can be transferred from NetWare during the WinFrame installation, with the Migration Tool for NetWare, or with the NetWare User Access for WinFrame utility. See Migrating UserIDs from a NetWare Server for more information on using these utilities.

This feature can be enabled on a per-user basis in User Manager. Start User Manager and double-click on the user to be configured. The User Properties dialog box appears. Select the Config button. The User Configuration dialog box appears. Click on the NetWare button. The NetWare Logon Configuration dialog box appears. To enable integrated NetWare password support, enter the name of a NetWare 3.x server or NetWare 4.1x server running bindery emulation in the Default NetWare Server text box. This server is the password master that the WinFrame password is synchronized with. Deleting the NetWare Authentication Server name disables integrated NetWare password support.

For each domain that will use integrated NetWare password support, a domain administrator username and password must be entered in the Domain Admin section. This only needs to be done once for each WinFrame server or domain using integrated NetWare password support.


Migrating UserIDs from a NetWare Server

If you have a Novell NetWare 3.x or 4.x file server on your network, you can transfer (also referred to as migrating) the configured userids from the NetWare server to your WinFrame server. This makes it easy to create accounts on the WinFrame server by migrating the userids already configured for your NetWare network.

Note

You can only transfer bindery users from NetWare 3.x and 4.x servers. Users that exist outside of a NetWare server's bindery context cannot be transferred.

There are two ways to transfer users:

1.	The Migration Tool for NetWare (NWCONV.EXE). This utility moves all users and optionally files from a NetWare server to a WinFrame domain controller. Refer to Chapters 9 through 12 of the Services for NetWare Networks manual for more information.

2.	NetWare User Access for WinFrame (NW2NT.EXE). This utility presents you with a list of users from which you can select users to be granted access to the WinFrame server. The user's password on the WinFrame server is automatically synchronized with the user's password on the NetWare server. Password synchronization only works for NetWare bindery users.

While the Migration Tool for NetWare utility transfers either all the users or none of the users, the NetWare User Access for WinFrame utility allows you to transfer only the users that you select. However, the NetWare User Access for WinFrame utility does not have all of the other options available in the Migration Tool for NetWare: trial migrations, transferring files, using mapping files, etc. Before using the NetWare User Access for WinFrame utility, you must have Gateway Services for NetWare installed. See Chapter 2, "Setting Up the Gateway Service and NWLink", in the Services for NetWare Networks guide for more information.

To Grant Selected NetWare Users Access to the WinFrame Server with the NetWare User Access For WinFrame Utility

1.	If you want to grant NetWare users access to the entire domain, you must logon as an Administrator to the WinFrame or Windows NT computer acting as the domain controller. If you logon to a server in the domain that is not a domain controller, you can only grant NetWare users access to that WinFrame server.

2.	Double-click on the NetWare User Access for WinFrame icon in the Administrative Tools group. The Select NetWare Server dialog box appears.

3.	Select a NetWare server from the server list. You must then logon with a NetWare administrator username and password. The NetWare User Access for WinFrame window is displayed.

Two lists of usernames are displayed. The Access Disabled list contains usernames on the NetWare server that do not exist on the WinFrame server. The Access Enabled list contains usernames that exist on both systems and are configured for integrated NetWare password support with the selected NetWare server.

4.	Select the usernames in the Access Disabled list you want to be granted access to the WinFrame server and click on the Add button.

5.	Click on Apply to commit the changes. A dialog box displays the status of the transfer.

The selected users are created on the WinFrame system. The WinFrame accounts are configured for integrated NetWare password support and initially have no password. When a user logs on, they are authenticated on the NetWare server, and then their WinFrame password is synchronized with their NetWare password. If a username already exists on the WinFrame system, it is added to any groups that the corresponding NetWare user is a member of.

6.	When the transfer is completed, you are given the option of viewing the log files. Click OK.

7.	Click Exit to finish the process.

The log files created by the NetWare User Access for WinFrame utility are stored in the current user's home directory as Error.LOG, Summary.LOG, and LogFile.LOG.

If you have not done so already, you will now need to set the administrator account that will be used to update passwords when a user's NetWare password changes. This process only needs to be done for one of the migrated users; the others will inherit their settings. The administrator account is only used for changing passwords and can be any account that has administrator privileges.

To Configure an Administrator Account for Changing Integrated Domain Passwords

1.	From the Program Manager, run User Manager for Domains

2.	The NetWare accounts were migrated to a specific WinFrame server, choose Select Domain from the File menu and enter the name of the server the migrated NetWare accounts are on.

3.	Double-click on one of the migrated accounts to display the User Properties window.

4.	Click the Config button.

5.	Click the NetWare button.

6.	Enter the user name and password of an account in this domain (or on this server) that has administrator privilege.

7.	Click the OK button in the NetWare Logon Configuration window.

8.	Click the OK button in the User Configuration window.

9.	Click the OK button in the User Properties window.

10.	Exit User Manager for Domains.

Note

No passwords are created for the new accounts. If the policy for the WinFrame administrator account is set to only allow passwords of a set length, the migration process will not work. To verify this setting, follow these steps:

1.  Go to User Manager for Domains.

2.	Change to the server you will be transferring the accounts to, if it isn't already selected.

3.	Select the Administrator account you will be using for the migration process by clicking on it only once.

3.  Select Account from the Policies menu.

4.  Under Minimum Password Length, ensure that Permit Blank Password is selected.

Troubleshooting

The following is a list of error messages you may encounter when logging on, and what to do to correct them.

"The system could not log you on. Make sure your username and domain are correct, then type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps Lock is not accidentally on."

This message really does not have anything to do with the password synchronization feature. It occurs because the username, domain or password was entered incorrectly in the login dialog box.

"The default domain administrator is not configured correctly. Notify your system administrator. Now attempting to logon user UserName on domain DomainName."

You can bypass the error message and continue to login to the system.

This message occurs because the administrator account's password or ID is incorrect in NetWare Logon Configuration. To change the administrator's ID or password:

1. In the Administrative Tools group, double-click on User Manager for Domains.

2. Double-click on any user.

3. Click on the Config button at the bottom of the next screen.

4. Click on the NetWare button.

5. Enter the new password in the NetWare Authentication Server field and press Enter.

It is important to note that the password fields are case sensitive and must match the actual administrator account's password (which is also case sensitive). For example, if the administrator account "Administrator" has a password of "AbCdEfG", "AbCdEfG" must be entered in the NetWare Logon Configuration password fields. If case sensitivity is not maintained, the error message will be displayed when the user logs in.

"NetWare password is invalid on server ServerName. Now attempting to logon user UserName on domain DomainName."

This is seen when the password has changed on the NetWare server. If the password is valid on this domain, the user will be logged onto WinFrame and will then be prompted for his/her NetWare password.

"Logon failed. The NetWare password is valid; however, an error occurred when attempting to update the password for user UserName on domain DomainName" followed by "The system cannot log you on (6). Please try again or consult your system administrator."

These messages occur when the NetWare password is out of sync with the WinFrame password and the user has attempted to login with the NetWare password. This usually indicates that the account specified in NetWare Logon Configuration is not an administrative account. This error may also be generated when the "Minimum Password Length" on WinFrame is set to require more characters than the length of the current NetWare password. It is also possible that the Netware password is greater than 14 characters, the maximum allowed by WinFrame.

"Invalid NetWare user on server ServerName. Now attempting to logon user UserName on domain DomainName."

This message occurs because the user does not exist in the specified NetWare server's bindery. It is important to note that WinFrame's password synchronization only works with bindery users. NetWare 4.x NDS users that do not exist within the specified NetWare server's bindery context will receive this message. To remedy this message it is necessary to either add the user to the specified NetWare server's bindery or specify a different NetWare server in User Manager for Domains.


Load Balancing and Application Publishing

This section contains the following topics:

ICA Browsing and Error Handling Overview

Frequently Asked Questions About Load Balancing

Configuring a Load-Balanced Windows NT Desktop (Single Server Image)

Replicating Gateway Services for NetWare Settings Between WinFrame Servers in a Load-Balanced Server Farm

Load Balancing and Application Publishing Across a Firewall

Load Balancing and Application Publishing Across Domain Trusts with WinFrame 1.7

Load Balancing Registry Entries

See Also:

Browsing for a WinFrame Server

Configuring a Firewall for TCP/IP WinStations


ICA Browsing and Error Handling Overview

ICA Browsing is at the heart of WinFrame license pooling, load balancing, and application publishing.

There is a separate ICA Browsing system in operation for each network protocol (TCP/IP, IPX/SPX, or NetBIOS) supported by WinFrame servers on a subnetwork. Each ICA Browsing system is independent of the other systems. If a WinFrame server supports a network protocol then it can support license pooling; you must configure network WinStations for that network protocol to support user logons and published applications on that server. If a server has two network cards, it belongs to two subnets.

For example, if two of the three servers in a subnetwork support IPX/SPX and all three servers in the subnetwork support TCP/IP, and each server has 15 licenses (all of which are pooled), there are 45 pooled licenses available for TCP/IP connections but only 30 pooled licenses available for IPX/SPX connections. If TCP/IP WinStations are configured on only two of the three servers, then only those two servers can support TCP/IP user logons or published applications, up to a total of 45 users. The total number of users includes all connection types; for instance, with all 45 licenses in use you might have 30 TCP/IP users, 10 IPX/SPX users, and 5 Dial-In users on at one time, and 20 TCP/IP users, 15 IPX/SPX users, and 10 Dial-In users on at another time.

ICA Browsing System Description

The ICA Browsing system contains two categories of servers:

The Master Browser. The Master Browser is a server that is selected by an election process (called Master Browser Election) to contain the master list of available Citrix servers (WinFrame or pICAsso servers), published applications, and pooled licenses. At any time, there is only one Master Browser per protocol (TCP/IP, IPX/SPX, or NetBIOS) per subnet. If several protocols are supported on a subnet, the Master Browsers for each protocol can be different computers. License pooling is not supported across subnets; however, ICA Browsing can be configured to allow Citrix server logons, load balancing, and published application access across subnets.

Member Servers. Member Servers are the other WinFrame servers on the network that have not been elected as the Master Browser. Member servers periodically report information about their available connections, published applications, and pooled licenses to the Master Browser. If a network protocol is not configured on a server, that server is not a member server of the ICA Browsing system for that protocol. Citrix server logon access is controlled by WinStation Configuration; the number of concurrent users for a connection type is limited by the number of configured WinStations as well as free licenses.

The Master Browser collects and maintains information from Member Servers in a database on the Master Browser for use by the Citrix ICA Clients for locating servers and published applications, by License Management support, and by Application Publishing support. The Master Browser does not initiate contact with the Member Servers, but merely collects information provided by the Member Servers.

Each Member Server reports its server data to the Master Browser periodically (the default interval is every 30 minutes), or whenever a change occurs, such as a user logging on or off at a client or an administrator adding a new published application or changing the pooled license count.

The Master Browser retains the information reported by a server in its database for up to 30 minutes, with the exception of license information which is retained for 48 hours.

Whenever there is a browser election and a new Master Browser is elected, the server information database on the new Master Browser starts out empty and all information from the database on the previous Master Browser is lost. Each Member Server automatically updates the new Master Browser within a few seconds after the election.

If a Member Server goes down or off-line, its pooled licenses time out after 48 hours or at the next master browser election, whichever comes first. Member Server information used for server browsing or application publishing times out after 30 minutes or at the next master browser election, whichever comes first.

To determine which server is the current master browser for each protocol, type QUERY SERVER at the command prompt and look for the letter M after the server address. The letter G indicates a server is acting as an ICA gateway.

Master Browser Elections

Master Browser elections can be initiated by a client (WinFrame PC Client, Citrix ICA Client, or ICA device such as a Wyse Winterm), by a Member Server, or by a Master Browser. They are usually caused by the Master Browser going down or off-line. Whenever there is a browser election and a new Master Browser is elected, the server information database on the new Master Browser starts out empty and all information from the database on the previous Master Browser is lost.  Each Member Server automatically updates the new Master Browser within a few seconds after the election.

A client will initiate a Master Browser election if it does not receive a response from the Master Browser to a request such as a request for the server or published application list or a request to map a server name to a network address.

A Member Server will initiate a Master Browser election if it does not receive an acknowledgement from the Master Browser after sending information to the Master Browser or requesting information from the Master Browser.

A Master Browser will initiate a Master Browser election if it detects the presence of another Master Browser on the network (this is rare).

Handling Fault Conditions

In most cases, a single server (which can be the Master Browser or a Member Server) fails or is brought off-line for maintenance. In this case, the 30-minute timeout for application publishing and server enumeration ensures that momentary interruptions (such as a quick reboot after a system crash) have a minimal impact on the overall system. Because many installations depend on license pooling to support large numbers of users with server farms, the pooled license timeout has been made longer (48 hours) to avoid impacting system throughput if a server needs to be replaced or requires more extensive maintenance. However, if the Master Browser goes down or off-line, the next user logon or logoff will force a Master Browser election causing the licenses associated with the downed server to disappear.

Because licenses are only used to validate logons, active user sessions are not terminated if the license count on the network goes below the numer of currently logged on users; however, new users will not be able to log in until the number of active user connections goes below the number of available licenses, freeing up licenses.

Citrix does not recommend placing all the pooled licenses on a single server. Although it is unlikely that a Master Browser election would occur while the server containing the pooled licenses is down, if it does occur all those licenses would be lost until that server comes on-line again.


Frequently Asked Questions About Load Balancing

Can the Web Clients be used to connect to a WinFrame Load Balanced Server Farm?

Yes. Follow the instructions in Chapter 23 of the System Guide to create a published application for the server farm. When finished, select Write ICA File from the Application menu (in Application Configuration). Select the resolution and color depth you want to use and click OK. Type a file name and click OK. Now move the ICA file you just created to your Web server. You may also want to modify the ICA file to contain the IP address of a second server in the farm for redundancy. Under the [WFClient] section, insert TcpBrowserAddress2=address where address is the IP address of a different server in the farm than the one listed in TcpBrowserAddress. The second address is only used by WinFrame 1.7 clients. See ICA File Syntax for more information about the syntax of ICA files.

Can WinFrame 1.7 pool licenses across several servers without the load balancing option pack?

Yes. Servers that belong to the same subnet can share licenses. Licenses cannot be pooled between subnets. There is one master browser for each subnet that all member servers ask for licenses. See the topic "ICA Browsing and Error Handling Overview" for more information about the ICA Master Browser.

What statistics should be monitored to determine how to adjust the load balance calculation?

Use the QUERY SERVER servername /LOAD and QUERY SERVER servername /STATS commands on each server with one user connected, and then with multiple users connected to determine approximately how the values change for each successive connection. These commands must be run from a WinFrame server on which you have administrator privileges. Once you have a "baseline" established, use Performance Monitor to monitor specific factors. For more information refer to Chapter 19, "Performance Monitor", and Chapter 23, "Application Publishing", in the System Guide.

Can users reconnect to published applications?

Yes. The WinFrame 1.7 ICA Browser allows sessions disconnected from published applications to reconnect. The ICA Browser contains a list of disconnected sessions and associates a client name and published application name with a specific server so if the same client computer attempts to reconnect to the same published application, it will be directed to the server it was disconnected from.

The user must disconnect the session "gracefully." To do so, press Shift+F3 (or another hotkey assigned to close a remote application) and then click OK in the dialog box that is displayed. The user must then logon with the same username and the same CLIENTNAME (the name for the client computer specified in WFNAME.INI) to get reconnected to the same session. If the user tries running the published application from a different client computer, he or she will be connected to the least busy application server, which may or may not be the server with the disconnected session.

If this is not working properly, verify that the session was disconnected properly by typing
query server /disc at a command prompt to display a list of the currently disconnected sessions. If the disconnected session is not listed, the user did not disconnect properly.


Configuring a Load-Balanced Windows NT Desktop (Single Server Image)

To configure a group of WinFrame servers to share the load of clients logging on to the Windows NT desktop, configure a published application with no command line specified. This is also referred to as a Single Server Image. For general information about published applications, see Chapter 23, "Application Publishing", in the System Guide.

To Configure a Load-Balanced Windows NT Desktop (Single Server Image)

1.	While logged on to a WinFrame server, run Application Configuration from the Administrative Tools group in Program Manager.

2.	Press Insert to create a New Published Application.

3.	Type a name for the application and click the Next button.

4.	Choose Explicit if you want a username and password to be entered before the application is run or Anonymous if you want the application to be run without a username and password (users are logged on using the anonymous AnonXXXX accounts).

5.	Do not enter a Command Line or Working Directory when prompted to do so. Click the Next button without entering anything on this screen.

6.	If you want to hide the title bar of Program Manager check the box for hiding the application title bar and then click Next.

7.	If you chose Explicit in step 4, choose the users and/or groups that will be allowed to use this Published Application.

8.	Add other servers you wish to make available for this Published Application.

9.	Click the Finish button to create the Published Application (the Windows NT desktop).


Replicating Gateway Services for NetWare Settings Between WinFrame Servers

The preferred NetWare server setting in Gateway Services for NetWare is user-specific. Once all users have logged onto a single WinFrame server, their settings can be replicated to other WinFrame servers by copying the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NWCWorkstation\
Parameters\Option

To Replicate Gateway Services for NetWare Settings

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions.

1.	Run the Registry Editor by choosing Run from the File menu in the Program Manager and typing REGEDT32.EXE.

2.	In the Registry Editor, find the Registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NWCWorkstation\

Parameters\Option

3.	From the Registry menu, select Save Key and type a name for the output file.

4.	Copy this file to the other servers in the server farm.

5.	On the other servers in the farm, run Registry Editor and follow these steps.

A.	Find the Registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
NWCWorkstation\Parameters\Option

B.	From the Registry menu, select Restore and type the name used for the output file in Step 4 above.


Load Balancing and Application Publishing Across a Firewall

The ICA Browser service uses UDP port 1604. ICA browsing is used by the ICA client to obtain a list of available Citrix ICA servers. Citrix ICA Server farms use the ICA browser service to balance ICA client connections between servers.

The firewall must be configured to allow inbound UDP port 1604 connections to ICA servers for load balancing and ICA server browsing to function correctly. If your firewall uses address translation on TCP/IP packets, you will also need to install Hotfix SE170016.

Warning

Allowing untrusted access to the ICA Browser service entails some security risk. Only configure the firewall to pass ICA Browser data if Load Balancing and server browsing across a firewall is essential.

Note

You cannot share licenses across a firewall or subnet.

Firewalls use IP address translation to convert public (Internet) IP addresses into private (Intranet) IP addresses. Public IP addresses are called "external" addresses because they are external to the firewall, whereas private IP addresses are said to be "internal" addresses.

When a WinFrame client is configured for an IP "server location", it sends a directed UDP datagram to the server location IP address using port 1604. For communication to be successful between a WinFrame client and server, the firewall must be configured so it will pass UDP port 1604 packets. The server location is configured in Remote Application Manager by selecting Settings from the Options menu.

If a server location is specified, the WinFrame client contacts that server to determine the address of the ICA master browser. When a user creates a new entry, the list of available servers and published applications is retrieved from the ICA master browser. When the client connects by server or published application name, the ICA master browser returns the address of the desired server or published application.

Prior to Hotfix SE170016, the server specified as the server location could only return the internal IP address of the ICA master browser. Clients would be unable to communicate with the ICA master browser using the internal IP address because it was usually an invalid Internet address. With this hotfix, the server specified as the server location can return the external address of the ICA master browser to the WinFrame client. Likewise, when the client is connecting using a server or published application name, the ICA master browser returns the external IP address of the desired server or published application.

This hotfix must be installed on all WinFrame servers that will be contacted by external clients. It must also be installed on the server acting as the ICA master browser. For server farms, the ICA master browser must be running on one of the WinFrame servers in the farm and all the servers in the farm must be visible from outside the firewall.

Each WinFrame server must have its external address configured with the master browser. The external address will be referred to as the WinFrame server's "alternate address". A utility, ALTADDR.EXE, that configures alternate addresses for each server is included with this hotfix. See "ALTADDR Usage" below for more information. ALTADDR stores alternate addresses in the Registry under the key:

HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet \Services \ICABrowser \Parameter \AlternateAddress \TCP

Alternate addresses are only supported for the TCP protocol.

Once the servers are configured, the external clients must be configured to request the alternate address from a server inside the firewall. Version 3.00.329 or later of the WinFrame Client is required in order for the client to request an alternate address from the server. At the time of this writing, the latest clients are DE000329, WE000329, and NE000329 (DOS, Win16, and Win32, respectively).

To configure the client, edit the APPSRV.INI and add the line:

UseAlternateAddress=1

to the "[WFCLIENT]" section. This setting is a flag that instructs the client to request an alternate IP address. If this flag is added to the [WFCLIENT] section, the client will request the alternate IP address for all sessions. It will also request the alternate IP address when browsing WinFrame servers and published applications. This allows the client to browse across firewalls even when IP address translation is enabled on a firewall.

It is also possible to configure the client so that it requests the alternate IP address on a case-by-case basis. Instead of adding the "UseAlternateAddress=1" flag to the [WFCLIENT] section, add it to each entry's section in APPSRV.INI. This is useful for situations where clients primarily connect to servers on the local LAN, but ocassionally connect to a specific server across the Internet. In this scenario, the client will be able to browse for servers on the LAN but must know the actual address of one of the servers accessed across the Internet. That server will function as the "server location" server, and will provide the address of the ICA master browser.

You can also add the UseAlternateAddress=1 flag to the [WFCLIENT] section, and then override the setting for those server connections that are on the same side of a firewall as the client. This is useful in a scenario where clients primarily connect to servers over the Internet but occasionally connect to servers on the local intranet. Add the UseAlternateAddress=0 to each connection section to override the global setting.

ALTADDR

This utility is used to query and set the alternate (external) IP address that a WinFrame server will return to clients who request it. The alternate IP address is an external address used by WinFrame clients outside a firewall.

Syntax

ALTADDR [/SERVER:servername] [/SET alternateaddress]

ALTADDR [/SERVER:servername] [/SET adapteraddress alternateaddress]

ALTADDR [/SERVER:servername] [/DELETE]

ALTADDR [/SERVER:servername] [/DELETE adapteraddress]

Options

/SERVER:servername

Specifies the WinFrame server on which to set an alternate IP address; otherwise the current WinFrame server is used.

/SET

Sets alternate IP addresses. If adapteraddress is specified, alternateaddress is assigned to that network adapter only.

/DELETE

Deletes all alternate addresses on the specified server. If adapteraddress is specified, deletes only the alternate address for that adapter.

/V (verbose)

Displays information about the actions being performed.

/?

Displays the syntax for the utility and information about the utility's options.

Examples

Example 1: Set the alternate address to 1.1.1.1 for the current server:

altaddr /set 1.1.1.1

Example 2: Set the alternate address to 1.1.1.1 on the network interface with adapteraddress 2.2.2.2:

altaddr /set 2.2.2.2 1.1.1.1

Example 3: Delete all alternate addresses on the currrent server.

altaddr /delete


Load Balancing and Application Publishing Across Domain Trusts

If you have a master domain model where a resource domain trusts an accounts domain and a WinFrame server farm resides in the resource domain, users who authenticate via the account domain may receive the following error message:

"The system could not log you on. Make sure your username and domain are correct, then type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps lock is not accidentally on."

This is a known issue for WinFrame Version 1.7. There are two workarounds at present:

1.	Establish a two-way trust between the domains.

2.	Have the WinFrame server farm reside in the accounts domain.


Load Balancing Registry Entries

The following Registry entries are configurable using the Adjust Load Balancing dialog in the Application Configuration program. It is suggested that you only use that program for modifying these values. They are listed here for completeness.

AppName	REG_MULTI_SZ	One or more text strings

Specifies a list of one or more application names used for load balancing.  The application name can be thought of as a server farm name.  To configure load balancing , two or more systems must be configured with the same application name.  The application name can appear in the client's server list along with the other WinFrame servers.  When the client selects an application name, the master browser returns the WinFrame server address with the least load, based on the following.

Weighting Factor	Limit	Description
BalanceWinStations	Configured WinStations	Number of free WinStations
BalanceUserLicenses	BalanceMaxUserLicenses	Number of free user licenses
BalancePageFile	BalanceMinPageFile	Size of remaining paging file
BalancePageFaults	BalanceMaxPageFaults	Number of page faults
BalanceMemoryLoad		Memory load level
BalanceProcessorBusy		Processor load
BalanceBias	REG_DWORD	0 - 0xffffffff	(0 = default)

After all load balance calculations are done, BalanceBias is added to the resulting load level. An idle system will have a very small load level, a busy system a larger load level. By specifying a positive number here, a system can be made to look busier than it actually is. By specifying a negative number (i.e. 0xfffffff0) a system can be make to look less busy.

BalanceMaxPageFaults	REG_DWORD	0 - 0xffffffff	(1000 = default)

Specifies the maximum number of page faults used for load balance calculations.

BalanceMaxUserLicenses	REG_DWORD	 0 - 0xffffffff	(10 = default)

By changing this value, the maximum number of user licenses used for load balance calculations can be limited. Load balance calculations use the lesser of BalanceMaxUserLicenses and the number of installed user licenses. Load balancing will never select a system that does not have at least one available user license.

BalanceMemoryLoad	REG_DWORD	0 - 1000	(100 = default)

Specifies the memory load weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The memory load is calculated by the following algorithm:

if	(available memory pages < 100) then
memory load = 100 * memory load ratio
else
memory load = (100 - ((available memory pages - 100) / 10)) * memory
load ratio

Increasing BalanceMemoryLoad gives more "weight" to memory load in computing the load level. Setting this value to 0 causes load balancing to ignore memory load.

BalanceMinPageFile	REG_DWORD	 0 - 0xffffffff	(500 = default)

Specifies the minimum number of bytes that must be remaining in the paging file for load balancing to select the system.

BalancePageFaults	REG_DWORD	0 - 1000	(100 = default)

Specifies the page fault weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The page fault load is calculated by dividing number of page faults by BalanceMaxPageFaults and multiplying by the paging file ratio. Making BalancePageFaults higher gives more "weight" to page faults in computing the load level. Setting this value to 0 causes load balancing to ignore page faults.

BalancePageFile	REG_DWORD	0 - 1000	(10 = default)

Specifies the paging file weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The paging file load is calculated by dividing number of free bytes in the paging file by the total number of bytes in the paging file and multiplying by the paging file ratio. Making this number higher gives more "weight" to the paging file in computing the load level. Setting this value to 0 causes load balancing to ignore the paging file. Load balancing will never select a system that does not have at least BalanceMinPageFile bytes left in the paging file.

BalanceProcessorBusy	REG_DWORD	0 - 1000	(100 = default)

Specifies the processor weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The processor load is calculated by multiplying by the processor busy percentage by the processor busy ratio. Increasing this value gives more "weight" to processor load in computing the load level. Setting this value to 0 causes load balancing to ignore the processor load.

BalanceUserLicenses	 REG_DWORD	0 - 1000	(10 = default)

Specifies the user license weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The user license load is calculated by dividing the number of free user licenses by the number of installed user licenses and multiplying by the user license ratio. The maximum number of user licenses used for this calculation can be set by changing BalanceMaxUserLicenses. Increasing BalanceUserLicenses higher gives more "weight" to the number of free user licenses in computing the load level. Setting this value to 0 causes load balancing to ignore the number of free user licenses. Load balancing will never select a system that does not have at least one available user license.

BalanceWinStations	REG_DWORD	0 - 1000	(10 = default)

Specifies the WinStation weighting factor. Each of the weighting factors are divided by the sum of the weighting factors to arrive at ratios that are used to compute the system load level. The WinStation load is calculated by dividing the number of free WinStations by the number of configured WinStations and multiplying by the WinStation ratio. Increasing this number gives more "weight" to the number of free WinStations in computing the load level. Setting this value to 0 causes load balancing to ignore the number of free WinStations. Load balancing will never select a system that does not have at least one available WinStation.


How To
How To ...

This section contains How To information on installing licensing add-ons, configuring terminals and WinStations, administering users, WinStations, and processes.


Creating User Accounts on WinFrame

To logon to WinFrame, you must have a userid. The userid can be created on the WinFrame server or on the domain. If a user is configured for use on a particular WinFrame server, that user can logon and use only that WinFrame server. If the userid is configured on the domain, the user can logon to any WinFrame or Windows NT system that is in the domain. This flexibility allows users to logon from any system on the network. If desired, access can be restricted to specific WinFrame servers or it can be granted across the network domain. If you have not already done so, see Chapter 2, "Setting Up a WinFrame Environment", in the Solutions Guide for a more detailed discussion of local and domain user accounts. Below are quick instructions on adding both types of users to your WinFrame server.

You can also migrate NetWare UserIDs to your WinFrame server. This can be done during WinFrame installation, with the Migration Tool for NetWare, or with the NetWare User Access for WinFrame utility. Refer to Migrating UserIDs from a NetWare Server for more information on using these utilities.

To Configure Local User Accounts on a Particular WinFrame Server

1.	As an Administrator, logon to the WinFrame console and run the User Manager for Domains Utility.

2.	Once in the User Manager, click the Select Domain option from the User menu. When the Select Domain dialog box appears, type \\wfservername, where wfservername is the name of the particular WinFrame server for which the user will be configured. Click the OK button in the Select Domain dialog box to set the User Manager to that WinFrame server.

3.	The User Manager shows only the users configured for that particular WinFrame server. By default, only administrator and guest logons appear. The administrator can create new user logons by clicking the New User option from the User menu. When adding a new user, click the Profile button to set the home directory and Profile file name for the user. The home directory is where the user's files and .INI files are stored. The Profile file name is where the user's desktop settings are saved. This can be local on the WinFrame server or anywhere on the network to which the user has access. Click the Add button when done to save the new user.

Note

Users MUST have at least a home directory in order to run applications on WinFrame. Many applications will cause errors if users do not have unique home directories to which they can save temporary files and save application documents.

4.	Once the user is created for that particular WinFrame server, the user can logon and use the WinFrame server.

To Configure Domain User Accounts on a Network Domain

1.	You must have a domain controller set up and running on your network. This can be either a WinFrame server or a Windows NT server. Refer to Chapter 4, "How Network Security Works", in the Concepts and Planning manual for more information about domain controllers.

2.	As a domain administrator (not a local administrator), logon to the WinFrame console and run the User Manager for Domains Utility.

3.	In the User Manager, click the Select Domain option from the User menu. In the Select Domain dialog box, select the name of the domain you wish to create users for. When done, click the OK button in the Select Domain dialog to set the User Manager to that network domain.

4.	The User Manager shows the users configured for the network-wide domain. The administrator can create new user logons by clicking the New User option from the User menu. When adding a new user, click the Profile button to set the home directory and profile file name for the user. The home directory is where the user's data and INI files are stored. The profile file name is where the user's desktop settings are saved. Both the home directory and profile file should be on the network so the user can logon to any WinFrame server on the network and access his/her home directory and profile. If you wish, you can place these on the domain controller and then Net Share those directories so that users can access them on the network. If desired, you can specify separate Windows NT and WinFrame profiles if you want users to have different profiles for Windows NT logons and WinFrame logons. Click the Add button when done to save the new user.

Note

Users MUST have at least a home directory in order to run applications on WinFrame. Many applications will cause errors if users do not have unique home directories to which they can save temporary files and application documents.

5.	To allow a WinFrame server domain access you must add the server to the domain. Logon to the WinFrame server as an administrator. Run the Network application from the Control Panel and add the WinFrame server to the domain. Do this for each WinFrame server that domain users will logon to. This can be done during or after installing WinFrame. See Chapter 15, "Server Manager", of the System Guide for more information on adding and configuring your WinFrame server for domain access.

6.	Users can now logon and create remote control sessions on any WinFrame server on the network unless access is restricted to particular WinFrame servers. Refer to Chapter 13, "User Manager for Domains", of the System Guide for more information on restricting access.


General Installation of Applications on WinFrame

See Also:

Application Integration in the Solutions Guide

Application Performance Tuning

Does WinFrame support Windows applications that require VxDs?

While logged in to WinFrame and running an application stored on another server, a network error caused my application to crash and display a Dr. Watson error of type (0xC0000005). None of the WinFrame users were then able to access the application. Why?

I can't seem to run programs stored on a mapped drive when configured as Initial Applications in Remote Application Manager.

WinFrame is based on the Microsoft Windows NT Server Version 3.51 operating system, which is already designed to support multiple users for file and print services. WinFrame is different in that multiple users can run applications on the WinFrame server itself, instead of just accessing file and print services as with Windows NT. This difference means special care needs to be taken to keep settings specific to each user separate from other users and the system itself. Knowing how WinFrame handles these different settings will help you diagnose and fix any applications that do not work correctly when first installed.

Most applications can be used with WinFrame operating system to provide the same functionality as they would under the operating system they were designed for. WinFrame supports Windows 32-bit applications, Windows 16-bit applications, DOS text applications, DOS graphical applications, OS/2 text applications, and Posix applications. DOS graphical applications are supported on the console only. ICA WinStations will not support DOS graphics programs, only DOS text programs. OS/2 programs that make use of the OS/2 graphical user interface (GUI) are not supported on either the console or on the ICA WinStations. OS/2 text applications, however, are supported on both the console and the ICA WinStations. WinFrame's flexibility comes with (in most cases) no additional management procedures.

Separating System and User Settings

For applications to work properly with multiple simultaneous users, each user must have their own copy of the application's configuration settings. For 16-bit Windows applications (applications designed for Windows 3.x and Windows for Workgroups) and some 32-bit Windows applications, these settings are stored in .INI files. For 32-bit Windows applications (applications designed for Windows 95 and Windows NT), these settings are stored in the Registry-a centralized database of user, application, and computer-specific configuration information.

By default, all users use the directory \USER\DEFAULT on the WinFrame server as their home directory. For most applications to work properly, you must assign a separate home directory to each user using User Manager for Domains. See the Managing Profiles section of Chapter 13 in the System Guide for more information on home directories.

Installing an Application

Making applications multi-user accessible usually requires no additional effort, but for this process to work the applications need to be installed properly. Installation of DOS and OS/2 text applications should follow the standard installation procedure for those applications. Check the Solutions Guide for information on specific DOS or OS/2 text applications. There are three ways to install Windows applications: user-specific, network, and user-global.

A User-specific installation is when an application is installed by a specific user for their own use only. The default installation is user-specific. Any .DLL, .INI, or other files the application tries to place in the default WINDOWS directory are installed to that user's home WINDOWS directory. Even if the application is installed to a network or shared directory, other users may not have access to all the .DLLs and .INI files needed to run the application, and must do a user-specific install for themselves. In short, a separate install must be done for each user who wants to use the application.

Because doing a separate user-specific installation for many individual users can be a time consuming process, many applications offer the option of doing a network installation. This process usually just copies the installation diskettes or CD-ROM files to a common directory on the network. Individual users can then change to that directory and run a SETUP or INSTALL utility, which copies the required .DLL and .INI files to that user's home WINDOWS directory. Network installations will work with WinFrame. While it does use less space on the WinFrame server than multiple user-specific installations, it still requires a separate process be run for each user.

The third (and preferred) installation method is a user-global installation. With this method, an application is installed only once by an administrator and can then be run by anyone who logs on to that WinFrame server. To do a user-global installation type CHANGE USER /INSTALL at a command prompt before installing the application. This ensures that the .INI and .DLL files are installed to the %SYSTEMROOT% directory instead of the user's home WINDOWS directory. After the installation is complete, type CHANGE USER /EXECUTE to restore .INI file mapping. Now, when a user starts the application for the first time, the required .INI and .DLL files are automatically copied to the user's home WINDOWS directory. For a detailed discussion of the difference between install mode and execute mode and step-by-step instructions for installing applications, see Application Integration in the Solutions Guide.

Most 32-bit Windows applications install in a user-global fashion by default, even when CHANGE USER /INSTALL is not run because they make use of WinFrame's Registry, where each new user can have his/her own Registry settings. 16-bit Windows applications make use of INI files so they must be installed with CHANGE USER /INSTALL in order for multiple users to access them. It is recommended that you always install any Windows application, whether 16-bit or 32-bit, with CHANGE USER /INSTALL. Make sure to revert to execute mode when you are finished installing the application, or any changes will be propagated to all users.

If you need to determine if the system is in execution or installation mode, type CHANGE USER /QUERY at the command prompt.

Troubleshooting

The first step in troubleshooting is to make sure the user has his own home directory. To do so, logon with that userid and start a DOS session. If the DOS session places you in the \USERS\DEFAULT directory, you must create a unique home directory for that user. See the section Configuring Existing Users to Use Separate Home Directories above for instructions on configuring a home directory for a user.

How can I manually force a user's .INI files to be updated?

If you manually edit a user's WIN.INI or SYSTEM.INI files, the date of the file may be newer than the system's, preventing the update. To force an update in this case, delete the file INIFILE.UPD from the user's WINDOWS directory. When this file is deleted, all .INI files listed in HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\IniFiles are updated (either replaced or merged, depending on the flags set). The next time the user logs on, INIFILE.UPD will be recreated.

To replace a single .INI file, delete it from the user's WINDOWS directory. The next time the user runs a program that access that .INI file, it will be automatically copied from the WinFrame system directory.

Is it possible to use a different name for the user's WINDOWS directory?

Yes. See the topic Changing the Default name of Users' Windows Directories.

Periodically when using an application I get an error from the application that the hard disk or some group of files is corrupted or missing. Why is this happening?

Many applications create temporary files while running. These files may be used to store information about the document you are working on or information about your particular settings. These temporary files get saved in your home directory. If your home directory is on another computer in your network and your network is unstable, you may get these errors. A network server going down or the network becoming overloaded are possible causes of such instability. Moving your home directory to a hard drive on the WinFrame server will prevent these temporary files from getting saved over the network. This will decrease the amount of traffic across your network, make your system more fault-tolerant, and improve perceived performance.

What if I want to remove an application?

If an application was installed as user-specific, the user can run the application's Uninstall program to remove it. If any program groups are left behind after uninstalling, delete them. Delete their directories using File Manager. User-global installs should be removed only by an administrator.

What if the Program Manager icon cannot find the correct path?

Check the path of an application by highlighting the application icon and selecting properties from the File menu. If the application is being run from another server, make sure the user can access that server and the drive mapping has not been removed. If the application was installed as user-global, check the path against the path used by another user who is able to run the application and change it if necessary.

A user-global installation was done for an application but the application complains that it cannot find some files. What can be done?

Do a user-specific installation and verify that the application works correctly on WinFrame. Once verified, look in the user's home directory to see what files are being installed that are missing in the user-global install user's directories. Copy these files into the %SYSTEMROOT% directory so they will be available to all users. Check with your Citrix support representative, the latest Solutions Guide, and the Citrix web site for specific instructions for that application. If no information is available, do user-specific installations for all users.

Is it possible to dynamically point an application's Working Directory to the user's home directory?

Yes. You can use environment variables in the Working Directory field of the Program Item Properties for icons in Program Manager. For example: if you want to have an application use the user's home directory as the working directory, enter %HOMEDRIVE%%HOMEPATH% as the Working Directory for the application's Program Manager icon. Environment variables can also be used in the Working Directory field of the Application tab for Remote Application Manager items. See WinFrame-Specific Environment Variables for a list of environment variables.


Accessing the NDS Tree

After Gateway Services for NetWare is installed, when a user first logs on they are prompted to set their default tree and context. The tree and context define the position of the user object (the user name you use to logon). You can have either a default tree and context or a preferred server, but not both; usually, in NDS environments, you want a default tree and context. (You can still access NetWare servers that use bindery-style security as normal.) If you have a preferred server you can access volumes and printers in a NDS tree, but you must specify a full NDS context (including the user name).

For example, if your default tree is treename and your default context is Sales.Orgname then you will be logged into treename as UserName.Sales.Orgname. The context may use NDS types or be typeless (OU=Sales.O=Orgname).

If you choose to have a preferred server instead of a default tree and context, you may still access the NDS tree, however you must specify a full NDS user name when connecting to a NDS volume (I.E. UserName.Sales.Orgname).

If you need to change your tree and context later, use the GSNW option in Control Panel.

If NDS tree names exceed 31 characters in length WinFrame users will be to unable access them. In order to change the NDS tree name follow this procedure:

WARNING

Changing the NDS tree name can have serious consequences! Do not follow this procedure unless you understand the ramifications. Consult your NetWare manuals for more information before performing this procedure.

1.	Run RCONSOLE.EXE to connect to the Master Replica for the NDS tree.

2.	At the NetWare console prompt type: LOAD DSMERGE.

3.	Select the option "Rename this tree"

4.	You will have to type in the NetWare Administrator's name and password along with the new tree name.

5.	Press F10 to perform the rename.

6.	Exit DSMERGE

7.	At the NetWare console prompt type: LOAD DSREPAIR

8.	Select the option "Replica synchronization"

9.	You will have to type in the NetWare Administrator's name and password  to complete this process.

10.	You may need to run DSREPAIR on other Read/Write Replicas in the NDS that were not synchronized from the Master Replica.

11.	Change all DOS workstation's NET.CFG "Preferred Tree" statement to reflect the new tree name.

To browse an NDS tree and to connect to NDS volumes

1.	Start File Manager.

2.	Click Disk; then click Connect Network Drive.

3.	Double-click NetWare or Compatible Network.

NDS trees (as well as NetWare or Compatible servers) appear in the NetWare or Compatible Network list. Double-click a tree name to expand it, and then double-click any container object to expand its contents and structure.

To map a local drive to a volume on the NDS tree, select the volume, then click OK. You can connect to and assign a local drive letter to any volume or subdirectory anywhere in the tree hierarchy.

Accessing any volume in your default tree requires no further logon or password. Accessing another tree prompts you to supply a full context (including user name) for that tree. Likewise, if you have no default tree, you must supply a full context with the user name.

The best way to connect to a printer is to use the Print Manager.

To connect to a printer on the NDS tree

1.	Start Print Manager, then click Printer.

2.	Click on the Connect to Printer icon:

3.	Double-click NetWare or Compatible Network if it is not expanded already.

4.	Double-click any NDS tree or NetWare server to expand it. You can then double-click any other container objects to expand them.

5.	When you find a printer (shown with a printer icon) you want to connect to, select it and click OK.

Enhancements To the NET USE Command To Provide NDS Access From the Command Prompt

To connect to a network drive, type:

NET USE drive: \\treename\volumename.ouname.orgname [/U:username.OUName.OrgName [password]]

where drive is the drive letter to assign to the volume, treename is the name of the tree, volumename.ouname.orgname is the full path (either labeled or label-less) to the volume, username.ouname.orgname is the user name and context to use for this tree (labeled or label-less), and password is the password

To connect to a network printer, type:

NET USE LPTn: \\treename\printname.ouname.orgname [/U:username.ouname.orgname [password]]

where n is the printer port to assign to the printer, Treename is the name of the tree, PrintName.OUName.OrgName is the full path (either labeled or label-less) to the volume, UserName.OUName.OrgName is the user name and context to use for this tree (labeled or label-less), and Password is the password

To end a connection to a volume or printer use the NET USE drive: /D or NET USE LPTn: /D commands as usual.


COM Port Mapping

The WinFrame Client for DOS and selected Windows terminals (the Wyse Winterm, for example) support COM port mapping. COM port mapping is similar to printer and drive mapping, and allows the WinFrame server to use a COM port on the client WinStation as if it were a COM port on the WinFrame server. COM port mapping is not currently supported by the WinFrame Windows Clients.

Use the NET USE command to map a client COM port. For example, the following command maps COM2 on the WinFrame server to the COM1 port of the remote WinStation:

NET USE COM2: \\CLIENT\COM1

Some versions of the Wyse Winterm may not support COM port mapping. Contact Wyse for further information.


Making a Backup Copy of the Registry

The Registry is a centralized database of user, application, and computer-specific configuration information. Just as it is important to backup the files on your WinFrame system, it is also a good idea to backup the Registry. Some backup programs allow you to backup the Registry whenever you backup files. Another method is to use the Windows Repair Disk Utility.

To Use RDISK to Backup the Registry

1.	Log on to the WinFrame server as an administrator.

2.	In the Program Manager, choose Run from the File menu.

3.	Type RDISK /S and press enter. A dialog box appears showing the progress of the operation. The Registry, along with the AUTOEXEC.NT and CONFIG.NT files is saved to the %SYSTEMROOT%\REPAIR directory.

5.	When finished, you are asked if you want to create an Emergency Repair Disk. This will attempt to copy the files to a diskette disk. If the files do not fit, you must manually copy them to separate disks.

6.	When finished, click on the Exit button to exit the Repair Disk Utility program.


Creating Application Icons to WinFrame
Creating WinFrame Application Icons

On the WinFrame clients it is possible to create icons for entries configured in the Remote Application Manager. When a user clicks on these, a remote control connection to a WinFrame server is made. The entry can either just give the user a standard logon to Windows NT or it can automatically start a predefined application on the WinFrame server.

When you create a remote application entry using the WinFrame Win16 or Win32 Client Remote Application Manager, you can create a remote application icon. A user can then double-click on this icon to start the WinFrame Win16 or Win32 Client, connect to a WinFrame server, and start an application.

1.	When you create a new remote application, select Select Program Group on the Icon/Group screen in the Remote Application Wizard. Select the program group you want the remote application icon added to. You can also select Change Icon to select from a list of icons for the remote application.

2.	To create an icon for an existing remote application, edit the remote application. Click on Select Program Group in the Properties Application page to select a program group for the remote connection icon.


Designing ALE Web Pages to Support Multiple Browsers

It gets very confusing working with putting embedded Windows apps into a web page due to the various methods Netscape and Internet Explorer browsers use to handle embeds. While Internet Explorer 32-bit will understand both ActiveX controls (represented by the HTML tag <OBJECT>) and 32-bit Netscape Plugins (<EMBED> tag), IE 16-bit only understands 16-bit Netscape Plugins. Netscape 2.0 and 3.0 understand only the Plugins, while Netscape Communicator confuses itself when it finds an <OBJECT> tag. JavaScript can be used to help the user's browser decide on the best way to implement the Embedded Application.

The following is an example of such a script, written in JavaScript/JScript to work with both Netscape and Explorer. To use, just paste into your web page, and then modify the variable assignments as necessary.

<script language="JavaScript">

<!-- Author: Thomas Pierce, tomp@citrix.com

// YOU SHOULD ONLY NEED TO CHANGE THE VARIABLES BELOW.

//

// icaFile: location of the .ICA file for both the OBJECT and EMBED.

 var icaFile = "/bin/ica/solg.ica";

// width and height: pixel-size of the embedded application.

 var width = "440";

 var height = "438";

// start attribute: if Auto, app fires up upon pageload. If Manual, app waits to be clicked by user.

 var start = "Auto";

// border attribute: On/Off, to specify border around app window.

 var border = "On";

// Want vertical/horizontal space around the app? Set these just like for the <IMG> tag.

 var hspace = "2";

 var vspace = "2";

// Where is the ActiveX CAB file located? It's probably best to leave this set to Citrix:

 var cabLoc = "http://www.citrix.com/bin/cab/wfica.cab#Version=2,00,259,239";

// Where is the Plugins Reference page located? It's probably best to leave this set to Citrix:

 var plugRefLoc = "http://www.citrix.com/demoroom/plugin.htm";

// The following is the ActiveX tag:

 var activeXHTML = '<OBJECT classid="clsid:238f6f83-b8b4-11cf-8771-00a024541ee3" data="' + icaFile + '"   CODEBASE="' + cabLoc + '" width=' + width + ' height=' + height + ' hspace=' + hspace + ' vspace=' + vspace + '> <param name="Start" value="' + start + '"><param name="Border" value="' + border + '"></OBJECT>';

// And the Plugin tag:

var plugInHTML = '<EMBED SRC="' + icaFile + '" pluginspage="' + plugRefLoc + '" width=' + width + ' height=' + height + '  start=' + start + ' border=' + border + ' hspace=' + hspace + ' vspace=' + vspace + '>';

var userAgent = navigator.userAgent;

if (userAgent.indexOf("Mozilla") != -1) {

        if (userAgent.indexOf("MSIE") != -1) {

                if (userAgent.indexOf("Windows 3") > 0)

                        { document.write(plugInHTML); }

                else

                        { document.write(activeXHTML); }

                }

        else

          { if (userAgent.indexOf("Win16") > 0) { document.write(plugInHTML); }

                else { document.write(plugInHTML); }

          }

}

//-->

</script>

If you want to include some kind of content for non-embeddable browsers, include the following at the end (after the </script> tag):

<noscript>

<a href="URL of ICA file">

Click here to launch the application!

</a>

</noscript>

This allows anyone using a browser that can't handle an embedded application the choice to launch the application instead.

See Also:

Configuring Microsoft Internet Explorer on WinFrame

ICA File Syntax


Configuring Microsoft Internet Explorer on WinFrame

The latest version of Microsoft Internet Explorer that will run on WinFrame is 3.03 16-bit. This version of Internet Explorer does not support ActiveX controls, but does support Netscape Plug-ins. To configure Internet Explorer for use with the ICA Netscape Plug-in, follow these instructions.

Configuring Internet Explorer 3.03 16-bit for use with the ICA Netscape Plug-in

1.	If Internet Explorer is not installed, install it now. Make note of the directory where Internet Explorer is installed.

2.	Run the Web Client Plug-in installation file, %SYSTEMROOT%\SYSTEM32\CLIENTS\WFCWEB\DISKS\DISK1\NSPLUGIN\Wfplug16.exe

3.	In Unzip To Directory, type a directory to unzip the files to (C:\TEMP, for example) and then click Unzip.

4.	Start File Manager and change to the directory used in Step 3.

5.	Copy Wfica16.exe and Npicaw.dll to the PLUGINS subdirectory of the directory where Internet Explorer is installed (C:\IEXPLORE\PLUGINS, for example).

6.	Change to the PLUGINS subdirectory.

7.	Click on the file Wfica16.exe, and then on the File menu, click Run.

8.	In the Command Line field type:

Wfica16.exe /setup

9.	Exit File Manager.

See Also:

Designing ALE Web Pages to Support Multiple Browsers


Optimizing Performance

This section contains instructions for getting the most performance out of your WinFrame server.


Application Performance Tuning

See Also:

General Installation of Applications on WinFrame

Application Integration in the Solutions Guide

This information is intended for system administrators who are either attempting to maximize the number of users able to use an application at the same time, or attempting to increase the responsiveness of an application that appears to be unresponsive or very sluggish even for a single user. It is assumed that the reader understands how to use the Performance Monitor, the PIF editor, and how to set up AUTOEXEC.BAT files.

Some applications tend to use large amounts of CPU time when in an idle state and thus could be termed a "bad application" for a multi-user system such as WinFrame. For these applications, WinFrame has the following integration techniques that make the application behave better.

Tuning DOS Applications

Given a chance, most DOS applications will use nearly 100% of the system CPU. Most DOS applications constantly look for keyboard input even while they appear to be doing nothing. Many DOS applications will also check for keyboard input while executing commands in order to be responsive to the user.

In order to maximize the number of concurrent users the system can handle, an aggressive DOS keyboard polling algorithm has been implemented. This support attempts to take the CPU away from a DOS application if it checks the keyboard frequently enough during a single system timer tick. System defaults are intended to handle most cases; however, the optimal settings depend on the specific DOS application that you are running. The DOSKBD utility is used to tune the DOS Keyboard Polling algorithm. Change the default settings only if you are trying to solve a problem. Refer to Appendix A, "WinFrame Command Reference" of the System Guide for more information on DOSKBD.

Tuning Windows 16- and 32-Bit Applications

WinFrame provides the following Registry entries for Windows application tuning. The entry names and default values are:

FirstCountMsgQPeeksSleepBadApp = 0xF
MsgQBadAppSleepTimeInMillisec = 0x1
NthCountMsgQPeeksSleepBadApp = 0x5
Flags = 0x8

To customize settings for a particular executable file, run the Registry editor (REGEDT32) and add or edit the Registry variables under

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications\xxx

where xxx is the name of the application executable (without an extension). For example, the key for an application with the name APPNAME.EXE would be simply APPNAME.

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions on making a backup of the Registry.

FirstCountMsgQPeeksSleepBadApp

The number of times the application monitors the message queue before it decides that it is ill-behaved. Decreasing this value puts the application to sleep more often so it uses less CPU time.

MsgQBadAppSleepTimeInMillisec

The number of milliseconds the application is put to sleep for once it is determined that it is ill-behaved. Increasing this value causes the application to use less CPU time.

NthCountMsgQPeeksSleepBadApp

The number of times the application monitors the message queue after it is determined that it is an ill-behaved application for it to be put to sleep again. Decreasing this value causes the application to use less CPU time.

Flags

Controls what type of application the bad application flags apply to. Set Flags to 0x8 for 32-bit applications only, 0x4 for 16-bit applications only, or 0xC for both 16- and 32-bit applications.


Advanced Performance Considerations

See Also:

Performance Tuning in the Solutions Guide

Adjusting Keyboard and Mouse Responsiveness

The time a WinFrame client or server holds a packet before sending can be reduced to make the client more responsive. Normally, data is held in an effort to maximize data-per-packet, while minimizing the number of packets sent across the network. This helps throughput on high-latency networks. The default settings are recommended for most situations, but on a network with low-latency, you may find that adjusting these settings yields better results.

Adjusting Settings on WinFrame Clients

For clients, the keyboard packets and mouse packets have separate delay timers. To modify them, edit the following parameters in the APPSRV.INI file on each WinFrame client computer:

MouseTimer=100

KeyboardTimer=50

These values, when in the [WFClient] section of APPSRV.INI, affect all sessions. To change the values for a particular connection listed in Remote Application Manager, copy these two lines to that section of APPSRV.INI file. For example, for a connection named "Accounting WinFrame server", look for [Accounting WinFrame server] in the APPSRV.INI and add these two lines below it.

The defaults work best over RAS connections and WAN links. For async dialin connections and low-latency LANs, lowering these values may yield faster perceived responsiveness on the WinFrame clients. Lowering them too far could have an adverse effect. As the mouse timer is lowered, network packets are sent more often, which will increase the network traffic and server load.

Adjusting Settings on WinFrame Servers

On the server, there is only one delay timer. The default value is 100 milliseconds, but when a keypress or mouse movement is received from the client this delay is temporarily lowered to 10 milliseconds. The default value for new WinStations and the value for existing WinStations are changed separately. Adjusting these values will have less of an effect than changing the client delay timers, and can increase network traffic and server load if lowered.

In the server Registry, the following value determines the default setting for newly created WinStations:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Pds
\trans\OutBufDelay

where trans  is the transport (protocol) to change.

The following Registry value sets the parameter for existing WinStations:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
\WinStations\trans#x\OutBufDelay

where trans is the transport and x is the number of the WinStation to change.

Memory

WinFrame will use all available memory for the processes that are active, minus a "goal" of about 20% free. When available memory drops below 20% (as determined by the Available Bytes counter in Performance Monitor) the system starts trimming working sets to make more memory available. If the system is under load due to a large number of active applications, the working sets will resist this trimming, and the system will continue to page as the sets reclaim pages that have been put onto the swap-out list. This will result in the 20% free memory not being maintained. This 20% memory cushion allows faster logging in and starting of applications.

How much memory is enough, beyond which there is only negligible improvement?

"Enough" memory is when working sets of active processes are resident while handling the normal or expected workloads. The paging file rate and percentage of disk bandwidth can be monitored with Performance Monitor after enabling disk performance counters by typing diskperf -y at the command prompt and then rebooting the server.

Separate Hard Drive(s) for the Paging File

Splitting the paging file between two or more disks will give a big performance boost. The optimal configuration is to configure multiple paging files on separate spindles (not partitions). This will make WinFrame automatically swap pages in a round-robin fashion among the paging files to balance the load. These should be "direct" partitions, and not through RAID 5 or other methods. RAID 5 will tend to break up transfers across the multiple drives, which increases I/O throughput  but decreases latency. Most paging delay is latency, not throughput. RAID 5 is not suited for write-intensive operations such as paging. Paging files should not be on RAID unless system reliability concerns are more important. An I/O error on a paging file will cause WinFrame to crash. A possible solution that combines speed with reliability is a straight shadow configuration.


Troubleshooting

This section contains information to help you diagnose and solve any problems encountered with your WinFrame server.


Anonymous User Access to a WinFrame Server with High Security Setting

If you use the C2 Security Manager to configure your WinFrame server for High Security and you want to allow Anonymous Users access to your system, you will have to allow Read and Execute permissions to the following list of files for the Anonymous group. You will also have to specifically allow access to any applications you want to be available for anonymous users. These changes are necessary because anonymous users are not members of the Users group. This is done for security purposes.

%SYSTEMROOT%\SYSTEM32\USERINIT.EXE

%SYSTEMROOT%\SYSTEM32\WINLOGON.EXE

%SYSTEMROOT%\SYSTEM32\WINSTA.DLL

%SYSTEMROOT%\SYSTEM32\CLIB.DLL

%SYSTEMROOT%\SYSTEM32\REGAPI.DLL

%SYSTEMROOT%\SYSTEM32\ULMREG.DLL

%SYSTEMROOT%\SYSTEM32\CTXSKU.DLL

%SYSTEMROOT%\SYSTEM32\SAMLIB.DLL

%SYSTEMROOT%\SYSTEM32\WINSPOOL.DRV

%SYSTEMROOT%\SYSTEM32\MPR.DLL

To Change File Permissions

1.	Run File Manager.

2.	Select the file.

3.	Choose Permissions for the Security menu.

4.	Click the Add button.

5.	In the List Names From box, select the current WinFrame server.

6.	Double click on the Anonymous group.

7.	Verify that the Type of Access is Read.

8.	Click OK.

9.	Click OK in the File Permissions window.


Examining a System Crash Dump

The crash dump file, usually called MEMORY.DMP, is a dump of physical memory and is the size of the physical memory installed on the server. In most instances, this file is far too large to upload to Citrix Technical Support. There is an analysis utility on the WinFrame CD-ROM called DUMPEXAM.EXE that can be run against MEMORY.DMP. DUMPEXAM outputs a text file with useful debugging information in a much more manageable size. This text file may be uploaded to Citrix Technical Support as requested by a Citrix representative in order to determine the cause of a Stop message.

Setup Before Crash

Make sure that the various system recovery settings have been set in Control Panel, System, Recovery. It is necessary that you enable the setting "Write debugging information to:". Use %SystemRoot%\MEMORY.DMP as the filename (default). It is also recommended you enable the setting "Overwrite any existing file" because the system will not write a dump file if one already exists with that name.

If a Crash Occurs

If WinFrame crashes, it writes a memory image in the install directory called MEMORY.DMP. This file will be the size of the machine's paging file. If there is not free drive space on the install partition equal to the size of the paging file plus between 1 and 20 megabtyes, the memory dump will be incomplete. An incomplete memory dump is not useful for problem diagnosis.

The paging file space is important because during the "blue screen" bug check, the system will write the memory image to the paging file. When the system reboots, it uses the portion of the paging file not containing the dump until it can copy the dump from the paging file into MEMORY.DMP. If the system is configured to start a large number of WinStations, you may get "System is running out of virtual memory" messages while the dump is being copied from the paging file. Once the dump is saved to MEMORY.DMP, the space is automatically reclaimed. Using the recommended paging file size of two times physical memory should avoid these restart messages.

Symbols

Before the dump can be examined, the WinFrame symbols must be copied to the WinFrame server. If any service packs, hotfixes, or third-party drivers have been installed, the symbols for them must be installed also. The service pack symbols include an installation batch file (INST_SYM.BAT) that will first copy the symbols from the WinFrame CD-ROM. Then the service pack symbols will be extracted, overwriting any obsolete files. See the Readme file included with the service pack symbols for further instructions.

To manually install the original symbols, create a directory called %SystemRoot%\SYMBOLS (for example, %SYSTEMROOT%\SYMBOLS or \WINNT35\SYMBOLS). Copy the entire Symbols directory from the WinFrame CD-ROM. The symbols are located in the \SUPPORT\DEBUG\I386 \SYMBOLS directory. Make sure all of the subdirectories in the SYMBOLS directory are copied onto the server drive. If any service packs have been applied, the symbols specific to that service pack must also be copied to %SystemRoot%\SYMBOLS.

Examining The Dump

The dump analysis utilities are stored in \SUPPORT\DEBUG\I386. The two utilities are:

1. CHKDUMP.EXE - Checks the dump image. Optional. Useful after transfer for validation.

2. DUMPEXAM.EXE - Outputs useful debug information about the memory dump file to a text file.

Usage

DUMPEXAM [-V] [-P] [-F filename] [-Y path] [-?] CrashDumpFile

-?	Displays syntax

-V	Verbose mode

-P	Print header only

-F filename	Specify output file name

-Y path	Set the symbol search path

If CrashDumpFile is not specified, the name specified in the Registry is used. If the symbol search path is empty, the CD-ROM is used for symbols.

To run the DUMPEXAM utility, change into the \support\debug\i386 directory on the CD-ROM. If the symbols have been applied correctly, the following command will output to the text file %SystemRoot%\MEMORY.TXT:

dumpexam -v -y %SystemRoot%\symbols

The resulting text file can then be sent to Citrix Technical Support as requested. The Citrix technician will provide instructions for the method of transferring the file.

NOTE: By default, the DUMPEXAM utility looks for the symbols on the CD-ROM. If the symbols are in a different location, use the -y parameter and specify the path. For example:

dumpexam -v -y c:\winframe\symbols

If the symbols are in more than one directory, separate the different directories by a semi-colon (;). For example:

dumpexam -y c:\winframe\symbols;c:\hotfix\sp3b_sym

For more information on DUMPEXAM.EXE see the Microsoft TechNet Knowledge base using the keyword DUMPEXAM.


Troubleshooting User Accounts

I'm trying to run an application but the application will not start, acts strangely, cannot access files, or cannot create temp files. What causes this?

This usually occurs because your userid does not have a unique home directory. By default, users get the \USERS\DEFAULT directory on the WinFrame server if they do not have a home directory or if WinFrame cannot find their home directory on the network. Because all users without a home directory are placed in the default directory, they all try to save and lock the same set of files. Users MUST have their own unique home directory, either on the WinFrame server hard disk or on a network server that has shared resources. To determine if your user is having this problem, logon with that userid and start a DOS session. If the DOS session places you in the \USERS\DEFAULT directory, you must create a unique home directory for your user. To configure your user for a home directory, start the User Manager for Domains, select the user name, and click the Profile button. In the Profile dialog, set the user's home directory to either use a directory on the local WinFrame hard disk or to connect to a drive on the network. If connecting to a drive on the network, select an unused drive letter and enter the UNC name of the home directory on the network in the Profile dialog. For example:

Drive:	W:

To:	%SYSTEMROOT%1\HOMEDIR\USERS\BOBW

This connects the user to the network server WINFRAME1 where the share name is HOMEDIR. It maps drive W to the \USERS\BOBW directory, which becomes the home directory for that user.

Periodically when using an application, I get an error from the application that the hard disk or some group of files is corrupted or missing. Why is this happening?

Many applications create temporary files as they run. They use these files to store information about the document you are working on or information about your particular settings. Any application temporary files are saved in the user's home directory. If your home directory exists on a network and your network is unstable, you may get these errors. This is usually caused by having network connections where the network goes up and down frequently. This can also be caused when a network server goes down, cannot be reached, or if the network becomes overloaded. If you are having these problems, work with your network administrator to locate the network problem and stabilize the network. You can also move your home directory to a directory on the local WinFrame hard drive. This will prevent the temporary files from getting saved over the network.

Do Not Keep Users' Temporary Files on a Client Drive

Make sure the paths for the TEMP and TMP environment variables do not point to a WinFrame user's client hard drives. If these variables point to a client drive, applications that store temporary files in the directories specified by the TMP or TEMP environment variables will run very slowly and may experience other problems. The best place for temporary files is on the WinFrame server itself.


Troubleshooting Client Connections

WinFrame 1.7 Setup automatically creates two WinStations for each installed network transport (NetBIOS, IPX, SPX, or TCP/IP) when you do a new installation. When upgrading an earlier version of WinFrame, any existing WinStations are kept and two new WinStations are added for any new network protocols. If you try to connect to the server and all the available WinStations are in use, you will get the following error. Use WinStation Configuration to add more WinStations. See Chapter 20, "WinStation Configuration", of the System Guide for more information.

General WinFrame Client Remote Application Manager Troubleshooting Tips

When using the WinFrame Client over a local network, first make sure that the network transport hardware and software on the client PC are properly configured and operational. If you can logon to the network and access network resources (including network resources on the WinFrame server), the client PC is configured correctly.

When using the WinFrame Client with an async connection (either direct serial cable connection or dial-in), make sure your client PC is properly configured and cabled. If you are using a direct serial connection to the server, make sure that the cable is a null modem cable. If you are using a Dial-In connection to the WinFrame server, make sure that the modems at each location are supported modems and that the cables used are modem cables. The WinFrame server supports any modem supported by Windows NT 3.51 Remote Access Service. See Modems Supported by WinFrame for a listing of the modems currently supported by WinFrame.

When using the WinFrame client with third-party software for remote node + remote control access, first make sure that the remote node hardware and software on the client PC are properly configured and operational. If you can logon to the WinFrame RAS server and access network resources (including network resources on the WinFrame server), the RAS configuration on both client and server is correct.

If the connection (Dial-In, local network, or remote node) is correct but you cannot logon to the WinFrame server, make sure that you have properly configured WinStations on the WinFrame server and that you are using a username and password valid for the WinFrame server. Use WinStation Configuration to verify that the WinStations are configured to use the proper network transport. Make sure that the WinStations are enabled (Advanced WinStation dialog).

Do not let WinFrame users share remote application manager files. Allowing multiple users to access a shared installation of the WinFrame Remote Application Manager can compromise security. The APPSRV.INI files contains username, domain, and encrypted password information that you may not want users to see. It is recommended that you use a shared copy of the Remote Application Manager only to run preconfigured remote applications and that you mark all files in the shared copy as Read Only so users cannot inadvertently modify the files.

Troubleshooting Network Clients

I can't connect to my WinFrame server using an IPX connection.

If other workstations are able to connect to the WinFrame server using IPX, you may need to manually set the IPX frame type on your workstation. To change this setting, see the documentation for the networking software installed on your computer (LAN Workplace,

If none of your workstations are able to connect to the WinFrame server using IPX, you may need to manually set the frame type for IPX on the server. On the WinFrame server, open the Network Control Panel. Select NWLink IPX/SPX Compatible Transport in the Installed Software list. Choose the Configure button to configure the IPX frame type. Make sure the frame type setting on your client matches the setting on the server. See Chapter 2, "Setting Up A WinFrame Environment", in the Solutions Guide for more troubleshooting suggestions.

I can't connect to my WinFrame server using an IPX connection.

If other workstations are able to connect to the WinFrame server using IPX, you may need to manually set the IPX frame type on your workstation. To change this setting, see the documentation for the networking software installed on your computer (LAN Workplace,

If none of your workstations are able to connect to the WinFrame server using IPX, you may need to manually set the frame type for IPX on the server. On the WinFrame server, open the Network Control Panel. Select NWLink IPX/SPX Compatible Transport in the Installed Software list. Choose the Configure button to configure the IPX frame type. Make sure the frame type setting on your client matches the setting on the server. See Chapter 2, "Setting Up A WinFrame Environment", in the Solutions Guide for more troubleshooting suggestions.

When I try to create a client printer, I get the error, "The application or DLL...is not a valid Windows NT image. Please check this against your installation diskette." What does this mean?

The printer driver (usually RASDDUI.DLL) has become corrupted. You must copy and expand the RASDDUI.DLL file from the WinFrame CD-ROM. To expand and copy the RASDDUI.DLL file type

expand x:\i386\rasddui.dl_ y:\winframe\system32\spool\drivers\w32x86\1\rasddui.dll

(where x is the drive letter of the CD-ROM drive, and y is the drive letter of your WinFrame partition). The command should be typed as one line.

I can't connect to my WinFrame server using the WinFrame Win32 Client running under Windows 3.1x with the 32-bit extensions installed.

The WinFrame Win32 Client will not work with Windows 3.1x or Windows for Workgroups, even with the 32-bit extensions installed. Use the WinFrame Win16 Client with these systems.

I have a Windows for Workgroups PC with the TCP/IP-32 add-on installed and I am unable to make a TCP/IP connection with the DOS WinFrame Client.

The DOS WinFrame Client requires a TCP/IP stack that supports DOS sockets. The TCP/IP add-on for Windows for Workgroups does not support DOS sockets. You must use a real-mode DOS TCP/IP stack like LAN Manager Client for DOS. The WinFrame Win16 Client will work with the WinSock interface included with the TCP/IP-32 add-on for Windows for Workgroups.

Why do I get a NetBIOS error 20 when trying to run the WinFrame Client for DOS from a Windows for Workgroups workstation that has already established a RAS connection to a WinFrame server?

The WinFrame Client for DOS requires real mode DOS networking protocol stacks in order to establish a network connection back to the WinFrame server. Windows 3.1 and Windows for Workgroups environments require a protected mode protocol stack that do not support calls made from DOS. Customers using these environments need to run the 16-bit WinFrame Client for Windows. Users of Windows 95 or Windows NT should run the 32-bit WinFrame Client for Windows 95 and Windows NT.

Troubleshooting WinFrame Dial-In Modem Problems

If there is a problem with a Dial-In connection, double-click on the modem's entry in the WinStation Configuration utility and then click the "Test" button. This will allow you to view the modem signal status to make sure you have a good connection. It will also allow you to manually send commands to the modem to make sure the connection is correct.

I configured my modem for Dial-in. The modem, however, will not answer when someone dials in or it will cycle and try to reset itself endlessly. Why is this?

Start the WinStation Configuration utility and edit the ICA dial-in entry. Set the Device Connect on to always connected and then click the OK button to save. Some modems do not raise Data Set Ready (DSR) when they turn on, so they never get the initialization string to answer the modem. Others drop DSR when they get the initialization string, causing WinFrame to resend the string endlessly. Setting the Device Connect on to always connected causes the initialization string to get sent once and to ignore the DSR signal. Use this setting only if your modem has this problem.

Troubleshooting WinFrame RAS Service Problems

RAS Modem Troubleshooting

If you have problems with RAS modem connections, enable RAS logging by starting REGEDT32 and setting the following subkey to 1:

HKEY_LOCAL_MACHINE\system\currentcontrolset\services\rasman\parameters

If the value does not exist, choose Add Value from the Edit menu and enter these values for the following fields:

Value Name: logging

Data Type: REG_DWORD

String: 1

If the value exists, change it to 1. At this point, you must stop and start the RAS server to execute the change and start logging to the file %SYSTEMROOT%\SYSTEM32\RAS\DEVICE.LOG. You can stop and start the RAS server from the RAS Admin program, found in the RAS group created when you installed the RAS server. Once RAS logging is enabled, you can periodically examine the DEVICE.LOG file. This is useful for debugging connection or modem problems. To disable RAS logging, set the value for the subkey to 0 (and then stop and start the RAS server).

RAS PPP Troubleshooting

If you are having problems using a PPP client to connect to a WinFrame RAS server, enable PPP logging by starting REGEDT32 and setting the following subkey to 1:

HKEY_LOCAL_MACHINE\system\currentcontrolset\services\rasman\PPP\Logging

If the value does not exist, choose Add Value from the Edit menu and enter these values for the following fields:

Value Name: Logging

Data Type: REG_DWORD

String: 1

If the value exists, change it to 1. At this point, you must STOP and START the RAS server to execute the change and start logging to the file %SYSTEMROOT%\SYSTEM32\RAS\PPP.LOG. You can stop and start the RAS server from the RAS Admin program, found in the RAS group created when you installed the RAS server. Once PPP logging is enabled, you can periodically examine the PPP.LOG file. This file contains a list of the PPP packet transactions and is useful for isolating problems with creating PPP connections. To disable PPP logging, set the value for the subkey to 0.

General RAS Host and Client Troubleshooting

Why do the RAS modems on the WinFrame server constantly recycle themselves?

First turn on RAS logging. Let the modem cycle a few times and then examine the DEVICE.LOG file. You may find that the modem initialization string used is causing the modem to return an error that causes RAS to try to reset the modem forever. WinFrame RAS is compatible with the Hayes modem command set but does not recognize all modem error codes. If an unrecognized error code is sent by the modem, RAS may not handle it properly. If this is what is happening, verify that you selected the correct modem when installing the WinFrame RAS server. If the modem information is correct, modify the %SYSTEMROOT%\SYSTEM32\RAS\MODEM.INF file that RAS uses and change the initialization string to remove the invalid command. Make sure you back up the MODEM.INF file before altering it. You can stop the RAS server and use the Windows Terminal program to echo out the AT commands the MODEM.INF file is using to see which command is causing the error. You can then remove the command from the string or replace the string with a more appropriate one.

If the error is not due to the initialization string, try stopping and restarting the RAS server on the WinFrame server. If that does not work, power off the modem, wait at least one minute, and then power it back on. You can also try sending the AT&F command and then an ATW command to the modem to write the factory defaults back to the modem. If all else fails reboot the server.

When I logon at the console, I can see the network and logon to Novell file servers with no problem. When a RAS user connects remotely, the user gets an IPX and IP address but cannot see any Novell file servers. Why is this?

The problem may be that you have your WinFrame server connected to an intelligent 10 Base-T hub. Some 10 Base-T hubs allow only one network address per port. With WinFrame, the server itself is the first network address and every user thereafter has a unique address. In this case, the WinFrame server gets the port and any RAS connections get ignored on the network. To fix this, you can either use a 10 Base-T hub that allows multiple network addresses per port or change the WinFrame server network connection to coax Ethernet cable. Another solution is to set the RAS IPX settings to assign the same network IPX address to all clients. Then set your clients to use server assigned IPX addresses rather than client assigned IPX addresses

Why does my user logon fail to authenticate on the RAS server when I dial-in?

This is caused by not using a local username on the WinFrame server or by not granting the local username RAS access permissions. Refer to "Granting RAS Permissions to WinFrame Users" below for information on granting RAS access permissions.

Why does it take so long to logon to a NetWare File Server over a PPP connection?

Asynchronous serial PPP connections are much slower than normal network connections. Operations must be optimized and program executable files must be stored on the client's hard disk in order to achieve good performance. Use the Windows File Manager to logon to a NetWare File Server and map drives rather than using the standard DOS logon command. The Windows File Manager logon code is local to the client system. If you prefer to use the DOS logon commands, copy these commands to the local client system hard disk rather than trying to load them over the network. This will make access much faster.

As a general rule, only data should go across the PPP connection, not programs. If you load programs from the remote network, they must be moved across the PPP connection first before being loaded into memory on the client system. This slows down access significantly. If the program is installed on the client system's hard disk, the program can be loaded into memory directly from hard disk and only data packets traverse the PPP connection. In general, if an entire application must be run remotely, you should use a WinFrame remote control connection instead of a remote node connection.

Why does the LAN Manager RAS client say that the workstation is not started?

This is caused by not selecting Run the Network Client during RAS client installation. To solve this problem, type NET START WORKSTATION at the DOS command prompt. You can place this command in AUTOEXEC.BAT so it will start automatically when the client boots.

Why does LAN Manager RAS client not recognize the modem or have a problem accessing the modem?

Power down the DOS system and then power it back on after ten seconds. The DOS client can affect the COM port UART to the point that only a cold boot will clear it. A warm boot (pressing CTRL+ALT+DEL) will not fix this problem. If the modem is still not working, make sure that you have the correct modem configured in the RAS Setup or a Hayes compatible setting. Verify that the modem is Hayes-compatible. If all else fails, try a different brand of modem.

When I try to dial, the Windows for Workgroups 3.11 RAS client says it cannot find my COM port. Why?

Your COM port's UART is probably in an invalid state. To fix it, exit Windows and power off your client system and modem. Power them back on, restart Windows, and try to dial again.

After I connect to the RAS server, I get an error that says that the NetBIOS name for my system is already being used. What causes this?

Another system on the remote network is using the same name as your system or you are trying to make a RAS connection to a network you are already connected to. If another system on the network is using the same name as your system, use Windows Control Panel to change the name of your computer. If the client system is trying to make a RAS connection to the same network that it is connected to, disable or disconnect the other network connection.

Note

The Microsoft Developer Network CD-ROMs provide various tips and hints for RAS that you may find useful.


Advanced Topics

This section contains information for advanced WinFrame administrators.


Multiuser NetDDE Support
Multi-user NetDDE Support

NetDDE support on a Windows NT Server, Windows NT Workstation, or Windows for Workgroups machine uses the machine name to choose the point of data exchange. However, in a multi-user environment like WinFrame, multiple users may be logged onto a single machine. In order to use NetDDE support on WinFrame, utilize the user name you are attempting to connect to as the point of contact.

Chat and ClipBook Limitations

NetBIOS limitations dictate that a machine name have a maximum of 15 characters. Because the name used by NetDDE is replacing a machine name, this limitation also exists for users intending to use NetDDE. In addition to being limited to 15 characters, the username must also be unique on the network. For example, the two users LongUserNameNumber1 and LongUserNameNumber2 would appear as the same user to NetDDE (because the first 15 characters of the two user names are the same). In the above example, if LongUserNameNumber2 attempts to use NetDDE when LongUserNameNumber1 is already using it, the user receives an error message stating that a user (or machine) by that name is already using NetDDE.

The NetDDE service is not started by default. A user cannot use NetDDE or be called with the Chat utility until the NetDDE service is started. The easiest way to establish the service is to start the ClipBook program or Chat program in your Startup group as a minimized program. This establishes your username as a valid NetDDE name.

NetDDE Shares

Although all users have access to the Chat and clipboard applications, a normal user, by default, does not have the ability to set up a NetDDE share point. For instance, if a user from one machine wants to share some information using the ClipBook with another user, he/she needs to set up a NetDDE share. Currently, in the Domain environment, only users in the Domain Administrators or Administrators groups are allowed to set up NetDDE shares. In a workgroup environment, only members of the Power Users group can set up NetDDE shares. A qualified user can set up a NetDDE share on behalf of another user either by using the supplied DDESHARE utility, or if the shared data is in the user's ClipBoard, he/she can share this data from the ClipBook application while logged into his/her own account on the same machine.


The ICA Server Browser
The WinFrame ICA Server Browser

Users of the WinFrame Client need to know what WinFrame servers are available for a given network protocol (IPX, TCP/IP, or NetBIOS). The WinFrame ICA Browser (also known as the Server Browser) is used by the WinFrame Client to obtain a list of available WinFrame servers for a given network type.

The ICA Browser system consists of a master browser, gateways, browsers, and client systems. The master browser maintains the browse list and periodically gets updates from the other browsers. When a WinFrame Client PC needs information on available WinFrame servers, the WinFrame Client PC obtains the information by sending a request to the master browser. See Chapter 23, "Application Publishing", of the System Guide for more information on configuring ICA Gateways.

Each WinFrame server contains a browser for IPX, TCP/IP, and NetBIOS over NetBEUI network types. Each network protocol has one master browser. The network master browsers can be separate systems, but there is only one master browser system per protocol.

See the topic "TCP/IP Connections" for information on how the WinFrame client finds the ICA Master Browser.

Specifying the Master Browser

When a browser needs to force a master browser election, it notifies the other browsers on the network by broadcasting an election datagram. There is a separate election for each network protocol. The election datagram contains the election criteria. The election criteria (in priority order) consists of:

1.	Statically configured as a master browser

2.	Highest browser version number

3.	Running on a WinFrame domain controller

4.	Longest running browser

5.	Lexically lower browser name

When a browser receives an election datagram, the receiving browser compares the election criteria:

If the browser has a higher election criteria than the issuer of the election datagram, the browser issues its own election datagram.

If the browser does not have a higher election criteria than the issuer of the election datagram, the browser attempts to determine which system is the new master browser.

If a browser believes itself to be the master browser it sends an election request. The browser broadcasts up to four election datagrams. If, after four election datagrams, no other browser has responded with a higher election criteria, this browser becomes the master browser. If another browser responds with higher election criteria, the current browser ceases broadcasting election datagrams.

A master browser election occurs under the following conditions:

After a browser starts

The current master browser fails to respond with an ACK (acknowledgment) after a browser update

The current master browser fails to respond to a client request

Two master browsers are detected on the same network protocol

After being elected the master browser, the master browser broadcasts a master declare datagram every MasterDeclareTime seconds. A master declare is used to detect multiple master browsers on the same network protocol. If a master browser ever receives this packet from another browser it forces an election to get rid of the extra master browser.

The WinFrame servers in a network negotiate the ICA Browser protocol among themselves in a manner transparent to system users. However, advanced administrators can use the Registry Editor (REGEDT32) to modify some of the ICA Browser parameters on a WinFrame server.

Modifying the Registry

The WinFrame ICA Browser adds variables to the WinFrame Registry. You do not normally need to override the default values for these parameters. However, for some systems you may want to adjust individual parameters to suit your particular needs.

To edit the Registry

1.	In the Program Manager, choose Run from the File menu.

2.	At the prompt, type REGEDT32 and press Enter.

This command can also be run from File Manager and the Task List, or an icon can be created in a Program Group.

For detailed information on how to add a parameter to a key in the Registry, see the on-line Help for the Registry editor.

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions on making a backup of the Registry.

ICA Browser Registry Key Values

The ICA Browser variables have the following Registry path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ICABrowser

Important

If any of the Registry variables below are changed, the ICA Browser must be stopped and restarted for the new values to take effect. The ICA Browser can be stopped and started using the Services option in Control Panel. When the Browser is restarted, a new election will take place using the changed values.

AckRetries	REG_DWORD	0 - 0xffffffff	(3 = default)

Specifies the number of times the browser will retry sending a master browser update before forcing a browser election.

AckTimeout	REG_DWORD	0 - 0xffffffff seconds	(5 = default)

Specifies the interval a browser will wait for an ACK after sending a master browser update. If no ACK is received, the browser will resend the update. The browser will retry AckRetries times before forcing a browser election.

AgeDatabaseTime	REG_DWORD	0 - 0xffffffff seconds	(300 = default)

Indicates how frequently the master browser checks the "time to live" value associated with browser data. If the browser data is not being updated, the data is deleted. This value can be set to zero to disable aging of browser data.

ClientElectionTime	EG_DWORD	0 to 0xffffffff seconds	(30 = default)

After receiving a election request (BR_ELECTION) from a client, all subsequent client initiated election requests are ignored for ClientElectionTime seconds.  This allows the original election to complete before another election is allowed.

DisableEnumeration	REG_DWORD	0 or 1	(0 = default)

Setting this value to 1 prevents the computer name of this WinFrame server from appearing in the client's server list.  All configured server farm names will still appear in the client's server list. This provides a way to hide a server.

DisableGateway	REG_DWORD	0 - 1	(0 = default)

Setting this value to 1 causes this browser to ignore all configured gateway addresses. It also prevents this browser from accepting gateway data from another browser.

DisableIpx	REG_DWORD	0 - 1	(0 = default)

Setting this value to 1 prevents this browser from participating on IPX networks.

DisableNetBios	REG_DWORD	0 - 1	(0 = default)

Setting this value to 1 prevents this browser from participating on NetBIOS networks.

DisableTcp	REG_DWORD	0 - 1	(0 = default)

Setting this value to 1 prevents this browser from participating on TCP/IP networks.

GatewayAddTime	REG_DWORD	0 to 0xffffffff seconds	(1800 = default)

Indicates how frequently the browser sends the gateway add command (BR_GATEWAY_ADD).  The gateway add command configures all gateways that are specified in the Registry by GatewayIpx and GatewayTcp.

GatewayIpx	REG_MULTI_SZ	WinFrame server addresses

To setup an IPX gateway, the remote IPX address (network:node) of a WinFrame server must be specified in this list.

When a master browser receives an update from a browser, it forwards the data to all configured gateways on the same network protocol.

It does not matter which WinFrame server the gateway address is configured on. The same address can be configured on multiple WinFrame servers.

GatewayTcp	REG_MULTI_SZ	WinFrame server addresses

To setup a TCP/IP gateway the remote IP address (or DNS name) of a WinFrame server must be specified in this list.

When a master browser receives an update from a browser, it forwards the data to all configured gateways on the same network protocol.

It does not matter which WinFrame server the gateway address is configured on. The same address can be configured on multiple WinFrame servers.

IsMasterBrowser	REG_DWORD	0 - 1	(0 = default)

When this value is set to 1, it raises the browser's priority during a master browser election. As long as no other system has this value set, this system will become the master browser.

LoadLevelBoost	REG_DWORD	0 to 0xffffffff	(10 = default)

After a server is selected on a load balance request, LoadLevelBoost is added to the load level of the server.  When two servers have nearly identical loads, this prevents the same server from being selected on the next request.  This boost gets overwritten on the next browser data update.

LogFlush	REG_DWORD	0 or 1	(0 = default)

When this value is set to 1, all log events are immediately written to disk as they occur, without any buffering.  This has a significant performance penalty.   This option should not normally be used.

LogMask	REG_DWORD	0 - 0xffffffff	(0 = default)

Specifies a bit mask for logging debug information.  After changing this value, STOP and START the ICA Browser to start logging to the file %SYSTEMROOT%\IBROWSER.LOG. The bit mask values are:

Bit Mask	Description
0x00000001	browser initialization
0x00000002	browser elections
0x00000004	browser updates
0x00000008	gateway updates
0x00000010	client requests
0x00000020	reads and writes
0x00000040	reads and writes data
0x00000080	database updates
0x00000100	browser data
0x00000200	load balancing
0x10000000	timers
0x20000000	semaphores
LogToDebugger	REG_DWORD	0 - 1	(0 = default)

Specifies logging messages should be written to the kernel debugger in addition to the log file.

MasterDeclareTime	REG_DWORD	0 - 0xffffffff seconds	(3600 = default)

Indicates how frequently the master browser broadcasts a master declare. A master declare is used to detect multiple master browsers on the same network. If a master browser ever receives this packet from another browser it forces an election to get rid of the extra master browser. This value can be set to zero to disable master browser declares.

NotMasterBrowser	REG_DWORD	0 or 1	(0 = default)

When this value is set to 1, it lowers the browser's priority during a master browser election. This will prevent this browser from becoming the master browser.

PingAddressTime	REG_DWORD	0 to 0xffffffff seconds	(5 = default)

Specifies the time a browser will wait, after sending a ping request, for a ping reply.  If no ping reply is received, the browser will try sending the update again.  The browser uses pings to verify a server still exists before returning the address of a server to the client.

RefreshDelay	REG_DWORD	0 - 0xffffffff seconds	(30 = default)

Specifies the delay after which a client connects or disconnects from the WinFrame server, that a master browser update is sent. This delay should be large enough to let the system "settle" before sending the master browser update.

SendRetries	REG_DWORD	0 - 0xffffffff	(3 = default)

Specifies the number of times the browser will send a gateway add or delete command.

UpdateTime	REG_DWORD	0 - 0xffffffff seconds	(1800 = default)

Indicates the frequency the browser updates the master browser. After an election all browsers know the address of the master browser. After a random delay (4-6 seconds) each browser sends an update datagram to the master browser. After this initial update, the browsers update the master browser every UpdateTime seconds. Upon receiving data from a browser, the master browser replies with an ACK. Master browser updates are also sent whenever a client connects or disconnects from the WinFrame server. Lowering this time makes browser data more accurate, but increases the CPU and network load. This value should be lowered when load balancing is used. This value can be set to zero to disable periodic updates.

Version	REG_DWORD	0 to 0xffffffff

Specifies the current browser version.


NetWare Directory Services (NDS) Support

WinFrame 1.7 includes an NDS-aware version of the WinFrame Gateway Services for NetWare.

This version enables users of WinFrame platform computers to access Novell NetWare 4.x servers running NetWare Directory Services (NDS). With NDS, shared objects on participating NetWare servers are organized into a hierarchical tree. This updated version of Gateway Services for NetWare includes all the functionality of previous versions, in addition to NDS compatibility.

Supported NDS Features

1.	NDS volumes may be accessed by both the command line interface and File Manager.

2.	NDS printer queues may be accessed by both the command line interface and Print Manager.

3.	NDS naming is supported, including typed and typeless names.

4.	NDS user names are supported.

5.	A default NDS tree and context may be specified.

6.	The user is automatically logged into their default NDS tree using the WinFrame user name and default context.

7.	NDS logon scripts are supported.

NDS Restrictions

1	DOS and Windows NDS APIs are not supported. NDS aware applications will run only if they will operate in a Bindery (NetWare 3.x) mode.

2	The NDS(NetWare 4.x) administration utilities netadmin and nwadmin are not supported because DOS and Windows NDS APIs are not supported. It is possible to run these programs locally on a RAS client. See Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection for more information.

3.	NDS drive map objects are not supported. Use direct assignments to a volume and directory path instead.

4.	The administrator may occasionally get an error when trying to save changes to a user's NDS script, even though the script is not currently running. The user must log off before the script can be saved.

Installing the Software

On a computer running WinFrame 1.7, if you have not already installed Gateway Services for NetWare, use the following procedure.

Note

If you have installed WinFrame 1.7 as an upgrade to a WinFrame 1.6 system that was already running GSNW, no action is needed; GSNW is installed automatically.

1.	In the Program Manager, double-click on Control Panel in the Main group.

2.	Double-click Network.

3.	Click the Services tab.

4.	Click Add.

5.	Select Gateway Service for NetWare from the list, then click Add.

6.	In the resulting dialog box, type the path to your WinFrame 1.7 CD in the box, and then click OK.

When the file copying is finished, reboot the computer. See Accessing the NDS Tree for information on using Gateway Services for NetWare.


Changing the Default Name of Users' Windows Directories

By default, WinFrame uses a WINDOWS subdirectory in each user's home directory as the user's Windows directory. If you are migrating users whose current Windows directory name is not 'WINDOWS' to your WinFrame server, you may find it helpful to change the default setting. Note that this specification is global to the entire system. To change this setting, follow this procedure:

Warning

Make a backup of your Registry before changing any settings. See the topic Making a Backup Copy of the Registry for instructions on making a backup of the Registry.

1.	From the File menu in Program Manager, choose Run, type REGEDT32 in the Command Line box, and click OK to load the Registry Editor.

2.	From the Windows menu, select HKEY_LOCAL_MACHINE.

3.	Double-click on the Software folder, then double-click on the Citrix folder.

4.	From the Edit menu, choose Add Key. Name the key Windows.

5.	Click once on the newly created Windows folder.

6.	From the Edit menu, choose Add Value. Make the Value Name UserDirectoryName and the Data Type REG_SZ.

7.	A second dialog box will appear prompting you to enter a string. Enter the Windows directory name you want to use instead of WINDOWS.

The Windows directory can also be set to be the user's home directory by setting the Registry key to '.': HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Windows\UserDirectoryName = .

Note

When this value is set to '.', no WINDOWS subdirectory is created under the user's home directory; the home directory is used as the Windows directory. It is not recommended that the value be set to '.' because it is then difficult to tell which files in the user's home directory are used by Windows programs.

It is also possible to override this behavior on a per-application basis so that %SystemRoot% is returned to the GetWindowsDirectory system call. This allows specific applications to read and write .INI files to and from the %SystemRoot% directory instead of the user's home directory. See Application Integration in the Solutions Guide for instructions on setting the "Do not substitute user WINDOWS directory" compatibility bit.


WinFrame-Specific Environment Variables

There are a number of environment variables that can be used to simplify administering your WinFrame environment. These variables can be used in the Registry, to define user home directories, in login scripts, and in batch files.

Note

When these variables are used in the Registry, they must be capitalized as listed below to work.

The following variables can be used both on the server console, and on WinStations:

Variable Name	Example	Description
%HomeDrive%	P:	The location of the current user's home directory
%HomePath%	\USERS\ADAMM	The location of the current user's home directory
%HomeShare%	\\ZAPHOD\SYS2 \USERS \adamm	The uniform naming convention (UNC) name of the user's home directory (1)
%SystemDrive%	E:	The location of the WinFrame system files
%SystemRoot%	E:\WINFRAME	The location of the WinFrame system files
%UserName%	adamm	The username of the current user
CLIENTNAME	AdamClient	The client name specified in WFCNAME.INI on the client machine (2)
WINSTATIONNAME	tcp#002	The WinStation the client is logged on to (3)
1 If the user's home directory is not a shared network directory on a computer other than the WinFrame server, %HomeShare% will return nothing. To test for this condition in a batch file, use the following syntax:

IF "%HomeShare%" == "" GOTO HomeDirNotShared

2 For a session on the console, this will return "Console"

3 This variable is present only for ICA sessions. Sessions running on the console or on a DirectICA station will not have the WINSTATIONNAME environment variable.

These environment variables are set during logon. Therefore, if a user reconnects to a disconnected session, environment variables will not be changed. This can cause the CLIENTNAME and WINSTATIONNAME environment variables to be incorrect.

Usage Examples

If you want to copy a file named SAMPLE.TXT from the WINFRAME\SYSTEM32 directory into a user's own WINDOWS\SYSTEM32 directory every time the user logs on, create a batch file with the following command:

COPY %SystemRoot%\SYSTEM32\SAMPLE.TXT %HomeDrive%%HomePath%\WINDOWS\SYSTEM32

(Type the entire command on one line)

You could setup a LOGS directory on your WinFrame server with separate subdirectories for all users. You could then make a batch file to automatically copy a file named LOG.TXT from the current user's home directory to his or her subdirectory of the LOGS directory with the following command:

COPY %HomeDrive%%HomePath%\LOG.TXT %SystemDrive%\LOGS\%UserName%


Troubleshooting User Profiles

The following are error messages that you may encounter when using user profiles and how to solve them.

Unable to load your central profile. The cached copy of your profile will be loaded instead. Possible causes of this error include network problems, security rights, missing or corrupt profile.

Make sure the profile path follows the format \\ServerName\SHARENAME\Profilename.USR (or .MAN). The word SHARENAME is the share point that must be created for a directory that will contain the profiles. Check the permissions of the share point to make sure that users can use the directory. If the profiles happen to be stored on another server, make sure that server is running and accessible by the WinFrame server. Make sure that the user or group is configured to use the profile in the User Profile Editor.

Your locally cached profile is more recent than your central profile. Do you wish to update your central profile? If you choose NO, changes in your profile will be lost.

This is actually an alert and/or question-not an error. This can be caused by selecting a different profile in User Manager. When you log back in again, this message will pop up. It is telling you that the locally cached profile is more recent than your central profile (the one you opted to use the next time you log in.) If you say NO, any changes you made will not be saved to the central profile. If you say YES, any changes you made during the session will be saved to the profile, including the new profile you selected. This also happens if you have one copy of a profile running and make a change and then login again. The second connection will give this message. If the user's workstation is not part of the domain, the locally cached file is the only profile for that user. If the user's workstation is part of the domain, the user can have an additional server-based profile. If the user has a server-based personal profile, a locally cached version of this profile is saved at the workstation. This locally cached version is used when the server containing the user's profile is unavailable.

Loading User Profile. Your profile cannot be loaded. A copy of the default profile will be loaded instead.

This is an alert and/or an error. When a user's profile has not been assigned, or it is the first time a user logs on to a particular WinFrame computer, the computer's default profile is used. This may also occur if the user logs on to the guest account. A copy of this profile is saved, along with any changes the user makes to the environment. At all subsequent logons, the user's copy of the profile is loaded. However, a different user profile is saved at each computer the user logs on from; thus default profiles are dependent upon each computer that resides on the network. This also can be an error when your profile points to a .USR or .MAN file that does not exist and you have logged in before, but not since the system was rebooted. Auto-creation only works for the first login, so if the file is deleted, it will not be recreated. If this is the case but the system was already logged into before the profile was deleted, you will get the first error message listed. If making the user an administrator solves this problem it is one of two issues:

1.	The user does not have rights to the file.

2.	There are no Microsoft licenses on the server, preventing user access to shares. (This can be confirmed if changing the profile path from \\SERVERNAME\SHARENAME\%username%.man to C:\profiles\%username%.man solves the problem.

Unable to log you on because you do not have security access to information inside your mandatory profile. Please contact your Administrator.

This could be caused by not having specific access to the files specified in the profile (a wallpaper .BMP file, for example). Check the File Manager for specific Share Points to the necessary files and make sure the user is assigned under the specified .MAN profile.

Unable to log you on because your Mandatory Profile is Not Available. Please contact your Administrator.

This could be caused by not selecting the correct group or user that will be accessing these Profiles in the User Profile Editor "Permitted to Use" button. Also make sure the syntax and spelling of all the above settings are correct in User Manager for Domains. If making the user an administrator solves this problem it is one of two issues:

1. The user does not have rights to the file.

2. There are no Microsoft licenses on the server, preventing user access to shares. (This can be confirmed if changing the profile path from \\SERVERNAME\SHARENAME\%username%.man to C:\profiles\%username%.man also solves this issue.

NOTE: If this issue only occurs when some people who use mandatory profiles cannot login to WinFrame, increase the size of the registry in Control Panels / System under the Virtual Memory Button. You must reboot the server for this change to take effect. The size of these adjustments will vary as server environments are quite dissimilar.


TCP/IP Connections

TCP/IP WinStations, once configured on a WinFrame server, can be accessed by any of the WinFrame Clients over a LAN, a WAN, or the Internet. The names of all the WinFrame servers configured for TCP/IP WinStations are listed in the WinFrame server pull-down box when you configure a TCP/IP connection on a WinFrame client. You can also enter the network IP address of the WinFrame server in the Server box.

Setting TCP Keep Alives So TCP/IP Users Go To Disconnected State

By default, TCP/IP WinStations take two hours to recognize that a user has disconnected abnormally. The WinFrame server keeps the WinStation and its connected user in an "active" state for this two hour duration. If the same user reconnects within the two hour time period, he/she will receive a new session because the previous session is not in a disconnected state. The WinStation that is falsely in the "active" state will be unavailable for the two hour duration. This behavior is controlled by the default WinFrame (Windows NT) TCP protocol settings, because TCP/IP WinStations do not use "watchdog" packets like IPX, SPX, and NetBIOS WinStations.

The following Registry key contains the values that control this behavior:

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

As documented in the Windows NT Resource Kit, the values most important to WinStation connections are:

KeepAliveInterval     REG_DWORD     1 to 0xffffffff milliseconds

This parameter determines the interval separating keep alive retransmissions until a response is received. Once a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. The connection is ended after the number of retransmissions specified by TcpMaxDataRetransmissions have gone unanswered.

Default:  1000 (1 second)

KeepAliveTime     REG_DWORD     1 to 0xffffffff milliseconds

This parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If the remote system is still reachable and functioning, it acknowledges the keep alive transmission. Keep alive packets are not sent by default. This feature may be enabled on a connection by an application.

Default  7200000 (two hours)

TcpMaxDataRetransmissions     REG_DWORD     0 to 0xffffffff

This parameter controls the number of times TCP will retransmit an individual data segment (non- connect segment) before ending the connection. The retransmission timeout is doubled with each successive retransmission on a connection. It is reset when responses resume. The base timeout value is dynamically determined by the measured round-trip time on the connection.

Default:  5

The KeepAliveTime determines how often a keep alive packet is sent to TCP/IP WinStations. The default is two hours, which is too long. It is recommended that this value be set between 60000 and 300000 (1 to 5 minutes). Make sure that the "decimal" radio button is selected prior to typing this number into the Data field in the Registry Editor.

Once a keep alive packet is sent, the TcpMaxDataRetransmissions sets how many more keep alive packets will be sent before the connection is determined to be disconnected. The KeepAliveInterval sets the interval between these retransmission packets. It is not necessary to change these values - only the KeepAliveTime.

In summary, if no response is received after the first keep alive packet (every two hours by default), WinFrame will send another five keep alive packets with a one second interval between each packet. If no response is received, the user is disconnected from the WinStation and the WinStation is reset to an idle state.

Configuring a Firewall for TCP/IP WinStations

Note

If you will be using Published Applications across a firewall, you will need to install Hotfix SE170016.

Citrix ICA traffic uses the registered port 1494 with the TCP protocol. If you have a firewall or other TCP/IP network security protection, you need to configure it to allow information to pass to this port number on any WinFrame servers on your network. Allowing ICA traffic through a firewall generally entails defining a rule to allow port access for port 1494 traffic in the proper direction. If a

user receives a "There is no route to the specified address" message, this is usually due to a firewall not allowing port 1494 access.

If your firewall does not support port 1494 (for example: if your firewall does not support port numbers greater than 1024 or port 1494 is in use by another application), you can configure the client and server to use a different port number. Use the icaport command-line utility to change the default port number on the server. Refer to Appendix A, "WinFrame Command Reference" of the System Guide for information about the icaport utility. All WinFrame Client computers must then be changed to use the new port by editing the application properties.

To Modify a Remote Application Manager Entry to Use a Different ICA Port

1.	Load the Remote Application Manager.

2.	Click on the application entry to modify.

3.	Press ALT+ENTER to display the Properties window.

4.	In the server field, type a colon (:) and then the specified port number after the server name. For example, to connect to the server www.yourcompany.com through port 5000 enter www.yourcompany.com:5000 in the server field.

5.	Click the OK button to save the changes.

TCP/IP Timeouts

If the connection to a TCP/IP WinStation fails, some time can elapse before the WinFrame server recognizes that the remote control session is disconnected. After this time period, the user on that TCP/IP WinStation is left in a disconnected state or logged out, depending on the settings for the TCP/IP WinStations in the WinStation Configuration utility.

Because other users cannot connect to the TCP/IP WinStation during the timeout period, it is a good idea to reduce the Idle Timeout for TCP/IP WinStations in the WinFrame WinStation Configuration utility to approximately 15 minutes.

If your WinFrame server has a large amount of memory, you might want to configure more TCP/IP WinStations as well. This will ensure that free TCP/IP WinStations are available to users trying to connect during any 15 minute idle periods. This is particularly important when users connect with IP over RAS dial-in connections, where phone lines can get dropped.

Browsing for a WinFrame Server

The WinFrame TCP/IP client uses the UDP (User Datagram Protocol) feature of the TCP/IP protocol suite when browsing for a WinFrame server. UDP is a connectionless mode protocol, providing a potentially unreliable, unsequenced, and/or duplicated (since it leaves these functions to other protocol layers) communications layer. The WinFrame client broadcasts UDP packets to the network with a destination address of UDP port 1604 (0644 hex) and the source address of the client is any high UDP port (any port over 1023). A WinFrame server replies with a UDP packet where the data area contains the names of the current WinFrame servers. The pull down list is built using this information. This use of UDP can be eliminated by connecting using the IP address rather than by browsing.

Connecting to the WinFrame Server

WinFrame TCP/IP client connections actually use the TCP (Transmission Control Protocol) feature of the TCP/IP suite of protocols for communication between the server and client. TCP is a connection-oriented, end-to-end protocol. It provides reliable, sequenced, and unduplicated delivery of bytes to a remote or local user.

Any application that uses TCP as the transport is assigned a unique port identification number called a TCP Port. All TCP communications between the client and a server takes place through this TCP port. The client side dynamically assigns a port number when there is a request for service. The server side of the application uses a port number that has been pre-assigned by the InterNet Assigned Numbers Authority (IANA).

ICA has been assigned port 1494 in the same way FTP uses port 21 or HTTP uses port 80. For further information regarding ICA and port 1494 refer to RFC 1700.

The process of connecting to a WinFrame server from an ICA client is actually very similar to an FTP connection. The following steps are only a local subnet connection to simplify this discussion, crossing routers or WANs bring the same factors and concerns to WinFrame connection as any IP traffic would.

First the client ARPs for the hardware address of the server so it can begin the connection.

Once the hardware address is known the client sends a TCP packet to TCP Port 1494 (05d6 hex) on the server with a source TCP Port that is a high TCP Port (TCP Ports over 1023). The client TCP Port is randomly selected from available ports over 1023 at the time of connection.

At this point the server normally accepts the request from the client and the connection is negotiated at 1494 inbound and whatever port the client requested outbound. These negotiated ports remain valid for the duration of the session.


Client Scripting

The WinFrame clients that ship with WinFrame Version 1.7 support a limited scripting language. This script language can be used to negotiate asynchronous, X.25, or dial-up connections to a WinFrame server. It may also be useful for connections that go through a security device that requires additional authentication before starting the ICA session. As soon as ICA traffic is detected, the script is aborted and the WinFrame session is started. To view the progress of the script, check the "Display terminal window when making Dial-In Connections" checkbox in the preferences for the Remote Application Manager session.

Add these commands to a text file using a text editor (the Windows Notepad, for example). The file can be any name valid for DOS (an 8 character filename with a 3 character extension); long filenames are not supported. There is no user interface provided for using these scripts.

To Configure Scripting

1.	Edit the APPSRV.INI file and add the following lines to the [WFClient] section.

ScriptDriver=SCRIPT.DDL

ScriptDriverWin16=SCRIPTW.DLL

ScriptDriverWin32=SCRIPTN.DLL

ScriptFile=

2.	To attach a script file to a "Remote Application" you need to edit the APPSRV.INI file and add the following line to the section for the Remote Application.

ScriptFile=<script path\filename>

Example: suppose you create a script file named X25.SCR in the root directory of C: for the Remote Application "MyHost".  The line would look as follows:

[MyHost]

ScriptFile=C:\X25.SCR

Script Commands

;

Comment; anything after the semicolon (to end of line) is ignored.

BEEP

Provide a bell sound for debugging purposes.

EXIT

Terminate and unload the scripting driver.

SEND STRING "string"

Send the characters in the "string" as ASCII keystrokes.

SET IGNORECASE [ON | OFF]

Set case sensitive string compares for the WAIT command.

WAIT RECEIVE [time]

Wait for any character to be received, timeout optional.

WAIT SILENCE time

Wait for "time" seconds of silence.

WAIT STRING "string" [time]

Wait for "string" to be received, timeout optional.

WAIT TIME time

Wait for "time" seconds.


RAS page 52
Remote Access Service manual page 52

3.	The user types the current callback number in the dialog box and waits for the server to return the call.

Set this option to minimize telephone charges for anyone, such as field representatives, calling in from various locations.

No Callback

If the user account has not been configured for callback, the Remote Access Service establishes a connection as soon as the user's name and password is authenticated.

Network Access Permission

After passing remote access authentication and connecting to the LAN, users can access resources on the WinFrame server for which they have permission. For example, they can:

Do anything on the network for which they have privilege.

Use any network resource for which they have permission such as:

Use the File Manager to access files on the LAN server.

Access client-server applications such as electronic mail or SQL Server.

Remote users are also subject to WinFrame and Windows NT Server security, just as they are at the office. In other words, they cannot do anything for which they lack privilege, nor can they access resources for which they do not have permission.

Note

Remote access authentication does not negate security restrictions on the file or WinFrame server.

For information about adding a remote client to a domain, see Remote Access online Help, Control Panel Help, and Chapter 15, "Server Manager," in the System Guide.


Network Messages and Event Log Error Codes

Network messages have an error code or message identification number associated with them and can be seen by typing net helpmsg message_number at the command prompt where message_number is the identification number. They can also be divided into two groups: Windows NT Workstation/Windows NT Server Network Messages and Down-level Network Messages.

ID	Message Text
2102	The workstation driver is not installed.
2104	An internal error occurred. The network cannot access a shared memory segment.
2105	A network resource shortage occurred.
2106	This operation is not supported on workstations.
2114	The Server service is not started.
2115	The queue is empty.
2116	The device or directory does not exist.
2118	The name has already been shared.
2119	The server is currently out of the requested resource.
2121	Requested addition of items exceeds the maximum allowed.
2123	The API return buffer is too small.
2136	A general network error occurred.
2137	The Workstation service is in an inconsistent state. Restart the computer before restarting the workstation service.
2138	The workstation service has not been started.
2140	An internal Windows NT error occurred.
2141	The server is not configured for transactions.
2142	The requested API is not supported on the remote server.
2144	The computer name already exists on the network. Change it and restart the computer.
2146	The specified component could not be found in the configuration information.
2147	The specified parameter could not be found in the configuration information.
2150	The printer does not exist.
2151	The print job does not exist.
2180	The service does not respond to control actions.
2182	The requested service has already been started.
2184	The service has not been started.
2185	The service name is invalid.
2186	The service is not responding to the control function.
2187	The service control is busy.
2189	The service could not be controlled in its present state.
2191	The requested pause or stop is not valid for this service.
2194	A thread for the new service could not be created.
2202	The user name or group name parameter is invalid.
2203	The password parameter is invalid.
2211	The server is configured without a valid user path.
2219	The security database could not be found.
2220	The group name could not be found.
2221	The user name could not be found.
2222	The resource name could not be found.
2223	The group already exists.
2224	The user account already exists.
2226	This operation is only allowed on the primary domain controller of the domain.
2227	The security database has not been started.
2229	A disk I/O failure occurred.
2233	Unable to add to the user accounts database session cache segment.
2234	This operation is not allowed on this special group.
2236	The user already belongs to this group.
2237	The user does not belong to this group.
2239	This user account has expired.
2240	The user is not allowed to log on from this workstation.
2241	The user is not allowed to log on at this time.
2242	The password of this user has expired.
2245	The password is shorter than required.
2246	The password of this user is too recent to change.
2247	The security database is corrupted.
2249	This replicant database is outdated; synchronization is required.
2250	The network connection could not be found.
2251	This asg_type is invalid.
2270	The computer name could not be added as a message alias. The name may already exist on the network.
2273	This message alias could not be found on the network.
2276	This message alias already exists locally.
2277	The maximum number of added message aliases has been exceeded.
2278	The computer name could not be deleted.
2280	An error occurred in the domain message processor.
2281	The message was sent but the recipient has paused the Messenger service.
2282	The message was sent but not received.
2283	The message alias is currently in use. Try again later.
2285	The name is not on the local computer.
2289	The broadcast message was truncated.
2294	This is an invalid device name.
2297	A duplicate message alias exists on the network.
2298	This message alias will be deleted later.
2299	The message alias was not successfully deleted from all networks.
2310	This shared resource does not exist.
2311	This device is not shared.
2312	A session does not exist with that computer name.
2351	This computer name is invalid.
2357	Could not determine the type of input.
2362	The buffer for types is not big enough.
2378	This log file has changed between reads.
2401	There are open files on the connection.
2403	This share name or password is invalid.
2404	The device is being accessed by an active process.
2432	An invalid or nonexistent alert name was raised.
2453	Could not find the domain controller for this domain.
2457	This server's clock is not synchronized with the domain controller's clock.
2470	Try down-level (remote admin protocol) version of API instead.
2481	The UPS service is not configured correctly.
2482	The UPS service could not access the specified COM Port.
2483	The UPS indicated a line fail or low battery situation. Service not started.
2484	The UPS service failed to perform a system shutdown.
2550	The browser service was configured with MaintainServerList=No.
3020	A power failure was detected at name. The server has been paused.
3021	Power has been restored at name. The server is no longer paused.
3022	The UPS service is starting shutdown at name due to low battery.
3023	There is a problem with a configuration of user specified shutdown command file. The UPS service started anyway.
3030	The server cannot export directory name to client name. It is exported from another server.
3031	The replication server could not update directory name from the source on name due to error code.
3032	Master name did not send an update notice for directory name at the expected time.
3034	The domain controller for domain name failed.
3035	Failed to authenticate with name, a Windows NT Server for domain name.
3038	Replicator could not access name on name due to system error code.
3039	Replicator limit for files in a directory has been exceeded.
3040	Replicator limit for tree depth has been exceeded.
3041	The replicator cannot update directory name. It has tree integrity and is the current directory for some process.
3042	Network error code occurred.
3045	System error code occurred.
3047	IMPORT path path cannot be found.
3049	Replicated data has changed in directory name.
3051	The Registry or the information you just typed includes an illegal value for text.
3054	A request for resource could not be satisfied.
3056	A system error has occurred.
3057	An internal consistency error has occurred.
3060	The service did not respond to control and was stopped with the DosKillProc function.
3061	An error occurred when attempting to run the service program.
3062	The sub-service failed to start.
3064	There is a problem with the file.
3095	This Windows NT computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.
3096	The Windows NT primary domain controller for this domain could not be located.
3100	The operation failed because a network software error occurred.
3106	An unexpected network control block (NCB) was received. The NCB is the data.
3112	An illegal server message block (SMB) was received. The SMB is the data.
3113	Initialization failed because the requested service name could not be started.
3140	The service has stopped due to repeated consecutive occurrences of a network control block (NCB) error. The last bad NCB follows in raw data.
3152	An illegal server message block (SMB) was received. The SMB is the data.
3170	The Alerter service had a problem creating the list of alert recipients. The error code is code.
3172	There was an error sending name the alert message text. The error code is code.
3173	There was an error in creating or reading the alerter mailslot. The error code is code.
3206	The replicator cannot update directory name. It has tree integrity and is the current directory for some process.
3207	The server cannot export directory name to client name. It is exported from another server.
3208	The replication server could not update directory name from the source on name due to error code.
3209	Master name did not send an update notice for directory name at the expected time.
3210	Failed to authenticate with name, a Windows NT Server for domain name.
3212	Network error code occurred.
3215	Unrecognized message received in mailslot.
3216	System error code occurred.
3218	IMPORT path path cannot be found.
3222	Replicator could not access filename on name due to code system error.
3223	The primary domain controller for domain name has apparently failed.
3224	An error occurred while changing this computer's password.
3226	An error occurred while synchronizing with primary domain controller name.
3230	A power failure was detected at the server.
3231	The UPS service performed server shutdown.
3232	The UPS service did not complete execution of the user-specified shutdown command file.
3236	The UPS service failed to execute a user-specified shutdown command file filename. The error code is the data.
3257	The system returned an unexpected error code. The error code is the data.
3408	The program cannot be used with this operating system.
3501	You used an invalid option.
3502	System error code has occurred.
3503	The command contains an invalid number of arguments.
3504	The command completed with one or more errors.
3505	You used an option with an invalid value.
3506	The option name is unknown.
3507	Option name is ambiguous.
3510	A command was used with conflicting switches.
3511	Could not find subprogram name.
3513	More data is available than can be returned by Windows NT.
3515	This command can be used only on a Windows NT Server system.
3521	The name service is not started.
3523	The name service could not be started.
3527	The name service is stopping.
3528	The name service could not be stopped.
3533	The service is starting or stopping. Please try again later.
3534	The service did not report an error.
3538	The name service failed to resume.
3539	The name service failed to pause.
3540	The name service continue is pending text
3541	The name service pause is pending text
3544	The name service has been started by another process and is pending text
3547	A service-specific error occurred: code.
3679	An error occurred while reading your profile.
3689	The Workstation service is already running. Windows NT will ignore command options for the workstation.
3691	There are open files and/or incomplete directory searches pending on the connection to name.
3710	An error occurred while opening the Help file.
3711	The Help file is empty.
3712	The Help file is corrupted.
3713	Could not find a primary domain controller for domain name.
3716	The device type is unknown.
3719	A matching share could not be found so nothing was deleted.
3721	The password is invalid for name.
3722	An error occurred while sending a message to name.
3723	The password or user name is invalid for name.
3725	An error occurred when the share was deleted.
3726	The user name is invalid.
3727	The password is invalid.
3728	The passwords do not match.
3729	Your persistent connections were not all restored.
3730	This is not a valid computer name or domain name.
3732	Default permissions cannot be set for that resource.
3734	A valid password was not entered.
3735	A valid name was not entered.
3736	The resource named cannot be shared.
3737	The permissions string contains invalid permissions.
3738	You can only perform this operation on printers and communication devices.
3742	Name is an invalid user or group name.
3743	The server is not configured for remote administration.
3753	User username is not a member of group name.
3754	User username is already a member of group name.
3755	There is no such user: username.
3756	This is an invalid response.
3757	No valid response was provided.
3760	Date is not a recognized day of the week.
3761	The time range specified ends before it starts.
3762	Number is not a recognized hour.
3763	Number is not a valid specification for minutes.
3764	Time supplied is not exactly on the hour.
3765	12 and 24 hour time formats may not be mixed.
3766	Text is not a valid 12-hour suffix.
3767	An illegal date format has been supplied.
3768	An illegal day range has been supplied.
3769	An illegal time range has been supplied.
3770	Arguments to NET USER are invalid. Check the minimum password length and/or arguments supplied.
3771	The value for ENABLESCRIPT must be YES.
3773	An illegal country code has been supplied.
3774	The user was successfully created but could not be added to the USERS local group.
3775	The user context supplied is invalid.
3776	The dynamic-link library name could not be loaded or an error occurred while trying to use it.
3777	Sending files is no longer supported.
3778	You may not specify paths for ADMIN$ and IPC$ shares.
3779	User or group name is already a member of local group name.
3780	There is no such user or group: name.
3781	There is no such computer: computer name.
3782	The computer computer name already exists.
3790	The system could not find message: text.
3802	This schedule date is invalid.
3805	The Server service has not been started.
3806	The AT job ID does not exist.
3809	The command line cannot exceed 259 characters.
3813	The AT schedule file was deleted.
3815	The AT command has timed-out. Please try again later.
3816	The minimum password age for user accounts cannot be greater than the maximum password age.
3817	You have specified a value that is incompatible with servers with down-level software. Please specify a lower value.
3870	Computer name is not a valid computer name.
3871	Code is not a valid Windows NT message number.
3912	Could not locate a time-server.
3913	Could not find the primary domain controller for domain name.
3915	The user's home directory could not be determined.
3916	The user's home directory has not been specified.
3917	The name specified for the user's home directory name is not a universal naming convention (UNC) name.
3932	Name is not a valid domain or workgroup name.
3951	You specified too many values for the name option.
3952	You entered an invalid value for the name option.
3953	The syntax is incorrect.
3960	You specified an invalid file number.
3961	You specified an invalid print job number.
3963	The user or group account specified cannot be found.
4738	The share name entered is not accessible from an MS-DOS workstation. Are you sure you want to use this share name? name:
5022	Printing errors occurred.
5305	A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data.
5309	No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data.
5317	The local session table is full. The network control block (NCB) request was refused. The NCB is the data.
5334	There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data.
5508	The security database full synchronization has been initiated by the server name.
5509	Windows NT could not be started as configured. A previous working configuration was used instead.
5510	The exception 0xnumber occurred in the application application at location 0xnumber.
5511	The server name claims to be a primary domain controller for the name domain. However, the security identifier on the server name in that domain and on the primary domain controller name don't match. One of the servers should be removed from the domain.
5512	The server name and name both claim to be the primary domain controller for the name domain. One of the servers should be demoted or removed from the domain.
5513	The computer computer name connected to server name using the trust relationship to the name domain. However, the computer doesn't properly know the security identifier (SID) for the domain. Reestablish the trust relationship.
5601	The password for this computer is not found in the local security database.
5602	An internal error occurred while accessing the computer's local or network security database.
5700	The Netlogon service could not initialize the replication data structures successfully. The service is terminated.
5701	The Netlogon service failed to update the domain trust list.
5702	The Netlogon service could not add the RPC interface. The service is terminated.
5703	The Netlogon service could not read a mailslot message from name.
5704	The Netlogon service failed to register the service with the service controller. The service is terminated.
5705	The change log cache maintained by the Netlogon service for database changes is corrupted. The Netlogon service is resetting the change log.
5706	The Netlogon service could not create server share name.
5707	The down-level logon request for the user username from name failed.
5708	The down-level logoff request for the user username from name failed.
5709	The Windows NT network logon request for the user name from computer name (via name) failed.
5710	The Windows NT network logoff request for the user name from computer name failed.
5711	The partial synchronization request from the server name completed successfully. Number change(s) has (have) been returned to the caller.
5712	The partial synchronization request from the server name failed.
5715	The partial synchronization replication of the name database from the primary domain controller name completed successfully. Number change(s) is (are) applied to the database.
5716	The partial synchronization replication of the name database from the primary domain controller name failed.
5717	The full synchronization replication of the name database from the primary domain controller name completed successfully.
5718	The full synchronization of the name database from the primary domain controller name failed.
5719	No Windows NT Server for the domain name is available.
5720	The session setup to the Windows NT Server name for the domain name failed because the computer computer name does not have a local security database account.
5721	The session setup to the Windows NT Server name for the domain name failed because the Windows NT Server does not have an account for the computer computer name.
5722	The session setup from the computer computer name failed to authenticate. The name of the account referenced in the security database is username.
5723	The session setup from the computer computer name failed because there is no trust account in the security database for this computer. The name of the account referenced in the security database is username.
5724	Could not register control handler with service controller name.
5725	Could not set service status with service controller name.


General WinFrame Client Errors

The following table lists the error messages that may be returned by the WinFrame clients.

Error	Description	Text Message
1000	DLL_NOT_FOUND	"The DLL file or a DLL referenced by it was not found"
	To track this error down, compare the client .DLLs with a client that is working correctly and see which are different; or do a re-install of the client into the same directory.
1001	NO_MEMORY	"Insufficient memory"
1002	BAD_OVERLAY	"Bad overlay"
1003	BAD_PROCINDEX	"Bad procedure index"
1004	BUFFER_TOO_SMALL	"Buffer too small"
	Can be caused by hotfixes being out of sync or not installed correctly.  Verify hotfixes are installed successfully using the command HOTFIX /V; see if the same hotfixes are applied to the working and non-working servers.  Do the same for any client hotfixes.
1005	CORRUPT_ALLOC_HEADER	"Corrupt memory header"
1006	CORRUPT_ALLOC_TRAILER	"Corrupt memory trailer"
1007	CORRUPT_FREE_HEADER	"Corrupt free header"
1008	CORRUPT_SEG_HEADER	"Corrupt segment header"
1009	MEM_ALREADY_FREE	"Memory already free"
1010	MEM_TYPE_MISMATCH	"Memory type mismatch"
1011	NULL_MEM_POINTER	"Null pointer"
1012	IO_PENDING	"I/O pending"
1013	INVALID_BUFFER_SIZE	"Invalid buffer size"
1014	INVALID_MODE	"Invalid mode"
1015	NOT_OPEN	"Not open"
1016	NO_OUTBUF	"No output buffer"
1017	DLL_PROCEDURE_NOT_FOUND	"DLL procedure not found"
1018	DLL_LARGER_THAN_256K	"DLL larger than 256K"
1019	DLL_BAD_EXEHEADER	"Corrupted DLL"
1020	OPEN_FAILED	"Open failed"
1021	INVALID_HANDLE	"Invalid handle"
1022	VD_NOT_FOUND	"Virtual Driver not found"
1023	WD_NAME_NOT_FOUND	"WinStation Driver name not found in MODULE.INI"
1024	PD_NAME_NOT_FOUND	"Protocol Driver name not found in MODULE.INI"
1025	THINWIRE_OUTOFSYNC	"Thinwire out of sync"
1026	NO_MOUSE	"Mouse not available"
1027	INVALID_CALL	"Invalid request"
1028	QUEUE_FULL	"Queue is full"
1029	INVALID_DLL_LOAD	"Invalid DLL load"
1030	PD_ERROR	"Protocol Driver error"
1031	VD_ERROR	"Virtual Driver error"
1032	ALREADY_OPEN	"Already open"
1033	PORT_NOT_AVAILABLE	"Port not available"
1034	IO_ERROR	"Communication I/O Error"
1035	THINWIRE_CACHE_ERROR	"Thinwire cache error"
1036	BAD_FILE	"Bad file"
1037	CONFIG_NOT_FOUND	"WFCLIENT.INI not found"
1038	SERVER_FILE_NOT_FOUND	"APPSRV.INI not found"
1039	PROTOCOL_FILE_NOT_FOUND	"MODULE.INI not found"
1040	MODEM_FILE_NOT_FOUND	"MODEM.INI not found"
1041	LAN_NOT_AVAILABLE	"LAN not available"
1042	PD_TRANSPORT_UNAVAILABLE	"Transport not available"
1043	INVALID_PARAMETER	"Invalid Parameter"
1044	WD_NOT_LOADED	"No WinStation Driver is loaded"
1045	NOT_CONNECTED	"Not connected to a WinFrame Server"
1046	VD_NOT_LOADED	"The Virtual Driver is not loaded"
1047	ALREADY_CONNECTED	"Already connected to a WinFrame Server"
1048	WFENGINE_NOT_FOUND	"Can't find the WinFrame Engine %s."
1049	ENTRY_NOT_FOUND	"Entry not found in APPSRV.INI"
1050	PD_ENTRY_NOT_FOUND	"Protocol Driver for Entry not found in APPSRV.INI"
1051	WD_ENTRY_NOT_FOUND	"WinStation Driver for Entry not found in APPSRV.INI"
1052	PD_SECTION_NOT_FOUND	"Protocol Driver section not found in MODULE.INI"
1053	WD_SECTION_NOT_FOUND	"WinStation Driver section not found in MODULE.INI"
1054	DEVICE_SECTION_NOT_FOUND	"Device section not found in WFCLIENT.INI"
1055	VD_SECTION_NOT_FOUND	"Virtual Driver section not found in MODULE.INI"
1056	VD_NAME_NOT_FOUND	"Virtual Driver name not found in MODULE.INI"
1057	SERVER_CONFIG_NOT_FOUND	"[WFClient] section not found in APPSRV.INI"
1058	CONFIG_CONFIG_NOT_FOUND	"[WFClient] section not found in WFCLIENT.INI"
1059	HOTKEY_SHIFTSTATES_NOT_FOUND	"[Hotkey Shift States] section not found in MODULE.INI"
1060	HOTKEY_KEYS_NOT_FOUND	"[Hotkey Keys] section not found in MODULE.INI"
1061	KEYBOARDLAYOUT_NOT_FOUND	"[KeyboardLayout] section not found in MODULE.INI"
1062	UI_ENGINE_VER_MISMATCH	"Invalid client window process"
1063	IPC_TIMEOUT	"The client window process is not responding"
1064	UNENCRYPT_RECEIVED	"Data error, received unexpected unencrypted data"
1065	NENUM_NOT_DEFINED	"No network enumerator is defined in MODULE.INI"
1066	NENUM_NO_SERVERS_FOUND	"No WinFrame servers could be found"
1067	NENUM_NETWORK_ERROR	"A network error was encountered while searching for WinFrame servers"
1068	NENUM_WINDOWS95_NOT_SUPPORTED	"This feature is not supported in Windows95.  Use the WinFrame Server's IP address for TCP/IP or the network:node address for IPX/SPX."
1069	CONNECTION_TIMEOUT	"Connection dropped because of communication errors"
	This is the most common error reported back to the client. This can be caused by a line problem, a bad client or server network card, or a modem or phone line issue. This usually occurs when the line is interupted or dropped.
1070	DRIVER_UNSUPPORTED	N/A
1071	NO_MASTER_BROWSER	"Unable to contact the WinFrame Server Browser. Either your network is not functional,  or you need to configure an address under Server Browsing."
1072	TRANSPORT_NOT_AVAILABLE	"The specified Network Protocol is not available."
1073	NO_NAME_RESOLVER	N/A
1074	SEVEN_BIT_DATA_PATH	"A seven bit data path was detected to the WinFrame server.  An eight bit data path is required."
1075	WIN16_WFENGINE_ALREADY_RUNNING	"Your WinFrame Client connection is already running."


ICA File Syntax

ICA files are usually generated by an application such as the ICA File Editor or Application Configuration. This section contains a description of the syntax of an ICA file so that you can manually create or modify an ICA file if desired. These ICA file can also be used to create custom WinFrame client diskettes. See Creating Customized WinFrame Client Diskettes for more information.

The contents of an ICA file

Use a simple text editor such as Notepad to create and modify ICA files. A sample ICA file is shown below:

; CUSTOMER.ICA - ICA file to access a Customer Database using Microsoft Access

;

; The [ApplicationServers] section contains the name of the

; connection or published application defined by the ICA file.

; The name below (Access) appears in the title bar of the client window.

;

[ApplicationServers]

Access=

; The [<EntryName>] section describes the attributes of the connection or

; published application defined in the [ApplicationServers] section above.

; The name in the square brackets must exactly match the name defined in the

; [Application Servers] section above; in this example, Access.

;

[Access]

TransportDriver=TCP/IP

Address=206.103.132.12

WinStationDriver=ICA 3.0

Username=JBLOGGS

Domain=ABC

Password=000100

InitialProgram=d:\access\msaccess.exe d:\shareacc\access\nwind.mdb /X customer

WorkDirectory=d:\access

ClientAudio=On

UseAlternateAddress=0

;

KeyboardTimer=100

MouseTimer=50

;

; Use either ScreenPercent or DesiredHRES and DesiredVRES to specify

; the size of the client window.

; If both ScreenPercent and DesiredHRES and DesiredVRES are specified,

; only ScreenPercent is used.  ScreenPercent is available only with

; the Citrix Web Client.

ScreenPercent=75

DesiredHRES=640

DesiredVRES=480

DesiredColor=2

; The [WFClient] section describes the WinFrame Client.

;

[WFClient]

Version=2

The [ApplicationServers] Section

The [ApplicationServers] section defines the remote application entry referred to by the ICA file. The [ApplicationServers] section contains the following fields:

[Application Server]

This is the section header. This field is required and must be entered exactly as shown.

EntryName=

Defines the name of the remote application entry. The name must be followed by an equal sign. This name is used in the title bar of the client window.

The [EntryName] Section

The [EntryName] section begins with the EntryName defined in the [ApplicationServers] section enclosed in square brackets, or [Access] in the above example. The [EntryName] section contains the following fields:

TransportDriver=

The data transport type. Usually TCP/IP, but can also be IPX, SPX, or NetBIOS. This is a required field.

Address=

The address of the remote Citrix server. For TCP/IP connections, it can be the DNS name of a Citrix server, the IP address of a Citrix server, or the name of a published application, for example Database. For IPX, SPX, and NetBIOS connections, it can be the name of a Citrix server or the name of a published application. This is a required field.

WinStationDriver=ICA 3.0

Defines the presentation protocol as ICA 3.0. This is a required field.

Username=

Specifies the name of a user account to log on as. This is an optional field.

Domain=

Specifies the domain to log on to. This is an optional field.

Password=

Specifies the password for the user account. This is an optional field. The password, if used, must be encrypted. To enter an encrypted password into the ICA file, use the Citrix ICA Client Remote Application Manager New Entry Wizard to create a remote application entry. When you are prompted for the username and password, enter the password that you want to use in the ICA file. Finish the New Entry wizard. Open the file APPSRV.INI in the Windows directory and locate the entry you just created. Copy the password value and paste it into your ICA file.

ClearPassword=

Specifies the clear text (unencrypted) password for the user account. This is an optional field. To use a clear text password, the Password field must be set to a null value (for example: Password=).

InitialProgram=

Specifies the path of the application on the Citrix server to be automatically launched when the connection is made. Include any command line options. This is an optional field. If no initial program is specified, Program Manager is launched. If the name of a published application is specified in the Address field, the name of the published application must appear here prefixed with a pound sign (#), for example #Database. The published application name must be entered exactly as it is in the Address field.

WorkDirectory=

Specifies the working directory used for the application.

ScreenPercent=

Specifies the horizontal and vertical pixel resolution as a percentage of the client desktop size. If the ScreenPercent field is present, the DesiredHRES and DesiredVRES fields are ignored.

DesiredHRES=

Specifies the horizontal window size in pixels. If the ScreenPercent field is present, the DesiredHRES and DesiredVRES fields are ignored.

DesiredVRES=

Specifies the vertical window size in pixels. If the ScreenPercent field is present, the DesiredHRES and DesiredVRES fields are ignored.

DesiredColor=1 | 2

DesiredColor sets the color palette depth. Use 1 for 16-color and 2 for 256-color. The default is 2 (256-color).

ClientAudio=On | Off

Specifies if client audio is enabled. This is an optional field, and audio is disabled if the ClientAudio statement is not present.

UseAlternateAddress=0 | 1

This is an optional field, only used to support accessing Citrix server across a firewall. Firewalls use IP address translation to convert public (Internet) IP addresses into private (Intranet) IP addresses. Public IP addresses are called external addresses because they are external to the firewall, while private IP addresses are called internal addresses.

When an ICA client is configured for TCP/IP server location, it sends a directed UDP datagram to the server location IP address using TCP/IP port 1604. For communication to be successful between an ICA client and a Citrix server with an intervening firewall, the firewall must be configured so it will pass UDP port 1604 packets. Server location is configured in Remote Application Manager by selecting Settings from the Options menu.

If a fixed server location address is specified, the ICA client contacts that server to determine the address of the ICA master browser. When the ICA client connects by server or published application name, the ICA master browser returns the address of the desired server or published application.

If UseAlternateAddress=1 is specified, the client will request the IP address of the Citrix server's alternate address. UseAlternateAddress can only be used for TCP/IP connections. You must specify the IP address of the Citrix server that is configured for server location by including the statement TcpBrowserAddress=ipaddress in the [WFClient] section of the ICA file, where ipaddress is the IP address of the Citrix server; for example, 123.321.234.23. You must also use the ALTADDR command on the Citrix server with IP address ipaddress that is accessed by the ICA file.

See the "Load Balancing and Application Publishing Across a Firewall" topic in the WINFRAME Readme for more information about alternate addresses and the ALTADDR command.

KeyboardTimer=value

Specifies a time interval, in milliseconds, during which keyboard input will be collected before being sent to the Citrix server. The default value of 100 milliseconds is optimized for WANs; in a Dial-In or LAN environment, reducing this value may give better responsiveness. Using too low a value in a LAN environment may cause a large number of small packets to be generated, which may affect network performance.

MouseTimer=value

Specifies a time interval, in milliseconds, during which mouse input will be collected before being sent to the Citrix server. The default value of 100 milliseconds is optimized for WANs; in a Dial-In or LAN environment, reducing this value may give better responsiveness. Using too low a value in a LAN environment may cause a large number of small packets to be generated, which may affect network performance.

The [WFClient] Section

Version=2

Specifies the version of the client software. Do not change this value. This is a required field.

TcpBrowserAddress=ipaddress

Specifies the IP address of a Citrix server used for server location. This field is required if UseAlternateAddress=1 is specified in the [EntryName] section.


Creating Customized WinFrame Client Diskettes

Many system administrators want to create customized WinFrame PC Client installation diskette sets that are preconfigured for their users; for example, with a default set of predefined connection entries or published applications. Because most customization information for the WinFrame Clients is contained in several .INI files, this is not hard to do.

This document explains how to create a customized set of install diskettes for the WinFrame DOS and Win32 clients. This is not supported for the Win16 Client.

To create a customized WinFrame Client installation set:

1.	Create a diskette installation set for the desired client. To do this, start the WinFrame Client Creator, select the client from the client list, and follow the on-screen directions.

2.	Use the diskette installation set created in Step 1 to install the WinFrame PC Client on a target PC.

3.	Start the WinFrame PC Client and configure the client for your end users. This includes creating remote application entries and configuring any preferences, settings, modems, and direct serial connections.

4.	The changes you have made are stored in several .INI files:

A.	Changes to the client default settings are stored in the files WFCLIENT.INI and MODULE.INI.

B.	Remote application entries are stored in the file APPSRV.INI.

These files are present on the installation diskettes, but with an .SRC extension; for example, APPSRV.SRC.

5.	Compare the .INI files on the client directory of the client machine with the corresponding .SRC files on the installation diskette. For example, to compare the MODULE.INI file with the corresponding MODULE.SRC file on the diskette, type: COMP MODULE.INI A:MODULE.SRC and press ENTER.

6.	For all files that have changed, replace the .SRC files on the diskettes with the correpsonding .INI files, renamed to have a .SRC extension. For example, if the file MODULE.INI has changed, type: COPY MODULE.INI A:MODULE.SRC and press ENTER to replace it on the diskette.

7.	When you are finished creating the custom installation diskettes, you can use the DISKCOPY command to make copies of the diskettes, or you can replace the affected files in the directory %systemroot%\SYSTEM32\CLIENTS\<client>\DISKS\DISK<n> on the WinFrame server, where <client> is the client directory (WFCDOS or WFC32) and <n> is the disk number, and then use the WinFrame Client Creator to create installation diskettes.

Note

You may want to make a backup of the client installation files before overwriting client files. If you do not and want to use the original client files at a later time, they can be found in the \WFCLIENT directory of the WinFrame CD-ROM.


Additional Notes About Windows NT

This document contains information not available in the Microsoft Windows NT Installation Guide or in online Help, as well as information on changes that occurred after publication.

Additional information is available in the files PRINTER.WRI and NETWORK.WRI. PRINTER.WRI contains information related to printing, including information on specific printers. NETWORK.WRI contains information related to networks, including information on network adapter cards and network interoperability.

Note

The following information is from the Microsoft Windows NT 3.51 documentation, and is Copyright 1995, Microsoft, Inc.

Contents

This document contains information about the following topics:

1.0 Changes to Windows NT Documentation

2.0 Backup

2.1 Reading Windows NT 3.51 Backup Tapes on a Windows NT 3.1 Computer

2.2 Notes on Using Sytos Plus Tapes with Backup

3.0 Control Panel

3.1 Using Backslashes in Services

3.2 Setting Standard Formats Used By a Country on Printers

3.3 Paused Server Service Allows Administrators or Server Operators to Connect

3.4 Keyboard Layouts Require Installation of Unicode Font

4.0 File Manager

4.1 Uncompressed Files Access with NTFS Compression

4.2 File and Directory Access

4.3 Files Used at command prompt Must be in OEM Code Page

4.4 DOS Undelete Sentry Blocks Memory from Windows NT

4.5 Using HPFS with Windows NT

4.6 Disabling Short Name Generation on NTFS Partitions

4.7 Converting a FAT file into an NTFS File System

5.0 Program Manager

5.1 Program Manager Must Remain Default Shell

6.0 Administrative Tools

6.1 Computer Names Added to Audit Logs

6.2 Using Telnet

7.0 Other Application Environments

7.1 Using POSIX

7.2 Creating a Contents File

7.3 Suppressing Popup Messages at Startup

7.4 Floating Point Calculation Precision on RISC Computers

7.5 Using DOS-based Disk Utilities

7.6 Default Installation of 16-Bit Print Drivers May Cause Erroneous Popups

7.7 Removing the OS/2 Boot Manager

8.0 Multimedia Drivers and Applications

8.1 API Support in Windows NT

8.2 Some 16-Bit Applications Fail On RISC-Based Computers

9.0 Editing Registry Values

9.1 Starting the Registry Editor

9.2 Navigating Registry Keys

9.3 Changing a Registry Value

9.4 Adding a New Registry Value

10.0 Microsoft Windows NT Messages Database

10.1 Setting Up, Starting, and Quitting the Messages Database

10.2 Running the Database Under Windows NT

11.0 Installing Online Books

11.1 Windows 95 Help Features under Windows NT 3.51

11.2 Help on Windows Help

12.0 Notepad

13.0 Accessibility

14.0 Specific Computer Systems

14.1 Intel Pentium Processor Computers

14.2 ACER AcerFrame 3000 MP

14.3 Ambra Video Display

14.4 AST EISA Memory

14.5 AST Premmia

14.6 Dell

14.7 DFI 9800T

14.8 Gateway 2000 and Micronics Gemini 486 Vesa local bus motherboards

14.9 Gateway Nomad and TI TravelMate Notebooks

14.10 IBM PowerPC

14.11 IBM PS/2

14.12 IBM PS/2 models 53, 76, 76i, 77, and 77i. IBM ThinkPad models 700c and 720c

14.13 IBM ThinkPad portables

14.14 IBM ThinkPad Docking Station with built-in Future Domain SCSI

14.15 Olivetti LSX5030

14.16 Toshiba T4400SX Monochrome

14.17 Changing Memory Configurations on a Computer with an EISA Bus

15.0 Video Display Drivers and Adapters (x86-Based Computers)

15.1 Testing the Configuration

15.2 Updating to Windows NT 3.51 Video Drivers

15.3 Using Matrox MGA or Compaq QVision 2000 Display Adapters

15.4 Video Cards Using the S3 864 Chip

15.5 Troubleshooting Video Display Configuration

15.6 Cirrus and ET4000

15.7 S3 VGA

15.8 VESA VGA

15.9 ATI Driver Notes

15.10 Weitek P9000-based Video Cards

15.11 Switching Between a Window and Full Screen

16.0 Disk Drive Information

16.1 Unrecognized Disks

16.2 Volume Sets Created via the BIOS

16.3 Caching Disk Controllers and Drives

16.4 Installing Windows NT on an ESDI Disk Drive with More Than 1024 Cylinders

16.5 Data Technology Corp. (DTC) Model 6282-24

16.6 DTC Model 6290-24

16.7 DTC Model 6290 SEZ (Dual SCSI/ESDI Controller)

16.8 DTC Model 6295-24

16.9 Adaptec Model 2322D

16.10 UltraStor with PROM versions less than nnnnn-009

16.11 UltraStor with PROM versions equal to or greater than nnnnn-009

17.0 SCSI Devices

17.1 Adaptec BIOS Detection

17.2 Installing Windows NT with a Windows Driver Library Adapter Driver

17.3 Replacing SCSI Adapters

17.4 Notes on Specific SCSI Devices

17.5 Adaptec

17.6 Adaptec 1510, 1520, and 1522

17.7 Adaptec AHA-1542C and Denon DRD-253

17.8 Adaptec 1542x

17.9 Adaptec 154x

17.10 Adaptec 1640 Micro Channel adapter

17.11 Adaptec AHA164x

17.12 Adaptec 1740

17.13 Adaptec 2940

17.14 Buslogic

17.15 COMPAQ Smart SCSI Array

17.16 Dell Drive Array

17.17 Future Domain 8xx

17.18 PS/2 SCSI Adapter

17.19 Maynard SCSI Adapter

17.20 Mylex DCE376 and Tangent 48933 USA

17.21 NEC Intersect CD-ROM

17.22 Plextor (Texel) DM-5024 CD-ROM

17.23 ProAudio Spectrum 16 TMU1

17.24 PCMCIA Cards

17.25 PCMCIA Event Log Error

17.26 Enabling PCMCIA Cards

17.27 Using PCMCIA Devices

17.28 Trantor

17.29 UltraStor SCSI Controllers

17.30 AT/API IDE Devices

18.0 Tape Devices

18.1 DEC TZ86, TZ87, DLT2000 Based Tape Drives

18.2 QIC 40/80 Tape Devices

19.0 Non-SCSI CD-ROM Drives

19.1 Creative Labs CD-ROM Drives

19.2 Mitsumi CD-ROM Drives

19.3 Panasonic CD-ROM Drives

19.4 Sony Proprietary CD-ROM Drives

20.0 Removable Media

20.1 Installing from CD-ROM with Floptical Drives Present

20.2 PCMCIA Cards

21.0 Multiport Serial Adapters

22.0 Mice and Other Pointing Devices

22.1 Serial Mouse (SERMOUSE.SYS Driver)

22.2 Microsoft InPort Bus Mouse (INPORT.SYS Driver)

22.3 Bus Mouse (BUSMOUSE.SYS Driver)

22.4 Mouse Port or PS/2 Mouse (I8042PRT.SYS Driver)

22.5 Support for Multiple and Alternative Pointing Devices

23.0 Sound

23.1 Sound Blaster

23.2 Pro Audio Spectrum-16

23.3 Windows Sound System

23.4 Sound on RISC-based Computers

24.0 Video Capture

25.0 Application Notes

25.1 Viewing Compressed Files in Windows NT 3.51

25.2 Opening Files Created in Windows NT Using Windows 3.x

25.3 Using DOS-based Disk Utilities

25.4 Running SNA Server

25.5 Running Serial Communications Applications

25.6 Running DOS-based Remote Control Applications

25.7 Running DOS-based Multimedia Applications

25.8 Limits to Application Support on RISC-based Computers

25.9 Information on Specific Windows 3.1 and DOS-based Applications

Various Multimedia Applications

Applications that Play many Thousands of Intel Indeo-compressed Movies

Consecutively

Adobe Photoshop

After Dark

Aldus PageMaker

Aldus Persuasion

AutoCAD Release 11 286

AutoCAD Release 12

Autodesk 3D Studio, Release 2

Autodesk Generic CADD 6.0

Borland C++ 4.0

Borland Pascal with Objects 7.0

Borland Turbo Pascal for Windows

Broderbund KidPix for Windows 1.0

Broderbund Myst

cc:Mail

Chessmaster 3000

Commute

CompuServe Information Manager (CIM)

Corel Draw 4.0

Corel Ventura 4.2

Eicon Access

Extra! for Windows

F-19 Stealth Fighter

Fastback 6.0 for DOS

FileMaker Pro

Filewalk

Integraph G91 Display Adapters

Lap-Link V

LHX Attack Chopper

Lotus 1-2-3 Version 2.4 and greater

Lotus Ami Pro 3.1

Lotus Agenda

Lotus Notes

Micrografx Windows Draw 3.0

Microsoft C 7.00

Microsoft Dinosaurs

Microsoft Encarta 1994

Microsoft Encarta 95

Microsoft Excel Version 5.0

Microsoft Entertainment Pack, Idlewild

Microsoft Magic School Bus Explores The Solar System

Microsoft PowerPoint

Microsoft PowerPoint 4 Presentations with Embedded Video Clips or Midi Sequences

Microsoft Word for Windows 6.0a

Microsoft Word, Version 5.5

Microsoft Works 3.0

Multiplan 4.2 for DOS

Norton Utilities 6.01

ORACLE DBMS for DOS

OzCIS

PackRat 5.011 for Windows

pcANYWHERE III

Photoshop

ProComm 2.0

Quantum Gate

Quattro Pro for Windows 1.0

Quicken 4.0

Rumba

SimAnt

Smartcom Windows Communication Software 1.0A

Software Toolworks Multimedia Encyclopedia

SQLWindows 4.0/4.1 for Windows

SuperPrint 2.2

US Atlas 3.1.0, The Software Toolworks

Ventura Publisher

Delrina WinFax Pro 2.0

WordPerfect Windows 6.0a

26.0 Introducing Windows NT Demonstration Program

1.0 Changes to Windows NT Documentation

There are no changes at the present time.

2.0 Backup

2.1 Reading Windows NT 3.51 Backup Tapes on a Windows NT 3.1 Computer

If computers running Windows NT 3.1 must read backup tapes made on a computer running Windows NT 3.51, you must have Service Pack 2 installed on the Windows NT 3.1 computer. Computers running Windows NT 3.51 can read tapes from any previous version of Windows NT.

2.2 Notes on Using Sytos Plus Tapes with Backup

When using Sytos Plus tapes with the Windows NT Backup program, the following may occur:

Backup may have a problem restoring files from a Sytos Plus tape if the file is in a backup session that spans two Sytos Plus tapes and the file is entirely on the second tape. If this occurs, you can restore the file by rerunning Backup after setting the following Windows NT Registry key to 0:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Ntbackup\Backup Engine\Use fast file restore

After restoring the file, reset the key to 1.

When restoring or catalogong a Sytos Plus tape under Windows NT, you get the message "An error occurred during translation of data to or from the tape in the drive." This is because the backup error correction code (ECC) flag value in the Registry has been incorrectly set by the data on the tape. The value in the Registry is an override. To correct this problem, edit the following Registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Ntbackup\Translators \Sytos Plus ECC flag

If it is 0 (OFF), Backup assumes there is no software ECC. If it is 1 (ON), Backup assumes that it does have software ECC. If it is 2 (AUTO), Backup will trust the tape.

Values should be set accordingly for the following types of tape:

4mm DAT  0, 1/4 in. 525, 08mm DAT  0, 1/4 in. 150  1

3.0 Control Panel

3.1 Using Backslashes in Services

When using the Services option, you must include two backslashes (\) for each literal backslash in a parameter (for example, \\\\server\\share is interpreted as \\server\share).

3.2 Setting Standard Formats Used By a Country on Printers

In Working with Other International Settings in Chapter 5 of the System Guide, these settings do not control the Paper Size option in the Print Setup dialog box. To match the standard formats used by a country, you must set your choice using Print Manager.

3.3 Paused Server Service Allows Administrators or Server Operators to Connect

Notice that when you pause a computer's server service, users in the Administrators and Server Operators groups can still make new connections to the computer, but all other users cannot.

3.4 Keyboard Layouts Require Installation of Unicode Font

The following keyboard layouts are for use only with Unicode applications and require installing the Unicode font named Lucida Sans Unicode: Czech, Greek, Hungarian, Polish Programmer, and Russian.

To install the Lucida Sans Unicode font, use the Font option in Control Panel. The font is available on the Windows NT CD-ROM.

4.0 File Manager

4.1 Uncompressed File Access with NTFS File Compression

When you compress a file on an NTFS volume (using the COMPACT.EXE command or the Compress command in File Manager), the file is stored in compressed form on the hard drive. Only the NTFS file system itself can read the compressed form of the file. If any other program, such as an application like Microsoft Word or an operating system command like COPY requests access to the file, the NTFS file system uncompresses the file before making it available. For example, if you copy a compressed file on one Windows NT Server across the network to a directory marked for compression on another Windows NT Server, the file will be uncompressed, copied, and then compressed again.

4.2 File and Directory Access

Users can perform certain actions to files or directories even if permissions are set on a file or directory to prevent access to users. This access is due to permissions set for the parent directory.

For example, if you have a directory (DIR1) containing a file (FILE1) and you grant Full Control to a user for the directory DIR1 but specify that the user have No Access to FILE1, the user will be able to delete FILE1 because the user's Full Control rights in the directory allow the user to delete contents (or "children") of the directory.

To prevent files from being deleted, you must set permissions on the file itself and you must check permissions for the directory containing the file. Anyone who has Full Control in a directory will be able to delete files from the directory.

Similarly, anyone who has List, Read, or greater permissions in a directory will be able to view file properties on any file in the directory, even if they are prevented by file permissions from seeing the contents of the file.

4.3 Files Used at Command Prompt Must be in OEM Code Page

Although a range of characters can appear in filenames, the Windows NT command prompt is limited to the characters available in the OEM code page you installed when you set up Windows NT. If you plan to work with files at the command prompt, use alphanumeric characters in filenames and avoid using characters that do not map to the OEM code pages (such as the bullet character).

4.4 DOS Undelete Sentry Blocks Memory from Windows NT

Windows NT cannot recognize free space that was created on a FAT partition using the undelete sentry feature in MS-DOS Version 6.2. With the sentry method, DOS reserves part of the hard drive to remember deleted files, then compensates during DOS queries about free space. Because Windows NT doesn't understand sentry, it reports the space on the FAT partition as used.

4.5 Using HPFS with Windows NT

The high performance file system (HPFS) is supported for compatibility with OS/2. For optimal file system performance with Windows NT, you should use the NTFS or FAT file systems. Use the convert utility to convert an HPFS partition to an NTFS partition.

4.6 Disabling Short Name Generation on NTFS Partitions

Users may improve the performance of file operations and directory enumeration on an NTFS partition by disabling short name generation. Performance increases are best in directories with a large number of files or subdirectories that do not conform to the 8.3 FAT file system naming rules.

Disabling short name generation will make files with long filenames invisible to 16-bit applications on that system. If short name generation is disabled on a file server, the same set of files is also invisible to DOS clients on the server, or to 16-bit applications running on Windows NT clients. In general, the files that are invisible to 16-bit applications are those files that do not have valid 8.3 names.

To disable short name generation, set the following Registry entry to 1 using REGEDT32.EXE:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

NtfsDisable8dot3NameCreation  REG_DWORD

Range: 0-1

Controls the short name generation on all NTFS partitions in the computer.

Default: 0

4.7 Converting a FAT File into an NTFS File System

Converting a disk from the FAT file system to the NTFS file system can be a lengthy process, depending on the current state of the FAT volume and the size of the volume. For example, converting a 1GB volume may take up to serveral hours. When using convert or autoconvert, no status information is displayed to indicate that the conversion is proceeding and it may appear that the conversion process is hung. If this occurs, allow the conversion to run overnight.

5.0 Program Manager

5.1 Program Manager Must Remain Default Shell

Windows NT does not support applications that replace Program Manager as the default shell. Many features of such applications are supported; however, you should not run these applications as a complete replacement for Program Manager.

6.0 Administrative Tools

6.1 Computer Names Added to Audit Logs

Event Viewer log entries for logon events now include the computer name where the logon attempt originated.

6.2 Using Telnet

The Telnet Utility has various redraw problems when using proportional fonts. In addition, if the foreground and background are different colors, a small strip of the background color may appear above or below the text.

7.0 Other Application Environments

7.1 Using POSIX on Windows NT 3.51

The Portable Operating System Interface (POSIX) subsystem no longer supports nonstandard locales. POSIX applications can now only set their locale to either C or POSIX. As a result, serveral function entry points in LIBCPSX.LIB and PSXDLL.LIB have changed. Old POSIX applications must be recompiled to ensure that they use the new set of entry points. If you run an old POSIX application that has not been recompiled, you will see a popup message that indicates an entry point cannot be found.

7.2 Creating a Contents File

To create a contents file, you must know the names of the files you want to group, and select one file to be the base file, that is, the file from which the full-text search file will be built. You can use any text editor to create the contents file but you must save the file in ASCII text format.

To create a contents file

1.	Type the name of the base Help file in the following format:
Base helpfile.hlp

2.	For each Help file you want to combine, specify the following line:
Index title=helpfile.hlp

3.	Save the file with the same name as the base file, but use the .CNT extension.
Example:
Base usrmgr.hlp
Index Server Manager Help=srvmgr.hlp
Index User Manager Help=usrmgr.hlp
Index User Profile Editor=upedit.hlp

7.3 Suppressing Popup Messages at Startup

If you are running a special application for Windows NT, such as an automatic teller machine, where no popups are acceptable at computer startup, you might need to suppress the popup messages at startup. The following messages might appear on the screen during the startup process: At least one service or driver failed during system startup and the system reverted to its last known good configuration. To suppress these popup messages

1.	Start the Registry Editor by running the REGEDT32.EXE file from File Manager or Program 	Manager, or type start regedt32 from a command prompt and then press ENTER.

2.	Locate the following Registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Windows

3.	From the Edit menu, select Add Value. The Add Value dialog box is displayed.

4.	In the Value Name box, type NoPopupsOnBoot.

5.	In the Data Type box, select REG_DWORD.

6.	Choose OK. 	The DWORD Editor dialog box is displayed.

7.	In the Data box, add data or edit the string that appears and make it a non-zero value. For 	example, you can just type 1.

8.	In the Radix box, select one of the three numerical representation options.

9.	Choose OK to display the new entry in the Registry Editor window.

7.4 Floating Point Calculation Precision on RISC Computers

The precision of floating point calculations on RISC computers running 16-bit applications is limited to 64 bits. The precision of floating point calculations on x86 and Pentium computers running 16-bit applications is 80 bits. As a result, some 16-bit applications on RISC-based Windows NT systems may not give exactly the same values as DOS and Windows 3.x based systems.

7.5 Using DOS-based Disk Utilities

The long filename format in Windows NT 3.51 uses file elements on FAT partitions differently than DOS. When using DOS-based disk utilities on FAT partitions used by Windows NT 3.51, files can be deleted or long filenames can be lost. Microsoft recommends that you run only disk utilities specifically designed for Windows NT 3.51, or when running DOS, the chkdsk or scandisk utilities.

To prevent the Windows NT 3.51 FAT file system from using long names, you must set the following Registry entry to 1:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\Win31FileSystem

After changing the entry, restart your computer for the change to take effect.

Caution

PCTools diskfix utility is known to delete all files on the FAT partition. If you use DOS-based disk utilities on a FAT disk partition used by Windows NT 3.5, the utility may cause the loss of long filenames or delete files on the FAT partition unless this Registry entry is set to 1. Back up the FAT partition before running any disk utility other than chkdsk.

7.6 Default Installation of 16-Bit Print Drivers May Cause Erroneous Popups

Some 16-bit Windows-based applications may erroneously display popups indicating Out Of Memory, Insufficient System Resources, or similar messages. Many of these popups are caused when a 16-bit printer driver has been designated as the driver for the default printer. This occurs when the setup program for a 16-bit application installs a 16-bit printer driver and designates it as the default printer for the system. Once installed, subsequent calls to the device driver from the Win32 API will fail since the Win32 API isn't designed to work with 16-bit device drivers.

This problem can usually be resolved by using Print Manager to set a different printer as the default.

7.7 Removing the OS/2 Boot Manager

If you choose to remove the OS/2 Boot Manager, you must restart the computer twice to complete the steps required to disable it in Windows NT.

8.0 Multimedia Drivers and Applications

8.1 API Support in Windows NT

API support (32-bit and 16-bit) providing audio and video compression, playback, and capture equivalent to Microsoft Video for Windows 1.1 is installed automatically as part of Windows NT 3.51. This includes Cinepak by Radius Inc. 32-bit video compression and decompression support required to display certain video clips (in Microsoft Encarta and other titles). Windows NT 3.51 also provides 32-bit support for Intel's Indeo compression and decompression algorithm used in certain titles and Video Conferencing applications.

8.2 Some 16-Bit Applications Fail On RISC-Based Computers

Some 16-bit applications fail on RISC-based computers with Invalid instruction errors because the Video for Windows 1.1 runtime installed with these applications under Windows NT includes some 386 enhanced mode instructions. A number of updates that include 286-execution paths are in Windows NT. This will not affect most multimedia titles that use MCI playback, but might affect some applications that use some in-depth functions of the Video for Windows APIs.

9.0 Editing Registry Values

The Windows NT Registry is a database that contains information used by the system. In a few cases, you may need to change or add values in the Registry to provide the system with information needed when running certain hardware or software. For those cases, Windows NT provides the Registry Editor to allow you to work with values in the Registry.

Values in the registry appear in the format name:datatype:value. The following data types are supported.

Data Type	Description

REG_BINARY	Binary numbers that can be displayed in binary or hexadecimal notation.

REG_DWORD	Data represented by a four-byte number that can be displayed in binary,

hexadecimal, or decimal notation.

REG_EXPAND_SZ	Text data containing a variable.

REG_MULTI_SZ	Text data containing multiple values.

REG_SZ	Text data.

Caution: Incorrect changes or deletions made to the Registry can damage Windows NT and prevent the system from running properly.

9.1 Starting the Registry Editor

The Registry Editor is installed with your other Windows NT files, usually in the directory \systemroot\SYSTEM32, when you set up Windows NT. To start the Registry Editor, run REGEDT32.EXE from File Manager or Program Manager or at the command prompt, type regedt32 and press ENTER.

9.2 Navigating Registry Keys

The Registry Editor displays a window for each root key in the registry. Each window contains two panes. The left pane displays registry keys in a tree structure. You can navigate through the keys of the registry just as you would navigate through the structure of directories using File Manager. For example, double-click the name of a key to expand or collapse the display of the keys below it in the tree. When you select a key in the left pane, the right pane displays the values, if any, for the key.

The location of a value in the registry is specified by the path of keys to the value. For example, to reach HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW, start at the HKEY_LOCAL_MACHINE window and navigate down through each of the keys in the path until you reach the WOW key. Once you select the WOW key, values in that key are displayed in the right pane of the window.

9.3 Changing a Registry Value

1.	Display the value by navigating down the registry tree to the appropriate key.

2.	In the right pane of the Registry Editor window, double-click the value entry. Or, select the value and, from the Edit menu, choose the appropriate editor based on the value's data type.
Choose Binary to edit REG_BINARY data.
Choose String to edit REG_SZ and REG_EXPAND_SZ data.
Choose DWORD to edit REG_DWORD data.
Choose Multi String to edit REG_MULTI_SZ data.

3.	Edit the value in the Editor dialog box and then choose the OK button. For more information on using the Editor dialog boxes, choose the Help button in the dialog boxes.

9.4 Adding a New Registry Value

1.	Select the key where you want to add the value by navigating down the registry tree.

2.	From the Edit menu, choose Add Value.

3.	In the Add Value box, type the name for the new value.

4.	In the Data Type box, select the data type for the new value.

5.	Choose the OK button. The Registry Editor displays the appropriate editor based on the data type of the new value.

6.	Type the new value in the Editor dialog box and then choose the OK button. The Registry 	Editor adds the value to the registry in the correct format.

For more information on using the Registry Editor dialog boxes, choose the Help button in the dialog boxes.

10.0 Microsoft Windows NT Messages Database

The Microsoft Windows NT Messages database is the online version of Microsoft Windows NT Messages for Windows NT Workstation and Windows NT Server, which is the printed guide to most of the error and system information messages generated by the Windows NT operating system.

10.1 Setting Up, Starting, and Quitting the Messages Database

Use the Setup program (SETUP.EXE) located on the Windows NT compact disc to install the Microsoft Windows NT Messages database on your computer for individual use or on a network server for shared use.

To set up the Messages database from a CD-ROM drive:

1.	Start Windows NT. If you want to share the Messages database with other users, be sure to logon as the Administrator before installing the database.

2.	Insert the Windows NT compact disc in the CD-ROM drive.

3.	In Program Manager, choose Run from the File menu. The Run dialog box appears.

4.	Type CD-ROM Drive letter:\SUPPORT\WINNTMSG\SETUP in the Command Line box.

5.	Choose the OK button.

6.	Follow the instructions on screen to complete Setup.

If you want to share the Messages database with other users, specify a path to a network 	when Setup asks where you want to install it. When it asks if you want to join a workgroup, 	choose the No button unless you have already established a workgroup.

After installing the files you need, the Setup program creates a Microsoft Windows NT Messages program group and puts the following icons in the program group: Microsoft Windows NT Messages, Change Workgroup, Compact Database, and Readme.

Note

If you have installed the Messages database on a Windows NT File System (NTFS) partition, use the File Manager Security menu to ensure that all users have Change (RWXD) permission to the directory and its contents.

10.2 Running the Database Under Windows NT

Detailed procedures on how to use the Find, Notes, and Print buttons on the Messages form to work in the database are provided in the online Help files that accompany this database. Last-minute changes to the product are documented in the Readme file located in the Microsoft Windows NT Messages program group. The Help procedures include information on the following topics:

Searching for information in the Messages database

Using a variable as a search criterion

Initiating a new search

Adding and removing notes to the Messages database

Setting up to print

Printing a database report

11.0 Installing Online Books

The online version of the Windows NT documentation is located on the Windows NT compact disc. To view the online books from Program Manager, you must first create a program item for them.

To create a program item for the online books:

1.	Start Windows NT.

2.	Insert the Windows NT compact disc in the CD-ROM drive.

3.	In Program Manager, open the program group to which you want to add the Online Books 	icon. You may want to use a common group rather than a personal group so that anyone who 	logs on can view the books.

4.	From the File menu, choose New to display the New Program Object dialog box. Then select the Program Item option and choose OK. The Program Item Properties dialog box appears.

5.	In the Description box, type a description such as Online Books.

6.	In the Command Line box, type the program name, including its path and extension. For example, if you want to keep the document files only on the compact disc in drive D, you would type: d:\support\books\workstn.hlp (or server.hlp for Windows NT Server)

If you want to keep the files on your hard disk, create a directory for them and then copy all 	the files from the compact disc to that directory. You can then use that path in the 	Command Line box.

7.	Choose OK. The dialog box closes, and a generic Help icon appears in the chosen group.

11.1 Windows 95 Help Features Under Windows NT 3.51

With the new Help system, you now have the option to group certain Help files to create full text searching across Help files. While you could search across Help files in previous versions of Windows NT, you can now choose which files you want grouped for full-text searching. The Help files that are shipped with Windows NT 3.51 are already grouped and the full-text search indexes (*.FTS files) are created and installed when you install Windows NT 3.51. For complete information about the new Help system, see the Help file HCW.HLP in the Software Development Kit.

However, the new Help system does not support the previous full-text search indexes (files that end with .IND) that may have been created for the previous versions of Windows or Windows NT Help files. When you perform a full-text search in a Windows NT 3.51 Help file the first time, if the full-text search index (*.FTS file) has not been built, the new Help system prompts you to build the full-text search index. You have the option to build an index for a single Help file or for a group of Help files, if those files have been grouped together by a common contents file. For more information about using the new Help system and building full-text search indexes, see the How To Use Help command on the Help menu.

Full-text search indexes are built from the Search page in the Help window. When you build your own full-text search indexes, by default, the information is stored wherever the Help files that you used to build your index are located. However, if the Help files are stored on a read-only server, the full-text search files will not be written to the read-only server; they will be stored locally. Depending on the size of the Help file or files (if there are grouped Help files), the combined *.FTS files can become rather large.

To group files for full-text, cross-file searching on Windows NT 3.51, you need to create a contents (.CNT) file that lists all the files you want grouped.

Note

All the Windows NT 3.51 Help files have contents files and full-text search files. You do not need to create new contents or full-text search files for Windows NT 3.51 Help.

11.2 Help on Help

The files that have been grouped together for cross-file full-text searching in Windows NT Workstation and Windows NT Server are:

Group 1: SCHDPL32.HLP, MSMAIL32.HLP

Group 2: USERMGR.HLP, SVRMGR.HLP, UPEDIT.HLP, LICCPA.HLP

Group 3: WINDISK.HLP (or WINDISKA.HLP), PERFMON.HLP, BACKUP.HLP, EVENTVWR.HLP

Group 4: WINNT.HLP, GLOSSARY.HLP, NTCMDS.HLP

Group 5: PROGMAN.HLP, WINFILE.HLP, PRINTMAN.HLP, CLIPBRD.HLP

Group 6: SNDVOL32.HLP, SOUNDREC.HLP, CDPLAYER.HLP, MPLAYER.HLP

All other Help files in Windows NT Workstation and Windows NT Server are not grouped.

If you need to run Help in 16-bit mode, Windows NT Workstation and Windows NT Server include WINHELP.EXE, which is the Windows Help executable for 16-bit mode. You can use File Manager to associate the Help files with WINHELP.EXE; however, you can only associate all Help files, not individual Help files. If you associate a 32-bit Help file (all the Windows NT Workstation and Windows NT Server Help files are compiled for 32-bit help) with the 16-bit WINHELP.EXE, you will lose some functionality, such as cross-file searching. WINHELP.EXE is located in the \<sysroot> directory.

12.0 Notepad

You can include three switches when starting Notepad. The switches will work at the command prompt, in Task List, and in Program Manager (using Run from the File menu or in the Command Line option for an icon).

notepad [/p] [/a | /w] filename

/p

Prints the file specified.

/a

Loads the specified file as ASCII.

/w

Loads the specified file as Unicode.

13.0 Accessibility

Microsoft is committed to making computers easier for everyone to use, including individuals with disabilities.

Microsoft distributes Access Pack for Microsoft Windows NT, which provides people with motion or hearing disabilities better access to computers running Microsoft Windows NT. See the Windows NT Installation Guide for locations where you can get an Access Pack.

14.0 Specific Computer Systems

14.1 Software Update for the Intel Pentium Processor Floating-Point Error

This release of Windows NT 3.51 includes a utility (PENTNT.EXE) that checks whether the processor contains the Pentium floating point division error, reports the current status of floating point, and allows disabling and re-enabling of hardware floating point. This software effectively turns off the math co-processor by trapping the floating point instructions. This utility makes the processor behave similarly to 486SX or 386 processors that do not have a math co-processor. The utility works on x86-based systems.

Additionally, the solution is implemented through Registry settings so that system policy administrators can control the use of Pentium floating-point hardware on user systems.

Performance Considerations

Core operating system code (for windows management, disk and file operations, and application programming interfaces) in Windows NT does not perform floating-point calculations and will not be affected either by the potential floating-point hardware division errors or by disabling hardware floating point. However, choosing software emulation of floating point will result in lower performance of floating-point operations. Some utilities and applications such as the Calculator application provided with Windows NT and the OpenGL rendering engine, may use floating-point hardware when present. Most software programs for word processing, databases, electronic mail, and so on, perform few or no floating point-operations.

Math-intensive applications, including spreadsheets and technical applications, typically perform floating-point operations and, therefore, will experience some performance degradation. The OpenGL rendering engine, which is part of Windows NT 3.51, and other 3D and CAD applications, are instances of this type of application. The user of such applications will be able to choose between the higher speed of hardware floating point or slower floating-point software emulation libraries, which will not encounter the Pentium processor floating-point division error. Many applications contain their own floating-point libraries to use in this case. A few applications require floating-point hardware and will not run without it. Customers running these applications will need to replace their Pentium processor to avoid the floating-point division error. The floating-point software emulation libraries are used on systems with 486SX or 386 processors.

Running PENTNT.EXE

To find out how to run PENTNT.EXE utility, type pentnt -? at the command prompt.

Registry Entry

The Registry entry for the PENTNT.EXE utility is located in the Registry subtree HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager. The following parameter is used by the PENTNT.EXE utility:

REG_DWORD

ForceNpxEmulation = 0 | 1 | 2

The parameter specifies if the floating-point emulation is turned on or off. If set to 0, floating-point emulation is not enabled and floating-point hardware is enabled. If set to 1, conditional floating-point emulation is enabled. If set to 2, unconditional emulation is enabled. By default, this parameter is set to 0.

14.2 ACER AcerFrame 3000 MP

Before installing Windows NT, disable shadow RAM Video BIOS.

14.3 Ambra Video Display

When 16 colors are selected on Ambra computers, the video image has some scattered imperfections. Switch to 256 colors to get a clean image.

14.4 AST EISA Memory

Enable access to memory above 16MB even if the computer has only 16MB of RAM. To enable memory, run the EISA configuration utility supplied with the computer.

14.5 AST Premmia

Certain BIOS versions of the Premmia are incompatible with Windows NT. To work with the onboard IDE drive, you must have BIOS Version 2.03.

14.6 Dell

If you experience problems updating the Dell Omniplex system to Windows NT 3.5, you may need a BIOS update. A BIOS level of 5xx_a08 is required. This BIOS update can be obtained from Dells BBS at 512-728-8528.

Some Dell models, for example the 486D/50, 433DE EISA, and 25/50 MHz ISA systems, may be unable to recognize more than 16MB of RAM on Windows NT. Contact Dell Product Support for a BIOS upgrade to Version A11 or greater.

Before installing Windows NT on a Dell Omniplex, you must run the MONITOR.EXE program supplied by Dell. If you are using 65,000 color mode, set the refresh rate to 60Hz.

14.7 DFI 9800T

To install Windows NT on the DFI 9800T system, select Custom Setup and then press S to skip SCSI detection. If a SCSI host adapter is present on your system, you can add it manually by selecting the appropriate entry.

14.8 Gateway 2000 and Micronics Gemini 486 Vesa local bus motherboards

Windows NT may stop running because of a timing issue on systems that use the UltraStor U34F local bus controller with the Micronics Gemini 486 Vesa local bus motherboard. Some older Gateway systems include this combination of hardware.

Disabling the motherboard's external cache should allow Windows NT to run. The problem does not occur with ISA bus controllers from UltraStor. This problem does not occur on Gateway 2000 or Micronics Vesa local bus motherboards with a blue OverDrive socket.

You can resolve this problem by obtaining an upgrade offered by Micronics for the Gemini 486 Vesa local bus motherboard. The motherboard will need to be returned to Micronics for the upgrade. The Micronics reference number for this is VLBA03. Micronics can be reached at 510-651-2300 for additional information. If you have a Gateway computer, contact Gateway 2000 at 1-800-846-2301 for upgrade information.

14.9 Gateway Nomad and Texas Instruments TravelMate Notebooks

To successfully install Windows NT on these computers, you must choose Custom Setup. If you encounter problems running Setup while scanning for SCSI adapters, you can skip SCSI detection to solve the problem.

To properly use the diskette drive with Windows NT, configure the system using its setup utility. Set the Advanced Operating System option to Auto. When power management drivers for these computers are available from Texas Instruments, it will not be necessary to use the Auto option.

The built-in InPort/QuickPort mouse adapter requires a mouse driver from Texas Instruments to work properly under Windows NT. You can use a serial mouse until this driver is available from Texas Instruments.

To use the internal modem for these computers, you will need a power management driver and software from Texas Instruments.

14.10 IBM PowerPC Computers

Before updating or reinstalling Windows NT 3.51, you must make sure that the ARC Main Boot Menu has a Start Dummy or Start Default entry that points to the correct disk partition where Windows NT 3.51 should be installed.

To create an entry for Windows NT 3.51 installation:

1.	Under the Advanced Setup menu, choose System Management Services.

2.	Choose Add a Systems Selection to add an entry.

ARC Boot Loading for IBM PowerPC Computers

To run Windows NT 3.51 on an IBM PowerPC computer, you might need the latest version of the ARC Boot Loader. The latest version number is 1.44 and is displayed on the ARC Bootload screen. If you do not have the latest version, you can get assistance by calling the Power Personal System Help Center at 1-800-472-7693.

Updating System Firmware to Run Windows NT 3.51 with IBM PowerPC Computers

If you have an NE-2000 compatible Ethernet card, you must upgrade your system firmware to the latest version, which is 1.24, to run Windows NT 3.51 on your IBM PowerPC computer. To view the version number of your system firmware, press F4 during startup. If the F4 key does not start the system firmware utilities, repeat the process using the F1 key. If you do not have the latest version, you can get assistance by calling the Power Personal System Help Center at 1-800-472-7693.

Configuring Network Interface Cards to Use Windows NT 3.51 with IBM PowerPC Computers

You must configure NE-2000 network interface cards before using them with IBM PowerPC computers. Cards can be configured using the NIC supplied configuration utility on a DOS-based computer or the ETHER.EXE configuration utility on an IBM PowerPC computer. If you do not have the ETHER.EXE program, you can get assistance by calling the Power Personal System Help Center at 1-800-472-7693.

14.11 IBM PS/2

On some IBM PS/2 systems, only planar memory is recognized when booting from the Windows NT CD-ROM boot disk or Setup Boot Disk of the diskette disk installation set. This is a memory card problem. You may encounter this problem if your system contains a card with the following part numbers:

FRU-88F0075Option 87F9856 or 87F9860

Newer model cards are available that correct this problem. Part numbers for the newer cards are:

FRU-87F9916 or 34F2825Option 34F3077 or 34F3011

Using Kingston expansion memory can also correct this problem.

It is recommended that before you install Windows NT, you update your system configuration using the PS/2 Reference Diskette Version 1.12 or later.

14.12 IBM PS/2 models 53, 76, 76i, 77, and 77i. IBM ThinkPad models 700c and 720c

These systems require an ABIOS patch to install and run Windows NT. Copy the following file from the IBM Reference Diskette into the C:\ directory:

ABIOS.SYS*.BIO

14.13 IBM ThinkPad portables

These portables can only use 640x480 resolution using 16 colors.

14.14 IBM ThinkPad Docking Station with built-in Future Domain SCSI

The Future Domain SCSI chip must be configured to IRQ 5 for proper performance.

14.15 Olivetti LSX5030

Disable all ROM shadowing.

14.16 Toshiba T4400SX Monochrome

This display is not supported when an external monitor is connected.

14.17 Changing Memory Configurations on a Computer with an EISA Bus

If you change the memory in a computer running Windows NT, you must run the EISA configuration utility provided with the computer. If you fail to use the EISA configuration utility, Windows NT will fail.

15.0 Video Display Drivers and Adapters (x86-Based Computers)

Windows NT supports over 70 video display adapters, including excellent high-end support. This section presents some detailed notes on video support for Windows NT. The information in this section is applicable for x86-based computers only.

This release supports the VGA standard video cards plus some newer video cards. If your video card is not supported with an enhanced driver, VGA will be selected automatically.

15.1 Testing the Configuration

If you want to change your display settings, you should always use the Test button in the Display dialog box to view what the video display will look like. Serveral things might not be working correctly that Windows NT cannot detect. For example, 65536-color and true color modes are supported on many adapters. However, not all cards with these chip sets are capable of displaying these new modes. Limitations can be due to older chip versions, the amount of video memory on the card, or other hardware features.

Caution

If you install a new video card before using the Display option in Control Panel for the new configuration, your computer may not restart correctly. In such a case, you can either install the original card (if it is available) and revise the configuration using the Display option or select the VGA boot option on the Boot Loader startup screen. If you use the latter method, you must manually disable the video driver that was running.

15.2 Updating to Windows NT 3.51 Video Drivers

It is strongly recommended that you use the latest video drivers for Windows NT 3.51. You can continue to use video drivers from Windows NT 3.1, but you will be missing the benefits of performance enhancements and the new functionality provided by the Display option in Control Panel. Also, numerous bug fixes have been made to video drivers.

If you are using a video driver that was not provided by Microsoft, you should be able to continue to use that driver even though many of these drivers have not been tested with Windows NT 3.51. If you have problems, contact the provider of the driver.

15.3 Using Matrox MGA or Compaq QVision 2000 Display Adapters

The Matrox MGA and Compaq QVision 2000 compatible display driver included with Windows NT 3.51 may incorrectly report I/O conflicts with other devices in the Event Log. If there are no messages in the Event Log for either the MGA or for the conflicting device stating that the corresponding drivers failed to load, the conflict messages are innocuous and may be ignored.

Some ISA Matrox MGA compatible cards in some systems may cause an access violation in NTVDM after logon if the MGA card is configured to have its memory aperture at AC000 with 8-bit access. If this is the case, consult your MGA manual to determine how to change the memory location and bit access of the card.

The Matrox MGA display driver included with Windows NT 3.51 permits full 3D hardware acceleration via the Microsoft 3D DDI when using a 4MB Matrox Impression Plus and running at 256 color resolutions of 640x480, 800x600, 1024x768, or 1152x882, or when running at 32768 color resolutions of 640x480 and 800x600. When running at 3D accelerated 256 color resolutions, many OpenGL applications require the entire 256 color palette and will cause the colors in background windows to change when the OpenGL application is given the input focus; the colors will be restored when non-OpenGL applications are given the input focus.

15.4 Possible Address Conflicts Between Cards Using an S3 864 Chip

If you are using a video card with an S3 864 chip, it may use an address that conflicts with other cards and might cause the cards to function incorrectly. As a result of this conflict, a device driver will usually fail to load. If the device driver does not catch the problem, the results could be random.

S3 cards that might be affected have the address C0000 through CFFFF. These addresses might be incorrectly reported by Windows NT 3.51 as C0000 through C7FFF. To correct this problem, re-configure the conflicting card to use a non-conflicting address range. Each card has its own possible address change. See the card manufacturer's documentation for more information.

One example of this address conflict is with the IBM Token Ring 16/4 ISA adapter, which by default uses the address range CC000 though CDFFF. If an address conflict occurs, the token ring device driver will fail to load. The error message "IbmTok1, The I/O base address supplied does not match the jumpers on the adapter" will appear in the event log.

A simple fix for this conflict is to change the ROM address of the token ring card from CC000 to DC000 by changing the switches on Switch Block S-2. Switches 1 through 6 on Switch Block S-2 should be changed from off-on-on-off-off-on to off-on-off-off-off-on.

15.5 Troubleshooting Video Display Configuration

If you encounter problems, read the manual for your video display adapter for the proper settings. You may have overlooked something in the manual that pertains to Windows NT if you previously installed the card under Windows 3.1.

In general, Windows NT video drivers do not use interrupts. Many VGA cards use jumpers to enable IRQ 2 interrupt for EGA compatibility. When possible, you should disable the IRQ 2 interrupt.

During Setup, Windows NT may allow you to set the vertical refresh rate for your card. Read your monitor manual to see what settings you can use. If you are unsure, select the lowest resolution and refresh rate. Once Setup is complete, you can use the Display option in Control Panel to select the best setting for your monitor.

Caution

Some monitors may be physically damaged by incorrect video settings. Check your monitor's manual carefully before choosing a new setting.

If, after changing resolution settings and rebooting, you find that your display is not operating correctly, restart your computer again and choose the VGA mode option when you select an operating system or start the Last Known Good feature during initial startup to restore your previous video settings.

The following list presents information about specific video display types. See also ATI Driver Notes later in this file.

15.6 Cirrus and ET4000

Only some systems support 64K VGA, and 64K VGA supports only 640x480 resolution. For 800x600 resolution, 1MB of video memory is required at 8bpp.

15.7 S3 VGA

The vertical refresh rate for S3-based video is often set by DIP switches on the card or by running a DOS-based utility that programs the adapter's ROM.

For these systems, select the default refresh frequency in the Display option of Control Panel. The DOS-based setup program for these cards must be run under MS-DOS.

If you experience difficulties using the S3-based video card on your Hewlett-Packard« Vectra« computer, call Hewlett-Packard technical support to upgrade your BIOS EEPROMS.

The Windows NT S3 driver supports only 256, 32768, 65536, and true-color resolutions, but not 24bpp. The modes that are available depend on the S3 chip, the DAC type, and the amount of memory on the adapter. See your S3 manual for details.

15.8 VESA VGA

If you have a card that requires a DOS-based, memory-resident program to implement super VGA functionality, only standard VGA mode is supported.

15.9 ATI Driver Notes

The ATI drivers support the following boards:

8514/UltraATI Graphics Xpression

ATI Graphics Pro TurboGraphics

UltraGraphics Ultra ProGraphics

UltraPlusGraphics

VantageGraphics Wonder

You should run the ATI-supplied Install program before setting up Windows NT. You need to do this only once. When you run this program, select the monitor that your computer is using. The Install program sets the vertical refresh rate that works with your selected monitor at every resolution. Some versions of the Install program do not do this correctly for all monitors. In such cases, you can select the Custom monitor option and then set the refresh rate for every resolution.

All Graphics Wonder boards with 1MB of graphics memory and Graphic Ultra Pro and Graphics Ultra Plus cards with a -006 Mach32 chip (or 68000AX) will support 800x600 16bpp mode.

The Graphics Ultra Pro, Graphics UltraPlus, and Graphics Wonder on an ISA bus computer with the aperture disabled support the following resolutions:

640x480

800x600

1024x768

1280x1024, 8bpp (256 colors)

640x480

800x600

1024x768, 16bpp (65,536 colors)

The supported resolutions and pixel depths assume enough memory on the card. All cards require a minimum of 1MB of graphics memory. The pixel depth depends on the DAC type on the display adapter. If you choose a resolution that is not supported or that your card has not been installed for, the driver substitutes a supported resolution.

The Graphics Ultra Pro, Graphics Ultra Plus, and the Graphics Wonder with aperture enabled will support:

640x480, 24 bpp

800x600, 24bpp [requires 2MB RAM and a -006 Mach32 chip (or 68000AX) or later]

AST Premmia users should select ATI AST for all AST-supplied ATI video adapters.

If your ATI card does not initialize properly for the selected mode, restart your computer using DOS and run the ATI card Install program to set the cards' parameters for a monitor that can handle high-resolution graphics.

15.10 Weitek P9000-based Video Cards

Some video cards based on the Weitek P9000 chip will not automatically be detected during setup. After Windows NT has been installed, use the Display option in Control Panel to select the Weitek P9000 Graphics Adapter.

15.11 Switching Between a Window and Full Screen

When running DOS-based graphics applications using 256 colors, you may encounter a problem switching between a window and the full screen with the following video boards:

ATI 8514 Ultra

ATI GraphicsUltra Plus

COMPAQ Qvision

DiamondViper

IBM XGA2

Trident 8900cTrident 9000a

Video Seven VRAM(1)

When switching back to full screen, the display can become scrambled. Although the application is still running, the graphics screen is incorrect. Close the application. If this is not possible, switch back to Windows NT and use the Task List to stop the application.

The IBM XGA2 also exhibits this problem with 16-color, DOS-based graphic applications. Both problems only occur in 640x480 mode on the XGA2 system.

16.0 Disk Drive Information

The following section presents issues for hard disks and diskette disk drives.

16.1 Unrecognized Disks

In a few cases, Windows NT may not recognize a hard or diskette disk even though DOS recognizes the disk. Windows NT requires strict conformance to proper partition table formats, boot blocks, and so on. This enhances protection against viruses. If you suspect that a disk's partition table is incorrect, take the following steps:

1.	Back up any data you need, including the files required to run DOS.

2.	For a hard disk, use a recent version of DOS FDISK to delete and then recreate all 	partitions.

3.	Format the hard or diskette disk.

16.2 Volume Sets Created via the BIOS

On controllers other than the UltraStor 124f, Windows NT does not support disk controllers that create volume sets via the BIOS (that is, two different drives merged into a single drive letter).

16.3 Caching Disk Controllers and Drives

Windows NT supports caching disk controllers and drives only if one of the following is true:

*  The controller has a driver that specifically supports caching (serveral of these exist, for example, DPT and IBM SCSI Caching Adapter).

*  Write-through is active (that is, write caching is disabled) either by setting it manually or by default when the computer starts.

*  The entire cache option is off, either by setting it manually or by default when the computer starts.

Using a caching controller or drive in other situations risks loss of data if the computer is rebooted or a power failure occurs before the cache has flushed itself. You can minimize risk by waiting at least one minute after all system activity stops before you reboot. (You can wait a shorter time if you know the maximum time the cache waits before flushing itself.) The disk activity light is a good indicator of how write caching is being done on your system. This applies to the initial Windows NT installation as well as shutdown.

Notice that unexpected power failure at any time can potentially corrupt data on the disk, possibly to the extent that the disk becomes unreadable. To reduce this risk, use the smallest possible time for the delay time that Write data is cached before it is flushed to disk.

Certain applications are data-sensitive and require that write-through is active. Examples of this are SQL server-based applications and NTFS partitions.

16.4 Installing Windows NT on an ESDI Disk Drive with More Than 1024 Cylinders

In some cases, Windows NT installation proceeds normally until the first boot from the hard drive where Windows NT is installed. The Windows NT Boot Loader will load various files and then produce a Fatal System Error, 0x0000006b, with the message that Phase 1 Process Initialization failed. Following this message will be some type of hexadecimal dump and the system will be locked up. If you experience this difficulty, the following information can help.

Testing has been done on the ESDI controllers listed later in this section using a hard drive with a capacity exceeding 516MB (MB=1,048,576 bytes) formatted. The DOS limit of 1024 cylinders creates a situation where special BIOS mapping on the controller is used to change the geometry of the drive. ESDI drives are capable of being prepared with various values of sectors per track (spt) such as 53 or 63spt geometry during a low-level format, as shown in the following example.

1024 cylinders x 15 heads x 53spt x 512 bytes per sector = 398MB formatted capacity

Or

1024 cylinders x 15 heads x 63 spt x 512 bytes per sector = 472MB formatted capacity

Thus, using 63spt will yield 74MB more space. Windows NT is perfectly compatible with either geometry and, depending on the drive or controller, can access the remaining cylinders beyond 1024. This space can be partitioned and formatted but not accessed by DOS. However, some controllers can successfully remap the remaining cylinders beyond 1024 so that either DOS or Windows NT can use the entire capacity. For example:

1632 cylinders x 15 heads x 53spt x 512 bytes per sector = 634MB formatted capacity

Testing has been done on the following ESDI controllers.

16.5 Data Technology Corp. (DTC) Model 6282-24

Maximum Windows NT-compatible geometry is to use 63spt and a limit of 1024 cylinders under DOS. Windows NT will be able to access the cylinders beyond 1024. Do not perform a low-level format on the drive using Head Mapping mode.

16.6 DTC Model 6290-24

Maximum Windows NT-compatible geometry is to use 63spt and a limit of 1024 cylinders under DOS. Because this card does not have an onboard BIOS, Windows NT cannot access the remaining cylinders beyond 1024.

16.7 DTC Model 6290 SEZ (Dual SCSI/ESDI Controller)

Maximum Windows NT-compatible geometry is to use BIOS translation in the EISA configuration, using 63spt and a limit of 1024 cylinders under DOS. Windows NT can access the remaining cylinders beyond 1024.

16.8 DTC Model 6295-24

Maximum Windows NT-compatible geometry is to use 63spt and a limit of 1024 cylinders under DOS. This model does have an onboard BIOS, so Windows NT can access the remaining cylinders beyond 1024. Do not perform a low-level format on the drive using Head Mapping mode.

16.9 Adaptec Model 2322D

The methods that can achieve maximum drive capacity are as follows:

1.	Disable drive translation and the on-board controller BIOS. Then use a user-defined drive 	type with the actual drive parameters. For example: Drive Type in CMOS=48 Cylinders=1632 Heads=15 SPT=53 This will give 634MB capacity. DOS will still be limited to the first 1024 cylinders, which makes 398MB available. Windows NT will be able to access the cylinders beyond 1024, yielding another 236MB.

2.	This option allows both DOS and Windows NT to access the entire drive. Set jumpers on 	the controller for Drive Splitting. Disable drive translation and the on-board controller BIOS. 	Set up the first physical drive in the CMOS as: Cylinders=1024 Heads=15 SPT=53 which will give a drive capacity of 398MB. Set up the second drive (it appears as a physical drive) in the CMOS as: Cylinders=606 Heads=15 SPT=53 This will yield another 236MB. Windows NT will actually see the drive as two physical drives.

16.10 UltraStor with PROM versions less than nnnnn-009

Maximum Windows NT compatible geometry is to use 63spt and a limit of 1024 cylinders under DOS. Windows NT will be able to access the cylinders beyond 1024.

16.11 UltraStor with PROM versions equal to or greater than nnnnn-009

Maximum Windows NT compatible geometry is to use Track Mapping during low-level formatting. Both DOS and Windows NT will have access to the entire drive capacity.

17.0 SCSI Devices

The following section presents issues for SCSI devices.

17.1 Adaptec BIOS Detection

Windows NT includes a new BIOS detection code from Adaptec. The detection code helps identify BIOS conflicts with other network or video adapters. If BIOS conflicts are detected, you may encounter a number of problems that might be interpreted as a driver problem. If Windows NT detects a BIOS conflict, the system will write information in the event log to describe the conflict and identify the adapters in conflict. Please consult the vendor's manual to adjust the location of the BIOS to eliminate the conflict.

17.2 Installing Windows NT with a Windows Driver Library Adapter Driver

Some SCSI and proprietary CD-ROM adapter drivers are provided in the Windows Driver Library on the Windows NT compact disc. These drivers are contained in a directory tree below the \DRVLIB directory. Some of the drivers will have a README file containing additional configuration information.

Please read this information before installing.

To install Windows NT using a \DRVLIB adapter driver:

1.	Using your current operating system, access the Windows NT CD-ROM and change to the 	directory containing the driver that you want to use.

2.	Copy all files in that directory to a blank, formatted diskette disk placed in drive A (Windows 	NT Setup requires the driver to be on a disk in drive A). Label the disk Driver Disk.

3.	Shut down your current operating system (if necessary) and reboot with the Windows NT 	CD-ROM Setup Boot Disk in drive A.

4.	When Setup asks for Custom or Express Setup, choose Custom.

5.	When choosing an adapter, type S to select from additional SCSI adapters.

6.	Choose the Other (requires disk provided by hardware manufacturer) option.

7.	Setup prompts for the driver disk. Insert Driver Disk in drive A and then choose OK.

17.3 Replacing SCSI Adapters

If you want to replace a SCSI adapter in your hardware configuration, you must enable the new adapter miniport driver and disable the old adapter.

To enable a new boot device adapter:

1.	Using the Devices option in Control Panel, set the new adapter Startup value to Boot.

2.	Change NTBOOTDD.SYS, the loader environment miniport driver. This is a read-only, hidden system file called NTBOOTDD.SYS in the root of the drive containing NTLDR. Usually this is drive C unless drive letters were changed. Use the following commands at the command prompt to copy the new miniport driver over the existing driver. (In this example, we are using an adapter that uses BUSLOGIC.SYS. Your adapter may use a different driver.)

attrib -r -s -h c:\ntbootdd.sys
copy %systemroot%\system32\drivers\buslogic.sys c:\ntbootdd.sys
attrib +r +s +h c:\ntbootdd.sys

The final attrib statement protects users from removing the file by mistake.

3.	Restart the computer.

17.4 Notes on Specific SCSI Devices

The following table presents issues for specific SCSI devices.

During the testing of SCSI devices, a significant number of errors were corrected by using a SCSI-II active terminator on the SCSI bus. We highly recommend the use of active terminators.

17.5 Adaptec

An Adaptec adapter might use memory addresses that conflict with other cards, such as network adapters. Reconfigure the hardware by changing jumpers.

17.6 Adaptec 1510, 1520, and 1522

These adapters (and others using the SPARROW.SYS driver) must be configured for IRQ 11.

17.7 Adaptec AHA-1542C and Denon DRD-253

This adapter and drive are incompatible together under Windows NT. The AHA-1542C requires active termination and the Denon DRD-253 CD-ROM has built-in passive termination.

17.8 Adaptec 1542x

There is a known problem using Micronics VL bus motherboards with these adapters.

17.9 Adaptec 154x

DMA speed cannot be set on an Adaptec 154x SCSI controller. Currently the AHA154X.SYS driver supports a DMA transfer rate of 5.0MB.

The Adaptec AHA154xC card is extremely sensitive to termination and cabling. Systems with this card should use SCSI-II cables and/or SCSI-II active terminators. SCSI-II cables are available from Amphenol, Quintec, and Icontec. If these recommendations are not followed, unreliable operation, including data corruption, is possible.

The 1988 Version 3.08 Adaptec 154x BIOS has a problem with the Scatter/Gather feature. This problem is detected by the Adaptec driver and the feature is disabled. If you have this BIOS version, a message informs you that the Scatter/Gather feature has been disabled. If you get this message, you can contact Adaptec Technical Support at 408-945-2550 for information on the most recent version, 3.20, of the BIOS. BIOS versions after 3.08 do not have this problem.

The latest 154x BIOS also supports drives that are larger than 1GB under both BIOS/DOS and Windows NT. Windows NT will be able to access drives larger than 1GB even without this upgrade, provided an extended partition is used.

17.10 Adaptec 1640 Micro Channel« adapter

This adapter does not support the Maynard 2000 or 1300 DAT drives in this release. The 1640 adapter is not supported on IBM PS/2 Model 70 computers.

17.11 Adaptec AHA164x

The AHA164x driver logs unnecessary errors. These occur while Windows NT Backup is used with a tape connected to the AHA164x. The entries look like this:

7/10/93 2:41:40 AM AHA154x Error None 11 N/A  [ComputerName]The driver detected a controller error on  \Device\ScsiPort1.

These entries can be ignored. When too many of these entries are generated, a popup message indicates the error log is full. This can be avoided by setting the system event log settings to overwrite the events as needed.

17.12 Adaptec 1740

If this card is configured for Standard mode, Windows NT detects the card as an AHA-154x. If you change the card to Enhanced mode, you must use Windows NT Setup to remove the AHA-154x driver and install the AHA-1740 driver. An active terminator is recommended for proper performance with this adapter.

17.13 Adaptec 2940

The Adaptec 2940 (and others based on the Adaptec AIC-78xx series chips) must have host adapter negotiated synchronous transfers for the ID number of each CD-ROM drive attached. This is done in the Adaptec SCSI Select BIOS configuration utility.

17.14 Buslogic

When using a Buslogic 747 SCSI adapter with an AST Manhattan SMP computer, you must disable the BIOS on the adapter. For more information on disabling the BIOS, see the adapter's documentation. An active terminator is recommended for proper performance with this adapter.

17.15 COMPAQ Smart SCSI Array

This adapter must be configured to use any possible interrupt other than IRQ 2 to function properly under Windows NT. This requires COMPAQ Version 2.08 and firmware Version 2.04.

17.16 Dell Drive Array

This adapter is not supported in Adaptec emulation mode.

17.17 Future Domain 8xx

This adapter might use conflicting memory addresses. This requires reconfiguring the hardware by changing jumpers.

The Windows NT driver that supports the Future Domain 845, 850, 860, and 885 adapters assumes operation on IRQ 5. If the adapter is set for another interrupt, the Future Domain driver will continue to work, but in a polling fashion that may slow down operation of the system. Further, the Future Domain driver will register as claiming the use of IRQ 5 and this may disrupt operation of another device that is actually configured for IRQ 5. If you are using one of the above mentioned Future Domain adapters, please complete the Windows NT installation normally, then change the IRQ information for the driver in the Registry. If the IRQ is incorrect, the driver will log an event that you can view using Event Viewer.

If you have a 16-bit Future Domain card or an 8-bit M series card configured with an external SCSI device, make sure the SCSI termination is correct. You must set a jumper on the card for this setting. Check the card's documentation for details.

17.18 PS/2 SCSI Adapter

To configure an IBM SCSI adapter with a BIOS dated before 1991 for use with Windows NT, use a PS/2 Reference Diskette Version 1.12 or later.

The IBM PS/2 SCSI Adapter does not support Logical Unit Numbers (LUNs). The adapter views them as IDs instead of identifying them as LUNs. This may cause SCSI ID conflicts with other devices if more than one SCSI device is connected to this adapter.

17.19 Maynard SCSI Adapter

You cannot use Express Setup to install Windows NT onto a hard disk attached to a WD33C9C SCSI host adapter (Maynard SCSI adapter) because Setup cannot identify this adapter. However, you can use Custom Setup to install this adapter card, or after Setup, you can use Windows NT Setup in the Main Program group to install the adapter card.

17.20 Mylex DCE376 and Tangent 48933 USA

The Tangent and Zeos 433 EISA system comes standard with a Mylex 376 controller, which operates in WD1003 emulation mode by default. This will no longer be necessary when a SCSI driver for this card becomes available for Windows NT.

17.21 NEC Intersect CD-ROM

Readers for this device have a switch that enables disconnects during accesses to the reader. This switch is off by default, disabling disconnects. Because of this, while your CD-ROM is being read, no other devices on that SCSI bus can be accessed. Since reads from a reader can take a significant amount of time, having this switch off can degrade system performance noticeably. This slow-down may occur even if you are not using the CD-ROM reader. To avoid this problem, set switch number 5 to On. The switch is located with switches labeled SW1.

17.22 Plextor (Texel) DM-5024 CD-ROM

A firmware level of 1.10C is required to make the DM-5024 CD-ROM compatible with Windows NT. Contact Plextor at 1-800-886-3935 for information on this upgrade.

17.23 ProAudio Spectrum 16 TMV1

The PAS-16 SCSI driver for the ProAudio Spectrum 16 card defaults to IRQ 15.

No other adapters should use IRQ 15. Once NT is installed, the Mediavision ProAudio Spectrum 16 adapter driver can be added through CONTROL PANEL\DRIVERS, which allows you to configure both the sound I/O as well as change the SCSI IRQ.

Tape drives are not supported with the ProAudio Spectrum 16.

17.24 PCMCIA Cards

Support for certain modem cards, small computer system interface controller cards, network adapter cards, and hard disk PCMCIA cards has been included in Windows NT Server 3.51. However, be sure to check the Hardware Compatibility List to determine which cards and computers are supported.

To use a supported PCMCIA card, insert the card after shutting down your computer. When the computer is restarted, Windows NT Server detects the card in the socket. You must also shut down Windows NT Server before removing a PCMCIA card.

For Windows NT Server to detect a supported SCSI or network adapter PCMCIA card, you must first load a Windows NT Server device driver or you must configure the network adapter card before shutting down Windows NT Server to insert the card.

For more information about using supported modem, SCSI, and network adapter PCMCIA cards and verifying their installation, see the following sections. For more information about viewing the Registry, see the procedure "To view the Registry," later in this section. For additional information about using the Registry Editor, also see "Editing Registry Values" in the README.WRI file.

17.25 PCMCIA Event Log Error

If you get an error in the Event Log such as, There is no configuration information for the PCCARD manufacture/product, you should check the PCMCIA Database key in the Registry to see if there is an entry for your device. If there is not an entry for your device, you will need to call the manufacturer of the PCMCIA card for new drivers or have Microsoft PSS assist you in creating an entry for the device in the Registry.

17.26 Enabling PCMCIA Cards

If a PCMCIA card is not being enabled, check in Control Panel/Devices to confirm the PCMCIA driver is set to Boot and has started automatically. If the Control Panel is set to start PCMCIA automatically and still is not doing so, check the Event Log for details on errors.

17.27 Using PCMCIA Devices with Windows NT 3.51

When using PCMCIA devices, such as modems and network cards, on a Windows NT Workstation, power management features on the computer system should be turned off. Consult the manufacturer's system manual for procedures to disable power management.

17.28 Trantor

The Windows NT driver that supports the Trantor T-128 and T-130B adapters assumes operation on IRQ 5. If the adapter is set for another interrupt, the Trantor driver will continue to work, but in a polling fashion that may slow down operation of the system. Also, the Trantor driver will register as claiming the use of IRQ 5 and this may disrupt operation of another device actually configured for IRQ 5. If you are using one of these Trantor adapters, complete the Windows NT installation normally and then change the IRQ information for the driver in the Registry. If the IRQ is incorrect, the driver will log an event that you can view using Event Viewer.

In addition, these adapters are SCSI-termination sensitive. If Windows NT hangs upon booting or if Windows NT Setup cannot find devices attached to a Trantor adapter, verify that the SCSI termination occurred and that one of the SCSI devices attached to the Trantor adapter is providing termination power.

Tape drives are not supported with the T-128 for this release.

17.29 UltraStor SCSI Controllers

If you experience a problem in tape functionality with a supported 4mm DAT tape device and an UltraStor 14F or 24F controller, contact UltraStor for an upgrade to resolve this.

If you have an UltraStor 34F controller installed in a Micronics VLB motherboard, it is recommended that you turn the motherboard external cache off.

The UltraStor 124 adapter is compatible with removable media drives but does not allow the user to remove and replace media. For this reason, Windows NT does not support removable media drives when used with this controller.

The combination of the UltraStor 14F and DECTalk speech synthesizer card can cause Windows NT Setup to fail because of an I/O port conflict. To avoid this problem, either set the Digital I/O to 350 or delete the ULTRA14F.SYS file from the boot diskette while leaving the DECTalk card at default settings.

17.30 AT/API (IDE) Devices

Avoiding Accidental Bug Checking

The following actions will cause you to bug check and should, therefore, be avoided:

* Starting the computer from ATDISK and then adding an AT/API (IDE) drive without installing ATAPI.SYS and SCSICDRM.SYS.

* Removing an AT/API(IDE) device from the cable with the boot drive, without starting ATDISK.SYS.

18.0 Tape Devices

Windows NT supports over 50 tape drives.

18.1 DEC TZ86, TZ87, DLT2000 Based Tape Drives

Firmware revision number 20 (9514) is required for proper operation.

Tape drive autochangers based on these drives are supported only in manual operation mode (single tape) with the Windows NT Backup program.

18.2 QIC 40/80 Tape Devices

QIC 40/80 tape devices should be attached to your computer's native diskette controller. Proprietary diskette tape controller cards are not supported. Also, hardware data compression is not supported on QIC 40/80 diskette tape drives.

19.0 Non-SCSI CD-ROM Drives

19.1 Creative Labs CD-ROM Drives

Please see the section on Panasonic CD-ROM Drives.

19.2 Mitsumi CD-ROM Drives

Windows NT supports the Mitsumi CRMC-FX001D and Mitsumi CRMC-FX001D1.

To use this drive, please select the Mitsumi CD-ROM entry under Add SCSI Adapter in Setup. This drive will not be auto-detected during the installation of Windows NT. You must select the driver manually.

The Mitsumi CD-ROM drive is supported on the Creative Labs Sound Blaster 16 MultiCD and the Mitsumi 74-1881A 16-bit interface card.

If you already have the interface board installed, you should consult your user manual to ensure you have the supported interface board.

If the computer screen goes blank during the loading of the Mitsumi driver, it is due to an I/O conflict with another device installed in the computer. To resolve this, reconfigure the system and restart the installation.

The Mitsumi drive is slow to respond to certain system events, which can cause problems such as broken-up sound in some timing-sensitive Multimedia titles. This should not cause problems when the drive is being used to access CD-ROM data with no real-time requirements.

19.3 Panasonic CD-ROM Drives

Windows NT supports the Panasonic CR-521, CR-523, CR-562, and CR-563 CD-ROM drives.

These drives may be labeled on the top or bottom of the drive by Panasonic, Creative Technology (Creative Labs), or Matsushita-Kotobuki.

Some of these drives may be labeled on the front bezel with the Sound Blaster logo.

To use these drives, please select the Panasonic CD-ROM entry under Add SCSI Adapter in Setup. These drives will not be auto-detected during the installation of Windows NT, so you must select a driver manually.

The Panasonic CD-ROM drives are supported on the Creative Labs Sound Blaster Pro, Sound Blaster 16, Sound Blaster 16 MultiCD, and the Panasonic (Matsushita-Kotobuki) LMEP0084B 8-bit interface card.

If you already have the interface board installed, you should consult your user manual to ensure you have the supported interface board.

This driver can take a considerable length of time to initialize the hardware during boot and your system may appear to hang. This initialization period can take serveral minutes. An updated driver will be available through the Windows NT Driver Library when this problem is resolved. Please see the Windows NT Hardware Compatibility List for more information on the Windows NT Driver Library.

19.4 Sony Proprietary CD-ROM Drives

Windows NT supports the Sony CDU31A and the CDU33A.

To use these drives, please select the Sony CD-ROM entry under Add SCSI Adapter in Setup.

The Sony CD-ROM drives are supported on the Creative Labs Sound Blaster 16 MultiCD and the Sony CDB-334 8-bit interface card. The Sony CDB-334 is sold in a Sony CD-ROM interface kit. Sony has two kits, one for external drives and one for internal drives. The Sony part numbers for these kits are OPA-474E (external) and OPA-474I (internal).

If you already have the interface board installed, you should consult your user manual to ensure you have the supported interface board.

Contrary to the documentation for the Sony CDB-334, an interrupt is required for this board to work under Windows NT. A jumper will need to be placed on JP4 (the IRQ channel jumper).

20.0 Removable Media

Windows NT supports over 10 SCSI removable media systems.

Removable media drives (such as the Bernoulli Box and Syquest) are supported for use with the NTFS and FAT file systems only.

If you install Windows NT or any portion of Windows NT onto removable media, or have partitioned the media to NTFS, be sure to shut down Windows NT before removing the media. (That is, choose Shutdown from the File menu of Program Manager.) Do not remove the media until after Windows NT has completed its shutdown process.

20.1 Installing from CD-ROM with Floptical Drives Present

Users with configurations that have a 21MB floptical drive configured as drive A will not be able to perform a diskette setup of Windows NT 3.5.

To install from CD-ROM in a configuration that has a 21MB floptical drive as drive A, edit the TXTSETUP.SIF file on Disk 1. Under the section [SetupData], add the line ForceOEMSCSI=1. This will disable SCSI adapter detection; the appropriate driver must be chosen manually.

20.2 PCMCIA Cards

Support for certain modem cards, small computer system interface controller cards, network adapter cards, and hard disk PCMCIA cards has been included in Windows NT Server 3.51. However, PCMCIA card and socket support have not been included. Be sure to check the Hardware Compatibility List to determine which cards and computers are supported.

To use a supported PCMCIA card, insert the card after shutting down your computer. When the computer is restarted, Windows NT Server detects the card in the socket. You must also shut down Windows NT Server before removing a PCMCIA card. Integrated Device Electronics (IDE) PCMCIA hard disks should be inserted before you install Windows NT Server.

For Windows NT Server to detect a supported SCSI or network adapter PCMCIA card, you must first load a Windows NT Server device driver or you must configure the network adapter card before shutting down Windows NT Server to insert the card.

Before you insert a PCMCIA card, you might want to check certain applications or look for a particular key in the Registry so that after the card is inserted, you can verify that the Windows NT Server detected the card. For more information about using supported modem, SCSI, and network adapter PCMCIA cards and verifying their installation, see the following sections. For more information about viewing the Registry, see the procedure "To view the Registry" later in this section. For additional information about using the Registry Editor, see also "Editing Registry Values" in the README.WRI file.

This adapter defaults to IRQ 15 and may conflict with other adapters.

If are not using this CD-ROM drive but you experience problems during Windows NT Setup, you must remove the adapter and restart Windows NT Setup. After Windows NT is installed, reinstall the adapter.

21.0 Multiport Serial Adapters

Windows NT supports over ten multiport serial adapters. Support for the intelligent Digi adapters is incorporated in Windows NT. If you want to use a dumb multiport serial adapter or a Comtrol Hostess or Stargate Technologies adapter, you will either need a driver from your hardware vendor or you will need to modify the Registry to support your card. If you need to modify the Registry, follow these steps.

To configure multiport serial adapters for Windows NT:

1.	Determine the correct IRQ and port address values for your adapter.

2.	Install the adapter according to the manufacturer's instructions.

3.	Using Registry Editor, open the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial\Parameters

For more information on using the Registry Editor, see Editing Registry Values in 	README.WRI.

4.	From the appropriate table below, add the Serial* keys under Parameters, and add the 	corresponding values for each Serial* key.

The actual values for your adapter may be different. Also, if you have only one serial port 	on your computer, you can start with the Serial1 and Com2 keys. If no serial ports are built 	into your computer, you can start with Serial0 and Com1.

5.	If no serial ports are built into your computer, the following values need to be added under the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial
Add value name	Data type	Data
ErrorControl	REG_DWORD	1
Group	REG_SZ	Extended base
Start	REG_DWORD	2
Type	REG_DWORD	1

6.	Quit REGEDT32.EXE and enter the following two commands at the command prompt to 	activate the changes:

net stop serial
net start serial

The serial ports should now work. Restarting Windows NT will also activate the changes.

Notice that COM1 through COM9 can be directly referenced just like a filename from programs and from the command prompt. However, COM10 and above must be referenced with the following syntax:

\\.\com10

The command line mode command does not recognize ports above COM9.

The samples below all assume that two serial ports are already available that will be listed as Serial0 and Serial1 in the Registry and assigned to COM1 and COM2 respectively. The additional ports will start at COM3. For more than four port adapters, simply continue the pattern for as many ports as needed. The following values will work even if one of the first two ports has a serial mouse attached.

Hostess 4-Port Adapter at IRQ 2, Starting Port Address 500, Starting at COM3

Add key (no class)	Value names	Data type	Data

Serial2	PortAddress	REG_DWORD	0x500
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM3
PortIndex	REG_DWORD	1
InterruptStatus	REG_DWORD	0x507
Serial3	PortAddress	REG_DWORD	0x508
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM4
PortIndex	REG_DWORD	2
InterruptStatus	REG_DWORD	0x507
Serial4	etc.	etc.	etc.

Digi 4-Port Adapter at IRQ 2, Starting Port Address 100, Starting at COM3

Add key (no class)	Value names	Data type	Data

Serial2	PortAddress	REG_DWORD	0x100
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM3
PortIndex	REG_DWORD	1
InterruptStatus	REG_DWORD	0x140
Indexed	REG_DWORD	1
Serial3	PortAddress	REG_DWORD	0x108
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM4
PortIndex	REG_DWORD	2
InterruptStatus	REG_DWORD	0x140
Indexed	REG_DWORD	1
Serial4	etc	etc.	etc.
Serial5	etc.	etc.	etc.

Notice that the Digi adapter has a buffer size limitation that can cause bad behavior with some Windows communications applications, such as Procomm Plus. To overcome this limitation, set the buffer size in the application to 8K or less.

Stargate 4-Port Adapter at IRQ 2, Starting Port Address 180, Starting at COM3

Add key (no class)	Value names	Data type	Data

Serial2	PortAddress	REG_DWORD	0x180
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM3
PortIndex	REG_DWORD	1
InterruptStatus	REG_DWORD	0x580
Serial3	PortAddress	REG_DWORD	0x188
Interrupt	REG_DWORD	2
DosDevices	REG_SZ	COM4
PortIndex	REG_DWORD	2
InterruptStatus	REG_DWORD	0x580
Serial4	etc.	etc.	etc.
Serial5	etc.	etc.	etc.

22.0 Mice and Other Pointing Devices

Windows NT supports over 30 mice and other pointing devices. Windows NT includes four mouse port drivers that support various types of mice.

22.1 Serial Mouse (SERMOUSE.SYS Driver)

The serial mouse connects to COM1 or COM2. This driver also provides support for serial ballpoints (the default right-handed ballpoint orientation and primary/secondary buttons are supported). A ballpoint-specific driver that supports the selection of right/left orientation and primary/secondary buttons may be released via the Windows Driver Library.

On x86-based computers, support for the serial mouse is automatic. On RISC-based computers, the serial mouse may not be detected but is supported.

To enable a serial mouse on a RISC-based computer, add one of the following to the Registry:

OverrideHardwareBitstring:REG_DWORD:0x1 or OverrideHardwareBitstring:REG_DWORD:0x2

Use the value 0x1 when the mouse is connected to COM1 and the value 0x2 when the mouse is connected to COM2. The value is located in the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sermouse\Parameters

For more information on editing the Registry, see Editing Registry Values earlier in this file.

22.2 Microsoft InPort Bus Mouse (INPORT.SYS Driver)

The Microsoft InPort bus mouse is supported on x86-based computers. It connects to the Microsoft InPort Adapter via a round 9-pin connector (the female connector is on the adapter). The mouse itself is labeled InPort Mouse or Bus Mouse. However, the InPort bus mouse is not the same as the bus mouse supported by BUSMOUSE.SYS, as described later in this section.

Jumpers must be set manually on the InPort adapter. A typical jumper setting for Windows NT is as follows (notice that we chose IRQ 2, because IRQs 3 or 4 conflict with the COM ports, and IRQ 5 is often used by network cards):

J2 NORMAL (v. XT SLOT 8)J3 PRI. INPORT (v. SEC. INPORT)J4 INTERRUPT 2 (v. 3 or 4 or 5)

22.3 Bus Mouse (BUSMOUSE.SYS Driver)

The bus mouse is supported on x86-based computers. It connects to a Microsoft or Logitech« bus mouse adapter via a rectangular 9-pin connector (the female connector is on the adapter). The Microsoft bus mouse is an older version with green buttons and a steel ball. This mouse is not the same as the InPort bus mouse. The Logitech bus mouse is typically labeled MouseMan Bus.

One jumper must be set manually on the bus mouse adapter to select the IRQ. Typically, the IRQ selected for Windows NT is 2, because IRQs 3 and 4 conflict with the COM ports, and IRQ 5 is often used by network cards.

22.4 Mouse Port or PS/2 Mouse (I8042PRT.SYS Driver)

The Mouse Port mouse (sometimes called the PS/2 mouse) is supported on both x86-based and RISC-based computers. It connects to a round, 6-pin connector built into the computer as the Intel 8042 (or Intel 8742) auxiliary device. The keyboard is also connected to the Intel 8042 and is supported by the same driver.

The I8042PRT.SYS driver also provides support for Mouse Port ballpoints. The default right-handed ballpoint orientation and primary/secondary buttons are supported. A ballpoint-specific driver that supports the selection of right/left orientation and primary/secondary buttons may be released via the Windows Driver Library.

Support for the Mouse Port mouse is automatic on both x86-based and RISC-based systems. It is the standard pointing device on RISC-based computers.

22.5 Support for Multiple and Alternative Pointing Devices

Windows NT can support the simultaneous use of more than one mouse or pointing device. The use of multiple pointing devices is not, however, supported by default. Windows NT Setup enables only one pointing device driver to load when starting.

Windows NT does not include drivers for alternative pointing devices, such as tablets, touch screens, and so on. Contact your hardware vendor for Windows NT drivers.

23.0 Sound

Sound devices are configured after running Windows NT Setup. This section describes how to install Sound Blaster, Media Vision Pro Audio Spectrum 16, and the Windows Sound System to work with Windows NT.

When using a sound card, you may encounter an IRQ or DMA channel conflict with another device. Use the Drivers tool in Control Panel to reconfigure if necessary.

23.1 Sound Blaster

The recommended settings for the sound card are the following:

DMA 0,1, or 3 (configurable; must be 1 except for Sound Blaster Pro and Sound Blaster 16)

Additionally a second DMA channel is required for the Sound Blaster 16. DMA 5,6, or 7 can be used. DMA 5 is often used by the system for SCSI adapters.

The current default IRQ for the Sound Blaster is 5; other possible IRQ settings are 2, 7, or 10. IRQ 7 may conflict on some Dell machines, causing repeated sounds.

Port I/O addresses range from 220H to 280H. The default setting is 220H.

There may be a DMA or IRQ conflict with another device. Change the DMA or IRQ setting on the other device or on the sound card. The default settings for the sound card are DMA 1, IRQ 7, and port 220H. For the Sound Blaster 16, change the conflicting DMA and IRQ setting and try again. For earlier Sound Blaster cards, try physically changing the Sound Blaster card to a new DMA channel; i.e., IRQ 2, and then using Control Panel to reconfigure the Creative Labs Sound Blaster driver to IRQ 2.

The original (8-bit) Sound Blaster boards require DSP 2.0 or later for proper sound output under Windows NT.

To install and configure a Sound Blaster driver:

1.	Start Windows NT and logon with Administrator rights.

2.	Run Control Panel and then double-click the Drivers icon.

3.	In the Drivers dialog box, choose the Add button.

4.	In the Add Driver dialog box, select Creative Labs Sound Blaster 1.x and then choose the 	OK button.

5.	In the configuration dialog box, select the correct port and press Continue.

6.	If the port number is correct and the card is found, a new dialog box will appear with a list of 	configuration parameters for the card you have. This will include the interrupt number and DMA channel number for the Pro and Sound Blaster 16 and the 16-bit DMA channel number and MPU401 address for the Sound Blaster 16.

The typical default setting for the interrupt number is IRQ 7 and the port setting is usually 	220. However, you might need to change these settings on your card to avoid conflicts with other hardware on your computer.

7.	When the message asks if you want to restart your computer, choose Restart Now.

23.2 Pro Audio Spectrum-16

The Pro Audio Spectrum-16 includes an option for Sound Blaster emulation. This emulation is not supported by Windows NT. When installing the Pro Audio Spectrum-16, do not use the same interrupt value as that option. Using the same interrupt may cause unpredictable system behavior.

On earlier cards, the default for this interrupt is 5, and jumpers can be set to be 2, 3, 5, or 7. On later cards without jumpers, the default is usually 7. Please check the documentation for the card before installing it under Windows NT.

To perform optimally on the Digital DECpc AXP 150, the Pro Audio Spectrum-16 card should be installed using either channel 5 or channel 7. This restriction does not apply to other Alpha AXP models.

If you do not use the Sound Blaster emulation under DOS or Windows 3.1, you should disable it. For more information, see the section "Changing I/O Address for Sound Blaster Compatibility" in the Pro Audio Spectrum-16 User Guide.

To install and configure the Pro Audio Spectrum-16, follow the steps above for installing the Sound Blaster.

23.3 Windows Sound System

Windows NT 3.51 supports the Windows Sound System and its utilities. In addition, Windows NT includes versions of Sound Recorder and Volume Control in the Accessories Group in Program Manager.

To install and configure the Windows Sound System driver:

1.	Start Windows NT and logon as an Administrator.

2.	Run Control Panel and then double-click the Drivers icon.

3.	In the Drivers dialog box, choose the Add button.

4.	In the Add Driver dialog box, select Windows Sound System and then choose the OK button.

5.	Insert the Windows NT Setup CD-ROM or insert the appropriate diskette disk in drive A.

6.	Accept the default configuration settings suggested by Windows NT. These settings depend upon your actual hardware, which may be improperly detected by Windows NT Setup in rare circumstances.

7.	When the message asks if you want to restart your computer, choose Restart Now.

23.4 Sound on RISC-based Computers

Some RISC-based systems have built-in sound capabilities. For example, sound drivers are available for the following systems:

Olivetti M700-10

Acer ARC1

MIPS ARCSystem Magnum or Millennium PC-50

MIPS ARCSystem Magnum or Millennium SC-50

Follow the same steps as previously described to install one of these drivers. However, you do not have to change any configuration settings.

24.0 Video Capture

Some Video Capture drivers are provided in the Windows Driver Library on the Windows NT compact disc. These drivers are contained in a directory tree below the \DRVLIB directory. Some of the drivers will have a README file containing additional configuration information.

25.0 Application Notes

The following sections provide general information about running applications on Windows NT 3.51 that were created for Windows 3.1, Windows NT 3.1, or DOS. Windows NT 3.51 has excellent support for those applications. If you do encounter a problem, this section provides some solutions.

25.1 Viewing Compressed Files on Windows NT 3.5

If you are running Windows NT Version 3.5 or earlier on your computer, you will not be able to see compressed files until you upgrade to Windows NT 3.51 or install Service Pack 2.

25.2 Opening Files Created in Windows NT Using Windows 3.x

If you create a file using a DOS- or Windows 3.1-based application on Windows NT 3.5, you may get the error "Cannot find WINSPOOL.DRV" when using the file in Windows 3.x. The error occurs because some 16-bit applications attach drive location information to the files they create.

Click the Close button in the error message dialog box and save the file in its related application to prevent this error while using the file in Windows 3.x. To prevent the error for all applications and their files, create a file in the \WINDOWS\SYSTEM directory called WINSPOOL.DRV. The file is not used, so the contents of the file do not matter.

25.3 Using DOS-based Disk Utilities

The long file name format in Windows NT 3.51 uses file elements on FAT partitions differently than DOS. When using DOS-based disk utilities on FAT partitions used by Windows NT 3.5, files can be deleted or long file names can be lost. Microsoft recommends that you only run disk utilities specifically designed for Windows NT 3.5, or when running DOS, the chkdsk or scandisk utilities.

To prevent the Windows NT 3.51 FAT file system from using long names, you must set the following Registry entry to 1:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\Win31FileSystem

After changing the entry, you must restart your computer for the change to take effect.

Caution

PCTools diskfix utility is known to delete all files on the FAT partition. If you use DOS-based disk utilities on a FAT disk partition used by Windows NT 3.5, the utility may cause the loss of long filenames or delete files on the FAT partition unless the Registry entry is set to 1. Back up the FAT partition before running any disk utility other than chkdsk.

25.4 Running SNA Server

During the course of testing SNA Server 2.0 on the Windows NT 3.51 Beta 2, two bugs were discovered in SNA Server 2.0. These bugs were uncovered as a result of the improved parameter checking and fault detection included in Windows NT 3.51 and do not affect the operation of SNA Server 2.0 on Windows NT 3.1.

The symptoms of these bugs are that SDLC and X.25 SNA connections will not go active and 802.2 SNA connections will cause an exception in SNALINK.EXE. Fixes for these problems are available in the SNA directory of your Windows NT 3.51 Beta 2 CD and are also available in the Library 2 section of the MSSNA forum on CompuServe.

If you have SNA Server 2.0 installed on your system, please copy the contents of the SNA directory to your <snaroot>\SYSTEM directory after you have upgraded your system to Windows NT 3.5.|

The contents of the SNA directory are:

IBMSDLC.DLLIBMX25.DLLSNADLC.DLL

Although these patches are openly available, Microsoft recommends that you use SNA Server 2.1 Beta on all Windows NT 3.51 systems. Please see the MSSNA forum on CompuServe for any additional updates or notices.

25.5 Running Serial Communications Applications

For reliable data transfer at the highest baud rate, use communications protocols that support end-to-end flow control. If the protocol you use does not support flow control, you may need to reduce the serial port baud rate for reliable communication. The following table shows which protocols support flow control.

Serial flow control protocol	Flow control

ASCII (Xon/Xoff)	No
XMODEM	Yes
XMODEM-1K	Yes
YMODEM	Yes
YMODEM-G1	No
ZMODEM2	No
Kermit	Yes
CompuServe B+	Yes

1.	The -G option disables flow control.

2.	Some applications allow flow control with ZMODEM. For example, you can enable flow control with Procomm Plus 2 by setting the Transmit Method to 4K WINDOW.

Windows NT supports 16-bit Windows communications programs using the communications driver COMM.DRV. Other communications drivers are not supported and may not function reliably. You can check or change the communications driver using the Registry Editor. The value should be:

comm.drv:REG_SZ:comm.drv

The value is located in the following Registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WOW\boot

For more information on using the Registry Editor, see "Editing Registry Values" in this file.

To run multiple 16-bit communications applications simultaneously, or to run a 16-bit communications application in the background or minimized and still maintain a reliable connection, it is suggested that you modify the Tasking on your system to Foreground And Background Applications Equally Responsive. To do this, in Control Panel, choose the System option. Choose the Tasking button. In the Tasking dialog box, select Foreground And Background Applications Equally Responsive and then choose the OK button.

Procomm Plus for Windows

The Procomm Plus implementation of the XMODEM protocols for uploads may yield less-than-expected throughput when running NT on slower 386-based machines.

Generally, you shouldn't experience any problems using the ZMODEM protocol for transfers on 486-based computers. On slower computers, try using 16-bit CRC and 4K sliding windows for ZMODEM downloads to increase the throughput and robustness.

Using ZMODEM for uploads and XMODEM for downloads on slower computers will give the expected performance at higher baud rates.

25.6 Running DOS-based Remote Control Applications

Remote control applications control a remote computer from a local computer through a serial connection. The local computer runs a program that sends keystrokes to the remote computer while displaying a copy of its screen. The remote computer runs a memory-resident program that allows the local computer to control it. If the remote computer is running Windows NT, you must create custom startup files and a custom PIF to set up the DOS environment for the memory-resident program.

To create the startup files:

Edit the AUTOEXEC.NT and CONFIG.NT files to change the following items, and then save the files under new names:

In the custom AUTOEXEC file, add the name of the memory-resident program if you want to start it when you run the PIF.

In the custom CONFIG file, add the commands dosonly and echoconfig. The dosonly command ensures that no programs can be started that can disable the memory-resident program.

To create the PIF:

1.	Double-click PIF Editor in the Main program group and select the _DEFAULT.PIF file.

2.	In the PIF Editor dialog box, type COMMAND.COM in the Program Filename box.

3.	In the Advanced Options dialog box, clear the Allow Fast Paste check box.

4.	In the Windows NT Options dialog box, specify the names of the custom startup files you created.

5.	Save the file under a new name.

For more information on creating PIFs and custom startup files, see the "Other Application Environments" chapter in the System Guide.

25.7 Running DOS-based Multimedia Applications

All DOS based applications (and many 16-bit Windows applications) that play multimedia do so by directly accessing the hardware involved. Direct access of most multimedia hardware (sound cards, and so on) is not supported. Consequently, any application that uses such methods to access hardware will be unsuccessful. Results may vary according to the way applications handle error conditions. Typically, the application will execute without the multimedia portions, but the application may be slow.

25.8 Limits to Application Support on RISC-based Computers

On RISC-based computers, Windows NT provides emulation for the 80286 instruction set. Applications that rely on the 80386 instruction set are not supported.

25.9 Information on Specific Windows 3.1 and DOS-based Applications

This section provides application-specific information about running DOS-based and Windows 3.1-based applications on Windows NT. It describes problems you might encounter and provides solutions where possible. Applications are listed in alphabetical order.

Various Multimedia Applications

Some older applications install an old version of the 16-bit Video for Windows runtimes. This may cause system problems with other 16-bit applications that play video.

Start the Media Player from the Accessories group in the Program Manager. It will tell you that the Registry has been changed and give you the option to fix it. Accept that option.

Applications that play many thousands of Intel Indeo-compressed movies consecutively.

Your system may run out of virtual memory, resulting in warning popups to that effect.

The problem is related to the Indeo codec, and its associated runtime. This is being investigated, and a fixed version will be placed on CompuServe and Microsoft's FTP server once available. In the meantime, close down your 32-bit application after serveral thousand movies have been played consecutively. If you are using a 16-bit application, log off and log back on again after a similar number have been played.

Adobe Photoshop

When using Adobe Photoshop 2.5, image windows may not repaint properly if you are using 256 colors and open gray scale files. Loading pattern files (*.AI) in Photoshop 2.5 may fail. You will receive a message such as:

"Could not open C:\PHOTOSHOP\PATTERNS\[FILENAME].AI because Photoshop was unable to parse the PostScript."

If you choose OK in the dialog box, you can continue working in Photoshop but you can't access the specified pattern file.

Other windows may not repaint properly when you are running Adobe Photoshop using 256 colors and an operation, such as restoring a file, changes the color palette.

Loading pattern files (*.AI) in Photoshop can cause the application to fail.

After Dark

Pressing CTRL+ESC to display the Task List dialog box disrupts the journal record in After Dark so it does not recognize keyboard or mouse activity, causing it to start the screen saver even when the computer is in use. If you press CTRL+ESC, close and restart After Dark.

AutoCAD Release 11 286

The Autolisp extensions (EXTLISP.EXE) for AutoCAD are not supported because they require VCPI.

AutoCAD Release 12

To correctly redraw and perform other graphic operations, such as cut and paste, you must use the correct AutoCAD video driver. The default video driver when you install AutoCAD is Windows Accelerated Display Driver ADI 4.2 by Autodesk, Inc (#1). If you use this driver, you will have problems with cut and paste and with redraw operations. Use the Windows driver by Autodesk, Inc (#2) and these operations will function correctly.

Autodesk 3D Studio, Release 2

3D Studio is not supported. The application fails when attempting to run the processor in protected mode.

Autodesk Generic CADD 6.0

The Generic CADD 6.0 screen is limited to 640x480 VGA resolution on Windows NT. To use this application, select the IBM VGA (Video Graphics Array) and compatible video graphics display from the Generic CADD 6.0 configuration utility (CONFIG.EXE).

Aldus Persuasion

Attempting to embed an AVI clip causes the application to crash. The audio clips will embed and play correctly but video will not.

Borland C++ 4.0

The 16-bit character-mode debugger (TD.EXE) is supported; however, the 16-bit Windows-based debugger (TDW.EXE) is not supported. Borland Online Books cannot be viewed because they incorporate Adobe Type Manager (ATM) when being viewed. ATM is not supported on NT.

Borland Pascal with Objects 7.0

Turbo Debugger and WinSight are not supported.

Borland Turbo Pascal for Windows

The 16-bit character-mode debugger is supported; however, the 16-bit Windows-based debugger is not supported.

Broderbund KidPix for Windows 1.0

The application may fail when printing to a printer whose port name is greater than 12 characters. To avoid this problem, before you print, use Print Manager to make sure that the name of the printer's destination shown in the Print To box in the Printer Properties dialog box is fewer than 12 characters.

Broderbund Grandma and Me

This application works on Windows NT; however, the installation program does not work in Windows NT. Instead, you must use Program Manager to create an icon to start the program.

cc:Mail

The PATH environment variable cannot exceed 143 characters or a general protection fault will occur in cc:Mail. The path used by Windows NT is created by using the Windows NT path settings and appending the path in the computer's AUTOEXEC.BAT file. Reduce the length of your path and restart the computer.

While installing cc:Mail for Windows, a general protection fault in MSCONSTF.DLL will occur if you do not have a CONFIG.SYS file. Although CONFIG.SYS is required by Windows, it is not required for Windows NT. The cc:Mail setup program looks for CONFIG.SYS and the fault occurs if the file doesn't exist. Shut down Windows NT and create a file named CONFIG.SYS in the root directory of your boot drive. The content of the file is irrelevant.

Using the system mouse pointer during the installation of cc:Mail can lock the keyboard. To work around this problem, you can either hide the mouse pointer or, on x86-based computers only, run the installation program using the full screen. To hide the mouse pointer, follow the instructions in "Using an Application's Own Mouse Cursor" earlier in these Release Notes.

Broderbund Myst

Introductory videos don't play and some movies within the game don't play either. This is a Myst problem that has been fixed by Broderbund. Please contact them for an updated copy.

CA SuperProject

You cannot resize the main window in CA SuperProject for Windows if fulldrag is enabled. Fulldrag can be disabled in Control Panel.

Chessmaster 3000

Because of copy protection on the Chessmaster distribution disks, Windows NT does not support installation of this application.

Commute

Start Commute using a custom PIF and custom startup files. Be sure to clear the Allow Fast Paste check box in the Advanced Options when creating the PIF. For more information, see "Running DOS-Based Remote Control Programs" earlier in these Release Notes.

CompuServe Information Manager (CIM)

The DOS-based version of CIM attempts to access COM1 through COM4 when it starts. If any of these ports is not installed or is already in use, you may see the following error message: "The system cannot open COM port requested by the application." You can safely ignore this message unless your modem is installed on the unavailable port.

Copydoubler (Macintosh application)

When doing a "fast replace" of an existing folder, Copydoubler may incorrectly assume the first directory does not exist and will attempt to recreate it on the server resulting in Error 48 (DuplicateFileName). Other copying errors may occur with the program when used with Windows NT Macintosh-accessible volumes.

Corel Draw 4.0

When choosing Save As from the File menu, the error "Not enough disk space" may appear, because the application is trying to load its own 16-bit driver, which is not supported under Windows NT. To solve this, select None or Only Mono Formats for the Image Header option.

Corel Ventura 4.2

On RISC-based computers, the Ventura Setup2 program will cause a general protection fault beause it accesses beyond the KRNL286 segment limit. To avoid this, use Custom Install and clear the Examples and Design Galleries options. After installation, you can copy files (for example., style sheets) manually.

Eicon Access

For information on running Eicon Access, see "Running Windows Mainframe Connectivity Software" in the Installation Guide.

Extra! for Windows

For information on running Extra!, see "Running Windows Mainframe Connectivity Software" in the Installation Guide

F-19 Stealth Fighter

This application is not supported.

Fastback 6.0 for DOS

If you experience display and/or mouse problems, try to disable the 3-D by changing the Screen Mode to Flat Color and changing Show Mouse to Block.

Filewalk

FILEWALK.EXE (version 1.0A CDRM 566200), included on the Microsoft Multimedia Development Kit CD-ROM, attempts direct disk access and is not supported. A working version (S/B 1.0, CDRM 837500) of this application is available from Microsoft.

Intergraph G91 Display Adapters

The Weitek-compatible display driver included with Windows NT 3.51 does not currently work with Intergraph TD-5 computers that have Intergraph G91 display adapters.

To use Intergraph G91 display adapters with Windows NT 3.51, run the G91 display driver that comes with the Intergraph computer. (Windows NT 3.51 Intergraph G91 drivers work fine on Version 3.51.)

To use Intergraph G91 display adapters with Windows NT 3.51"

1.	During the Windows NT 3.51 Setup process, choose Cancel when the Display Settings dialog box is displayed.

2.	 Once installation has been completed, load the Windows NT 3.51 Intergraph G91 drivers.

Lap-Link V

File transfer between parallel ports and between serial ports is not supported. You can transfer files using modems.

LHX Attack Chopper

Windows NT does not allow applications to directly adjust the computer's timer. In this case, it results in sound that runs slowly.

Lotus 1-2-3 Version 2.4 and greater

Lotus 1-2-3 can be configured to print in either parallel or LPT mode. For optimal printing performance with Windows NT, configure the application in LPT mode.

Lotus Agenda

Start Agenda using the forcedos command. For more information, see the forcedos topic in the Command Reference section of Windows NT Help.

Lotus Notes

Lotus Notes will not run if you are using a NetWare Notes server.

Lotus Notes depend on quick carrier detect notification. The simulated modem interrupt in Windows NT does not always respond fast enough to this notification when it is run at a low priority. A fix is available on CompuServe.

Lotus Notes/FX links are not supported in Word for Windows NT 932-bit. Notes/FX links are supported for Word for Windows 6.0c 16-bit under Windows NT 3.51.

No alert sound is heard when Lotus Notes mail is received. Notes uses undocumented Windows 3.0 calls to produce its mail alert sound. The undocumented calls are not supported under Windows NT 3.51.

Lotus Organizer

Alarm tunes cannot be heard from Lotus Organizer 1.1. Organizer uses undocumented Windows 3.0 calls to produce its alarm tunes. The undocumented calls are not supported under Windows NT 3.51. Organizer 2.0 supports .WAV files in addition to its internal tunes for alarm sounds. The .WAV files will play as expected when an alarm occurs.

Lotus ScreenCam

Lotus ScreenCam is not supported under Windows NT 3.51.

Lotus SmartSuite

When installing Lotus SmartSuite, a dialog may appear warning that the SmartSuite installation program has tried to directly access system hardware, which is not supported by Windows NT. Choose the ignore button and the installation will proceed normally.

Using Lotus Notes over NetBIOS on Multi-Protocol Windows NT Workstation

Lotus Notes clients that use NetBIOS to communicate to the Notes server must be configured correctly to establish communication. The server and client must be configured to use the same network protocol. By default, a Notes client uses the first protocol (for example, NetBIOS LANA number 0). If this does not match the Notes server configuration, you must configure the correct protocol for LANA0 using the Network option in Control Panel. You will configure NetBIOS. You can also change your NOTES.INI file to use the appropriate LANA number. For example, the following configures Notes to communicate over LANA number 1:

LAN1=NETBIOS, 1, 15, 2000

Ports=LAN1

Printing with Lotus AmiPro 3.1

Lotus AmiPro Version 3.1 does not recognize the settings of Print Setup for printing. If a user changes any print attributes, such as Duplex in File, Print Setup will not work. To make settings work, the user must set the default document properties in Print Manager.

To set default document properties:

1.	Start Print Manager.

2.	Select the printer on which you want to set default document properties.

3.	From the Printer menu, select Properties.

4.	Select Details.

5.	Select Job Defaults.

6.	Set the various attributes of the document. To select Advanced Document Properties, select options and select the properties.

7.	Choose OK.

Micrografx Windows Draw 3.0

Version 3.0 (720K) release disks may fail during installation. You cannot copy or cut elements from Micrografx Draw.

Microsoft C 7.00

CodeView for Windows (CVW.EXE) is not supported. To debug 16-bit Windows-based applications, use the Windows NT debugger, WINDBG.EXE. The character-mode version of CodeView is supported.

Microsoft Dinosaurs

Microsoft Dinosaurs does not install the Macromind Multimedia Player (MMP) when installed on a Windows NT computer. You must copy MMCIMMP.DRV and MMP.DLL from the \XFILES\DRIVERS directory on the Microsoft Dinosaurs CD to the \systemroot\SYSTEM directory. After copying the files you must add the following entries to the Registry:

Add the REG_SZ value MMMovie=MCIMMP.DRV to the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows NT\CurrentVersion\MCI

Add the REG_SZ value mmm=MMMOVIE.DRV to the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows NT\CurrentVersion\MCI Extensions

Microsoft Encarta 1994

If you have a RISC-based Windows NT 3.51 computer, you must set up and run Encarta on a hard disk so you can replace two files. Copy ENC94IMG.DLL and POEMWINC.DLL from the \ENCARTA\NT directory on the Encarta CD to the root directory of your Encarta installation (the default is C:\ENCARTA).

Microsoft Encarta 95

Cannot be installed. It gives an error popup when attempting to change the attributes of a font file. This will occur if you are logged on as a normal user and your Windows NT 3.51 is installed on an NTFS-formatted partition. Log off and log back on as an Administrator and rerun the installation.

When installed on a RISC machine (Alpha, MIPS or PowerPC) you get an "Illegal Instruction" popup when you attempt to run it.

Read the release notes that come with Encarta and manually copy the Windows NT 3.51 version of POEMWINC.DLL as instructed in the release note.

Microsoft Excel Version 5.0

Windows NT does not support computer-based tutorial (CBT) files. The Help files use CBT files for the Examples, Demos, and Quick Previews. When viewing sections of Help that use the CBT files, you will receive a popup box saying "You cannot run the CBT with this operating system" or "CBT directory not found." Some database calls to Query may not work on RISC-based computers because they only work on 80386 or above computers.

Viewing Microsoft Excel 5.0 Files on a Compressed NTFS Drive

Windows NT 3.51 allows you to compress your NTFS drives. If you use the File Open dialog box in Microsoft Excel 5.0 for Windows NT to view files on an NTFS compressed drive, your existing files will not be displayed. This might also affect any macro commands designed to open or read files. This situation only occurs in the 32-bit version of Excel 5.0 for Windows NT on the x86 platform. The DEC, Alpha, MIPS, PowerPC, and 16-bit versions of Microsoft Excel are not affected.

Microsoft Excel 5.0 for Windows NT does not have any problems reading from non-compressed NTFS or FAT drives. A fix for this bug will be incorporated into a future release of Microsoft Excel for Windows NT.

There are two ways to view your Microsoft Excel for Windows NT spreadsheet files on a compressed drive:

* From the File Open dialog box in Microsoft Excel for Windows NT, type the name of the file you want to open in the File Name box and then press ENTER.

Or

* In File Manager, double-click on the spreadsheet file you want to open.

Microsoft Entertainment Pack, Idlewild

To use Idlewild screen savers with Windows NT, the full path to the screen savers must be added to the system path. Otherwise, the system will be unable to locate the screen savers and the screen will blank when a screen saver is supposed to start. You can either add the screen savers directory to the path in your AUTOEXEC.BAT file or use the System option in Control Panel to add an environment variable containing the path.

Microsoft Magic School Bus Explores The Solar System

Videos play the audio but no video shows, giving a blank black rectangle on the screen. Start the Control Panel, start Drivers, select [MCI] Microsoft Video for Windows, click on Setup, click on Advanced, click on the "Maximum 16-bit compatibility" checkbox. Restart the application.

Microsoft PowerPoint

The Genigraphics driver included with PowerPoint is not supported.

Microsoft PowerPoint 4 presentations with embedded video clips or midi sequences

The embedded media clips don't play when the slide show is run.

You need to add the following lines to your POWERPNT.INI file, found in the %SystemRoot% directory of your system (typically %SYSTEMROOT%).

Under the [OLE Play Options] section add:

AVIFile=Movie,1,1

MIDFile=Sound,1,2

Microsoft Word for Windows 6.0a

Windows NT does not support computer-based tutorial (CBT) files. The Help files use CBT files for the Examples, Demos, and Quick Previews. When viewing sections of Help that use the CBT files, you will receive a popup box saying "You cannot run the CBT with this operating system" or "CBT directory not found."

Microsoft Word, Version 5.5

When using Word with a foreign language keyboard, start the application using the forcedos command. This enables you to compose accented characters with two keystrokes. For more information, see the forcedos topic in the Command Reference section of Windows NT Help.

Microsoft Works 3.0

Windows NT does not support computer-based tutorial (CBT) files. The Help files use CBT files for the Examples, Demos, and Quick Previews. When viewing sections of Help that use the CBT files, you will receive a popup box saying "You cannot run the CBT with this operating system" or "CBT directory not found."

Multiplan 4.2 for DOS

The MP.PIF file has the Windows 2.11 format which forcedos doesn't support. To fix this problem, open MP.PIF using the Windows NT PIF editor and save it. This will save it in the proper format.

Norton Utilities 6.01

Utilities that directly address system hardware are not supported. This includes, for example, disk caching, virus checking, and error diagnostics utilities.

ORACLEDBMS for DOS

Because Oracle for DOS uses VCPI memory management, the application is not supported. Windows NT clients, however, can access data on Oracle servers.

OzCIS

If OzCIS loses characters when transmitting data, try using a lower baud rate.

PackRat 5.011 for Windows

On RISC-based computers, the PackRat setup program generates illegal instructions when trying to modify the path. Select No when the PackRat setup program asks if you would like to add the PackRat directory to your path. After installation, add the directory to your path manually.

pcANYWHERE III

Start pcANYWHERE using a custom PIF and custom startup files. Be sure to include the dosonly command in the custom configuration file. For more information, see "Running DOS based Remote Control Applications" earlier in these Release Notes.

Procomm 2.0

When setting up Procomm 2.0 for Windows, Setup does not properly add its icon to Program Manager. You can either add the Procomm icon to Program Manager manually or you can start the application from the command prompt.

Quantum Gate

When installing Quantum Gate, when it asks you to select the audio driver for your hardware, do not select the actual driver, but answer Other. Quantum Gate does not use the Windows APIs to access your audio hardware and attempts to address the hardware directly.

Quattro Pro for Windows 1.0

Multiple-copy printing is not supported.

When you choose Redirect To File in the Printer Setup dialog box, the printer output will be redirected to a file in the \systemroot\system32 directory, even if you choose a different directory using the Browse button. The file will overwrite an existing file of the same name without any warning message. Another file with the same name will also be created in the directory you select using the Browse button, or in the Quattro Pro directory by default. This file will not contain any printer information and will have a size of zero bytes.

Quattro Pro 6.0

Some embedded OLE objects may not behave as expected in files opened with Quattro Pro 6.0. Quattro Pro 6.01 has improved an OLE implementation. Contact Novell 1-800-861-2774 for Quattro Pro upgrade information.

Quattro Pro may display printers in its Printer Setup dialog box that are no longer available. A General Protection Fault may occur if you try to print to an unavailable printer. To see if a printer is still available, open Print Manager, select the printer, and look at the status bar at the bottom of the window.

Quicken 4.0

The communications portion of Quicken Version 4.0 will run on Windows NT 3.51 only if it is installed on Intel-based computers. To run Quicken on a 386x platform, follow the specific instructions in the communications portion of Quicken.

The communications portion of Quicken 4.0 does not operate on any other platforms when running Windows NT 3.51, although other parts of Quicken 4.0 will run fine.

Rumba

For information on running Rumba, see "Running Windows Mainframe Connectivity Software" in Chapter 2 of the Installation Guide.

7th Guest

This application will not run under Windows NT.

SimAnt

Maxis SimAnt can fail when the mouse is moved if sound is enabled for the computer's speaker. To prevent this, disable the sound. You can either edit SIMANT.CFG and change the setting for Sound Mode to 0 or install the application and change the setting for Sound Driver to None.

Smartcom Windows Communication Software 1.0A

Use the Smartcom custom utility program to configure Smartcom to use the Windows NT communications driver COMM.DRV.

Software Toolworks Multimedia Encyclopedia

Fullscreen videos don't play; you get neither video nor sound. Do not select the Fullscreen option; allow the videos to play in their normal mode.

SQLWindows 4.0/4.1 for Windows

At the end of installation, always choose Replace Existing Program Group, even on first installation. If you choose to create a new program group, any name used will be considered invalid.

Report templates that are created or modified using Report Windows cannot be saved. The application reports it cannot create temporary files. This problem is fixed in SQLWindows 5.0.

SuperPrint 2.2

The application is not supported because it relies on incompatible 16-bit device drivers.

US Atlas 3.1.0, The Software Toolworks

The application may fail when printing to a printer whose port name contains more than 12 characters. To avoid this problem, before printing, use Print Manager to make sure that the name of the printer's destination shown in the Print To box in the Printer Properties dialog box is fewer than 12 characters.

Ventura Publisher for DOS

On RISC-based computers, the application can fail when attempting to open more than one document or when some mathematical formulas are entered.

Delrina WinFax Pro 2.0

The application is not supported because device drivers are not yet available.

WordPerfect Windows 6.0a

The tutorial is not supported.

26.0 Introducing Windows NT Demonstration Program

The "Introducing Windows NT" online demonstration (\systemroot\system32\INTRO.EXE, with an icon in the Main program group) is the version from Windows NT 3.1. The opening sequence shows an outdated picture of the Windows NT logon screen but the tutorial information is generally accurate.

One important point not covered in the "Creating User Accounts" topic: if a Windows NT workstation is in a domain, you no longer need to create user accounts on the workstation. Instead, you can assign permissions for the workstation using user account names established for the domain.


WinFrame Activation Guide
Citrix WinFrame Version 1.7 Activation Guide

This Activation Guide tells you how to activate your WinFrame Version 1.7 software.

What is WinFrame Activation?

WinFrame Version 1.7 uses an activation key-based licensing system. Every licensed WinFrame product (WinFrame Server software, User Bump Pack, or Add-On Pack) has an associated serial number. When you install the software, you enter the product’s serial number from the product’s Serial Number Sticker and get a license number. You must then obtain an activation key. The activation key is based on the product’s license number and is used by the WinFrame Licensing program to enable the product. This method offers many benefits, including:

Your system is usable immediately.  All you need to do is enter your activation key and your software is enabled.

You can obtain your activation key any time, 24 hours a day, 7 days a week.  The WinFrame Activation Server gives you your activation key immediately — all you need to do is access the WinFrame Activation Server and answer a few simple questions.

You can activate a WinFrame server remotely.  You do not need to be on site to activate your WinFrame software. You can activate your WinFrame software remotely by logging on and entering the activation key, no matter where the server is actually located. All you need is access to an administrator logon account on the WinFrame server.

You can be up and running immediately, and register later.  You have a grace period after you install to activate your software. We recommend that you use the grace period to thoroughly test your hardware and software configuration. After you are sure your system is set up properly, then you can permanently activate your WinFrame software.

Any WinFrame Version 1.7 product that requires a license also requires activation. This includes all versions of the WinFrame server software and all WinFrame Add-On Packs.

You can obtain your WinFrame activation key using one of the following methods:

The WinFrame License Activation Wizard. Just logon as an administrator, double-click on the WinFrame Activation icon in the Administrative Tools program group, and follow the simple instructions. The WinFrame License Activation Wizard uses a TCP/IP Internet connection or a dialout modem to connect to the WinFrame Activation Server. See the Quick Activation Guide for more information about the WinFrame License Activation Wizard.

Over the Internet

By Direct Dial-In

By Fax

By Telephone

Gathering Your Activation Information

Before you obtain an activation key, you need to gather the information needed for the
activation process. Use the Activation Data Form to help you gather the information you
need to supply to activate your WinFrame software. This form is available on-line as the file %systemroot%\SYSTEM32\REGFORM.TXT.

Obtaining Your WinFrame Activation Key Over the Internet

The Internet is a quick and easy way to get your WinFrame activation key. You can access the WinFrame Activation Server over the Web in one of two ways:

If your WinFrame server is connected to the Web through a TCP/IP connection, you can use the WinFrame License Activation Wizard. Just logon using the administrator account you configured during Setup, start WinFrame Activation, and select the Activate Over The Internet option. Follow the displayed instructions. See the Quick Activation Guide for more information about the WinFrame License Activation Wizard.

If your WinFrame server is not connected to the Web, you can use any computer running an ICA-enabled Web browser to connect to the WinFrame License Activation Server using the Internet Activation URL listed on your Support Services card. Follow the displayed instructions. See Chapter 24, “WinFrame Web Computing” in the System Guide for information on configuring an ICA-enabled Web browser.

Obtaining Your WinFrame Activation Key by Direct Dial-In

If you do not have an Internet connection but have access to a modem, you can access the WinFrame Activation Server by direct dial-in in one of two ways:

If your WinFrame server has a dialout modem configured, you can use the WinFrame License Activation Wizard. Just logon using the administrator account you configured during Setup, start WinFrame Activation, and select the Activate By Modem option. Follow the displayed instructions. See the Quick Activation Guide for more information about the WinFrame Activation Wizard.

If your WinFrame server does not have a modem configured, you can use any computer running the WinFrame Client that has a modem attached to access the WinFrame Activation Server. Just install the WinFrame DOS, Win16, or Win32 client and create a serial connection entry to dial the WinFrame Activation Server. The Direct Dial-In Activation number is listed on your  Support Services card. Dial in to the WinFrame Activation Server and follow the displayed instructions.

Obtaining Your WinFrame Activation Key by Fax

If you cannot access the WinFrame Activation Server over the Web or by Direct Dial-In and you cannot obtain your WinFrame activation key by email, you can register by fax. To register by fax, send your completed Activation Data Form to the Activation Fax telephone number listed on your  Support Services card. Be sure to include the email address or fax number of someone to receive the activation key. You should get a response within three working days.

Obtaining Your WinFrame Activation Key by Telephone

If you absolutely cannot obtain your WinFrame activation key by any other method, you can obtain your WinFrame activation key by telephone. To obtain your WinFrame activation key by telephone, call the Telephone Activation number listed on your Support Services card to request an activation code and leave your company name, your name, and your telephone number. You should get a reply within five working days.

Entering Your Activation Key

To apply an activation key to a WinFrame License

1.	Logon as an administrator. On the WinFrame desktop, double-click on WinFrame Licensing in the Administrative Tools program group. The WinFrame Licensing dialog appears, displaying the licenses installed on your WinFrame server.

2.	Select the WinFrame License you are activating from the list of displayed licenses, and then click on the Activate button on the toolbar or select Activate License from the License pull-down menu. The Activate License dialog appears.

3.	Enter your activation key and click OK.

4.	Exit WinFrame Licensing.

Troubleshooting

Here are some common problems encountered when activating WinFrame software and their solutions.

I’m trying to access the WinFrame Activation Server over the Web but I can’t get through our company’s firewall.

Your firewall may be filtering out Citrix ICA data packets. Contact your network administrator.

When I try to access the WinFrame Activation Server over the Web or try to use a Web browser, I get an error message stating that TCP/IP is not installed.

You must install TCP/IP support to access the WinFrame Activation Server over the Web.


Quick Activation Guide
Citrix WinFrame Quick Activation Guide

Follow these quick and easy steps to install and activate your WinFrame software. For more information, see the Citrix WinFrame Version 1.7 Activation Guide and Chapter 22, “WinFrame Licensing,” of the System Guide.

1.	Find your WinFrame Serial Number Sticker. This sticker contains the serial number for your WinFrame software, and is on the back of the CD-ROM case included in your WinFrame package.

2.	Install your WinFrame software or your Add-On or Bump Pack.  Follow the directions in the Quick Installation Guide if you are installing WinFrame server software, or the directions in the Release Notes if you are installing a WinFrame Add-On or Bump Pack. Enter the serial number exactly as it appears on the serial number sticker when you are prompted to during WinFrame Setup.

3.	Logon as an administrator. On the WinFrame desktop, double-click on WinFrame Licensing in the Administrative Tools program group. WinFrame Licensing displays all of your installed licenses and their license numbers. You must use the license number displayed by WinFrame Licensing when activating your software in Step 10 below.

4.	The next step in the installation process is to activate your software by contacting the WinFrame Activation Server. This is done by the WinFrame License Activation Wizard.

5.	The WinFrame License Activation Wizard can connect to the WinFrame Activation Server using either a TCP/IP Internet connection or a modem connection. If you will use a TCP/IP Internet connection, you must install TCP/IP on your server and have Internet access. If you will use a modem connection, you must have a modem attached and properly configured for dial out.

6.	To use the WinFrame License Activation Wizard to contact the WinFrame Activation Server, logon as an administrator. Double-click on the WinFrame Activation icon in the Administrative Tools program group. The WinFrame License Activation Wizard dialog appears.

7.	Select Activate Over The Internet or Activate By Modem and click Next.

8.	If the WinFrame Win32 Client is not installed, you are prompted to install the client. Follow the simple instructions that appear to install the WinFrame Win32 Client. After installing the client, select Activate Over The Internet or Activate By Modem again and click Next.

9.	Click Finish to connect to the WinFrame Activation Server. When the WinFrame Activation System screen appears, follow the simple directions. Record your activation code exactly as it appears and exit. Depending on the licenses, you may be able to obtain activation codes for more than one license at a time.

10.	To activate your WinFrame software, start WinFrame Licensing or click on the WinFrame Licensing window if it is already started. Select the WinFrame license you are activating from the list of displayed licenses, and then click on the Activate button on the toolbar or select Activate License from the License pull-down menu. The Activate License dialog appears. Enter your activation code from Step 9 above and click OK. Your WinFrame software is now activated.


Citrix Winframe Version 1.7 Activation Data Form

Use this form to record the information you need to activate your WinFrame Version 1.7 software.  See the WinFrame Version 1.7 Activation Guide and the WinFrame Version 1.7 Quick Activation Guide supplied with your WinFrame software for more information.

REGISTRANT INFORMATION

Company: __________________________________________________________________

Address 1: ________________________________________________________________

Address 2: ________________________________________________________________

City: ________________________  State/Province: __________________

Postal Code: _________________  Country:  ________________________

Telephone: ___________________  Fax: _____________________________

Internet URL: ___________________________

Contact Name (First/Last): _______________________________________

Contact Title: ________________________ Contact Email or Fax: _____________

Reseller Name: ____________________________________________________________

Reseller City: ________________________ Reseller State/Province: __________

Serial Numbers of the Products to be Registered:

Serial Number 1: _____________________________________________

Serial Number 2: _____________________________________________

Serial Number 3: _____________________________________________

APPLICATION/USAGE INFORMATION

What is your company's primary business?

__ Consulting  __ Education/Research  __ Banking/Finance

__ Government  __ Manufacturing       __ Retail/Distribution

__ Other:______________________________________

How many employees at this site?

__ Under 100       __ 100-1,000     __ 1,000-10,000

__ 10,000-100,000  __ Over 100,000

How many employees in your company?

__ Under 100       __ 100-1,000     __ 1,000-10,000

__ 10,000-100,000  __ Over 100,000

What types of connections will you be using? (Check all that apply)

__ Analog modem  __ Internet (Public)  __ Intranet (private)

__ ISDN  __ LAN  __ Remote Node (RAS/Third Party)

__ WAN   __ X.25

What interests you most about WinFrame? (Check all that apply)

__ Deploying existing applications without having to modify

__ Centralized control and management of applications

__ Easy deployment of applications to users

__ Providing access to mobile users and telecommuters

__ Running Windows applications on older PCs without expensive upgrades

__ Increased application performance

__ Providing application access for branch offices and remote locations

__ Publishing applications over the Internet or an Intranet

__ Running Windows applications on UNIX or Macintosh systems

SERVER INFORMATION

Server Base License: ________________________________________

Additional Licenses: ________________________________________

Processor:

__ Pentium  __ 133MHz  __ 150 MHz  __ 166 MHz  __ 180 MHz

__ Pentium Pro  __ 180MHz  __ 200MHz

__ Other: ______________________________________________

Number of Processors:

__ One  __ Two  __ Four  __ Eight  __ Sixteen

__ Other: __________

Memory:

__ 32MB or less  __ 64MB  __ 128MB  __ 256MB

__ 512MB  __ 1GB  __ Over 1GB: ___________

Manufacturer:

__ Compaq    __ Digital  __ Dell  __ Hewlett-Packard  __ IBM

__ NetFrame  __ Other: ______________________________


Citrix WinFrame/Enterprise Version 1.7 Release Notes

Before you install WinFrame, please read these Release Notes for information about the materials in this package.

Service and Support

For information on obtaining service and support for WinFrame, please read the Support Services Card included in this package. You can also obtain a wealth of technical information from the Citrix On-line Technical Support Services at http://support.citrix.com

Hardware Compatibility Information and System Guidelines

For information on hardware compatibility and guidelines for configuring your WinFrame server, see the Microsoft Windows NT 3.51 Hardware Compatibility List. The Hardware Compatibility List contains information about systems, adapters, and other peripherals compatible with Microsoft Windows NT 3.51 and Citrix WinFrame Version 1.7. The Hardware Compatibility List can be found online in the Main program group.

WinFrame Licensing and Activation

WinFrame Version 1.7 uses an activation key-based licensing system. Every licensed WinFrame Version 1.7 product (WinFrame server software or Add-On Pack) has an associated serial number. When you install the software, you enter the product's serial number. You must then contact Citrix to obtain an activation key. The activation key is based on the product's serial number and is used by the WinFrame Licensing program to enable the product. The WinFrame/Enterprise Version 1.7 Serial Number Sticker attached to the CD-ROM case contains the software license serial number for your copy of WinFrame/Enterprise.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

WinFrame Hotfixes and Service Packs

WinFrame Hotfixes are patches to the WinFrame operating system. Hotfixes are tested and verified to fix specific problems, and should only be applied on the advice of Citrix Technical Support. WinFrame Service Packs are collections of patches released between major revisions of the WinFrame operating system. Service packs are cumulative; that is, they contain all patches included in prior service packs.

WinFrame Hotfixes and Service Packs can be downloaded from the Citrix Web site (support.citrix.com) or the corporate BBS at (954) 267-2590, or obtained from your reseller.

SETUP.TXT, Quick Install Guide, and WinFrame Help

The SETUP.TXT file is available in the \I386 directory of the WinFrame/Enterprise CD-ROM. It contains additional information from Microsoft regarding Windows NT 3.51, also applicable to WinFrame, that you may need prior to installing WinFrame on some hardware configurations.

The WinFrame Quick Install Guide contains information on system hardware requirements and a condensed version of the steps you need to follow for a quick and easy WinFrame installation. Use this manual and the Installation Guide to install WinFrame on your computer.

After installing WinFrame, please read the WinFrame online Help by double-clicking the WinFrame Help icon in the Main program group. The WinFrame online Help (also referred to as the WinFrame Readme) contains hardware- and software-specific information and descriptions of product features that were added or changed after the documentation was printed.

WinFrame Books Online

WinFrame Books Online contains the complete set of WinFrame manuals (except for the Quick Install Guide) in a convenient help file format. You can access Books Online from the WinFrame CD-ROM, or copy the files from the \SUPPORT\BOOKS directory on the WinFrame CD-ROM to a \SUPPORT\BOOKS directory on your hard drive to free up your CD-ROM drive. The complete WinFrame manual set is not shipped with WinFrame. To order a complete WinFrame documentation set, call Citrix Sales at (800) 437-7503.

New Features in This Release

Integrated WinFrame Setup Procedure. You can install the NetWare Gateway, multiport serial adapters, and Remote Access Service during Setup. Setup automatically configures two WinStations for each network protocol you install (IPX, TCP/IP, and NetBIOS).

Sync-up With Windows NT 3.51 Service Pack 5. WinFrame is totally compatible with the latest release of Windows NT Version 3.51 and all released service packs up to Service Pack 5.

Activation Key-Based Licensing.  WinFrame Version 1.7 uses a serial number/activation key licensing scheme.  Every licensed WinFrame product (WinFrame server software or Add-On Pack) has an associated serial number.  When you install the software, you enter the product's serial number.  You must then register the serial number with Citrix to obtain an  activation key.  The activation key can then be applied to the serial number by using the WinFrame Licensing utility.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

License Pooling.  License pooling allows the licenses installed on a WinFrame server to be used on any WinFrame server in a server farm.  It does not matter how many licenses are in use on any particular machine or to which machine a user is connected. For example, if there are three WinFrame servers in a server farm, each with a base user license count of 15, and a 10-user Add-On Pack has been installed on one of the servers, the three servers in the farm can support up to 55 (15+15+15+10) concurrent users in any combination. Use WinFrame Licensing to control the number of licenses that are pooled on a WinFrame server. See Chapter 22, "WinFrame Licensing," of the System Guide for information on using WinFrame Licensing.

Application Publishing Support.  WinFrame Version 1.7 supports application publishing. A published application contains all of the information needed to launch an application on a WinFrame server and can be used with WinFrame load balancing support.  See Chapter 23, "Application Publishing" of the System Guide for information on how to use the Application Configuration utility to publish applications.

Windows NT Multi-Protocol Routing Service (MPR) Included.  WinFrame Version 1.7 includes the Windows NT Multi-Protocol Routing Service (MPR) in the \MPR directory. Multi-Protocol Routing allows a WinFrame server to act as a low cost LAN-to-LAN routing solution for TCP/IP and IPX networks. MPR can also be used to link LANs that have different network topologies, such as Ethernet and Token-Ring. Run the UPDATE.EXE program in the \MPR directory of the WinFrame CD-ROM to install the Windows NT Multi-Protocol Routing Service. See the Solutions Guide for more information on installing and using the MPR Service.

Load Balancing Support. WinFrame 1.7 supports load balancing. With load balancing, several WinFrame servers can be logically pooled in a server farm. When a user launches a published application that is configured for load balancing, the WinFrame load balancing support routes the application to the most lightly loaded server in the farm for execution. You can create a farm of several servers that run predefined applications and fine-tune the load determination criteria on each server. Each WinFrame server that will support load balancing must have a copy of the WinFrame 1.7 Load Balancing Option Pack installed. See Chapter 23, "Application Publishing" of the System Guide for information on configuring applications for use with a server farm.

Web Computing Support.  WinFrame Version 1.7 supports Web computing features that let you publish applications on your corporate Intranet or the Internet. The WinFrame Internet Client can be used with Microsoft Internet Explorer and Netscape Navigator to support Application Launching and Embedding (ALE), allowing users to run Windows applications within Web pages. Firewall support lets you interpose firewalls between your WinFrame server and the Internet for increased security. See Chapter 24, "WinFrame Web Computing" of the System Guide for information on how to use the Application Configuration utility to publish applications.

Enhanced Security Features.  WinFrame Version 1.7 supports enhanced security utilities and procedures that help you protect your system from unauthorized access. See the  Security Guide for more information.

New WinStation Administration Utility.  WinStation Administration has been significantly updated.  WinStation Administration can now be used to maintain and display information about every WinFrame server, WinStation, and WinFrame user on a network.  See Chapter 21, "WinStation Administration," in the System Guide for more information.

WinFrame Client Creator.  The WinFrame Clients are now shipped on the WinFrame CD-ROM.  The WinFrame Client Creator can be used to create diskettes containing the WinFrame Clients (DOS, Win16, Win32, and Web).  See Chapter 10, "WinFrame Client Creator," in the Installation Guide for more information.

Client Printer and Disk Drive Mapping.  WinFrame users who access the server with the WinFrame client can transparently access their local printers and disk drives (fixed and removable).  The drive letters used for drive mapping are configurable and long filenames are supported.

Password Synchronization With NetWare File Servers. Passwords can be optionally synchronized between a NetWare 3.x server and the WinFrame server. The password on the WinFrame server tracks the password on the Novell server. When the password on the Novell server changes, the WinFrame password also changes. Use the User Manager for Domains to manage what users have NetWare password synchronization. Password synchronization with NetWare 4.x servers running Bindery Emulation is supported; however, password synchronization with NetWare 4.x NDS servers is not supported at this time.

Novell NetWare 4.x NDS Support. NetWare 4.x Network Directory Services (NDS) are supported. You can use File Manager and Print Manager to access NDS trees on NetWare 4.x servers, net use NDS names, and use NDS features in NetWare login scripts.

NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme "Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection" in WinFrame Help for detailed information.

Dial-In Setup Wizard With Automatic Modem Detection. WinFrame's Dial-In Setup Wizard makes configuring Dial-In WinStations quick and easy. Automatic modem detection determines the type of modem connected to the WinFrame server and configures it for optimum throughput.

Configurable TCP/IP Port Setting for ICA Protocol.  This feature lets you configure Citrix ICA packets to be compatible with many popular TCP/IP firewall products.

User Information Stored in the Security Account Manager (SAM) Database.  For added reliability, user information is now stored in the Security Account Manager (SAM) database instead of the registry of the primary domain controller (PDC).  The SAM database is automatically propagated from the PDC to all backup domain controllers (BDCs), which ensures that user information is available as long as the PDC or any BDC is available.  The CNVRTUC utility included with WinFrame 1.7 can be used to convert registry-based user information into SAM-based user information.

The Citrix WinFrame Clients (DOS, Win16, Win32, and Web Versions).  Version 1.7 of the WinFrame Clients includes the following features:

Dial-In support lets you dial in to your WinFrame server from DOS, Windows 3.1, Windows for Workgroups, Windows 95, and Windows NT client PCs and start a remote control session.

TCP/IP, NetBIOS, IPX, and SPX network protocol support let you access your WinFrame server over a LAN, WAN, or RAS connection and start a remote control session.

The Remote Application Wizard makes creating remote application entries quick and easy. Automatic modem detection is supported for creating Dial-In remote applications.

You can create a remote application entry to connect to a WinFrame server or to a published application that contains all of the information necessary to launch a user session or an application. All the end-user needs to do is double-click on the application entry's icon on the desktop.

Disk caching and data compression can be used to increase performance over low-speed Dial-In and WAN connections.  Disk caching stores commonly-used portions of your screen (such as icons and bitmaps) locally, increasing performance by avoiding retransmission of locally cached data.  Data compression reduces the amount of data sent over the communications link to the client PC.

The Remote Application Wizard lets you specify disk caching and data compression when creating a remote application. The Connection Options tab on the Properties menu for a remote application lets you change disk caching and data compression settings for a remote application.  The Disk Cache tab on the Settings menu lets you specify the path to the local disk cache and the amount of disk cache to allocate.

The ICA Browser provides a method for a user at a network-connected WinFrame Client PC to view a list of all WinFrame servers and published applications on the network with WinStations configured for that network type (IPX, TCP/IP, or NetBIOS). The WinFrame Clients supplied with this release use the ICA Browser to locate WinFrame servers and published applications on a network.

The ability to cut and paste data between the client and the WinFrame session using the Windows clipboard (Windows clients only).

The WinFrame Client for DOS supports COM port mapping. COM port mapping is similar to printer and drive mapping, and allows the WinFrame server to utilize a COM port on the client PC as if it were a COM port on the WinFrame server. COM port mapping is not currently supported by the WinFrame Windows clients. Use the net use command to map a COM port; for example, the command net use com2: \\client\com1 maps COM2 on the WinFrame server to the COM1 port of the WinFrame client PC.

Client printers are configured automatically (Windows clients only). Any printers detected when you connect to a WinFrame server are automatically added to the Print Manager. Client printers can be browsed and connected to in the same way as network printers.

Additional Notes

Installing WinFrame 1.7 on an NTFS Partition Formatted Using Windows NT 4.0

The NTFS file system driver shipped with Windows NT 4.0 renders the disk partition incompatible with prior versions of Windows NT and WinFrame. This problem is fixed in Windows NT 4.0 Service Pack 2. If the WinFrame 1.7 install partition was formatted using a version of Windows NT 4.0 prior to Service Pack 2, WinFrame Setup may fail. Other partitions used by WinFrame 1.7 (and Windows NT 3.51) may become corrupt if the partitions were also formatted with Windows NT 4.0 prior to Service Pack 2. Installing Windows NT 4.0 Service Pack 2 does not automatically correct the problem.

To correct this problem, the partitions must be deleted, recreated, and formatted with WinFrame 1.x, Windows NT 3.51, or Windows NT 4.0 with Service Pack 2 or greater before installing WinFrame 1.7.

Installing Applications on a WinFrame Server

See the Readme "General Installation of Applications on WinFrame" in WinFrame Help before you install any applications on your WinFrame server. This Readme contains important information about setting up applications in the WinFrame multiuser environment.

Incompatibilities Among WinFrame Servers Running Different Versions of WinFrame

You cannot mix WinFrame Version 1.6 and WinFrame Version 1.7 servers in a load balancing group. All servers in a load balancing group must be running the same version of WinFrame.

Licenses cannot be pooled among servers running different versions of WinFrame.

The WinFrame Version 1.7 Beta Release is not compatible with WinFrame Version 1.7 for load balancing, WinStation Administration server viewing, published applications, or license pooling.

Frequently Asked Questions About WinFrame

The following is a list of the most frequently asked questions about WinFrame.

Integration - Network

What NDS functions are supported under WinFrame?

The following NDS features are supported:

1.	NDS volumes may be accessed by both the command line interface and the File Manager.

2.	NDS printer queues may be accessed by both the command line interface and the Print Manager.

3.	NDS naming is supported, including typed and typeless names.

4.	A default NDS tree and context may be specified. The user is automatically logged into the NDS tree using the WinFrame  username and default context. NDS login scripts are supported.

NOTE: NDS usernames are not supported.

Can I remap WinFrame drive letters so that my clients can transparently access their local drive C?

Yes. You can use the Disk Administrator utility to do this. This is covered in detail in Chapter 1 of the WinFrame Installation Guide.

How do I create/configure user profiles for WinFrame ?

See Chapter 14 of the System Guide for information and instructions on how to create and use user profiles. Chapter 5 of the Concepts and Planning Guide describes how these profiles work in an NT environment.

How do I set up a default user profile?

Setting up a default user profile is covered in Chapter 14 of the WinFrame System Guide.

Why don't NWADMIN and NETADMIN run on WinFrame?

NetWare 4.x command line utilities do not run on WinFrame in an NDS environment; for example, capture and map. Any application that makes use of the NDS API will not work.

Integration - Application

My application is causing an error on WinFrame.

1.	Make sure your application is compatible with Windows NT 3.51.

2.	You must execute change user /install to install Windows 16-bit and 32-bit applications.

3.	Turn on file and registry auditing to determine what files or registry keys are being accessed.

Async

My modem is not on the list of supported modems for WinFrame. How do I make it work?

I am having trouble connecting with my US Robotics Sportster 28.8.

The MODEM.INF file lists all modems supported, along with the command and response strings each modem needs for correct operation. When you select a modem during installation, the Setup program associates the selected modem with the specified communication port. You can find MODEM.INF in the \systemroot\SYSTEM32\RAS directory.

If your modem is not listed in MODEM.INF, download the latest MODEM.INF file from the modem manufacturer's BBS or FTP server.

My system cannot locate any of my COM ports after installing a DigiBoard multiport adapter. What should I do next?

1.	Use the Terminal application or WinStation Configuration in WinFrame to establish whether or not the system can locate the ports.

2.	Check the event viewer to see if the DigiBoard initialized.

3.	If it did not, contact DigiBoard to download the latest NT DigiBoard drivers.

Why do I receive a "connection refused" error when trying to connect to a WinFrame server?

You must have a WinStation configured or available for the transport protocol being used by the client.

WinFrame Client

My DOS application will not display in full screen.

At this time, only the DOS WinFrame client will allow a remote full screen session to be displayed as a true DOS video full screen session.

Because the remote Application Manager is a Windows application, it conforms to the Windows video APIs and, therefore, continues to run as a Windows application when displaying remote DOS full screen sessions. Because the session is displayed as Windows video and not true DOS video, the column and row settings for the remote DOS session are translated into pixel coordinates on the local machine. Change the column and row settings for the remote DOS session to change the appearance of the locally displayed session.

How do I minimize my WinFrame session when using the Windows 16-bit and 32-bit clients?

Press SHIFT+F2. This will give you a task bar at the top of the screen that you can use to minimize the session.

Restrictions

Novell NetWare 4.x NDS Support. NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme "Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection" in WinFrame Help for detailed information. NDS drive map objects are not supported; use direct drive assignments to a volume and directory path instead.

Password Synchronization With NetWare 4.x NDS File Servers. Password synchronization with NetWare 4.x NDS servers is not supported at this time; however, password synchronization with NetWare 4.x servers running Bindery Emulation is supported.

Modem Installation Wizard. Automatic modem detection using the modem wizard in WinStation Configuration is not enabled during WinFrame installation because the required device drivers are not loaded by Setup. If you want to use the modem installation wizard to automatically detect the modems connected to your WinFrame server, reboot after completing your WinFrame installation and double-click on the Dial-In Setup Wizard in the Administrative Tools group. All other features of WinStation Configuration are available during installation.

Server Browser Incompatibility With WinFrame Version 1.5 Servers. WinFrame Version 1.5 servers are not visible in the application server pull-down list when configuring application server entries on systems using the WinFrame Version 1.7 Client.

WinFrame/Enterprise Features Overview

Citrix WinFrame is the first application publishing platform to extend the reach of corporate applications to users outside the LAN, including mobile professionals, telecommuters, branch office workers, customers, prospects, and vendors. Based on Microsoft Windows NT Server 3.51 under license from Microsoft, WinFrame/Enterprise is the only tool you need to publish corporate applications across the Intranet and Internet while retaining local speed, control, and ease of use.

WinFrame/Enterprise Product Highlights

High Performance. With Citrix Independent Computing Architecture (ICA™) 3.0, applications run at full LAN speed from anywhere. Applications run on the WinFrame server while the user interface is executed by ICA 3.0 on the client PC.

Local/Remote Transparency. Easy to use, all-purpose remote connectivity over a single remote connection eliminates the user dilemma of having to choose between remote node or remote control for running various applications.

Enterprise Scalability. Easily build manageable TeleComputing connectivity for thousands of remote and mobile users. WinFrame/Enterprise can accommodate up to 60 concurrent users on a single four-processor SMP Pentium server, depending on the application mix.

Extensive Connectivity. WinFrame/Enterprise connects users to the network through standard telephone lines, ISDN lines, wide area network links, broadband connections, or the Internet.

Stringent Security. To protect sensitive data, WinFrame/Enterprise incorporates multilevel system security and fully complies with DOD C2-level certification.

Flexible Management and Administration. Server-based system administration makes configuration, problem identification, and problem resolution quick and efficient. WinFrame/Enterprise includes an extensive set of end-to-end Windows management tools that allow WinFrame servers and remote users to be configured, administered, monitored, and supported from anywhere.

Enterprise Interoperability. WinFrame/Enterprise easily integrates into your existing enterprise networks, including Novell NetWare 3.x and 4.x; Microsoft Windows NT, LAN Manager and Windows for Workgroups; LAN Server; SNA gateways; and UNIX networking environments.

Runs Server-Based Applications. WinFrame/Enterprise runs Windows NT server applications such as Microsoft BackOffice, allowing clients and server programs to be consolidated on a single server for performance gains and ease of system management.

Broad Application Support. WinFrame/Enterprise executes most Windows NT, Windows 95, Windows 3.1, DOS text, OS/2 text, and POSIX applications, including popular personal productivity, workgroup, client/server, and legacy programs.

Remote Node Compatibility. WinFrame/Enterprise can be used in conjunction with most popular third-party remote node hardware and software to significantly boost the performance of LAN-resident applications.

For more information on installing and configuring your system, see the Quick Install Guide, the Installation Guide, and the WinFrame Client User's Guide.


Citrix WinFrame Host/Terminal Version 1.7 Release Notes

Before you install WinFrame, please read these Release Notes for information about the materials in this package.

Service and Support

For information on obtaining service and support for WinFrame, please read the Support Services Card included in this package. You can also obtain a wealth of technical information from the Citrix On-line Technical Support Services at http://support.citrix.com

Hardware Compatibility Information and System Guidelines

For information on hardware compatibility and guidelines for configuring your WinFrame server, see the Microsoft Windows NT 3.51 Hardware Compatibility List. The Hardware Compatibility List contains information about systems, adapters, and other peripherals compatible with Microsoft Windows NT 3.51 and Citrix WinFrame Version 1.7. The Hardware Compatibility List can be found online in the Main program group.

WinFrame Licensing and Activation

WinFrame Version 1.7 uses an activation key-based licensing system. Every licensed WinFrame Version 1.7 product (WinFrame server software or Add-On Pack) has an associated serial number. When you install the software, you enter the product's serial number. You must then contact Citrix to obtain an activation key. The activation key is based on the product's serial number and is used by the WinFrame Licensing program to enable the product. The WinFrame Host/Terminal Version 1.7 Serial Number Sticker attached to the CD-ROM case contains the software license serial number for your copy of WinFrame Host/Terminal.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

WinFrame Hotfixes and Service Packs

WinFrame Hotfixes are patches to the WinFrame operating system. Hotfixes are tested and verified to fix specific problems, and should only be applied on the advice of Citrix Technical Support. WinFrame Service Packs are collections of patches released between major revisions of the WinFrame operating system. Service packs are cumulative; that is, they contain all patches included in prior service packs.

WinFrame Hotfixes and Service Packs can be downloaded from the Citrix Web site (support.citrix.com) or the corporate BBS at (954) 267-2590, or obtained from your reseller.

SETUP.TXT, Quick Install Guide, and WinFrame Help

The SETUP.TXT file is available in the \I386 directory of the WinFrame Host/Terminal CD-ROM. It contains additional information from Microsoft regarding Windows NT 3.51, also applicable to WinFrame, that you may need prior to installing WinFrame on some hardware configurations.

The WinFrame Quick Install Guide contains information on system hardware requirements and a condensed version of the steps you need to follow for a quick and easy WinFrame installation. Use this manual and the Installation Guide to install WinFrame on your computer.

After installing WinFrame, please read the WinFrame online Help by double-clicking the WinFrame Help icon in the Main program group. The WinFrame online Help (also referred to as the WinFrame Readme) contains hardware- and software-specific information and descriptions of product features that were added or changed after the documentation was printed.

WinFrame Books Online

WinFrame Books Online contains the complete set of WinFrame manuals (except for the Quick Install Guide) in a convenient help file format. You can access Books Online from the WinFrame CD-ROM, or copy the files from the \SUPPORT\BOOKS directory on the WinFrame CD-ROM to a \SUPPORT\BOOKS directory on your hard drive to free up your CD-ROM drive. The complete WinFrame manual set is not shipped with WinFrame. To order a complete WinFrame documentation set, call Citrix Sales at (800) 437-7503.

New Features in This Release

Integrated WinFrame Setup Procedure. You can install the NetWare Gateway, multiport serial adapters, and Remote Access Service during Setup. Setup automatically configures two WinStations for each network protocol you install (IPX, TCP/IP, and NetBIOS).

Sync-up With Windows NT 3.51 Service Pack 5. WinFrame is totally compatible with the latest release of Windows NT Version 3.51 and all released service packs up to Service Pack 5.

Activation Key-Based Licensing.  WinFrame Version 1.7 uses a serial number/activation key licensing scheme.  Every licensed WinFrame product (WinFrame server software or Add-On Pack) has an associated serial number.  When you install the software, you enter the product's serial number.  You must then register the serial number with Citrix to obtain an  activation key.  The activation key can then be applied to the serial number by using the WinFrame Licensing utility.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

License Pooling.  License pooling allows the licenses installed on a WinFrame server to be used on any WinFrame server in a server farm.  It does not matter how many licenses are in use on any particular machine or to which machine a user is connected. For example, if there are three WinFrame servers in a server farm, each with a base user license count of 15, and a 10-user Add-On Pack has been installed on one of the servers, the three servers in the farm can support up to 55 (15+15+15+10) concurrent users in any combination. Use WinFrame Licensing to control the number of licenses that are pooled on a WinFrame server. See Chapter 22, "WinFrame Licensing," of the System Guide for information on using WinFrame Licensing.

Application Publishing Support.  WinFrame Version 1.7 supports application publishing. A published application contains all of the information needed to launch an application on a WinFrame server and can be used with WinFrame load balancing support.  See Chapter 23, "Application Publishing" of the System Guide for information on how to use the Application Configuration utility to publish applications.

Windows NT Multi-Protocol Routing Service (MPR) Included.  WinFrame Version 1.7 includes the Windows NT Multi-Protocol Routing Service (MPR) in the \MPR directory. Multi-Protocol Routing allows a WinFrame server to act as a low cost LAN-to-LAN routing solution for TCP/IP and IPX networks. MPR can also be used to link LANs that have different network topologies, such as Ethernet and Token-Ring. Run the UPDATE.EXE program in the \MPR directory of the WinFrame CD-ROM to install the Windows NT Multi-Protocol Routing Service. See the Solutions Guide for more information on installing and using the MPR Service.

Load Balancing Support. WinFrame 1.7 supports load balancing. With load balancing, several WinFrame servers can be logically pooled in a server farm. When a user launches a published application that is configured for load balancing, the WinFrame load balancing support routes the application to the most lightly loaded server in the farm for execution. You can create a farm of several servers that run predefined applications and fine-tune the load determination criteria on each server. Each WinFrame server that will support load balancing must have a copy of the WinFrame 1.7 Load Balancing Option Pack installed. See Chapter 23, "Application Publishing" of the System Guide for information on configuring applications for use with a server farm.

Web Computing Support.  WinFrame Version 1.7 supports Web computing features that let you publish applications on your corporate Intranet or the Internet. The WinFrame Internet Client can be used with Microsoft Internet Explorer and Netscape Navigator to support Application Launching and Embedding (ALE), allowing users to run Windows applications within Web pages. Firewall support lets you interpose firewalls between your WinFrame server and the Internet for increased security. See Chapter 24, "WinFrame Web Computing" of the System Guide for information on how to use the Application Configuration utility to publish applications.

Enhanced Security Features.  WinFrame Version 1.7 supports enhanced security utilities and procedures that help you protect your system from unauthorized access. See the  Security Guide for more information.

New WinStation Administration Utility.  WinStation Administration has been significantly updated.  WinStation Administration can now be used to maintain and display information about every WinFrame server, WinStation, and WinFrame user on a network.  See Chapter 21, "WinStation Administration," in the System Guide for more information.

WinFrame Client Creator.  The WinFrame Clients are now shipped on the WinFrame CD-ROM.  The WinFrame Client Creator can be used to create diskettes containing the WinFrame Clients (DOS, Win16, Win32, and Web).  See Chapter 10, "WinFrame Client Creator," in the Installation Guide for more information.

Client Printer and Disk Drive Mapping.  WinFrame users who access the server with the WinFrame client can transparently access their local printers and disk drives (fixed and removable).  The drive letters used for drive mapping are configurable and long filenames are supported.

Password Synchronization With NetWare File Servers. Passwords can be optionally synchronized between a NetWare 3.x server and the WinFrame server. The password on the WinFrame server tracks the password on the Novell server. When the password on the Novell server changes, the WinFrame password also changes. Use the User Manager for Domains to manage what users have NetWare password synchronization. Password synchronization with NetWare 4.x servers running Bindery Emulation is supported; however, password synchronization with NetWare 4.x NDS servers is not supported at this time.

Novell NetWare 4.x NDS Support. NetWare 4.x Network Directory Services (NDS) are supported. You can use File Manager and Print Manager to access NDS trees on NetWare 4.x servers, net use NDS names, and use NDS features in NetWare login scripts.

NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme "Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection" in WinFrame Help for detailed information.

Dial-In Setup Wizard With Automatic Modem Detection. WinFrame's Dial-In Setup Wizard makes configuring Dial-In WinStations quick and easy. Automatic modem detection determines the type of modem connected to the WinFrame server and configures it for optimum throughput.

Configurable TCP/IP Port Setting for ICA Protocol.  This feature lets you configure Citrix ICA packets to be compatible with many popular TCP/IP firewall products.

User Information Stored in the Security Account Manager (SAM) Database.  For added reliability, user information is now stored in the Security Account Manager (SAM) database instead of the registry of the primary domain controller (PDC).  The SAM database is automatically propagated from the PDC to all backup domain controllers (BDCs), which ensures that user information is available as long as the PDC or any BDC is available.  The CNVRTUC utility included with WinFrame 1.7 can be used to convert registry-based user information into SAM-based user information.

The Citrix WinFrame Clients (DOS, Win16, Win32, and Web Versions).  Version 1.7 of the WinFrame Clients includes the following features:

Dial-In support lets you dial in to your WinFrame server from DOS, Windows 3.1, Windows for Workgroups, Windows 95, and Windows NT client PCs and start a remote control session.

TCP/IP, NetBIOS, IPX, and SPX network protocol support let you access your WinFrame server over a LAN, WAN, or RAS connection and start a remote control session.

The Remote Application Wizard makes creating remote application entries quick and easy. Automatic modem detection is supported for creating Dial-In remote applications.

You can create a remote application entry to connect to a WinFrame server or to a published application that contains all of the information necessary to launch a user session or an application. All the end-user needs to do is double-click on the application entry's icon on the desktop.

Disk caching and data compression can be used to increase performance over low-speed Dial-In and WAN connections.  Disk caching stores commonly-used portions of your screen (such as icons and bitmaps) locally, increasing performance by avoiding retransmission of locally cached data.  Data compression reduces the amount of data sent over the communications link to the client PC.

The Remote Application Wizard lets you specify disk caching and data compression when creating a remote application. The Connection Options tab on the Properties menu for a remote application lets you change disk caching and data compression settings for a remote application.  The Disk Cache tab on the Settings menu lets you specify the path to the local disk cache and the amount of disk cache to allocate.

The ICA Browser provides a method for a user at a network-connected WinFrame Client PC to view a list of all WinFrame servers and published applications on the network with WinStations configured for that network type (IPX, TCP/IP, or NetBIOS). The WinFrame Clients supplied with this release use the ICA Browser to locate WinFrame servers and published applications on a network.

The ability to cut and paste data between the client and the WinFrame session using the Windows clipboard (Windows clients only).

The WinFrame Client for DOS supports COM port mapping. COM port mapping is similar to printer and drive mapping, and allows the WinFrame server to utilize a COM port on the client PC as if it were a COM port on the WinFrame server. COM port mapping is not currently supported by the WinFrame Windows clients. Use the net use command to map a COM port; for example, the command net use com2: \\client\com1 maps COM2 on the WinFrame server to the COM1 port of the WinFrame client PC.

Client printers are configured automatically (Windows clients only). Any printers detected when you connect to a WinFrame server are automatically added to the Print Manager. Client printers can be browsed and connected to in the same way as network printers.

The Citrix WinFrame Version 1.7 PC Client Pack

Every WinFrame client PC that will access a WinFrame Host/Terminal server must install a copy of the WinFrame PC Client Pack. The WinFrame PC Client Pack contains a client serial number that allows the client PC to access the WinFrame Host/Terminal server. Contact your reseller for ordering information.

The Citrix WinFrame Version 1.7 Host/Terminal to Enterprise Migration Pack

The Citrix WinFrame Version 1.7 Host/Terminal to Enterprise Migration Pack adds the following features to WinFrame Host/Terminal:

Windows NT file services, allowing a WinFrame server to become a Windows NT file server.

Windows NT print services, allowing a WinFrame server to become a Windows NT print server.

Windows NT Remote Access Services (RAS), allowing a WinFrame server to become a Windows NT remote node server.

Windows NT Services for Macintosh, making it possible for PC and Apple Macintosh clients to share files and printers.

WinFrame Web computing support, that lets you publish applications on your corporate Intranet or the Internet. The WinFrame Internet Client can be used with Microsoft Internet Explorer and Netscape Navigator to support Application Launching and Embedding (ALE), allowing users to run Windows applications within Web pages without having to rewrite them. Firewall support lets you interpose firewalls between your WinFrame server and the Internet for increased security. See the System Guide for more information.

Installing the WinFrame Version 1.7 Host/Terminal to Enterprise Migration Pack upgrades your WinFrame Host/Terminal server to a fully functional WinFrame/Enterprise server. Contact your reseller for ordering information.

Additional Notes

Installing WinFrame 1.7 on an NTFS Partition Formatted Using Windows NT 4.0

The NTFS file system driver shipped with Windows NT 4.0 renders the disk partition incompatible with prior versions of Windows NT and WinFrame. This problem is fixed in Windows NT 4.0 Service Pack 2. If the WinFrame 1.7 install partition was formatted using a version of Windows NT 4.0 prior to Service Pack 2, WinFrame Setup may fail. Other partitions used by WinFrame 1.7 (and Windows NT 3.51) may become corrupt if the partitions were also formatted with Windows NT 4.0 prior to Service Pack 2. Installing Windows NT 4.0 Service Pack 2 does not automatically correct the problem.

To correct this problem, the partitions must be deleted, recreated, and formatted with WinFrame 1.x, Windows NT 3.51, or Windows NT 4.0 with Service Pack 2 or greater before installing WinFrame 1.7.

Installing Applications on a WinFrame Server

See the Readme "General Installation of Applications on WinFrame" in WinFrame Help before you install any applications on your WinFrame server. This Readme contains important information about setting up applications in the WinFrame multiuser environment.

Incompatibilities Among WinFrame Servers Running Different Versions of WinFrame

You cannot mix WinFrame Version 1.6 and WinFrame Version 1.7 servers in a load balancing group. All servers in a load balancing group must be running the same version of WinFrame.

Licenses cannot be pooled among servers running different versions of WinFrame.

The WinFrame Version 1.7 Beta Release is not compatible with WinFrame Version 1.7 for load balancing, WinStation Administration server viewing, published applications, or license pooling.

Frequently Asked Questions About WinFrame

The following is a list of the most frequently asked questions about WinFrame.

Integration - Network

What NDS functions are supported under WinFrame?

The following NDS features are supported:

1.	NDS volumes may be accessed by both the command line interface and the File Manager.

2.	NDS printer queues may be accessed by both the command line interface and the Print Manager.

3.	NDS naming is supported, including typed and typeless names.

4.	A default NDS tree and context may be specified. The user is automatically logged into the NDS tree using the WinFrame  username and default context. NDS login scripts are supported.

NOTE: NDS usernames are not supported.

Can I remap WinFrame drive letters so that my clients can transparently access their local drive C?

Yes. You can use the Disk Administrator utility to do this. This is covered in detail in Chapter 1 of the WinFrame Installation Guide.

How do I create/configure user profiles for WinFrame ?

See Chapter 14 of the System Guide for information and instructions on how to create and use user profiles. Chapter 5 of the Concepts and Planning Guide describes how these profiles work in an NT environment.

How do I set up a default user profile?

Setting up a default user profile is covered in Chapter 14 of the WinFrame System Guide.

Why don't NWADMIN and NETADMIN run on WinFrame?

NetWare 4.x command line utilities do not run on WinFrame in an NDS environment; for example, capture and map. Any application that makes use of the NDS API will not work.

Integration - Application

My application is causing an error on WinFrame.

1.	Make sure your application is compatible with Windows NT 3.51.

2.	You must execute change user /install to install Windows 16-bit and 32-bit applications.

3.	Turn on file and registry auditing to determine what files or registry keys are being accessed.

Async

1.	My modem is not on the list of supported modems for WinFrame. How do I make it work?

2.	I am having trouble connecting with my US Robotics Sportster 28.8.

The MODEM.INF file lists all modems supported, along with the command and response strings each modem needs for correct operation. When you select a modem during installation, the Setup program associates the selected modem with the specified communication port. You can find MODEM.INF in the \systemroot\SYSTEM32\RAS directory.

If your modem is not listed in MODEM.INF, download the latest MODEM.INF file from the modem manufacturer's BBS or FTP server.

My system cannot locate any of my COM ports after installing a DigiBoard multiport adapter. What should I do next?

1.	Use the Terminal application or WinStation Configuration in WinFrame to establish whether or not the system can locate the ports.

2.	Check the event viewer to see if the DigiBoard initialized.

3.	If it did not, contact DigiBoard to download the latest NT DigiBoard drivers.

Why do I receive a "connection refused" error when trying to connect to a WinFrame server?

You must have a WinStation configured or available for the transport protocol being used by the client.

WinFrame Client

My DOS application will not display in full screen.

At this time, only the DOS WinFrame client will allow a remote full screen session to be displayed as a true DOS video full screen session.

Because the remote Application Manager is a Windows application, it conforms to the Windows video APIs and, therefore, continues to run as a Windows application when displaying remote DOS full screen sessions. Because the session is displayed as Windows video and not true DOS video, the column and row settings for the remote DOS session are translated into pixel coordinates on the local machine. Change the column and row settings for the remote DOS session to change the appearance of the locally displayed session.

How do I minimize my WinFrame session when using the Windows 16-bit and 32-bit clients?

Press SHIFT+F2. This will give you a task bar at the top of the screen that you can use to minimize the session.

Restrictions

Novell NetWare 4.x NDS Support. NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme "Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection" in WinFrame Help for detailed information. NDS drive map objects are not supported; use direct drive assignments to a volume and directory path instead.

Password Synchronization With NetWare 4.x NDS File Servers. Password synchronization with NetWare 4.x NDS servers is not supported at this time; however, password synchronization with NetWare 4.x servers running Bindery Emulation is supported.

Modem Installation Wizard. Automatic modem detection using the modem wizard in WinStation Configuration is not enabled during WinFrame installation because the required device drivers are not loaded by Setup. If you want to use the modem installation wizard to automatically detect the modems connected to your WinFrame server, reboot after completing your WinFrame installation and double-click on the Dial-In Setup Wizard in the Administrative Tools group. All other features of WinStation Configuration are available during installation.

Server Browser Incompatibility With WinFrame Version 1.5 Servers. WinFrame Version 1.5 servers are not visible in the application server pull-down list when configuring application server entries on systems using the WinFrame Version 1.7 Client.

WinFrame Features Overview

Citrix WinFrame is the first application publishing platform to extend the reach of corporate applications to users outside the LAN, including mobile professionals, telecommuters, branch office workers, customers, prospects, and vendors. Based on Microsoft Windows NT Server 3.51 under license from Microsoft, WinFrame is the only tool you need to publish corporate applications across the Intranet and Internet while retaining local speed, control, and ease of use.

WinFrame Product Highlights

High Performance. With Citrix Independent Computing Architecture (ICA™) 3.0, applications run at full LAN speed from anywhere. Applications run on the WinFrame server while the user interface is executed by ICA 3.0 on the client PC.

Local/Remote Transparency. Easy to use, all-purpose remote connectivity over a single remote connection eliminates the user dilemma of having to choose between remote node or remote control for running various applications.

Enterprise Scalability. You can easily build manageable telecomputing connectivity for thousands of remote and mobile users. WinFrame can accommodate up to 60 concurrent users on a single four-processor SMP Pentium server, depending on the application mix.

Extensive Connectivity. WinFrame connects users to the network through standard telephone lines, ISDN lines, wide area network links, broadband connections, or the Internet.

Stringent Security. To protect sensitive data, WinFrame incorporates multilevel system security and fully complies with DOD C2-level certification.

Flexible Management and Administration. Server-based system administration makes configuration, problem identification, and problem resolution quick and efficient. WinFrame includes an extensive set of end-to-end Windows management tools that allow WinFrame servers and remote users to be configured, administered, monitored, and supported from anywhere.

Enterprise Interoperability. WinFrame easily integrates into your existing enterprise networks, including Novell NetWare 3.x and 4.x; Microsoft Windows NT, LAN Manager and Windows for Workgroups; LAN Server; SNA gateways; and UNIX networking environments.

Runs Server-Based Applications. WinFrame runs Windows NT server applications such as Microsoft BackOffice, allowing clients and server programs to be consolidated on a single server for performance gains and ease of system management.

Broad Application Support. WinFrame executes most Windows NT, Windows 95, Windows 3.1, DOS text, OS/2 text, and POSIX applications, including popular personal productivity, workgroup, client/server, and legacy programs.

Remote Node Compatibility. WinFrame can be used in conjunction with most popular third-party remote node hardware and software to significantly boost the performance of LAN-resident applications.

For more information on installing and configuring your system, see the Quick Install Guide, the Installation Guide, and the WinFrame Client User's Guide.


Citrix WinFrame/WorkGroups Version 1.7 Release Notes

Before you install WinFrame, please read these Release Notes for information about the materials in this package.

Important

WinFrame/WorkGroups is a five-user only version of Citrix WinFrame. The user count cannot be increased through the use of WinFrame User License Packs, and WinFrame/WorkGroups server licenses cannot be pooled. You can install the WinFrame Server Option Pack, the WinFrame SecureICA Option Pack, and the WinFrame Load Balancing Option Pack on a WinFrame/WorkGroups server, but user licenses cannot be increased or pooled. You cannot upgrade a WinFrame/WorkGroups server to WinFrame/Enterprise; to do this, you must purchase and install WinFrame/Enterprise.

Service and Support

For information on obtaining service and support for WinFrame, please read the Support Services Card included in this package. You can also obtain a wealth of technical information from the Citrix On-line Technical Support Services at http://support.citrix.com

Hardware Compatibility Information and System Guidelines

For information on hardware compatibility and guidelines for configuring your WinFrame server, see the Microsoft Windows NT 3.51 Hardware Compatibility List. The Hardware Compatibility List contains information about systems, adapters, and other peripherals compatible with Microsoft® Windows® NT™ 3.51 and Citrix WinFrame Version 1.7. The Hardware Compatibility List can be found online in the Main program group.

WinFrame Licensing and Activation

WinFrame Version 1.7 uses an activation key-based licensing system. Every licensed WinFrame Version 1.7 product (WinFrame server software or Add-On Pack) has an associated serial number. When you install the software, you enter the product’s serial number. You must then obtain an  activation key. The activation key is based on the product’s serial number and is used by the WinFrame Licensing program to enable the product. The WinFrame/WorkGroups Version 1.7 Serial Number Sticker attached to the CD-ROM case contains the software license serial number for your copy of WinFrame/WorkGroups.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

WinFrame Hotfixes and Service Packs

WinFrame Hotfixes are patches to the WinFrame operating system. Hotfixes are tested and verified to fix specific problems, and should only be applied on the advice of Citrix Technical Support. WinFrame Service Packs are collections of patches released between major revisions of the WinFrame operating system. Service packs are cumulative; that is, they contain all patches included in prior service packs.

WinFrame Hotfixes and Service Packs can be downloaded from the Citrix Web site (support.citrix.com) or the corporate BBS at (954) 267-2590, or obtained from your reseller.

SETUP.TXT, Quick Install Guide, and WinFrame Help

The SETUP.TXT file is available in the \I386 directory of the WinFrame/WorkGroups CD-ROM. It contains additional information from Microsoft regarding Windows NT 3.51, also applicable to WinFrame, that you may need prior to installing WinFrame on some hardware configurations.

The WinFrame Quick Install Guide contains information on system hardware requirements and a condensed version of the steps you need to follow for a quick and easy WinFrame installation. Use this manual and the Installation Guide to install WinFrame on your computer.

After installing WinFrame, please read the WinFrame online Help by double-clicking the WinFrame Help icon in the Main program group. The WinFrame online Help (also referred to as the WinFrame Readme) contains hardware- and software-specific information and descriptions of product features that were added or changed after the documentation was printed.

WinFrame Books Online

WinFrame Books Online contains the complete set of WinFrame manuals (except for the Quick Install Guide) in a convenient help file format. You can access Books Online from the Main program group. The complete WinFrame manual set is not shipped with WinFrame. To order a complete WinFrame documentation set, call Citrix Sales at (800) 437-7503.

New Features in This Release

Integrated WinFrame Setup Procedure. You can install the NetWare Gateway, multiport serial adapters, and Remote Access Service during Setup. Setup automatically configures two WinStations for each network protocol you install (IPX, TCP/IP, and NetBIOS).

Sync-up With Windows NT 3.51 Service Pack 5. WinFrame is totally compatible with the latest release of Windows NT Version 3.51 and all released service packs up to Service Pack 5.

Activation Key-Based Licensing.  WinFrame Version 1.7 uses a serial number/activation key licensing scheme.  Every licensed WinFrame product (WinFrame server software or Add-On Pack) has an associated serial number.  When you install the software, you enter the product’s serial number.  You must then register the serial number with Citrix to obtain an  activation key.  The activation key can then be applied to the serial number by using the WinFrame Licensing utility.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and the Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame server software.  You must activate your WinFrame server software after installing it.

Application Publishing Support.  WinFrame Version 1.7 supports application publishing. A published application contains all of the information needed to launch an application on a WinFrame server and can be used with WinFrame load balancing support.  See Chapter 23, “Application Publishing” of the System Guide for information on how to use the Application Configuration utility to publish applications.

Windows NT Multi-Protocol Routing Service (MPR) Included.  WinFrame Version 1.7 includes the Windows NT Multi-Protocol Routing Service (MPR) in the \MPR directory. Multi-Protocol Routing allows a WinFrame server to act as a low cost LAN-to-LAN routing solution for TCP/IP and IPX networks. MPR can also be used to link LANs that have different network topologies, such as Ethernet and Token-Ring. Run the UPDATE.EXE program in the \MPR directory of the WinFrame CD-ROM to install the Windows NT Multi-Protocol Routing Service. See the Solutions Guide for more information on installing and using the MPR Service.

Load Balancing Support. WinFrame 1.7 supports load balancing. With load balancing, several WinFrame servers can be logically pooled in a server farm. When a user launches a published application that is configured for load balancing, the WinFrame load balancing support routes the application to the most lightly loaded server in the farm for execution. You can create a farm of several servers that run predefined applications and fine-tune the load determination criteria on each server. Each WinFrame server that will support load balancing must have a copy of the WinFrame 1.7 Load Balancing Option Pack installed. See Chapter 23, “Application Publishing” of the System Guide for information on configuring applications for use with a server farm.

Web Computing Support.  WinFrame Version 1.7 supports Web computing features that let you publish applications on your corporate Intranet or the Internet. The WinFrame Internet Client can be used with Microsoft Internet Explorer and Netscape Navigator to support Application Launching and Embedding (ALE), allowing users to run Windows applications within Web pages. Firewall support lets you interpose firewalls between your WinFrame server and the Internet for increased security. See Chapter 24, “WinFrame Web Computing” of the System Guide for information on how to use the Application Configuration utility to publish applications.

Enhanced Security Features.  WinFrame Version 1.7 supports enhanced security utilities and procedures that help you protect your system from unauthorized access. See the  Security Guide for more information.

New WinStation Administration Utility.  WinStation Administration has been significantly updated.  WinStation Administration can now be used to maintain and display information about every WinFrame server, WinStation, and WinFrame user on a network.  See Chapter 21, “WinStation Administration,” in the System Guide for more information.

WinFrame Client Creator.  The WinFrame Clients are now shipped on the WinFrame CD-ROM.  The WinFrame Client Creator can be used to create diskettes containing the WinFrame Clients (DOS, Win16, Win32, and Web).  See Chapter 10, “WinFrame Client Creator,” in the Installation Guide for more information.

Client Printer and Disk Drive Mapping.  WinFrame users who access the server with the WinFrame client can transparently access their local printers and disk drives (fixed and removable).  The drive letters used for drive mapping are configurable and long filenames are supported.

Password Synchronization With NetWare File Servers. Passwords can be optionally synchronized between a NetWare 3.x server and the WinFrame server. The password on the WinFrame server tracks the password on the Novell server. When the password on the Novell server changes, the WinFrame password also changes. Use the User Manager for Domains to manage what users have NetWare password synchronization. Password synchronization with NetWare 4.x servers running Bindery Emulation is supported; however, password synchronization with NetWare 4.x NDS servers is not supported at this time.

Novell® NetWare™ 4.x NDS Support. NetWare 4.x Network Directory Services (NDS) are supported. You can use File Manager and Print Manager to access NDS trees on NetWare 4.x servers, net use NDS names, and use NDS features in NetWare login scripts.

NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme “Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection” in WinFrame Help for detailed information.

Dial-In Setup Wizard With Automatic Modem Detection. WinFrame’s Dial-In Setup Wizard makes configuring Dial-In WinStations quick and easy. Automatic modem detection determines the type of modem connected to the WinFrame server and configures it for optimum throughput.

Configurable TCP/IP Port Setting for ICA Protocol.  This feature lets you configure Citrix ICA packets to be compatible with many popular TCP/IP firewall products.

User Information Stored in the Security Account Manager (SAM) Database.  For added reliability, user information is now stored in the Security Account Manager (SAM) database instead of the registry of the primary domain controller (PDC).  The SAM database is automatically propagated from the PDC to all backup domain controllers (BDCs), which ensures that user information is available as long as the PDC or any BDC is available.  The CNVRTUC utility included with WinFrame 1.7 can be used to convert registry-based user information into SAM-based user information.

The Citrix WinFrame Clients (DOS, Win16, Win32, and Web Versions).  Version 1.7 of the WinFrame Clients includes the following features:

Dial-In support lets you dial in to your WinFrame server from DOS, Windows 3.1, Windows for Workgroups, Windows 95, and Windows NT client PCs and start a remote control session.

TCP/IP, NetBIOS, IPX, and SPX network protocol support let you access your WinFrame server over a LAN, WAN, or RAS connection and start a remote control session.

The Remote Application Wizard makes creating remote application entries quick and easy. Automatic modem detection is supported for creating Dial-In remote applications.

You can create a remote application entry to connect to a WinFrame server or to a published application that contains all of the information necessary to launch a user session or an application. All the end-user needs to do is double-click on the application entry’s icon on the desktop.

Disk caching and data compression can be used to increase performance over low-speed Dial-In and WAN connections.  Disk caching stores commonly-used portions of your screen (such as icons and bitmaps) locally, increasing performance by avoiding retransmission of locally cached data.  Data compression reduces the amount of data sent over the communications link to the client PC.

The Remote Application Wizard lets you specify disk caching and data compression when creating a remote application. The Connection Options tab on the Properties menu for a remote application lets you change disk caching and data compression settings for a remote application.  The Disk Cache tab on the Settings menu lets you specify the path to the local disk cache and the amount of disk cache to allocate.

The ICA Browser provides a method for a user at a network-connected WinFrame Client PC to view a list of all WinFrame servers and published applications on the network with WinStations configured for that network type (IPX, TCP/IP, or NetBIOS). The WinFrame Clients supplied with this release use the ICA Browser to locate WinFrame servers and published applications on a network.

The ability to cut and paste data between the client and the WinFrame session using the Windows clipboard (Windows clients only).

The WinFrame Client for DOS supports COM port mapping. COM port mapping is similar to printer and drive mapping, and allows the WinFrame server to utilize a COM port on the client PC as if it were a COM port on the WinFrame server. COM port mapping is not currently supported by the WinFrame Windows clients. Use the net use command to map a COM port; for example, the command net use com2: \\client\com1 maps COM2 on the WinFrame server to the COM1 port of the WinFrame client PC.

Client printers are configured automatically (Windows clients only). Any printers detected when you connect to a WinFrame server are automatically added to the Print Manager. Client printers can be browsed and connected to in the same way as network printers.

The Citrix WinFrame Version 1.7 Server Option Pack

The Citrix WinFrame Version 1.7 Server Option Pack adds the following features to WinFrame/WorkGroups:

Windows® NT™ file services, allowing a WinFrame server to become a Windows NT file server.

Windows NT print services, allowing a WinFrame server to become a Windows NT print server.

Windows NT Remote Access Services (RAS), allowing a WinFrame server to become a Windows NT remote node server.

Windows NT Services for Macintosh®, making it possible for PC and Apple® Macintosh clients to share files and printers.

WinFrame Web computing support, that lets you publish applications on your corporate Intranet or the Internet. The WinFrame Internet Client can be used with Microsoft Internet Explorer and Netscape Navigator to support Application Launching and Embedding (ALE), allowing users to run Windows applications within Web pages without having to rewrite them. Firewall support lets you interpose firewalls between your WinFrame server and the Internet for increased security. See the System Guide for more information.

Contact your reseller for ordering information for the WinFrame Version 1.7 Server Option Pack.

Additional Notes

Installing WinFrame 1.7 on an NTFS Partition Formatted Using Windows NT 4.0

The NTFS file system driver shipped with Windows NT 4.0 renders the disk partition incompatible with prior versions of Windows NT and WinFrame. This problem is fixed in Windows NT 4.0 Service Pack 2. If the WinFrame 1.7 install partition was formatted using a version of Windows NT 4.0 prior to Service Pack 2, WinFrame Setup may fail. Other partitions used by WinFrame 1.7 (and Windows NT 3.51) may become corrupt if the partitions were also formatted with Windows NT 4.0 prior to Service Pack 2. Installing Windows NT 4.0 Service Pack 2 does not automatically correct the problem.

To correct this problem, the partitions must be deleted, recreated, and formatted with WinFrame 1.x, Windows NT 3.51, or Windows NT 4.0 with Service Pack 2 or greater before installing WinFrame 1.7.

Installing Applications on a WinFrame Server

See the Readme “General Installation of Applications on WinFrame” in WinFrame Help before you install any applications on your WinFrame server. This Readme contains important information about setting up applications in the WinFrame multiuser environment.

Incompatibilities Among WinFrame Servers Running Different Versions of WinFrame

You cannot mix WinFrame Version 1.6 and WinFrame Version 1.7 servers in a load balancing group. All servers in a load balancing group must be running the same version of WinFrame.

The WinFrame Version 1.7 Beta Release is not compatible with WinFrame Version 1.7 for load balancing, WinStation Administration server viewing, published applications, or license pooling.

Frequently Asked Questions About WinFrame

The following is a list of the most frequently asked questions about WinFrame.

Licensing

How can I add additional user licesnes to WinFrame/WorkGroups?

WinFrame/WorkGroups cannot be upgraded with additional users, nor can WinFrame/WorkGroups user licenses be pooled. Contact your reseller for a copy of WinFrame/Enterprise if you need to support more than five users.

Integration - Network

What NDS functions are supported under WinFrame?

The following NDS features are supported:

1.	NDS volumes may be accessed by both the command line interface and the File Manager.

2.	NDS printer queues may be accessed by both the command line interface and the Print Manager.

3.	NDS naming is supported, including typed and typeless names.

4.	A default NDS tree and context may be specified. The user is automatically logged into the NDS tree using the WinFrame  username and default context. NDS login scripts are supported.

NOTE: NDS usernames are not supported.

Can I remap WinFrame drive letters so that my clients can transparently access their local drive C?

Yes. You can use the Disk Administrator utility to do this. This is covered in detail in Chapter 1 of the WinFrame Installation Guide.

How do I create/configure user profiles for WinFrame ?

See Chapter 14 of the System Guide for information and instructions on how to create and use user profiles. Chapter 5 of the Concepts and Planning Guide describes how these profiles work in an NT environment.

How do I set up a default user profile?

Setting up a default user profile is covered in Chapter 14 of the WinFrame System Guide.

Why don’t NWADMIN and NETADMIN run on WinFrame?

NetWare 4.x command line utilities do not run on WinFrame in an NDS environment; for example, capture and map. Any application that makes use of the NDS API will not work.

Integration - Application

My application is causing an error on WinFrame.

1.	Make sure your application is compatible with Windows NT 3.51.

2.	You must execute change user /install to install Windows 16-bit and 32-bit applications.

3.	Turn on file and registry auditing to determine what files or registry keys are being accessed.

Async

1.	My modem is not on the list of supported modems for WinFrame. How do I make it work?

2.	I am having trouble connecting with my US Robotics Sportster 28.8.

The MODEM.INF file lists all modems supported, along with the command and response strings each modem needs for correct operation. When you select a modem during installation, the Setup program associates the selected modem with the specified communication port. You can find MODEM.INF in the \systemroot\SYSTEM32\RAS directory.

If your modem is not listed in MODEM.INF, download the latest MODEM.INF file from the modem manufacturer’s BBS or FTP server.

My system cannot locate any of my COM ports after installing a DigiBoard multiport adapter. What should I do next?

1.	Use the Terminal application or WinStation Configuration in WinFrame to establish whether or not the system can locate the ports.

2.	Check the event viewer to see if the DigiBoard initialized.

3.	If it did not, contact DigiBoard to download the latest NT DigiBoard drivers.

Why do I receive a “connection refused” error when trying to connect to a WinFrame server?

You must have a WinStation configured or available for the transport protocol being used by the client.

WinFrame Client

My DOS application will not display in full screen.

At this time, only the DOS WinFrame client will allow a remote full screen session to be displayed as a true DOS video full screen session.

Because the remote Application Manager is a Windows application, it conforms to the Windows video APIs and, therefore, continues to run as a Windows application when displaying remote DOS full screen sessions. Because the session is displayed as Windows video and not true DOS video, the column and row settings for the remote DOS session are translated into pixel coordinates on the local machine. Change the column and row settings for the remote DOS session to change the appearance of the locally displayed session.

How do I minimize my WinFrame session when using the Windows 16-bit and 32-bit clients?

Press SHIFT+F2. This will give you a task bar at the top of the screen that you can use to minimize the session.

Restrictions

WinFrame/WorkGroups Fixed User Count of Five. WinFrame/WorkGroups Version 1.7 can only support five users. You cannot use WinFrame User License Packs to increase the user count.

WinFrame/WorkGroups Does Not Support License Pooling. WinFrame/WorkGroups Version 1.7 servers do not support license pooling. The user count for a WinFrame/WorkGroups server is always five.

Novell NetWare 4.x NDS Support. NDS-aware applications (for example, nwadmin and netadmin) are not supported at this time. However, these utilities can be run from a network workstation running DOS or Windows 3.x, or a remote workstation connected to WinFrame RAS using a third-party RAS package. This allows administration of NetWare 4.x servers from a remote DOS or Windows 3.x workstation. See the Readme “Remote NetWare 4.x Administration Using NETADMIN and NWADMIN Over a RAS Connection” in WinFrame Help for detailed information. NDS drive map objects are not supported; use direct drive assignments to a volume and directory path instead.

Password Synchronization With NetWare 4.x NDS File Servers. Password synchronization with NetWare 4.x NDS servers is not supported at this time; however, password synchronization with NetWare 4.x servers running Bindery Emulation is supported.

Modem Installation Wizard. Automatic modem detection using the modem wizard in WinStation Configuration is not enabled during WinFrame installation because the required device drivers are not loaded by Setup. If you want to use the modem installation wizard to automatically detect the modems connected to your WinFrame server, reboot after completing your WinFrame installation and double-click on the Dial-In Setup Wizard in the Administrative Tools group. All other features of WinStation Configuration are available during installation.

Server Browser Incompatibility With WinFrame Version 1.5 Servers. WinFrame Version 1.5 servers are not visible in the application server pull-down list when configuring application server entries on systems using the WinFrame Version 1.7 Client.

WinFrame Features Overview

Citrix WinFrame is the first application publishing platform to extend the reach of corporate applications to users outside the LAN, including mobile professionals, telecommuters, branch office workers, customers, prospects, and vendors. Based on Microsoft Windows NT Server 3.51 under license from Microsoft, WinFrame is the only tool you need to publish corporate applications across the Intranet and Internet while retaining local speed, control, and ease of use.

WinFrame Product Highlights

High Performance. With Citrix Independent Computing Architecture (ICA) 3.0, applications run at full LAN speed from anywhere. Applications run on the WinFrame server while the user interface is executed by ICA 3.0 on the client PC.

Local/Remote Transparency. Easy to use, all-purpose remote connectivity over a single remote connection eliminates the user dilemma of having to choose between remote node or remote control for running various applications.

Enterprise Scalability. You can easily build manageable telecomputing connectivity for thousands of remote and mobile users. WinFrame/Enterprise can accommodate up to 60 concurrent users on a single four-processor SMP Pentium server, depending on the application mix.

Extensive Connectivity. WinFrame connects users to the network through standard telephone lines, ISDN lines, wide area network links, broadband connections, or the Internet.

Stringent Security. To protect sensitive data, WinFrame incorporates multilevel system security and fully complies with DOD C2-level certification.

Flexible Management and Administration. Server-based system administration makes configuration, problem identification, and problem resolution quick and efficient. WinFrame includes an extensive set of end-to-end Windows management tools that allow WinFrame servers and remote users to be configured, administered, monitored, and supported from anywhere.

Enterprise Interoperability. WinFrame easily integrates into your existing enterprise networks, including Novell NetWare 3.x and 4.x; Microsoft Windows NT, LAN Manager and Windows for Workgroups; LAN Server; SNA gateways; and UNIX networking environments.

Runs Server-Based Applications. WinFrame runs Windows NT server applications such as Microsoft BackOffice, allowing clients and server programs to be consolidated on a single server for performance gains and ease of system management.

Broad Application Support. WinFrame executes most Windows NT, Windows 95, Windows 3.1, DOS text, OS/2 text, and POSIX applications, including popular personal productivity, workgroup, client/server, and legacy programs.

Remote Node Compatibility. WinFrame can be used in conjunction with most popular third-party remote node hardware and software to significantly boost the performance of LAN-resident applications.

For more information on installing and configuring your system, see the Quick Install Guide, the Installation Guide, and the WinFrame Client User’s Guide.


Citrix WinFrame Version 1.7 PC Client Pack Release Notes

The PC Client Pack contains a Client Serial Number which allows the Citrix  WinFrame Client to access a WinFrame Host/Terminal server.

After you install the desired WinFrame Client on a client PC, you must enable the client by entering the Client Serial Number found on the Client Serial Number Card in this package. This serial number uniquely identifies the PC running the WinFrame Client program, and must be correctly entered in order for you to log on to a WinFrame server. See the enclosed Client Software License Agreement for information on the terms and conditions of your Client License.

To enter your WinFrame Client License (Windows clients)

1.	Install the appropriate version (Win16 or Win32) of the WinFrame Client on the client PC. Start the WinFrame Client.

2.	Select the Preferences menu, found under Settings in the Options pull-down menu.

3.	Enter the Client Serial Number found on the Client Serial Number Card into the Serial Number field. Enter the serial number exactly as it appears on the sticker, including any hyphens and upper or lower case letters. If the serial number is incorrectly entered you will not be able to log on to a WinFrame server.

4.	Choose OK to save the serial number.

To enter your WinFrame Client License (WinFrame Client for DOS)

1.	Install the WinFrame Client for DOS on the client PC. Start the WinFrame Client.

2.	Select Preferences in the Options pull-down menu.

3.	Enter the Client Serial Number found on the Client Serial Number Card into the Serial Number field. Enter the serial number exactly as it appears on the sticker, including any hyphens and upper or lower case letters. If the serial number is incorrectly entered you will not be able to log on to a WinFrame server.

4.	Choose OK to save the serial number.

Important  This license can only be installed once on one client computer. See the enclosed Client Software License Agreement for detailed terms and conditions.


Citrix WinView to WinFrame/Enterprise Version 1.7 Migration Pack Release Notes

The WinView to WinFrame/Enterprise Migration Pack upgrades a WinView server to a WinFrame/Enterprise server by performing a complete reformat and reinstall.  See the enclosed Citrix WinFrame/Enterprise Version 1.7 Release Notes for more information about WinFrame/Enterprise features.

Warning  WinFrame/Enterprise is installed over your existing WinView software. No WinView data is retained, and you must reformat your hard drive when installing. Before installing the WinFrame/Enterprise Migration Pack, be sure to back up any important data on your WinView server.

Read the included Quick Install Guide, the WinFrame/Enterprise Installation Guide, and the Citrix WinFrame/Enterprise Version 1.7 Release Notes for information on how to install your WinFrame/Enterprise server software.

Read the included Citrix WinFrame Version 1.7 Quick Activation Guide and Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame/Enterprise server software.  You must activate WinFrame/Enterprise after installing it.


Citrix WinFrame Version 1.7 Host/Terminal to Enterprise Migration Pack Release Notes

The Host/Terminal to Enterprise Migration Pack adds the following features to WinFrame Host/Terminal:

Windows NT file services, allowing a WinFrame server to become a Windows NT file server.

Windows NT print services, allowing a WinFrame server to become a Windows NT print server.

Windows NT Remote Access Services (RAS), allowing a WinFrame server to become a Windows NT remote node server.

Windows NT Services for Macintosh, making it possible for PC and Apple Macintosh clients to share files and printers.

WinFrame Web Computing extensions that let you publish applications on the Internet and corporate Intranets.

Licensed clients (using the PC Client Pack) are no longer required. You can use the standard WinFrame PC Clients to connect to your WinFrame server.

You must consider how installing the Host/Terminal to Enterprise Migration Pack on your WinFrame server impacts Microsoft Client Access licenses. You may need to purchase Client Access licenses from Microsoft to support additional users. See Chapter 1 of the Installation Guide for more information on Microsoft Client Access licenses.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame Host/Terminal to Enterprise Migration Pack. You must activate the WinFrame Host/Terminal to Enterprise Migration Pack after installing it.

To install the WinFrame Host/Terminal to Enterprise Migration Pack on a WinFrame server

1.	Logon as an administrator. On the WinFrame desktop, double-click on the WinFrame Licensing icon in the Administrative Tools program group. The WinFrame Licensing screen appears, displaying the licenses installed on your WinFrame server.

2.	Select Add from the License pull-down menu. The Enter License Serial Number dialog appears.

3.	Enter the Host/Terminal to Enterprise Migration Pack serial number exactly as it appears on the Host/Terminal to Enterprise Migration Pack License Sticker and click OK. The license is added to the list of installed licenses.

4.	Exit WinFrame Licensing.


Citrix WinFrame Version 1.7 Load Balancing Option Pack Release Notes

The Load Balancing Option Pack enhances the features of WinFrame, the enterprise Windows telecomputing platform, by allowing users to access applications on a group of WinFrame servers instead of tying an application to only one server. Before you install the WinFrame Load Balancing Option Pack, please read the Release Notes for information about the materials in this package.

Note  You must install a WinFrame Load Balancing Option Pack on each WinFrame server in a server group. Every WinFrame server in a server group must be a WinFrame Version 1.7 server. The WinFrame Load Balancing Option Pack can only be installed on a WinFrame/Enterprise server.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame Load Balancing Option Pack. You must activate the WinFrame Load Balancing Option Pack after installing it.

To install the WinFrame Load Balancing Option Pack on a WinFrame server

1.	Logon as an administrator. On the WinFrame desktop, double-click on the WinFrame Licensing icon in the Administrative Tools program group. The WinFrame Licensing screen appears, displaying the licenses installed on your WinFrame server.

2.	Select Add from the License pull-down menu. The Enter License Serial Number dialog appears.

3.	Enter the Load Balancing Option Pack serial number exactly as it appears on the Load Balancing Option Pack License Sticker and click OK. The license is added to the list of installed licenses.

4.	Exit WinFrame Licensing.


Citrix WinFrame Version 1.7 Server Option Pack Release Notes

The Server Option Pack adds the following features to WinFrame Host/Terminal and WinFrame/WorkGroups:

Windows® NT™ file services, allowing a WinFrame server to become a Windows NT file server.

Windows NT print services, allowing a WinFrame server to become a Windows NT print server.

Windows NT Remote Access Services (RAS), allowing a WinFrame server to become a Windows NT remote node server.

Windows NT Services for Macintosh®, making it possible for PC and Apple® Macintosh clients to share files and printers.

WinFrame Web Computing extensions that let you publish applications on the Internet and corporate Intranets.

Note

The WinFrame Host/Terminal PC Client Pack is required in order to use client PCs with WinFrame Host/Terminal systems.

You must consider how installing the Server Option Pack on your WinFrame server impacts Microsoft Client Access licenses. You may need to purchase Client Access licenses from Microsoft to support additional users. See Chapter 1 of the Installation Guide for more information on Microsoft Client Access licenses.

Please read the included WinFrame Version 1.7 Quick Activation Guide and WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame Host/Terminal to Enterprise Migration Pack. You must activate the WinFrame Server Option Pack after installing it.

To install the WinFrame Server Option Pack on a WinFrame server

1.	Logon as an administrator. On the WinFrame desktop, double-click on the WinFrame Licensing icon in the Administrative Tools program group. The WinFrame Licensing screen appears, displaying the licenses installed on your WinFrame server.

2.	Select Add from the License pull-down menu. The Enter License Serial Number dialog appears.

3.	Enter the Server Option Pack serial number exactly as it appears on the Server Option Pack License Sticker and click OK. The license is added to the list of installed licenses.

4.	Exit WinFrame Licensing.


Citrix WinFrame Version 1.7 Bump Pack Release Notes

The Bump Pack adds support for additional concurrent users to your WinFrame server.

Note Bump Packs come in 5, 10, 20, and 50 user versions.

You must consider how installing the Bump Pack on your WinFrame server impacts Microsoft Client Access licenses. You may need to purchase Client Access licenses from Microsoft to support additional users. See Chapter 1 of the Installation Guide for more information on Microsoft Client Access licenses.

Please read the included Citrix WinFrame Version 1.7 Quick Activation Guide and Citrix WinFrame Version 1.7 Activation Guide for information on how to activate your WinFrame Bump Pack.  You must activate the WinFrame Bump Pack after installing it.

To install the WinFrame Bump Pack on a WinFrame server

1.	Logon as an administrator. On the WinFrame desktop, double-click on the WinFrame Licensing icon in the Administrative Tools program group. The WinFrame Licensing screen appears, displaying the licenses installed on your WinFrame server.

2.	Select Add from the License pull-down menu. The Enter License Serial Number dialog appears.

3.	Enter the Bump Pack serial number exactly as it appears on the Bump Pack License Sticker and click OK. The license is added to the list of installed licenses.

4.	Exit WinFrame Licensing.