			      NS Open for Windows
				 Version 4.02

		  (C)opyright 1995 Walker Richer & Quinn Inc.

---------------------------------------------------------------------------
				  Contents
---------------------------------------------------------------------------

* Reflection for Windows Emulator 4.10
* Tested TCP/IP stacks
* Troubleshooting Windows Sockets 

---------------------------------------------------------------------------
		     Reflection for Windows Emulator 4.10
---------------------------------------------------------------------------

NS Open operates with Reflection and a Windows Sockets Compliant TCP/IP 
stack to allow NS/VT access to HP 3000s using Reflection for Windows 
version 4.1 and above.  Reflection for Windows uses RNNSVT.DLL, shipped 
with NS Open, for this support. 

You must have Version 4.2 or higher of Reflection for Windows to use WRQ's 
fast file transfer with NS Open.  There may be other limitations specific 
to your TCP/IP stack.

WINSOCK.DLL is provided with your TCP/IP network software. 

After starting Reflection, select the VT-MGR Connection Type.

---------------------------------------------------------------------------
			     Tested TCP/IP stacks 
---------------------------------------------------------------------------

WRQ has tested the following TCP/IP stacks with RNNSVT.DLL:

DOS-based TCP/IP stacks that provide WINSOCK.DLL:
=================================================

Version No.        Product                      Vendor
-----------        -------                      ------
2.2                Reflection Network Series:   WRQ
		      3000 Connection
		      TCP Connection
		   
4.1                LAN Workplace for DOS        Novell

1.1                Microsoft Windows Sockets    Microsoft Corporation

2.2                PC/TCP                       FTP Software

1.0                TCP/IP for Windows           Microsoft Corporation
		   for Workgroups               


Windows-based TCP/IP stacks that provide WINSOCK.DLL:
=====================================================

Version No.        Product                       Vendor
-----------        -------                       ------

3.10               Chameleon                     NetManage, Inc.


Other TCP/IP stack vendors that provide WINSOCK.DLL:
====================================================

*  Microsoft Windows NT
*  IBM TCP/IP version 2.0 for OS/2 with DOS/Windows access kit

---------------------------------------------------------------------------
			Troubleshooting Windows Sockets
---------------------------------------------------------------------------

Windows Sockets Error Messages
==============================

The following errors may be displayed in Reflection if you are not 
configured correctly.  

"Cannot find WINSOCK.DLL-Cannot load connection-specific library"

When you select the VT-MGR Connection Type in Reflection for Windows 
version 4.1 or above, Reflection does the following in an attempt to 
establish a connection:

1. Reflection first checks to see if a file named VTMGR.EXE (the NS/VT 
   executable file available from Walker Richer & Quinn) has been loaded 
   in DOS.

2. If VTMGR.EXE is not detected, then Reflection loads RNNSVT.DLL,
   the NS Open module.

3. As RNNSVT.DLL loads, it attempts to load the WINSOCK.DLL file included 
   with your network software.  RNNSVT searches for WINSOCK.DLL in the 
   following order:

   * The Reflection directory (by default, \RWIN)
   * The Windows directory
   * The Windows \SYSTEM subdirectory
   * Directories listed in the PATH statement of the AUTOEXEC.BAT file

If Reflection cannot locate any of the files in the above three steps, 
then the "Cannot find WINSOCK.DLL-Cannot load connection-specific library" 
error message displays.

If you're using a TCP/IP that provides WINSOCK.DLL and you cannot find
WINSOCK.DLL in the files provided by your network vendor (step #3 above
failed), contact your network vendor.

"Unable to Connect to Host"

If you receive the above error message, do the following:

1.  Verify that the name and IP address of the host you are trying to 
    connect to is in the HOSTS file.  Check  your vendor's documentation 
    for information on where the HOSTS file can be found.

2.  Try connecting using the IP address of the host rather than the host 
    name.

3.  If you cannot connect using the IP address, check your vendor's
    documentation on troubleshooting your network software.

FTP's PC/TCP 
============

You may experience problems with flow control and sessions hanging with 
FTP's PC/TCP when the packet sent by the HP is larger than the PC's 
current TCP window.  This can happen with block mode applications when 
large screens of data are sent from the host to PC.  The HP does not 
fragment the packet at the TCP level.  With FTP, the FTP window size may 
not be updated and the session hangs.

If you experience this problem, raise FTP's window size.  Modify PCTCP.INI 
and change the entry for Window= from the default (2048) to 4096.  Some 
applications may require a larger window size.

IBM TCPIP for DOS
=================

You must have version 2.1.0.4 or above of the TCP INET Protocol Control 
Program to run with NS Open.

Microsoft TCP/IP 
================

When attempting a connection to an HP 3000 host using Microsoft TCP/IP for
Windows for Workgroups version 1.1, you cannot close a connection attempt
to a TCP/IP host that does not support NS/VT.  The Failure to Connect 
message is not returned to the NSVT protocol, and the connection attempt 
will not time out.  The only way to close the session is to restart 
Windows.  Confirm that you have a valid IP address or host name to an 
NS/VT host before attempting to make a connection.

TCP/IP for Windows for Workgroups or LAN Manager 
================================================

You may experience periodic hangs when sending or receiving large binary
files to fast hosts over the Microsoft TCP/IP stack.  After the transfer 
fails, Reflection displays the message "Unable to Transfer file--Transfer 
link failed".  After this message, the session is hung.  To resume your 
session, select Close from the Connection menu and then reconnect.  To 
avoid this problem, change the Transfer Link to 7-bit in the File Transfer 
Setup dialog box.

OS/2 and NDIS with ODI
======================

If you're using OS/2, do not use ODINSUP to operate with ODI and NDIS in 
an OS/2 enviroment.  Instead, use ODI2NDI, supplied by IBM.

Security 3000 Users
===================

If you use VESOFT's Security 3000 application to make connections from one
HP 3000 to another without entering all the passwords required on the 
second host, you may experience problems using NS Open.  You should disable 
the feature that allows you to bypass the security on the second host.

To do this, add the line

   $NO-HOST-CHECK @.<domain>.<organization>

to the file SECURCON.DATA.SECURITY *before* the first HOST= line in the 
file.  Substitute your domain and organization names for the <domain> and 
<organization>.

**Note: NS Open dynamically assigns node, domain, and organization values.
If the second host requires specific node, domain, and organization 
values, add the appropriate values for these keywords in RNAPPS.INI in 
your Windows directory.

If you have version 23.10109 of Security 3000, you may need to remove the
HOST= line altogether.
