Copyright: Copyright « 1998


16-bit Applications and Modems in Windows 95

16-bit applications cannot make use or TAPI in Windows** 95**.  Therefore, modems configured in Windows 95 will not respond correctly to 16-bit applications.  You must still specify the modem type in the application itself.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


16-bit Driver

This driver will indicate the progress of the search operation by displaying search information and a rocking wheel.  When it tries to communicate with the bad server, you see that it is taking a long time (60 seconds default) trying to communicate with that server.  You can then click the Cancel key to abort the operation.


32-bit Driver

This driver can display messages only when the connection process is complete.  Therefore, it has to search NetWare* servers either until it finds an available service or until there are no more NetWare servers to search before it can display a message indicating the state of the connection.  During this time, the Windows** 95** operating system is locked up and you might think that the system is dead.  If it happens to search a server that is not responding, you might think that the machine is hung and, consequently, reboot the machine.


3D Effect
3-D Effect

Allows you to enable or disable the 3-D look of the mapping utility.


Assigning COM Ports in Windows 95

If you are using the Custom Install option to install Win2NCS in Windows** 95**, you will be prompted to select the COM ports for Win2NCS configure.  If a COM port is already assigned to another device or program, Win2NCS will not change the assignment.

To assign COM Ports in Windows 95

1.	During the Custom Install program, select the COM ports for Win2NCS to configure.

2.	Click Next to continue the Custom Installation process.

3.	Once installation is complete, continue with the normal setup  and mapping processes.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Asterisk (*)

When you type an asterisk as the last character of a server name, this indicates that all servers whose names match the characters before the asterisk are restricted.


Asynchronous E-mail Gateway Does Not Periodically Download Messages

If you use asynchronous E-mail gateway software (such as Pegasus Mail**) running on a dedicated personal computer to periodically download messages from the Internet, then make sure that Busy Port Notification is disabled.  This allows the E-mail software to redial a busy port later without the need for user intervention.

Related Topics

Busy Port Notification

Using the Notify Process to Monitor a Busy Port

Using Modem Lights to Monitor Data Transfer

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Automating the Install Process

You  can predefine several options so that when a user runs the SETUP program, the install executes without user intervention.  This feature is useful for users that run in a shared install directory.

You can predefine the following capabilities:

How configuration files are managed.

The path of the installed directory.

The default mapping of COM ports.

To set up the automated install

1.	Install Win2NCS in a shared directory.

2.	Using the Win2NCS Mapping Utility, map the COM ports to the desired default configuration.

3.	Create a SETUP.INI file.

4.	Place the SETUP.INI file in the SETUP directory (the directory where SETUP.EXE resides).

Note:  You might want to have two SETUP directories: one for initial users which has the COM ports defined, and another for update users which does not have the COM ports defined.  In this way, the COM ports of the update users--which might have been mapped to another service--are not reset to the default values.

5.	Tell users to Run SETUP.EXE from the applicable SETUP directory.

The automated install process bypasses the Custom and Express install options.

Note:  In Windows** 95**, the automated install registers ports 3 through 8 as Win2NCS COM ports.

Once users have installed Win2NCS, they should do the following:

Set security

Test security

Define server restrictions (optional)

Set options (optional)

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Busy Port Notification

If this option is enabled, you will be notified if the communications port you want to access is in use. Win2NCS can monitor that port and notify you when the port is available.  You will be prompted to select which port you want to monitor.

In certain cases, it is preferable to disable Busy Port Notification.  For example, if you use asynchronous E-mail gateway software (such as Pegasus Mail**) running on a dedicated personal computer to periodically download messages from the Internet, then disabling Busy Port Notification allows the E-mail software to redial a busy port later without the need for user intervention.

Related Topics

Using Modem Lights to Monitor Data Transfer

Asynchronous E-mail Gateway Does Not Periodically Download Messages

Using the Notify Process to Monitor a Busy Port

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


COM Section of SETUP.INI File

This section defines how COM ports 1 through 8 are mapped.

If any of the COM port entries are left blank, no changes are made to the previous or default installation for that port.

The special value UNMAPPED must be placed in any port that is to be unmapped.

Notes:

If the value DYNAMIC is used for any port when running on Windows** 95**, that port is UNMAPPED because Win2NCS on Windows 95 does not support Dynamic mapping.

Because workstations vary as to the number of COM ports, some of the mappings might not occur when using Windows 95.  For example, if a workstation had 3Com** ports, COM1 through COM3 would be assigned to the Local Port for a Windows 95 workstation.


Cannot Cancel during Redirection

The 16-bit driver allows canceling the Win2NCS Redirection during the connection phase, whereas the 32-bit driver does not.


Cannot Switch to Another Application

In this release, you cannot switch to another application while Win2NCS is initializing (acquiring ports, etc.).


Changing the Mapping of Redirected or Active COM Ports

You can use the Win2NCS mapping utility to change the mapping of a COM port even though it is currently redirected and active.  However, the mapping will apply only to the next time the COM port is used and will not cause the current connection to be redirected.


Changing the Way Configuration Files Are Handled without Running Setup Again

You can change the way configuration files are handled at any time by changing the Networked entry in the [Config] section of the USERS.INI file:

0 = Config files in installed directory

1 = Config files based on login name (includes context).

2 = Config files always on drive C:.

3 = Config files in the WINDOWS directory.

4 = Config files based on username (ignores context).

These changes will take effect the next time you run Win2NCS.


COM Port Not Redirected

The Win2NCS Redirector will not direct the COM port to NCS and you will not see any informational messages from the Win2NCS Redirector when you start the application.

Make sure that Win2NCS Redirection is enabled.

If Win2NCS Redirection is enabled, check to make sure that the COM port is mapped correctly.

If the COM port is mapped correctly, make sure that the Redirector Informational Messages are enabled in the Global Mapping Options of the Win2NCS utility (Win2NCS Redirection could be taking place without you knowing it).


COM Ports Cannot Be Overmapped

When using the 16-bit driver, Win2NCS can determine whether to direct the COM port to the local COM port or to a NIAS port.  This is because the Win2NCS Redirector is at a very high level and can trap the calls to the COM ports, allowing the redirection to occur or not.

However, the 32-bit drivers are at a very low level and the trapping of calls is not possible when using these drivers.  Assignments of COM ports are performed by the operating system on both Windows** 95** and Windows NT**


Command Line Parameters

/PortNumber invokes the Modem Lights for the defined port.  For example, C:\WIN2NCS\MODEM/1 invokes the Modem Lights for COM1.


Configuration File Is Created in Installed Directory

This option is usually selected if the Win2NCS application resides on the workstation and will not be shared with other users.  The configuration file that is created is called NCS.INI and is placed in the default Win2NCS directory.


Configuration Files Are Always in WINDOWS Directory

This option can be selected if a private WINDOWS directory is available for each user and the Win2NCS application resides on a network drive.  When this option is selected, Win2NCS will look for the NCS.INI file in the WINDOWS directory; if one is found, it will use that configuration file.  If an NCS.INI file is not found, one will be created in the WINDOWS directory.


Configuration Files Are Always on Drive C:

This option can be selected if the WINDOWS directory and the Win2NCS application reside on a network drive and are shared by several users.  A different configuration file is created for each workstation and is placed on drive C: in the root directory of the workstation.  The name of the configuration file is WIN2NCS.INI.


Configuration Files Are Based on Logged In Name

This option can be selected if the WINDOWS directory and the Win2NCS application reside on a network drive and are shared by several users.  Each user is assigned a different configuration file based on the user's login name (including the NDS* context if available), and those configuration files are placed in the default Win2NCS directory.  The configuration files are prefixed with user and followed by a number and .INI (for example, USR1.INI, USR2.INI, etc.).  If the user is not logged in, a temporary configuration file called TPMXXX.INI is assigned.

This selection will use different configuration files when the user logs in to Directory Services as compared to logging in to a NetWare* 3* bindery server.  The configuration file will be found for Directory Services login based on the complete context and for the bindery login based on only the username.  If the users at a site log in to either Directory Services or a bindery server, the network supervisor might want to use selection 5 (Configuration Files Are Based on Username) for managing configuration files.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuration Files Are Based on Username

This option can be selected if the WINDOWS directory and the Win2NCS application reside on a network drive and are shared by several users.  Each user is assigned a different configuration file based on the username (common name for NDS* login), and those configuration files are placed in the default Win2NCS directory.  The configuration files are prefixed with user and followed by a number and .INI (for example, USR1.INI, USR2.INI, etc.).  If the user is not logged in, a temporary configuration file called TMPXXX.INI is assigned.

This selection should allow the use of one configuration file per user even if the user logs in to both Directory Services or a NetWare* 3 bindery server and it might be preferable to choose selection 2 (Configuration Files Based on Logged In Name).

The name of the configuration file in use by the user is displayed in the title of the Win2NCS mapping utility main display.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contents

Overview

What Is Win2NCS

Installing Win2NCS

Setting Up Win2NCS

Overview

Setting Security

Testing Security

Restricting Servers Searched for Modems

Mapping Communication Ports

Setting Options

Dialing In to and Out of the Network

Overview

Dialing Out of the Network

Dialing In to the Network

Answering Questions

Troubleshooting Configuration Issues

Troubleshooting Resource Issues

Troubleshooting Performance Issues

Troubleshooting Compatibility Issues

Other Important Troubleshooting Tips

References

Trademarks, Copyright, and Disclaimer


Controlling Your Host Machine Remotely
Controlling Your Host Workstation Remotely

To control your host workstation remotely

1.	Dial in to the network using the remote component of the communications package on the remote PC.

For specific instructions on how to dial in, refer to the third-party communications package documentation.

The Service Selector window appears.

2.	In the Service Selector window, type your username and then press Enter.

3.	Select the session you want to access.

Generally, you have access to only one session because you have access to only one dedicated host on the LAN network.

4.	Type the number of this session and then press Enter.

5.	(Conditional) If necessary, enter your remote client password.

You are now connected into the host workstation.

Note:  With some third-party communications packages, it might take several seconds to display the host's monitor contents.


Creating a SETUP.INI file

To create a SETUP.INI file

1.	With a text editor, create a file named SETUP.INI.

2.	In this file, create a section called [Setup].

3.	Under [Setup], make the following entries:

Networked=0, 1, 2, 3, or 4

InstallPath=Path to install

COM1=Mapping of COM1

COM2=Mapping of COM2

COM3=Mapping of COM3

COM4=Mapping of COM4

COM5=Mapping of COM5

COM6=Mapping of COM6

COM7=Mapping of COM7

COM8=Mapping of COM8

Related Topics

Example SETUP.INI file


Custom Install

Custom Install is generally used to install Win2NCS on the network or to select ports to be mapped in Windows** 95**.

When you use Custom Install, you must define how the configuration files are to be managed.  The y can be managed in the following ways:

Configuration File Is Created in Installed Directory

Configuration Files Are Based on Logged In Name

Configuration Files Are Always on Drive C:

Configuration Files Are Always in Windows Directory:

Configuration Files Are Based on Username

In Windows 95, you must assign the ports to be registered as Win2NCS ports by the Windows 95 Device Manager.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DOS Communications Applications

DOS communications programs cannot use the Win2NCS Redirector because they do not make use of the Microsoft** Communications APIs.


Default Push Button
Default Button

The Default button allows you to reset the Global Options to the preferred settings.  All settings are reset to the preferred settings.  The Save button must be clicked to save the defaults.


Defining Server Restrictions

To define server restrictions

1.	From the Options menu, select Define Server Restrictions.

2.	To select a server to restrict, do either of the following:

In the Available Servers list box, select the server name and then click Add.

Type the server name (you can use wildcard names) in the Restricted Servers field above the Restricted Servers list, and then press Enter.

The selected server appears in the Restricted Server list.

3.	Repeat Step 2 for other restricted servers you want to specify.

4.	To save your selections, click Save.


Delayed Messages

Messages on Windows** 95** might occur as much as a half second after an event occurs.  This is obvious when using the Modem program in the Control Panel.  The Modem program can connect to the port, find a "service in use" problem, and send you a message about it--but by the time you see the message, the Modem program will indicate that it is checking the next port.

Messages on Windows NT** might occur as much as 20 seconds after an event occurs.  However, messages usually will occur within one second.  This is due to the way that Windows NT task switches.  In extreme cases of a busy system, some Modem Lights messages can be lost due to the overflowing of the message queue.


Deleting a Server from the List

To delete a server from the list of restricted servers

1.	Select the server name in the Restricted Servers list box.

2.	Click Delete.

Note:  If a COM port is mapped to a particular server name (the Server Name radio button is selected on the Map Communications Ports window), then only the specified server is searched for available ports.


Dialin Group

The Dialin group is created automatically when NIAS installs on the file server.  It functions as a "virtual" port to which remote host workstations can be connected.  By redirecting the host workstation to the Dialin group, you can prevent the host from tying up one of the physical ports (and modems) on the NIAS server while waiting for a call.  The host will be connected to a physical port on the server only when you call in and request it.  This is a much more efficient use of the scarce communications resources.


Dialing In to the Network

Win2NCS allows you to dial in to the network and control a host workstation from your remote PC.  Win2NCS makes the host available to you by redirecting the host's communications ports to a virtual port on the network.  You can then request a session on the host and use it as if you were in the office.

Setting Up Your Host Workstation and Remote PC

Controlling Your Host Workstation Remotely

Troubleshooting: Remote Control Applications and Win2NCS Setup


Dialing Out of the Network

To dial out to a bulletin board service or to an Internet service provider using Win2NCS

1.	Double-click the Win2NCS icon to start the program.

2.	Respond to the security prompts.

3.	Type your network username and then press Tab.

If you are using a Novell* Internet Access Server (NIAS) 4.1 server, check the Prompt for Context check box and enter your username and context; then press Tab.

4.	(Conditional) If required, type your password and then press Tab.

5.	Type a name for your session.

6.	Click OK.

After you have set security, the Current Assignments/Connections dialog box appears, listing assigned ports and their status.  You can now dial out of the network using your third-party application.  Simply configure the application to use the COM port that you have redirected through Win2NCS.

If you want to monitor data transfer, see Using Modem Lights to Monitor Data Transfer

Related Topic

Mapping Communication Ports

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Differences Between 16 and 32 Bit Drivers
Differences between 16- and 32-bit Drivers

When using Windows **NT**, a 32-bit driver is used.

When using Windows 95**, the 32-bit driver is used as the default driver.  You can use the Global Options in the Win2NCS mapping utility to change the driver to the 16-bit driver.  However, the 16-bit driver does not support 32-bit applications.

So ,why would you ever use the 16-bit driver on Windows 95?

You use only 16-bit applications.

You troubleshoot problems with Win2NCS Redirection.

The 16 bit driver has the ability to display the progress of Win2NCS-to-NCS connection while the process is occurring, whereas the 32-bit driver can indicate the connection status only after the process is complete.

The last reason mentioned above can be significant, because the 16-bit driver can produce synchronous messages whereas the 32-bit driver can produce only asynchronous messages.

This difference can be extremely important in determining the state of the Windows 95 operating system.  When using the 32-bit driver under some conditions, you might think that the operating system is hung, whereas you will always be sure what the state of the operating system is when using the 16-bit driver.

Related Topics

Driver Selection

Limitations of the 32 Bit Driver

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Disable Win2NCS Redirection is Grayed Out

The Disable Win2NCS Redirection option is grayed out if Win2NCS services are currently in use.


Disabling Automatic Win2NCS Startup

If you do not want Win2NCS Redirection to be automatically invoked anymore, then disable Win2NCS Redirection on Windows Startup in the Global Options.


Disabling/Enabling Win2NCS Redirection

To disable port redirection

1.	Select Disable Win2NCS Redirection from the Options menu.

2.	Click Yes.

The color of the mapping utility screen changes to indicate that redirection is disabled, and the menu option changes to read Enable Win2NCS Redirection.

To enable redirection

1.	Select Enable Win2NCS Redirection from the Options menu.

The color of the mapping utility screen changes to indicate that redirection is enabled, and the menu option changes to read Enable Win2NCS Redirection.


Driver Selection

This option is available for Windows** 95** only.  This option is grayed for Windows 3.1 and the 16-bit driver is always selected.  When using Windows 95, the 32-bit driver is usually used (default selection).  You can switch to the 16-bit driver . However, switching to the 16-bit driver will prevent redirection of 32-bit applications.

See  Differences between 16- and 32-bit Drivers for information regarding why you might want to switch to the 16-bit driver.


Dynamic Mapping

Dynamic mapping refers to COM ports that can be redirected at the time that you are using a communications package.  At that time, a dialogue box appears allowing you to select how the redirection is to be performed.


Dynamic Mapping Is Not Supported

Dynamic mapping cannot be supported because messages cannot be displayed until the 32-bit driver is exited.


Dynamic Port Redirection Is Not Working

You do not see Win2NCS messages when using the Win2NCS mapping utility or an application that communicates with the COM port through Win2NCS.

Check with the network supervisor to make sure that the username and password that you are using has been assigned services by your NCS server.  Your network login name and password might not be assigned any services and you might have to use another username and password to acquire services.  You can also test the security see if this information is active.

If using Prompt for 4.x Context, make sure that you context is correct.

If you are using Windows** for Workgroups, you must disable the Microsoft**-compatible IPX*/SPX* driver so that the Novell* IPX/SPX driver will be used instead.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Example SETUP.INI file

The following is an example of a SETUP.INI file:

[Setup]

Networked=1

InstallPath=f:\winaps\win2ncs

COM1=UNMAPPED

COM2=DYNAMIC

COM3=TLV-NWC1,ANY_PORT,??????????????

COM4=TLV-NWC1,DIALIN,??????????????

When the above example SETUP.INI file is placed in the SETUP directory, the following occurs:

Win2NCS files is installed to the F:\WINAPS\WIN2NCS directory

Configuration files are managed based on user name

COM1 is left UNMAPPED

COM2 is DYNAMIC

COM3 is mapped to TLV-NWC1 [server name], ANY_PORT [general name], and ??????????????  [any specific name]

COM4 is mapped to TLV-NWC2 [server name], DIALIN [general name], and ??????????????  [any specific name]

COM5 through COM8 are left at previous mappings or default


Example of Changing Color Information

To change the colors for Alternate Color 1 to white background, black text, and red intensity, you would add the following entry in the [Nasi] section of your .INI file:

AltColor1=255,255,255;0,0,0;255,0,0

The format for the keywords is as follows:

AltColorx = Background Color; Text Color; Intensity Color

Colors are RGB colors that can be acquired from the Control Panel (Color ICON) when defining custom colors.


Express Install

The Express Install is recommended for most users and is the same for all platforms.  If you are not familiar with configuration file settings, Express Install is probably a better choice.  Follow the on-screen instructions to complete the Express Install.


Focus may not be Restored Correctly After a Win2NCS Redirection Message is Displayed
Focus Might Not Be Restored Correctly after a Win2NCS Redirection Message Is Displayed

When you are using Windows** NT** software, the cursor might not be restored correctly to the communications application window after a Win2NCS redirectional message is displayed.  It seems that in most cases, Windows NT ignores the System Modal capability of the Win2NCS redirectional messages, causing the communications application to run at the same time as the redirectional message.  And if the communication application changes the screen while the redirectional message is being displayed, the focus will be restored to the incorrect screen.

Although this can be a benefit, it can also cause problems where you will have to manually set the focus back to the communications applications window.


Hardware Flow Control

This option allows you to decide whether the hardware flow control is enabled by calls from the application (On Demand) or is permanently enabled (Always).  The default is On Demand.

Hardware flow control is the flow control between the NCS port and the modem.  With hardware flow control enabled, the baud rate of the port can usually be set to a higher rate than the modem baud rate without the fear of lost data.  With hardware flow control disabled, data can be lost if the transmitting port has a higher baud rate than the modem.

Some applications do not support hardware flow control or support either software or hardware flow control, but not both simultaneously.  If a user experiences data loss, slow file transfers, or disconnects during file transfers, setting this option to Always might solve the problem.


How Using Wildcards Will Affect Performance

Using wildcards (asterisk and question mark) with the General Name or Specific Name allows for filtering but will not increase performance, because the Win2NCS Redirector still needs to contact all NCS servers to request service information.


Important Information on Adding Win2NCS Users on a Networked System

Win2NCS will manage independent configuration files for a user on a networked Windows** system (by automatically generating or acquiring the correct configuration file on the fly if any setup option for managing configuration files is used--except Configuration File Is Created In Installed Directory).

Even when using a shared directory for Win2NCS, usually the Win2NCS setup utility must be run on each workstation to create program groups and icons for that workstation.  This operation will not reload new files but will only create program groups and icons.

This operation must be performed for all Windows 95** workstations.  Windows 95 also must have the local machines Registry updated.

It is highly recommended that each workstation use the Setup program to install or update Win2NCS to eliminate any possible problems.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Informational Messages Notification Time

This option is valid only if the Redirector Informational Messages option is enabled.  You can enter the number of seconds that the connection status will be displayed on the screen during a successful connection.  A zero indicates that the connection status will not be displayed.


InstallPath Section of SETUP.INI

This section of the SETUP.INI file specifies which directory the automated install places the Win2NCS files into.


Installing Support for Both Microsoft Networking and Novell Workstation Shell 4.0

To install support for both Microsoft** networking and Novell* Workstation Shell 4.0

1.	From inside Windows** for Workgroups, double-click the Network Setup icon.

2.	Click the Networks button.

3.	Choose Install Microsoft Windows Network, and then choose Other.

4.	Choose Novell NetWare (Workstation Shell 4.0 and above).

5.	Click OK.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Support for the IPX-NetBIOS Transport

To install support for the IPX-NetBIOS Transport

1.	Click the Drivers button and then the Add Adapter button.

2.	Choose IPX* Support driver (Monolithic) with NetBIOS transport.

3.	Click Close and then OK.

You will then receive two conflicting error dialogs.  The first one states: "You do not have an ODI* network driver installed and will not be able to connect to a Novell* server with Microsoft** Windows** Network until you install the driver.  Do you want to continue?"

4.	Click Yes.

The next dialog states: "You are running an ODI driver and have chosen to install an NDIS** driver.  The NDIS driver must be set up on a separate network adapter card other than the ODI driver.  Do you want to continue?"

5.	Click Yes.

The next dialog will prompt for Username, Workgroup, and Computer Name.

6.	Complete the information you are prompted for.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Win2NCS from the Network

Important:  If you have previously installed Win2NCS, you must first uninstall the previous version.

To install Win2NCS from the network

1.	Locate the Win2NCS system files.

Contact your network supervisor for access to these files.  By default, the files are located on the Novell* Internet Access Server (NIAS) 4.1 server in the SYS:SYSTEM\WIN2NCS subdirectory.

2.	Run SETUP.EXE from this directory.

If your network supervisor has automated the install process, skip Step 3 and go on to Step 4.

3.	Select either the Express Install or Custom Install.

4.	Follow the onscreen instructions.

Once you have installed Win2NCS, you must set up Win2NCS.

Related Topics

Important Information on Adding Win2NCS Users on a Networked System

Installing Win2NCS from the Novell Client CD

Overview of Setting Up Win2NCS

Manual Updating of Windows 3.1 Systems Using Shared Directory

Assigning COM Ports in Windows 95

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Win2NCS from the Novell Client CD

Note:  If you have previously installed Win2NCS, you must first uninstall the previous version.

To install Win2NCS from the Client CD

1.	Locate the Win2NCS directory on the client CD at PRODUCTS/WIN2NCS.

2.	Run SETUP.EXE from this directory.

3.	Select either the Express Install or Custom Install.

4.	Follow the on-screen instructions.

Once you have installed Win2NCS, you must set up Win2NCS.

Related Topics

Installing Win2NCS from the Network

Express Install

Custom Install

Overview of Setting Up Win2NCS

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Is There Ever a Need to Disable Win2NCS?

Generally, Win2NCS Redirection can always be left enabled even when it is not in use.  The part of the Win2NCS Redirector that monitors the COM API is fairly small and contains mostly discardable or movable code and data.  A large amount of code and data resides in memory only when Win2NCS Redirection is active.  When the last redirected connection is closed, the memory requirement again is small.  However, if an application is having problems communicating with a local port, Win2NCS Redirection can be disabled to make sure that the Win2NCS Redirector is not causing the problem.


It Takes a Long Time to Find Available Modems

If you work at a large site that has many NetWare* servers, it might take a long time to find available modems (acquire a service) when using Win2NCS Redirection.  For example, you might have four services available to you on two different NCS servers out of a total of 20 NCS servers.

Because the Redirector does not know which server your services reside on, it must contact each of the servers to request services information.  If your servers are some of the last servers to be contacted, the wait can be quite long, especially if some of the servers are on routers.  You can solve the problem in two ways:

Use the Define Server Restrictions option to select only the servers you would want to acquire services from.  Then, only the servers that you defined would be used for the query.

Use Manual Mapping with wildcards (asterisk and question mark) to restrict the servers searched.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Limitations of the 32 Bit Driver
Limitations of the 32-Bit Driver

Since the 32-bit driver can produce only asynchronous messages that occur after an operation has been fully completed, the following are limitations of the 32-bit driver:

COM Ports Cannot Be Overmapped

Dynamic Mapping Is Not Supported

Security On Line Requires That the Communication Application Be Restarted

Delayed Messages

Limited Messages during Connection and Configuration Process

Cannot Cancel during Redirection

Focus Might Not Be Restored Correctly after a Win2NCS Redirection Message Is Displayed


Limited Messages during Connection and Configuration Process

Messages such as search messages or other informational messages are not displayed.


Manual Updating of Windows 3.1 Systems Using Shared Directory

Although not recommended, manual intervention can be performed (Windows** 3.1 systems only) to add the Win2NCS program group and the Win2NCS mapping utility icon to the private WINDOWS directory.  Manual updating of Windows 3.1 requires that a shared system directory must be used by all users.

Once the Win2NCS group and icons have been installed on all Windows 3.x workstations, installation of Win2NCS updates needs to be run from only one workstation to update the Win2NCS files themselves.  In order to do this, the Win2NCS INSTALL directory must remain the same and a shared WINDOWS\SYSTEM directory must be used for all networked Windows users.  This is possible because the Win2NCS program group and icons under Windows do not change during the update.


Mapping Ports

You must map your computer's communication ports to servers with a modem pools.  If you have access to more than one Novell* Internet Access Server (NIAS) 4.1 server, reduce the amount of time required to search for available services by restricting the servers you will search before using the Mapping Communications Ports option.

To map communications ports

1.	From the Options menu, select Map Communications Ports.

The program detects and displays any ports previously configured.  These ports are displayed in the Map Communications Port window.  The Available Services list at the bottom of the window displays the available ports.

2.	Select the port you want to redirect.

Options that are not supported by the desktop operating system you are configuring will be grayed out.  For example, Windows** 3.x can share a local port with Win2NCS.  This is not true with Windows 95**.

3.	In the Select By box, specify the parts of the port name to display by clicking one of the radio buttons.

4.	In the Available Services list, select one of the following:

If you are configuring a dial-out port, select the desired port or group of ports.

If you are configuring a dial-in port, select a Dialin port group.

5.	Click Map or double-click the service you have selected in the Available Services list.

6.	(Conditional) If you are using Windows 3.x, click the Dynamic button if you want to map the port at the time you are using the third-party application.

7.	Repeat Steps 1 through 6 to map any other ports.

8.	To save your mappings and exit, click Save.

You return to the "Current Assignments/Connections" window.  You can close this window or leave it open.  Either way, the connection is active whenever you are logged in to the server.

You can also map a port manually or disable port redirection at any time.

Note:  If a port is marked "Local," then it is used by a device attached to the port on your PC.  If a port is "crossed-out" in the Status column, you cannot map that port or assign it to the local COM port.

Related Topic

Understanding the Mapping Utility Display

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Mapping Ports Manually

In addition to using the Map Communications Ports window, you can map ports manually by typing in the name of the port.

To map a port manually

1.	From the Options Menu, select Map Ports Manually.

2.	Type the information to define the server, general, and specific names.

You can use wildcards [asterisk (*) and question mark (?)] and absolute names for each one.

3.	Save the port names by clicking Accept.

4.	To return to the Win2NCS mapping utility, click Exit.

Note:  You can also disable port redirection at any time.


Maximum ECBs Requested

This entry is used only for OS/2** and Windows** 3.1 standard mode of operation.  Normally, the default value of 15 ECBs is sufficient.  However, if problems occur, this value can be either decreased to as little as 8 or increased to as much as 60 (if the IPX*/SPX* driver supports that many).

The Win2NCS application usually can work with as little as 8 ECBs if only one communications package is being executed.  However if more than one communications package is being executed simultaneously, the number of ECBs requested probably will have to be larger than 8.

Typically, an IPX/SPX driver will maintain 25 to 30 ECBs for use by IPX/SPX applications.  If 15 of these ECBs are reserved by Win2NCS, only 10 to 15 ECBs remain available for use by other IPX/SPX applications.  If other IPX/SPX applications will be running with Win2NCS, you might want to decrease the number of ECBs reserved by Win2NCS.

If the number of ECBs requested is set too low, a protection fault in NWIPXSPX.DLL could occur.  If this occurs, increase the number of requested ECBs.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Networked Section of SETUP.INI

This section specifies how the configuration files are managed.

0 = configuration files in installed directory

1 = configuration files to be base on logged in name

2 = configuration files to be always on drive C:

3 = configuration files to be in the WINDOWS directory

4 = configuration files based on User Name


No Communication Ports Assigned in Win 95
No Communication Ports Assigned in Windows 95

Communication ports are not assigned to Win2NCS if all COM ports (1 through 8) are already assigned to hardware.  If you have an 8-port COM board in your system, COM1 through COM8 probably have been assigned to that board.

To assign a COM port to Win2NCS

1.	Manually remove some of the COM port assignments using the Windows** 95** Control Panel (system icon).

2.	Run Win2NCS Setup again.

3.	Map the chosen COM ports to Win2NCS.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Notify Interval Time

Allows you to indicate the number of minutes that a Notify Process will wait prior to checking for the defined service.

Related Topic

Using the Notify Process to Monitor a Busy Port


OS/2 - 2.x, 3.x (Warp), and OS/2 Warp Connect
OS/2  v2.x, v3.x (Warp), and OS/2 Warp Connect

If running Windows** in OS/2** v2.x, v3.x (Warp), and OS/2 Warp Connect, standard mode must be used to invoke Windows or protection faults will occur in NWIPXSPX.DLL.

VxDs are not supported for OS/2 v2.x, v3.x (Warp), and OS/2 Warp Connect; therefore, any application that installs VxDs is not supported.

You must load TBMI2.COM (the Windows IPX* stack) in your AUTOEXEC.BAT prior to bringing up OS/2 v2.x, v3.x (Warp), and OS/2 Warp Connect.

Windows applications that attempt to install display or other Windows drivers will probably not work correctly.  This occurs most frequently with Remote Control applications.

Windows applications that are only marginally Windows-compliant probably will not work correctly.


Other Important Tips

Services Displayed in Win2NCS Mapping Utility but Not in Dynamic Redirection

Selecting the NASI Option in Applications

When Win2NCS Prompts for Security

Disable Win2NCS Redirection Is Grayed Out

Cannot Switch to another Application

Changing the Mapping of Redirected or Active COM Ports

Problems with Win2NCS after Reinstalling Window 95

16-bit Applications and Modems in Windows 95


Overview of Dialing In to and Out of the Network

Win2NCS allows you to dial out from the network to access bulletin boards, host computers, or other resources--or to dial in and remotely control a dedicated network workstation using third-party communication applications--by "redirecting" data to and from a Windows communication port.  Instead of going through a modem connected to the workstation's COM port, data is routed to a port controlled by NCS on the communications server.

To dial out using Win2NCS, you must have access to Win2NCS and a Windows communications application from the network workstation.

Dialing Out

To dial out through the modem pool using Win2NCS, you need to have access to Win2NCS and a Windows communications application on the network workstation.

Dialing In (Remote Control)

To dial in and remotely control a host workstation using Win2NCS, you need to have access to a supported third-party application on both the network workstation and on the remote PC.

Note:  Win2NCS does not currently work with Novell's Remote Access Dialer or the Windows** Mobile Dialer due to driver conflicts.

Related Topics

Dialing Out of the Network

Dialing In to the Network

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Installing Win2NCS

There are two ways to install Win2NCS:

From the Novell* Client CD

From the  network

In any case, Win2NCS will be functional only if you have a Novell* Internet Access Server (NIAS) 4.1 server.  Check with your network supervisor to ensure that you have rights to this server.

Note:  If you have previously installed Win2NCS, you must first uninstall the previous version.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up Win2NCS

Before you use Win2NCS for the first time, some basic configuration is necessary:

1.	You must set and test your security information to ensure that you can access the communications server.

2.	If there are several Novell* Internet Access Server (NIAS) 4.1 servers on your network, you should define the server restrictions so that Win2NCS searches only selected servers for available communications ports.

3.	You must map the communications ports you want Win2NCS to use for dialing out of or in to the network.

Once these features are set, you can access the network modem pool to dial bulletin board services and Internet service providers, or to dial in to the network to remotely control a host machine.

There are also several options you can set to customize Win2NCS.  These options can be set at any time.

Related Topics

Setting Security

Testing Security

Defining Server Restrictions

Mapping Ports

Setting Options

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Win2NCS

Win2NCS (previously called the NASI Redirector) allows you to dial out from the network through a pool of modems connected to the server to access bulletin boards, host computers, or other resources, or to dial in and remotely control a dedicated network workstation using third-party communications applications.

Win2NCS allows you to "redirect" data to and from a Windows** communication port.  Instead of going through a modem connected to the workstation's COM port, data is routed to a port controlled by the Novell* Connection Service (NCS) on the Novell Internet Access Server (NIAS) 4.1 server.  In this way, Win2NCS gives a sharing capability to modems similar to the capability that print servers have given to printers.  Instead of having a modem on each machine, you only need a modem pool on the server.

Note:  Novell also provides comparable software for Macintosh** workstations through a utility called Mac2NCS.  If you have Macintosh workstations on your network, they can also use the modem-sharing capabilities of the Novell* server.

Dialing Out

To dial out through the modem pool using Win2NCS, you need to have access to Win2NCS and a Windows communications application on the network workstation.

Dialing In (Remote Control)

To dial in and remotely control a host workstation using Win2NCS, you need to have access to a supported third-party application on both the network workstation and on the remote PC.  You will also need to configure your dial-up software.  Because Win2NCS works with many different dialers, follow the instructions included with your dial-up software.

Note:  Win2NCS does not currently work with Novell's Remote Access Dialer or the Windows Mobile Dialer due to driver conflicts. However, Win2NCS does work with third-party dialers that use the standard  Windows COMM driver (such as Trumpet WinSock).

Related Topic

Supported Operating Systems

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Port Query And Selection Criteria

This option allows you to determine what type of ports should be queried or selected.  The option defaults to Select Dial-In or Dial-Out Ports.  When Dial-In or Dial-Out Ports are selected and the Map Communications Ports option is selected, all ports on the servers will be queried and displayed.

If you map a port to "any" or to a wildcard capability [asterisk (*) and question mark (?)] and you have selected to direct communications application to that port, the port can be used as either a dial-in or dial-out port.

If you will be dialing out only, choose Select Dial-Out Ports Only.  When this selection is checked, only dial-out ports are displayed with the Map Communication Ports option, and the "any" wildcard selection [asterisk (*) and question mark (?)] will select only dial-out ports for redirection.


Problems with Win2NCS after Reinstalling Win 95
Problems with Win2NCS after Reinstalling Windows 95

If you had a problem with Windows** 95** (not related to Win2NCS) and decided to reinstall Windows 95, you might not have any port assignments after the reinstallation.

When you reinstalled Windows 95, the device manager searched for all available hardware to see if what was previously configured was correct.  Since Win2NCS does not use any hardware, the device manager assumed that those ports must have been configured incorrectly.  It therefore removed the assignments from Win2NCS and reassigned them as standard COM ports.

To reassign the COM ports

1.	Run Win2NCS Setup again.

Win2NCS will recognize those reassigned ports as probably not being attached to hardware and will ask you if you want to unassign those ports so that they can be reassigned.

2.	Click Yes.

The ports will be reassigned.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Prompt for Context

If Prompt User for 4.x Context is checked, you can enter your context.  It is not necessary to have a client that supports Directory Services in order to use Prompt for 4.x Context.

Context is valid only if the server is a Novell* Internet Access Servie (NIAS) 4.1 server.  However, if the client does not have Directory Sservices capabilities (NETx, Microsoft** Client without Directory Services, etc.), you must enter the context manually.


Public Session

The Public Session checkbox is used only for dial-in capability.  If this box is not checked, then the session is private and only users that dial in with the same username and password that were previously entered will be able to connect to your application.  If the Public Session is checked, then any dial-in NCS user can connect to your application.


Query Service Timeout

Allows you to set the maximum time that either the Win2NCS mapping utility or the Redirector will wait when trying to find services on any of the NCS servers.

The default time is 60 seconds, which is usually sufficient to find all services on the network.  However, if an NCS server is broadcasting to the network but filtering on a router does not allow a connection with or packets to be sent to that NCS server, the Win2NCS mapping utility or the Redirector will wait for the default 60 seconds before searching the next NCS server.

You can reduce the search time to as few as 4 seconds.


Question Mark (?)

When you type a question mark in any position of the server name, then a server with any characters in that position will match and be designated as a restricted server.

If you check the Restrict All Wild Card Servers check box and have a wildcard specified, then only servers starting with specified characters are checked for ports.


Redirector Informational Messages

If this option is enabled, informational messages such as Acquiring Services, Searching For Service, and Connection Status are displayed during the connection phase of the redirection process.  If this option is disabled, these messages are not displayed


Remote Control Applications and Win2NCS Setup

Scenario:  I use a remote control program that communicates from a client PC to a host PC.  Because my host PC will accept dial-in calls from the client PC, I assumed that I should define the NCS port as a dial-in port to accept connections to the host.  When I made the NCS port a dial-in port, the client PC would not communicate with the host PC.  However, after agonizing over the problem, I decided to define the NCS port as a dial-out port, and everything worked beautifully.  Do I have a problem with the dial-in port?

Response:  No.  The problem is in understanding what a dial-in port can be used for.  The purpose of a dial-in port is to allow for port sharing when multiple hosts might be waiting at the same port for a dial-in call.  When a call occurs at a dial-in port, NCS prompts you for a username and password.  If this is successful, then NCS displays a list of hosts that are waiting at that port and requests you to select which host to connect to.  When you select a host, the connection is made to the host PC.

Your problem probably occurred because the client PC did not know about the prompts and messages from NCS and, therefore, became confused and eventually broke the connection.  A dial-in port can work only if the client PC that is dialing in has an interactive screen that allows you to answer the questions posed by NCS, or if the client PC has a script language that can answer the questions posed by NCS.  Therefore, a dial-out port would normally be required as a service for host PCs.

Related Topics

Setting Up Your Host Machine and Remote PC

Controlling Your Host Machine Remotely

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Removing Windows for Workgroups' Support for Networks

To remove Windows for Workgroups' Support for Networks

1.	Double-click the Network Setup icon in Windows** for Workgroups 3.11.

2.	Click Networks.

3.	Select No Windows Support for Networks.

4.	Click OK.

Network Setup will notify you at this point that it has modified your NET.CFG, AUTOEXEC.BAT, SYSTEM.INI, WIN.INI, and PROTOCOL.INI files.

5.	Click Restart Computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Restricting Servers Searched for Modems

When you have access to more than one server, restricting the number of servers that are searched when using the Mapping Communications Ports option can greatly reduce the amount of time required to search for available services.

To restrict the servers searched, see Defining Server Restrictions.

To delete a server from the list, see Deleting a Server from the List.


Running Win2NCS Simultaneously with Other Applications

Having Win2NCS Redirection enabled should not significantly affect memory usage in other applications.  Even when Win2NCS Redirection occurs, the Win2NCS Redirector should not have a major effect on memory usage, because fixed memory is forced above the 1MB boundary.


Saving Window Coordinates

To save the current positions of the windows

1.	Select Save Windows Coordinates from the Options menu.

A check mark then appears next to the selection.

To discontinue saving window coordinates

1.	Select Save Windows Coordinates from the Options menu.

The check mark next to the selection disappears and the coordinates are no longer saved.


Security On Line Requires That The Communication Application Be Restarted
Security On-Line Requires That the Communication Application Be Restarted

If you turn off Save Security and the first Win2NCS Redirection occurs after Windows** is restarted, you will be prompted for security.  After security is entered, you must restart the Communications Application.  This is due to the fact that status of Open Failure had to be returned to the calling application in order to bring up the dialog box.


Selected Gray Screens

Allows you to enable or disable gray screens for the Map Communications Ports Dialog Box, Global Mapping Options Dialog Box, and Set Colors Dialog Box.  When the 3-D effect is enabled, gray screens on those dialog boxes generally give a better appearance.


Selecting Colors

You can use the Select Colors option in the Options menu to change the display colors of the Redirector and the Win2NCS mapping utility.  When you change the colors of the mapping utility, you can specify the color of the display when the Redirector is enabled and when it is disabled.

To change the display colors

1.	From the Options menu, choose Select Colors.

2.	Use the Assignment Option box at the top of the window to specify what aspect of the display you are changing.

3.	 In the Color Selection box, click the buttons next to the colors you want.

4.	To save your changes, click Save.

Color Information

You can also use one of the colors from the VGA SVGA color palette.  However, if a selection is made form the SVGA color palette, the installed display driver should be capable of producing at least 32,000 colors.  If the installed display driver is not capable of producing at least 32,000 colors, the colors might not be acceptable.

You can define the default alternate colors by making an entry in your .INI file (see Custom Install for more information on determining the configuration filename).

Related Topic

Example of changing color information.


Selecting the NASI Option in Applications

If you have a NASI option in an application, do not select it.  Normally, if an application has a NASI option, that option will communicate with a DOS TSR version.  The Win2NCS Redirector is a Windows** program.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Services Displayed in Win2NCS Mapping Utility but Not in Dynamic Redirection

The mapping utility displays all services associated with a user whether the services are busy or not.  This allows you to map any service for possible future use.  However, the Win2NCS Redirector will display only  those services that are not being used currently by someone else.  In this case, probably all the services are in use by others.


Session Name

This can be any name that you choose.  It will be used for the dial-in capability and allows for port sharing.


Setting Global Options

You can use Global Options to select settings that apply to all redirected COM ports.

To set global options

1.	From the Options menu, select Change Global Options.

2.	Set the fields on the Global Options dialog box as indicated below:

Driver Selection

Redirection On Windows Setup

Port Query And Selection Criteria

Hardware Flow Control

Redirector Informational Messages

3D Effect

Selected Gray Screens

Busy Port Notification

Informational Messages Notification Time

Notify Interval Time

Query Service Timeout

Maximum ECBs Requested

Default Push Button

3.	When you have finished making selections, click Save.


Setting Maximum Ports

Use this option to specify how many ports are displayed in the Mapping Communications Ports window.  When you choose this option, a Maximum Ports window is displayed.

To set the maximum ports

1.	Choose Set Maximum Ports from the Options menu.

2.	Type the maximum number of ports.

3.	Click Save.

The actual number of ports that can be accessed is determined by the third-party applications.  Therefore, even though you might specify eight ports in Win2NCS, you might not be able to access all eight.


Setting Options

In addition to setting up basic functions in Win2NCS, you can also set several other options.  These include the following:

Setting Global Options

Setting Maximum Ports

Selecting Display Colors

Tracing Port Data

Saving Window Coordinates


Setting Security

You can enter your username, password, and session name in Win2NCS and then choose options that will define your Win2NCS session.  Security is required by Win2NCS to determine which services are available to you.  Your network supervisor has determined what you can access via Win2NCS.  You can also save this information for future use.

To set your security information

1.	Choose Set Win2NCS Security from the Options menu.

2.	Enter a valid username, password, and session name in the corresponding fields in the Security dialog box.

3.	Check the Save Security check box to save these settings for future use.

If Save Security is checked (default), the password is encrypted and saved to a file.  The next time that Windows** is started, the password is decrypted and used for the security.

If Save Security is unchecked, the you will have to enter the password whenever Windows is restarted as well as the first time that Redirection takes place or the first time that the mapping utility is used.

4.	If you want to make your session available to any dial-in user, click the Public Session check box.

5.	If you are connected to a Novell* Internet Access Server (NIAS) 4.1 server, click Prompt for Context to enter your context, and then type your context in the Context field.

This information can be inserted automatically.

6.	Click OK to set security.

Once you have entered your security information, you will want to test the security information to make sure it is valid.  See Testing Security.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Win2NCS on Networked Windows PCs

To set up Win2NCS on networked PCs

1.	Make sure that during installation you selected a location for the Win2NCS files that is accessible by all users and that separate configuration files are managed for each Win2NCS user by choosing one of the following ways:

Configuration Files Are Based on Logged In Name

Configuration Files Are Always on Drive C:

Configuration Files Are Always in WINDOWS Directory:

Configuration Files Are Based on Username

NOTE:  If you have not selected a location for the Win2NCS files that is accessible by all users, you must uninstall Win2NCS and then select an accessible location when you reinstall Win2NCS.

2.	Choose an installed directory that is accessible to all users.

3.	Run the setup utility on each workstation with the same parameters to install the program group and Icons (Windows** 95** will also update the local Registry).

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Your Host Machine and Remote PC
Setting Up Your Host Workstation and Remote PC

To use Win2NCS to dial in to the network

1.	Install Win2NCS on your LAN (host) workstation.

2.	Map the COM port to the NCS DIALIN group.

3.	Install a supported communications package on the LAN workstation.

These packages include pcANYWHERE**, ReachOut**, PROCOMM**, LapLink**, CarbonCopy, etc.

4.	Install the remote component of the communications package on the remote PC.

For specific instructions on how to dial in, refer to the third-party communications package documentation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Sharing an Install Directory for Different Platforms

You can use a shared directory to install Win2NCS on all operating systems including Windows** 3.1, Windows 95**, Windows for Workgroups, and Windows running under OS/2**.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Supported Operating Systems

Win2NCS supports the following operating systems with some limitations when executing Windows** communications applications:

Windows 3.1 Enhanced Mode

Windows 3.1 Standard Mode

Windows 95** (16- and 32-bit applications)

Windows NT** (16- and 32-bit applications)

OS/2** v2.x, v3.x (Warp), and OS/2 Warp Connect

Windows for Workgroups 3.11

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Telling an Application to Use Win2NCS Redirection

To indicate that you would like to use Win2NCS Redirection from your application in Windows** 3.x

1.	Choose the port that has been redirected.  See Mapping Ports.

To indicate that you would like to use Win2NCS Redirection from your application in Windows 95** or Windows NT**

1.	Select a modem that has been defined using a Win2NCS port.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Testing Security

Once you have entered your security information in the Win2NCS Security dialog box, you should test this information for accuracy.

To test your security information

1.	Choose Test Win2NCS Security from the Options menu.

The dialog box appears.

2.	From the Available Servers list, select the server you want to test your security information for.

The name of the server selected appears in the Server to Test  list box.

3.	Click Test.

If your security information is valid, you can proceed with your Win2NCS session.

If your security information is invalid, check the information you entered in the Set Win2NCS Security dialog box for accuracy.  See Setting Security.

If you are not sure what you security information should be, contact your network supervisor for your correct username and password.

4.	Click OK.

5.	Click Cancel to close the Test Security dialog box.


The Modems Frequently Disconnect

Usually, modem disconnects are caused by either bad lines or an incorrect modem selection.

Make sure that you have the correct modem selection.  Selecting a modem that you might think is near to your modem could cause problems.

If you are using a pool of modems, make sure that if you used a wildcard selection (asterisk and question mark) with the Win2NCS mapping utility, all possible ports in the wildcard selection have modems that are identical.

To see if it is a modem problem

1.	Map a unique service to a COM port using the Win2NCS mapping utility.

2.	If using Windows** 95**, use the Modem program in the Control Panel to determine the modem type.  If you are not using Windows 95, then make sure that you assign the correct modem to the application.

3.	Run the application to see if it works better.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Time to Redirect Is Slow

If your communications port mapping is usually fast, but has recently become slower and displays a Searching Server message, your network might have an NCS server that is broadcasting to your network but will not allow Win2NCS to contact that server.  Try the following:

Ask the network supervisor to put a filter on the router to stop these broadcasts to the network.

Set the Query Service Timeout in the Global Options to a lower value to terminate the search earlier.


Tracing Port Data

Use this option to trace all data sent to or received from the port and to store the data in a log file in either a formatted or unformatted state.

To trace port data

1.	Choose Trace Port Data from the Options menu.

2.	Select the Enable Port Trace check box.

3.	(Optional) Check the Trace Reads check box.

If Trace Reads is selected, the trace program records the incoming data.

4.	(Optional ) Check the Trace Writes check box.

If Trace Writes is selected, the trace program records the outgoing data.

5.	(Optional ) Check the Format Data check box.

If Format Data is selected, the trace program adds carriage returns and line feeds so that the data does not exceed the line length.  Also, any character that is not a standard ASCII alpha-numeric or special character is converted to a period.  When saved in this form, any ASCII editor will be able to view the data.

If Format Data is not selected (unchecked), the data is stored in a binary format and will have to be read with a special editor.

6.	Click Save.

Tracing data might cause failures when writing to a file.  This will occur on any pre-emptive 16-bit applications and most 32-bit applications.  When a failure occurs writing the data to a file, the tracing is disabled for that redirection and you are notified.

Different log files are created for each redirection.  Log files are stored in the directory where the Win2NCS files are located and are named based on the time they were created.  A .LOG extension is added to these files.  You can identify the latest log file by the date and time stamp of the log files.


Trademarks
Trademarks, Copyright, and Disclaimer

Copyright © 1996-1998 Novell, Inc.  All rights reserved.  No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

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

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to make changes to any and all parts of NetWare software, at any time, without any obligation to notify any person or entity of such changes.

Novell Trademarks

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

IntranetWare is a trademark of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

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

NetWare 3 is a trademark of Novell, Inc.

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

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

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

Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Third-Party Trademarks

3Com is a registered trademark of 3Com Corporation.

LapLink is a trademark of Traveling Software, Inc.

Macintosh is a registered trademark of Apple Computer, Inc.

Microsoft is a registered trademark of Microsoft Corporation.

Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP.

OS/2 is a registered trademark of international Business Machines Corporation.

pcANYWHERE is a registered trademark of Symantec Corporation.

PROCOMM is a registered trademark of DataStorm Technologies, Inc.

ReachOut is a registered trademark of Stac, Inc.

Windows is a registered trademark of Microsoft Corporation.

Windows 95 is a trademark of Microsoft Corporation.

Windows NT is a registered trademark of Microsoft Corporation.


Troubleshooting Compatibility Issues

Windows for Workgroups

Remote Control Applications and Win2NCS Setup

Windows Communications Applications

DOS Communications Applications

Sharing an Install Directory for Different Platforms


Troubleshooting Configuration Issues

COM Port Not Redirected

Dynamic Port Redirection Is Not Working

Telling an Application to Use Win2NCS Redirection

Disabling Automatic Win2NCS Startup

While Running OS/2, a GPF in NWIPXSPX.DLL Occurs.

Setting Up Win2NCS on Networked Windows PCs

Changing the Way Configuration Files Are Handled without Running Setup Again

Differences between 16- and 32-Bit Drivers


Troubleshooting Performance Issues

Time to Redirect Is Slow

It Takes a Long Time to Find Available Modems

How Using Wildcards Will Affect Performance

The Modems Frequently Disconnect

The Communication Port is Busy

Asynchronous E-mail Gateway does not Periodically Download Messages


Troubleshooting Resource Issues

Running Win2NCS Simultaneously with Other Applications

Is There Ever a Need to Disable Win2NCS?

No Communication Ports Assigned in Windows 95


Understanding the Mapping Utility Display

The following is a description of the icons that appear in the Win2NCS mapping utility.

All Services  (16-bit driver only)  If a port is not in use and can be used as either a local connection to the local COM port or a remote connection to a Win2NCS port, this icon is displayed.

Win2NCS Only  Indicates that a port is not a local COM port but is available for a remote connection to a Win2NCS port.

Not Available  (32-bit driver only)  Indicates that a port is not a local port and has not been added as a Win2NCS port.

Win2NCS Not Available  For the 16-bit driver, indicates that Win2NCS Redirection is disabled.  For the 32-bit driver, indicates that the port has been assigned as a Win2NCS port but has not been enabled.  Mapping can still be performed, but redirection to Win2NCS will not occur until Win2NCS Redirection is enabled.

Active Server   The Active Server icon indicates that  an application is currently connected to Win2NCS on that COM port.  The current port connection information is displayed in the Intensity color.

Local Usage  (16-bit driver only)  Indicates that the COM port is active and currently directed to the local port.  The current port connection information is displayed in the Intensity color.

Local Defined  (32-bit driver only)  Indicates that a local port has been assigned to that COM port.  This port cannot be mapped or redirected.

     Mouse  Indicates that the mouse is attached to the defined local port and cannot be mapped or redirected.


Uninstalling Previous Versions of Win2NCS

Win2NCS Uninstall allows you to uninstall a previously installed version of Win2NCS using the Uninstall utility included with the previous version.  Uninstallation of a previous version must be completed before a new version is installed.

The Uninstall utility will uninstall either all Win2NCS objects or only the Win2NCS User objects.  When running Win2NCS Uninstall, you will be notified as to which objects are being removed.

To uninstall Win2NCS

1.	Double-click the Win2NCS Uninstall icon located in the old Win2NCS program group to start the utility.

2.	Check the check boxes corresponding to the objects you want to uninstall.

You might want to keep your configuration files or your port assignments for use in the latest version of Win2NCS.

3.	Click Uninstall.

A status window appears, indicating which objects are being removed.

4.	If non-Win2NCS files are found in the INSTALL directory, you will be asked whether those files should be removed.  Click Yes or No.

The selected files lected are removed from the directory.

The INSTALL directory will not be removed if any of the following is found in it:

Subdirectory

Read-only file

Hidden file

System file

The following will never be removed from the INSTALL directory:

Any subdirectories

Any read only files

Any hidden files

Any system files.

The Win2NCS INSTALL directory will not be removed if running Windows** 3.1.

Note:  In versions of Win2NCS earlier than 2.10, this utility is called NASI Uninstall.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using Modem Lights to Monitor Data Transfer

Modem Lights displays indicators for Read and Send Data, Carrier Detect, Data Set Ready, and Clear To Send similar to the LED indicators on an external modem.

To use Modem Llights to monitor data transfer

1.	To start the program, double-click the Win2NCS Modem Lights icon located in the program box.

2.	From the Port to Monitor list, select the communications port you want to monitor, and then click the OK button.

By default, the Modem Lights display appears in the lower-righthand corner of your screen.  If the display is moved to a different position on the screen, it will return to its last position when used again.


Using Win2NCS with Windows for Workgroups Peer-to-Peer Functionality

When using Microsoft’s NWLINK.386 driver, Win2NCS will fail to make an SPX* connection to any Novell* Internet Access Server (NIAS) 4.1 server.  Switching to VIPX.386 will solve this problem, but it usually requires disabling the peer-to-peer functionality of Windows for Workgroups.

To switch from using NWLINK.386 to VIPX.386 while retaining peer-to-peer functionality

1.	Remove Windows for Workgroups' support for networks.

2.	Install support for both Microsoft** networking and Novell Workstation Shell 4.0.

3.	While still in Network Setup, install support for the IPX*-NetBIOS transport.

4.	After exiting the Network Setup dialog box, you are prompted to install various files.

4a. If prompted to replace: The files for Novell* NetWare* (Workstation Shell 4.0 and later) are currently installed on your computer@, click No.

4b. If prompted to replace: The files for IPX Support Driver (Monolithic) with NetBIOS transport are currently installed on your computer@ click No.

4c. Answer Yes to any other files that need copying.

Network Setup then notifies you that it has modified your NET.CFG, AUTOEXEC.BAT, SYSTEM.INI, WIN.INI, and PROTOCOL.INI files.

5.	Click Restart Computer.

This procedure allows you to use peer-to-peer functionality by tunneling the packets through VIPX.386.  This allows full Novell SPX support for applications such as Win2NCS without disabling peer-to-peer file and print sharing.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using the Notify Process to Monitor a Busy Port

If the communications port you want to access is in use, Win2NCS can monitor that port and notify you when the port is available.

The Unavailable Win2NCS Service Message Box appears if you attempt to connect to a port that is already in use. This message indicates the Server Name, General Name, and Specific Name of the services in use. From this window, you can choose to monitor a busy communications port.

To monitor a busy communications port

1.	In the Unavailable Win2NCS Service Message Box, click Notify.

The notify process begins. The communications port will be checked at the time interval indicated in the Notify Interval Time option in Global Options.

When the communications port becomes available, an alert will notify you. Click OK and retry your connection.


When Win2NCS Prompts for Security

If the Save Security check box is checked in the Set Win2NCS Security option of the Win2NCS mapping utility, you will be prompted for security only once and never again, even if you reboot the system.  However, if Save Security is unchecked, the first time you use either the Win2NCS mapping utility or Redirector after Windows** is invoked, you will be prompted for security.

When you use the Redirector and select the Cancel button in the Services dialog box, you will be prompted for security the next time you use the Redirector.  If an error such as Service Not Found or Service In Use occurs during Win2NCS Redirection , you will be prompted for security the next time you use the Redirector.

When prompted for security, press Enter to accept the previously entered security information.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


While running OS/2, a GPFin NWIPXSPX.DLL occurs.
While Running OS/2, a GPFin NWIPXSPX.DLL Occurs

To correct the problem

1.	Load Windows** in standard mode.

2.	If that does not solve the problem, increase the Maximum ECBs Requested  value in the Global Options.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Wildcards

To specify a wildcard

1	Type a server name in the Restricted Servers field and include an asterisk (*) or a question mark (?) in the name.

2.	Press Enter to add the wildcard server name to the list of servers.


Win2NCS Redirection on Windows Setup

If this option is enabled (default), Win2NCS Redirection will be enabled each time you start Windows**.  When a communications application is run, Win2NCS Redirection will occur if that port is mapped.

If this option is disabled, you must enable Win2NCS Redirection prior to running a communications application if redirection is desired.  Win2NCS Redirection can be enabled by selecting Enable Win2NCS Redirection from the Options menu or by selecting the Enable Win2NCS Redirection icon in the program group.


Windows 3.1 Enhanced Mode

Most communications applications that call the Windows** communications APIs are supported.


Windows 3.1 Standard Mode

Most communications applications that do not install VxDs are supported.  VxDs are not supported in standard mode.

When using standard mode, you must load TBMI2.COM (the standard mode IPX** stack) in DOS prior to loading Windows**.


Windows 95 (16 and 32 bit applications)
Windows 95 (16- and 32-bit applications)

Both Windows** 95** and Windows 3.1 communications applications are supported if the 32-bit driver (default) is used.  If the 16-bit driver is used, only Windows 3.1 communications applications are supported.


Windows Communications Applications

Win2NCS should work with all communications applications that make use of standard Microsoft** communications APIs.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Windows for Workgroups 3.11

Windows for Workgroups should support the same applications as Windows** 3.1 Enhanced Mode if the Microsoft** IPX*/SPX* Compatible Transport Driver is not installed.  Not installing this driver will cause the Novell IPX/SPX Driver to be used.

When using the Novell IPX/SPX driver, NetBIOS packets are not routed.

If the Microsoft IPX/SPX Compatible Driver is used, the mapping utility and redirector will probably hang, requiring a reboot of the workstation.  This is due to bugs in the SPX implementation of the Microsoft IPX/SPX Compatible Driver.


Windows for Workgroups 3.11 Cannot Find Any Services

If Windows for Workgroups 3.11 cannot find any services, remove support for Microsoft Networking by removing the IPX/SPX compatible driver selection in Windows** For Workgroups 3.11. This enables the Novell VLMs to support IPX/SPX capability.

To remove support for Microsoft** Networking permanently

Note: If you plan to use it sometime in the future complete only steps 1 through 5.

1.	Double-click the Network icon in the Program Manager.

2.	Double-click Network Setup.

3.	Click the Drivers button.

4.	Highlight IPX/SPX Compatible Transport with NetBIOS in the Drivers box.

5.	Click the Remove button and follow the instructions.

Stop here and restart windows if you don’t want to remove support for Microsoft Networking permanently.

6.	In the Network Setup window select Networks.

7.	Select the radio button on Install Windows support for the following network only, at the bottom of the window.

8.	Use the scroll bar to locate Novell NetWare (Workstation shell 4.0 and above).

9.	Click OK on both windows.

10.	Restart Window for changes to take effect.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Windows NT (16 and 32 bit applications)
Windows NT (16- and 32-bit applications)

Both Windows** 32-bit communications applications and Windows 3.1 16-bit communications applications are supported.

Many Windows 32-bit communications applications were written to only support Windows** 95** (for example, LapLink** for Windows 95 and Qmodem 95) and, therefore, will not run on Windows NT**.

Most Windows 3.1 remote communications applications will not run on Windows NT because they were not designed to do so.

Any communications application that uses VxDs (virtual drivers) will not run on Windows NT because Windows NT does not support them.


Windows for Workgroups

Windows for Workgroups 3.11 Cannot Find Any Services

Using Win2NCS with Windows for Workgroups Peer-to-Peer Functionality