See correction to this article

ENHANCE YOUR SYSTEM'S DIAL-UP NETWORKING PERFORMANCE

In previous articles about Windows NT Remote Access Service (RAS--see "Related Articles in Windows NT Magazine," page 126), I covered several aspects of this multifaceted NT component, including new features of NT 4.0 RAS and Dial-Up Networking (DUN), Virtual Private Networks (VPNs), and Registry tweaks to implement new or hidden functionality. But I haven't covered RAS performance. For this article, I've collected a few of my favorite RAS optimization techniques that enhance RAS performance on NT servers and workstations.

A lot of what I have to share relates directly to TCP/IP and IP-based RAS connections. The advent of the Internet and the widespread deployment of TCP/IP networks have made IP-based RAS connections the most common connections in modern NT networks. As a result, I'll cover both the configuration side of the RAS/DUN service and some specific protocol-related optimizations you can use with RAS.

Configuring RAS Devices
The first step in optimizing RAS is to ensure you optimally configure the dial-up adapters. Whether you're using a standard modem or ISDN terminal adapter, be sure you configure the device (and the communications port to which it's attached) to achieve maximum performance.

With any dial-up adapter, choose the highest Data Terminal Equipment (DTE) rate your modem supports. The DTE rate is the speed at which the computer sends data to your modem's serial (COM) port. Setting the dial-up adapter's DTE rate higher than its Data Communications Equipment (DCE) rate, the physical speed at which the device transmits data (the line rate), optimizes the device's performance. Optimizing the dial-up adapter in this manner guarantees that the computer will provide data to the device as fast as the device can process it. Setting the DTE rate higher than the DCE rate is important because most modern modems and ISDN terminal adapters employ data compression techniques to achieve effective transfer rates that exceed their rated speeds. You set the DTE rate of a COM port via the Baud Rate setting in the Ports applet in Control Panel. Screen 1, page 122, shows my settings for COM2.

To maximize the throughput of most dial-up adapters (including modems and ISDN terminal adapters using COM ports), set the DTE rate for the device to the highest setting recommended by the manufacturer. For 28.8Kbps and faster devices that communicate through COM ports, the optimal setting is usually 57.6Kbps or 115.2Kbps. You might have a port or modem driver that supports a higher number, such as 128Kbps, which reflects the highest possible speed of that device or port as reported to NT by the Unimodem driver or a custom serial driver.

The optimal DTE rate for a particular device depends on the particular COM port that the device uses, and specifically the universal asynchronous receiver-transmitter (UART) chip driving the port. The COM ports on all modern PCs come with 16550 or faster UARTs, which use 16-byte or larger first in, first out (FIFO) buffers, and support maximum DTE rates ranging from 38.4Kbps to 115.2Kbps. In addition, multiport serial boards often have dedicated application-specific integrated circuits (ASICs) or microprocessors that handle the serial I/O and allow for maximum DTE rates of 230Kbps or more. With fast external modems or ISDN terminal adapters, don't use communication ports that have older 8250 UARTs (which are slower and use no FIFO buffer) or 16450 UARTs (which have only a 2-byte FIFO buffer). These slower UARTs won't let you achieve the dial-up device's maximum speed, and will likely cause the port to become overrun and lose data during transmission. Typically, you won't have these problems with internal modems, because they contain UARTs that are fast and well-matched to the device's capabilities.

The Ports applet in Control Panel isn't the only place you can configure the maximum DTE rate setting for your dial-up adapter. You can also define this rate in the Modems applet in Control Panel for each dial-up adapter (under the General tab of the Properties dialog box for each device; you can reach this tab while editing a RAS/DUN phonebook entry). Therefore, I recommend that you set the Maximum Speed setting for each dial-up adapter to the highest possible rate. In most cases, this rate is equivalent to the one you set for the COM port earlier. The modem's Maximum Speed setting (as configured in the Unimodem driver for the device in the Modems applet) will typically override the DTE rate settings in the Ports applet for the communications port in question. For this reason, you might want to use the Ports applet default settings. The only potential disadvantage to this approach might be a case where you are using a non-Unimodem aware (e.g., DOS or Win 3.x-based) communications application. In this case, not setting the proper DTE rate in the Ports applet could limit the device's performance.

When setting DTE rates, first consult the device's documentation to verify the manufacturer's recommended settings; different manufacturers will have different recommended configurations for their products, and the documentation might contain clues that will help you obtain maximum performance from the device. You might discover additional commands or a specific initialization string that you can issue to the device to enable or disable specific performance-related features. You can place this information into the Extra Settings field of the Advanced Connection Settings dialog box, which you can access via the Advanced button in the Connection tab of a device's Properties dialog box. To take advantage of all the features of your dial-up adapters, be sure you have the latest version of the correct driver for each adapter you install.

Two noteworthy settings for improving the performance of your RAS device are available in the Ports applet in Control Panel. The first setting is Flow Control. Flow Control defines the method of handling data transfer between two communications devices when the DTE and DCE rates are different (which is usually the case) so that data is not lost. For most RAS devices, choosing either the default setting of None or selecting Hardware (i.e., Request To Send/Clear to Send­RTS/CTS) flow control are typically the best choices. Hardware-based flow control means the hardware directly negotiates the flow of control. However, NT actually emulates hardware-based flow control in software. Although you might naturally suspect that this method is slower, my experimentation with different settings has shown little or no difference in regard to performance with different flow control settings selected. Leave the default settings of None or Hardware, because the Xon/Xoff setting (which is the standard for software-based flow control) is incompatible with binary transfers and therefore not recommended with dial-up adapters.

The other noteworthy setting is enabling FIFO buffers for the COM port attached to your RAS device (or created by the device, as with internal modems). Although the default in NT is to enable FIFO buffers whenever COM ports using them are detected, you still need to verify this setting. To view or change this setting, go to the Ports applet in Control Panel and choose Settings, Advanced to bring up the dialog box in Screen 2. With most dial-up adapters and communications ports, you obtain maximum performance and reliability when you enable FIFO buffer support.

Optimizing RAS/DUN Connections
Now that you've optimized the communications settings for hardware, you can tune the RAS configuration. I'll approach this subject first from the client side and then the server side.

First, when you're configuring DUN on a client to connect to a remote network running multiple protocols (e.g., an NT RAS server offering both IP and NetBEUI), try to limit the number of protocols, preferably to one. You'll greatly reduce the traffic flowing across the RAS connection and optimize the speed of the session. TCP/IP is usually the best protocol to use in routed networks or TCP/IP-only environments because doing so will not incur additional protocol overhead on servers or clients and will permit connectivity throughout the entire network. However, in terms of raw speed, NetBEUI is still usually the fastest LAN protocol for use with smaller networks (i.e., less than 200 users) and Microsoft RAS/DUN. Therefore, if your LAN is not connected to other networks or the Internet and is using NetBEUI as the primary or sole protocol, stick with this protocol for RAS, as well.

Next, consider implementing a Multilink Point-to-Point Protocol (MPPP--Multilink RAS in NT) RAS connection. A Multilink RAS connection lets you use more than one dial-up device simultaneously to achieve one, larger, virtual RAS connection. NT's RAS and the latest version of the Windows 95 DUN client support this functionality. To implement a Multilink RAS connection, you must install multiple devices at both ends. (The devices can be different types and speeds as long as they have a compatible counterpart at the other end of the connection.) In the DUN phonebook entry for the connection, select multiple adapters and enter the appropriate telephone number for each adapter to dial, as Screen 3 shows. Although this feature requires multiple RAS devices on the RAS server, it might be more attractive for increasing client bandwidth than upgrading the company's remote access infrastructure to support more expensive technologies such as ISDN. In addition, users connecting to the Internet via modem-based RAS connections can increase their bandwidth using Multilink RAS with their Internet Service Provider (ISP).

Many ISPs don't support Multilink RAS for analog connections, but several ISPs have recently started offering this service. The concept of Multilink RAS isn't very strange; after all, it's based on the technology used to bond the two 64Kbps bearer channels on ISDN terminal adapters. With modems, you use multiple physical modems rather than two bearer channels. (For more information about Multilink RAS, see "Related Articles in Windows NT Magazine," page 126.)

   Prev. page   [1] 2     next page
CORRECTIONS TO THIS ARTICLE:
"Optimizing NT RAS" incorrectly stated that "Ethernet runs at 10Mvps, far less than the average RAS PPP connection of 28.8Kbps to 128Kbps." The correct comparison is "far more than."




You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

I enjoyed reading “Optimizing NT RAS” (May) about how to tune Remote Access Service (RAS) for better performance. I’ve used a few of your tips, but I was wondering about how to use multiline dial-ups. I noticed this feature and tried to use it, but none of the Internet Service Providers (ISPs) in my area allow more than one instance of a user logon at once, so the dial-in fails. I tried dialing in and logging on with two accounts using different usernames, then activating my browser, but my browser picked one modem to use even though both were active. Is there a way to set a dial-up connection to use multiline access and automatically log on under two usernames or tell the browser to use all facilities available? I have two accounts for different purposes, but I want to access both at once for greater speed on the Internet. I’m using Windows NT Server 4.0 with Service Pack 3 (SP3) and Internet Explorer (IE) 4.01.<br> --Tom Cox<br><br>

<i>The behavior you experienced resulted from the type of connections you created. You created two separate connections via two distinct Point-to-Point Protocol (PPP) sessions to ISPs, each of which NT treated as a separate interface with a unique IP address. In this scenario, a TCP/IP session typically uses only one route (via only one of the RAS PPP sessions) to establish a connection to a remote host. For RAS to utilize the Multilink RAS (Multilink PPP) feature and use two or more connections as one virtual connection, the other end of the connection (i.e., the ISP) must be using NT Server 4.0 RAS with Multilink RAS support or another type of network access server that’s compatible with NT’s Multilink RAS feature. Unless this specific support exists, you won’t be able to use the Multilink RAS feature. I’ve heard about several ISPs that support NT Multilink RAS, but such support is still very rare. As more ISPs increase the deployment of NT within their organizations, support will probably increase.<br> --Sean Daily</i>

Tom Cox

I’m always amazed how timely the articles are in each month’s <i>Windows NT Magazine</i>. “Optimizing NT RAS” provides information that my company can use immediately. My question is, can you use RAS in Windows NT Server 4.0 with Service Pack 3 (SP3) for secure dial-in access to a WAN? My company (a manufacturing representative) is connected to a third-party WAN and accesses various computing resources over this WAN. The company must connect notebook users to the WAN and allow access to Internet and intranet sites for customer technical support. Can you point me to any relevant articles that have appeared in Windows NT Magazine discussing the security of RAS?<br> --Sam Creery<br><br>

<i>You can definitely use RAS and Dial-Up Networking (DUN) to provide secure remote access for your mobile and remote users. Microsoft includes support for several security options related to RAS, ranging from who can use the service (as defined in User Manager) to what level and type of encryption is used for RAS sessions (e.g., PAP, SPAP, CHAP, MS-CHAP). Zubair Ahmad wrote an excellent article (“Is RAS Safe?”) about this topic in the December 1997 issue of </i>Windows NT Magazine<i>; you can check it out online at http://www.winntmag.com. While you’re there, you might want to search on RAS to find other articles that contain the additional information you’re looking for.<br> --Sean Daily</i>

Sam Creery

I read Sean Daily’s “Optimizing NT RAS” (May) and found the article very informative, but where can I find more information about how to configure a Remote Authentication Dial-In User Service (RADIUS) server? I am the administrator of a small Windows NT 4.0 LAN (i.e., three servers) that has a Remote Access Service (RAS) server. We will be replacing the present RAS server with a new one. What do I get with RADIUS that I wouldn’t get with regular RAS authentication using CHAP or MS-CHAP? Our current RAS server connects directly to the LAN, so I don’t think I need Routing and RAS (RRAS). I’m a bit confused as to how to configure the new RAS server. Can you answer my questions?<br> —Roger Halverson<br><br>

<i>RADIUS is an authentication and accounting protocol that offers advantages in mixed network environments because it can provide centralized authentication and account for multiple and disparate network access server devices. Here are a few sources for information about RADIUS that you might find useful: the RFC for RADIUS Dial-In Authentication (RFC2058 at ftp://ftp.isi.edu/in-notes/rfc2058.txt), the RFC for RADIUS accounting (RFC2059 at ftp://ftp.isi.edu/in-notes/rfc2059.txt), and IEA Software (http://www.emerald.iea.com).<br> --Sean Daily</i>

Roger Halverson

Thanks for Sean Daily’s May article, “Optimizing NT RAS,” and his follow-up Reader to Reader submission, “Unsolved Mystery” (August). I followed the directions, and I noticed better modem performance. I have a question. If I go to Control Panel, Ports, COMx, Settings, Flow Control and choose Hardware, won’t that override the Registry settings for that port?<br> --Otto<br><br>

<i>The Registry setting for the port and the Control Panel, Ports setting for the Flow Control value are actually one and the same: The setting for communication ports-related entries, as configured in the Ports applet, are reflected in the Registry. So rather than override the Registry settings, the Control Panel, Ports utility sets those Registry values. Note that the process of changing certain settings (e.g., enabling/disabling the FIFO buffers) won’t take place until the system is rebooted.<br> --Sean Daily</i>

Otto

 
 

ADS BY GOOGLE