input.txt

CSLIB, a C++ database library.

RELEASE NOTES 
Remote Access Service Version 3.51

To easily view this file on screen, maximize the 
Notepad window, and then, from the Edit menu, 
choose Word Wrap.

CONTENTS ----------------------------------------

GENERAL NOTES
   Starting the Remote Access Server
   Browsing Remote Networks
   RAS Authentication
   Using Winchat with RAS
   Registry Key Name Changes and Additions
   RAS Compression
   Remote Access Support for Security Dynamics ACE Server
   Shadow RAM Conflicts
   NetBEUI Bindings on Computers with Multiple Network Cards 
   Using RAS with PCMCIA Cards
   
CONNECTING TO WINDOWS NT 3.51 RAS SERVERS
WITH THIRD-PARTY PPP CLIENTS
   NetManage Chameleon and Chameleon NFS 
     Version 4.1 Clients Required
   Third-Party FTP Software
   Wollongong Software

CONNECTING TO THIRD-PARTY PPP SERVERS
WITH WINDOWS NT 3.51 RAS CLIENTS
   Connecting to Internet Service Providers 
     that Use Older PPP Software
   Cisco Router Software
   3Com Access Builder Software
   Using Terminal Mode in RAS
   PPP Service Providers

RAS AND TCP/IP
   Resetting DHCP Leases on RAS Servers

RAS AND IPX
   Using NetBIOS Applications on IPX
   Using Shiva Remote Version 3.2 Client Software and IPX

ISDN
   Reinstalling RAS with ISDN
   Removing and Adding an ISDN Port to RAS Configuration
   Installing a PCIMAC ISDN Card on 
     a Gateway 2000 Pentium
   Installing New Modems with ISDN Cards

X.25 NETWORKS
   Eicon Drivers
   Configuring Null Modem Connections on X.25 Networks
   Creating Reliable Links Using Dial-up PADs
   Configuring a RAS Server for X.25
   X.25 Buffering
   Server Bandwidth and the Total Number of Clients
   Troubleshooting Remote Disconnections

FREQUENTLY ASKED QUESTIONS

-------------------------------------------------

For best printed results, open this document 
in Windows NT Write or another word processor, 
select the entire document, set the margins, and 
then format the text in 10 point Courier before printing.


=================================================
GENERAL NOTES
=================================================

Starting the Remote Access Server
---------------------------------
If the Remote Access server fails to start, check the Windows NT Event Viewer for more information.


Browsing Remote Networks
------------------------
To browse a remote network, the remote RAS computer must belong to a workgroup or domain on the network.  If the computer is not a member of a valid workgroup or domain on the network, the remote computer will not be able to browse the network from File Manager. 

Note:  You can still connect to servers directly using File Manager even if your RAS computer is not a member of a valid workgroup or domain. For example, in the File Manager Connect Network Drive dialog box, you can enter a server name and share name and connect to that server and share, even though the server does not appear in the browse box.


RAS Authentication
------------------
When you are dialing a number, the domain name you enter in the Authentication dialog box should be the Windows NT domain that the Windows NT RAS server is in. This is not the DNS domain name given by some PPP/SLIP providers. For example, you would enter accounting, not www.halcyon.com.

Using Winchat with RAS
----------------------
When using WINCHAT.EXE on a remote client, you must change a Registry key on the RAS server.

Using REGEDT32.EXE, change 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
  RemoteAccess\Parameters\NetBiosGateway\RemoteListen 

from 1 (the default) to 2.


Registry Key Name Changes and Additions
---------------------------------------
In the Windows NT Server RAS book, in Appendix C, the IPXRouter Parameters section incorrectly refers to the IPXRouter Registry key. The correct key name is NwLnkRip. All other information in the IPXRouter Parameters section is correct. The Registry path for this entry is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NwLnkRip\Parameters

In Appendix C, in the IP Parameters section, you should change all the parameters in a RAS server's Registry, not a RAS client's Registry. In the NdisWan Parameters section,  disregard paragraphs two and three. In the AsyncMac Parameters section, the XonXoff parameter is no longer a valid parameter.

The following Registry keys are not printed in Appendix C, "Modifying Registry Parameters". For information about each entry, see Remote Access Help.

PPP Subkey IPCP entries:
   AcceptVJCompression
   PriorityBasedOnSubNetwork
   RequestNameServerAddresses
   RequestVJCompression

RasArp Parameter
   FilterBroadcasts

Nbf Parameter
   InitUIFrames

NwlnkIpx Parameter
   DisableDialinNetbios


RAS Compression
---------------
Support for RAS software compression between Windows for Workgroups and Windows NT has been added.

The formulas used for calculating compression statistics in the Port Status dialog box are different for Windows for Workgroups 3.11 and Windows NT 3.51.

(1)	Bytes Transmitted/Received:
	
	On Windows for Workgroups, the values shown represent the
	number of bytes of data actually transmitted on the wire.
	Thus, 100K of user data that compressed by 40K will show
	as 60K Bytes Transmitted/Received.

	On Windows NT 3.51, the values shown represent the full
	number of bytes transferred.  In this example, 100K.

(2)	Percent of Compression:

	On all platforms RAS compression predetermines what data
	should or should not be compressed for optimal performance.

	On Windows for Workgroups 3.11 the "Compression%" value
	represents the ratio of compression achieved, accounting only
	for that data on which compression was attempted.

	On Windows NT 3.51, the "Compression%" accounts for all data,
	including the data on which compression was not attempted.  As
	a result, the reported "Compression%" figures for Windows NT 3.51
	will run lower than those shown on Windows for Workgroups 3.11.


Remote Access Support for Security Dynamics ACE Server ---------------------------------------------------------------------- 
Windows NT 3.51 Remote Access has the capability to authenticate dial-in
users using the Security Dynamics ACE Server. To enable authentication with the Security Dynamics ACE Server, you need to install a special module from Security Dynamics Inc. You can reach Security Dynamics Inc. at the following address:

 Security Dynamics  
 One AleWife Center
 Cambridge, MA 02140-2312
 Tel: [phone]
 Fax: [phone]
 

Shadow RAM Conflicts
--------------------
Computers that use Shadow RAM may experience problems with memory conflicts. You may need to disable BIOS Shadow RAM using the computer setup program provided by the computer manufacturer. See your computer documentation or manufacturer for more information.


NetBEUI Bindings on Computers with Multiple Network Cards
---------------------------------------------------------
RAS installs NetBEUI by default. If a computer has two network cards, NetBEUI is bound to both cards. This will cause your workstation service not to start due to duplicate computer names on the network. 
So, if your computer has more than one network card and you are installing RAS, during the installation process make sure NetBEUI is bound to only one of the network cards. You can change the bindings in the Network Control Panel icon by choosing the Bindings button in the Network Settings dialog box.
During RAS installation, you can also choose not to install NetBEUI by choosing the Network button in the Remote Access Setup dialog box. In the Network Configuration dialog box, clear the NetBEUI check box. 


Using RAS with PCMCIA Cards
---------------------------
If you are using RAS with a PCMCIA card and are experiencing difficulty with your computer, such as lock-ups or error messages about hardware failure, use the Terminal program in the Program Manager Accessories group to assure that the PCMCIA card is functioning properly. 
If Terminal locks up, the problem could be one of the following:
* The modem is not recognized by Windows NT
* FIFO needs to be disabled
* An incorrect IRQ or I/O address is being used
To reconfigure the communications port, in the Control Panel Ports icon, choose the Settings button, and then choose the Advanced button. Then, in the Registry, add the following entry for the new port key:
Pcmcia:REG_DWORD 1

If Terminal functions properly, verify that the modem type is being detected correctly and that the speed is set correctly. For information on speed settings, refer to the modem manufacturer's manual.



=================================================
CONNECTING TO WINDOWS NT 3.51 RAS SERVERS
WITH THIRD-PARTY PPP CLIENTS
=================================================

NetManage Chameleon and Chameleon NFS Version 4.1 Clients Required
------------------------------------------------------------------
Versions of NetManage Chameleon prior to 4.1 do not interoperate with Windows NT. You must update to version 4.1 to connect to Windows NT 3.51 RAS servers.

Also, you must make the following change in the SLIP.INI file located in the \NETMANAG directory, before connecting a NetManage client to a Windows NT RAS server.

[ppp]
SCRIPT=-n
TYPE=PPP

In order to configure the NetManage client to request an IP address from the Windows NT RAS server, set the client IP address to 0.0.0.0.

If you want the NetManage client to request a specific IP address, you must configure the RAS server IP configuration to allow remote clients to request their own IP addresses. You configure the RAS server using the Network option of Control Panel.