input.txt

CSLIB, a C++ database library.

Configuring a RAS Server for X.25
-----------------------------------
When configuring a RAS Server to use X.25 over an EiconCard, several steps must be followed to define the number of clients that can connect to the server.

 1. Define the total number of virtual circuits that the EiconCard will be configured for.

    a. Choose the Network option in Control Panel.

    b. In the Network Settings dialog box, select the EiconCard driver in the Installed Adapter Cards box.

    c. Choose the Configure button. 

    d. Follow the instructions in your Eicon WAN Services for Windows NT System Guide on how to configure the total number of virtual circuits.

       The sum of the two-way virtual circuits (TVC) and incoming virtual circuits (IVC) in the X.25 configuration screen must equal the number of incoming X.25 clients the server will support at one time. You may have to find out how many TVCs and IVCs your X.25 line has by contacting your X.25 vendor.

 2. Define the number of communication ports to be available for RAS in the XPAD 
    configuration program.

    a. Choose the Network option in Control Panel.

    b. In the Network Settings dialog box, select the Eicon X.PAD Driver in the
      Installed Network Software box.

    c. Choose the Configure button. 

    d. Configure the total number of COM ports by selecting the COM ports from the Available Ports list and then choosing the Add button.

       It is recommended that the number of communication ports should be equal to the number of virtual circuits (TVC+IVC) configured.

 3. Configure the number of communication ports (Eicon XPAD's) in RAS using the Network option in Control Panel.


X.25 Buffering
--------------
On each communication port in the Eicon PAD configuration, it is recommended that the packet length supported be left at the default of 128.  This will give optimum performance on the server.


Server Bandwidth and the Total Number of Clients
------------------------------------------------
To obtain maximum performance in the RAS clients and to ensure reliable connections, ensure that the aggregate throughput of all clients does not exceed the bandwidth of the RAS server.

For example, four clients running at 2400 bits per second (bps) can be connected to a server with a 9600 bps X.25 line. However, attaching a fifth client at 2400 bps will exceed the server's bandwidth. This will cause all clients to operate at speeds below 2400 bps.  If a virtual circuit, communication port, and RAS port are defined for five ports, then five clients can connect using X.25. However, connecting five clients at one time is not recommended since the throughput of each client will be very low and will cause time-outs in the network protocols running over RAS.


Troubleshooting Remote Disconnections
-------------------------------------
When a client connection is cleared, the system event log of the RAS server running X.25 can be examined for an error message. The event log can record why the remote client or the remote network disconnected.

If the remote client (through a dial-up PAD or local PAD) disconnects, the following warning message will appear in the system event log.

"Remote DTE cleared the X.25 call on XPADxxx, X.25 Return Codes: Cause yy (hex) Diagnostic yy (hex)"

The "XPADxxx" is the port name defined in the XPAD configuration.  "yy" is a hex string.  For DTE clearing the cause will always be 00.  The Diagnostic code can be 00--indicating that the remote client requested a disconnect--or another non-zero value.  When the diagnostic code is non-zero it indicates a clearing due to the remote client's dial-up PAD service.  Contact the remote client's X.25 service provider to determine the problem.

If the X.25 network disconnects, the following warning message will appear in the system event log.

"Network cleared the X.25 call on XPADxxx, X.25 Return Codes: Cause yy (hex) Diagnostic yy (hex)"

The "XPADxxx" is the port name defined in the XPAD configuration.  "yy" is a hex string.  For a network clearing the cause value will always be a non-zero value.  The diagnostic code in the cause can be any value. Consult your local X.25 service provider with the cause and diagnostic value to determine the exact reason for the network disconnect.


=================================================
FREQUENTLY ASKED QUESTIONS
=================================================
This section contains questions and answers from public bulletin boards, such as CompuServe. It is included to help customers with similiar questions.
You can find more information in the RAS online Help file or in Microsoft's whitepaper on RAS located on ftp.microsoft.com or www.microsoft.com.

QUESTION:
I had my DHCP server configured for an address pool.  I then
changed it to a different pool.  Now all my RAS clients continue to get addresses from the initial pool.  Why?

ANSWER:
See the section, "Resetting DHCP Leases on RAS Servers" earlier in this file.

---------------------------------------------------
QUESTION:
My site has a Shiva network modem which I can use to call into and 
establish a connection on the Novell network. Can I use the RAS client software to dial in and establish a connection directly with Shiva, without having to setup a Windows NT Server computer as a RAS server? If so, how would I go about doing this?

ANSWER:
The Windows NT RAS client will dial into a Shiva network modem.  You
need to install RAS on the Windows NT client.  Then dial in using a valid username and password.  

If you have problems, there are many things to check.  You can check to see if the client is requesting its own IP address, but the server is not configured to supply one.  Also, you must select PPP protocols that are supported on the server; for example, IP or IPX.

------------------------------------------
QUESTION:
I have an internal Intel SatisFAXtion/400 modem, which is installed on COM4.
When I try to setup RAS for this modem, it only lists Port 2 and Port 3 as
options.  It says if I want to access other ports to get a driver from the
manufacturer.  Does this mean that I need a SatisFAXtion driver for Windows NT from Intel?

ANSWER:
This means you probably do not have the modem configured correctly for COM4. The system is not recognizing a device on COM4, so COM4 is not being offered in RAS setup.  Try using Terminal to dial out through COM4. If the modem is correctly configured for COM4, you may have an IRQ conflict that is causing the problem.  Check the Windows NT Event Viewer to see if there are any
problems listed there.

---------------------------------------------------
QUESTION:
Does anyone have a fix for the SMC 16550 UART.... I get error messages when using RAS to connect to a computer above 19200. Is there a fix besides changing my serial card or going to an internal modem?

ANSWER: You can try setting the port speed a bit lower.  This is the speed at which the machine talks to the modem,
rather than the speed of the modem.  By default it is 38400.  Try setting it to the same speed as his modem.  To set this, edit the
phone book entry and choose the Modem button at the bottom of the
dialog.  Select a speed in the Initial Speed (bps) box.

----------------------------------------------------
QUESTION:
How, on a Windows NT Server version 3.5 network, do I provide primary DNS service?  Do I need to put a UNIX box on my LAN just to provide DNS?  Or is there a DNS Server that will run under the Windows NT Services system?

ANSWER:
Windows NT Server version 3.5 does not have a DNS service. A DNS server for Windows NT is available in the Windows NT 3.5 Resource Kit.

---------------------------------------------------
QUESTION:
Are there any plans to provide an upgrade for Windows for Workgroups RAS clients and Windows NT version 3.1 RAS clients so that they will be compatible 
with the new software compression scheme in Windows NT version 3.5?

ANSWER:
Support for Windows for Workgroups 3.11 RAS and Windows NT version 3.1 RAS software compression is available in the Windows NT version 3.51 release.

---------------------------------------------------
QUESTION:
1.  I can successfully connect using RAS on a Windows NT Workstation version 3.5 with a Windows NT Server version 3.1 running RAS.  However, I get the following message in the Connection Information dialog on the Windows NT version 3.5 client: "Using Down-Level RAS Protocol". 

2.  The connection information also shows that I am getting 0% compression. This message occured when I switched from a Windows for Workgroups 3.11 RAS client to a Windows NT Workstation version 3.5 RAS client. Any suggestions for getting my compression back?

ANSWER:
1.  Windows NT version 3.1 RAS does not support PPP, which the Windows NT version 3.5 RAS client is attempting to use when connecting. Windows NT version 3.5 RAS falls back to the older protocol to make the connection and displays the "Using Down-Level RAS Protocol" message.

2.  To get software compression with Windows NT version 3.5 RAS calling a Windows NT version 3.1 RAS server, upgrade your RAS client to Windows NT version 3.51 which supports the older software compression algorithm used in Windows NT version 3.1.

---------------------------------------------------
QUESTION:
Windows NT version 3.5 has PPP/SLIP built into RAS, so you can use the RAS client software to connect your Windows NT computer to the Internet.
Suppose I have a LAN which includes a bunch of Windows for Workgroups version 3.11 systems networked to a system running Windows NT version 3.5. If the Windows NT system uses RAS to connect to an Internet provider, and if I have the TCP/IP protocol on all computers on the LAN, will the Windows NT computer connect the two ends? That is, will it act as a gateway, allowing the Windows for Workgroups computers to see the Internet on the other end of the RAS connection?
If so, is it automatic, or do I have to do something to enable it? If not, is there any way to get this capability?  Is it in Windows NT Server or some third-party product?

ANSWER:
LAN to LAN routing is not supported today.  Look for it in the Windows NT 3.51 Service Pack release in the next few months.
For more information, see the Windows NT 3.5 Resource Kit or the following Knowledge Base article:
Enabling Routing of IP Packets on RAS Clients
ID: Q121877

---------------------------------------------------
QUESTION:
What are all the steps necessary to make a RAS connection from Windows for Workgroups to Windows NT version 3.5 with a null modem setup?

ANSWER:
1.  Install RAS on the RAS server.  Configure it for a null modem, at 9600 bps.
2.  On the RAS server, create an account for the user dialing in.
3.  On the RAS server, in RAS Admin, select the Permissions command under the Users menu. Grant dial-in permission for that user account.
4.  Install RAS on the Windows for Workgroups client.  Configure it for a null modem.
5.  In Remote Access, create a phonebook entry to the server you are dialing.  Enter 1 (or some random number) for the phone number.
6.  Choose the Dial button.  The rest happens exactly like an analog connection.
     Make sure you are using a standard null modem cable. See the RAS on-line Help topic "Cabling Requirements" for details.

---------------------------------------------------
QUESTION:
I have TCP/IP installed on both my RAS server and client, but when I dial in, I get an error saying PPP is not installed.

ANSWER:
You need to enable TCP/IP for RAS.
To enable a protocol for RAS, start the Control Panel Network icon.
In the Network Settings dialog box, select Remote Access Service and choose the Configure button. In the Remote Access Setup dialog box, choose the Network button. In the Network Configuration dialog box, make sure the appropriate protocols are checked in the Dial Out Protocols box.
---------------------------------------------------
QUESTION:
We would like to use RAS to administer a remote Windows NT Server computer version 3.5 at a client's site. What kind of software do we need to have on our side? Do we need to dial the server from our Windows NT Server computer version 3.5 or can we dial in from any computer?

ANSWER:
This is easiest if you dial them from a Windows NT Server computer. That way all you have to do is run the administrative tools already found on the Windows NT Server computer and point them at the remote client.

You can also install the Windows NT Server tools found on the Windows NT Server CD on a Windows NT Workstation computer. Then you can use that workstation to dial in and manage Windows NT Server computers on the remote network.

To install the Windows NT Server Tools on a computer running Windows NT Workstation, obtain a Windows NT Server CD and run the \CLIENT\SRVTOOLS\WINNT\SETUP.BAT batch file.

There are also Windows NT Server tools for use on computers running MS-DOS 5.0 or later, Windows version 3.1x (with LAN Manager for MS-DOS), or Windows for Workgroups 3.1x.
To install the Windows NT Server Tools obtain a Windows NT Server CD and follow the instructions in the README.TXT file in the \CLIENT\SRVTOOLS\WINDOWS directory.

---------------------------------------------------
QUESTION:
Does anyone have any experience tying two Windows NT computers together via null modem?  
I have two computers on my desk running Windows NT 3.5 and I have no other networking 
hardware, so I'm trying to use RAS and my null modem cable to link them together. But, everytime
I try to dial I get a message of hardware failure.
I've checked my cable for continuity, and it matches the table supplied in the Windows NT Help file.  Also, I've tried it with all the modem options (things like "enable hardware flow control")
turned off, as well as with a smattering of them turned on, but to no effect. 

ANSWER:
Are you using a 25-pin to 9-pin converter for either of the COM ports?
If so, make sure it is not the 25-9 adapter that ships with the Microsoft Mouse.  That is not a true converter, and will cause this problem.

If that is not the problem, double check that both client and server have the same speed Null Modem entry selected in the Configure Port dialog in RAS.
Also, make sure you are not using a standard null modem cable. See the RAS on-line Help topic "Cabling Requirements" for details.

---------------------------------------------------
QUESTION:
I was wondering how many RAS connections Windows NT Server version 3.5 supports, and what hardware for these connections was recommended (I.E. Dialogic, etc.).
Also, do you have any additional information on the optimum server (hardware/system) for X+ users?

ANSWER:
The RAS server for Windows NT version 3.5 or later will support up to 256 clients per server. To do that I would recommend 2 Digiboard EPC controllers and a 4-processor RISC computer for your RAS server.

Here are some very general guidelines for servers:
    Up to 40 clients, 486/66 with 48M of RAM
    Up to 64 clients, axp or MIPS with 64M of RAM, or P5 2-processor with 64M of RAM
    Up to 100 clients, MIPS or axp 2-processor with 64M RAM  (Yields about 70% CPU utilization.)
    More than 150 or so, use a 4-processor or better RISC computer.

For COM hardware, the Digiboard C/X controller is good.  For large client loads (70+)
on a single computer, I would recommend the Digiboard EPC controller, or two, to share
the load.

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