Softerm ACS (Asynchronous Communications Server)


What is an Asynchronous Communications Server?

Asynchronous Communications Servers (ACS) allow Local Area Network users to share modems, fax boards, serial ports, or other asynchronous devices across the Network.

Softronics' Softerm Asynchronous Communications Server (SACS) complies with IBM ACS (LANACS) standards, yet works across most LANs and with a variety of communications software.


What other software do I need?
Most people are familiar with communications packages used to call a local BBS or transfer files between computers. Softerm ACS -- any ACS -- still requires this software.

Unlike dialing a modem in the same machine, however, communications software now needs a way to tell the network to go find the modem, dial the number, and return the responses. While most ACS packages use proprietary communications software, SACS works with popular communications programs that can be configured for IBM ACS.

SACS talks to networks two ways.

Many networks (3Com, IBM PC Net and PC LAN, StarLAN) communicate using NetBIOS, and most others, including Novell and Banyan, supply NetBIOS emulators. Many network versions of communications software use NetBIOS to talk to an IBM ACS: Softerm PC, and network versions of ProComm and Crosstalk, are the most prominent examples. SACS works with all these.

SACS v2.0 also communicates directly with Novell's IPX, eliminating the need to use Novell's NetBIOS emulator. Only Softerm PC currently supports IPX addressing with SACS.


Modem Sharing

Communications servers let users share modems the way file servers let users share files. With a communications server and compatible software, LAN users gain access to Wide-Area Networking, E-mail, or electronic bulletin boards without installing a modem or serial connection in each workstation.

Softerm Asynchronous Communications Server (SACS) offers several advantages:

1. Works with virtually any network operating system (NOS). SACS works with IBM LANs, 3Com, StarLAN, and other NetBIOS networks; SACS also works with Novell under NetBIOS, or directly with IPX when Softerm PC is used as the communications software.

2. Works with many popular communications packages. NetBIOS operation is supported by Softerm PC, ProComm, Crosstalk, and other popular packages. Novell IPX communication is available with Softerm PC.

3. Supports up to 32 connections per ACS using widely-available serial cards from Digiboard, AST, and standard COM ports. No proprietary hardware needed.

4. Non-dedicated operation up to four ports. SACS runs in about 80K of memory and is designed for background operation. Word processing or data entry workstations are ideal as SACS servers.


Remote LAN Access

SACS helps users in the field or at home get work done on yourLAN in the office. By using SACS with a remote package like PCAnywhere or Carbon Copy, callers can use the SACS server as aremote workstation.

Setting up a remote workstation entails the following :

Your SACS server/remote workstation can be any PC that has at least three serial ports.

Configure SACS for only two of the ports, one the modem, the other used to connect to the remote package. Using the ANSERCNF utility included with SACS, tell SACS to redirect the modem port to the other serial port.

Using a null modem cable, connect the second SACS port, the one to which modem calls are redirected, to the third port, the one left out of the SACS configuration.

Install remote software, such as PCAnywhere or Carbon Copy, and configure it for the port not used for SACS. Select 'Hardwire' for the modem type (also called 'Null' in some packages).

Load the network shell, then start SACS, then run the remote package and set it for AutoAnswer. SACS will answer incoming calls, redirect them to the remote package, and callers have immediate access to the LAN.


Common Questions about Remote Configuration:

Do all incoming calls have to be directed to the remote? What if I want some callers to have LAN access, but others to have access to the minicomputer?

No problem. Using SACS' USERCNF utility you can define different connection paths for different callers. If you're using a Digiboard 8i serial board, for example, you can define a user REMOTE who will always connect to a specific port -- the port connected to the remote package. Other users can be defined (e.g., TERMINAL1, RTERMINAL, RICK, SUZY) to connect to other ports, or to connect to the first available port. SACS gives you flexibility.

What about security? I don't want everyone to have access to my network.

SACS offers extremely tight security through its ANSERCNF and USERCNF utilities. Password requirements can be defined for users through USERCNF, and separate password requirements for each port can be specified in ANSERCNF. Supervisors also can establish Access Rights Masks, explained in detail in the SACS users guide.

What's the difference between a remote connection through SACS and a Remote Asynchronous Bridge, like the one packaged with Novell ELSII and above? Why wouldn't I use what I already paid for?

Remote access through SACS, as detailed above, is essentially terminal emulation -- only screen and keyboard I/O are passed across the telephone line, while all the work is done by the workstation on the LAN.

Remote Asynchronous Bridges pass everything across the phone line, just like passing programs and data across a network, except that an async bridge at 2400 b.p.s. is roughly 4,000 times slower than an Ethernet connection on a LAN. A database query that might take 15 seconds across Ethernet requires more than 15 hours across an asynchronous bridge, hardly the best use of time and money. (Novell and other suppliers, to their credit, recommend only using asynchronous bridges for file transfer.)

Using a remote package, only keyboard and video signals travel at 2400 b.p.s., a little faster than most people type. All processing and disk I/O is done on the host workstation at network speeds.


Asynchronous Gateway

SACS provides an inexpensive solution to mainframe or minicomputer access through a LAN.

Serial ports from the SACS server can be hardwired to the asynchronous terminal connections of a host computer just by using a null modem cable. By installing additional serial boards, up to 32 users can get to the host through each SACS server -- and there's no limit to the number of SACS you can install on each network.

(Well, okay, you're limited by your pocket book, since each SACS software package is licensed for only one SACS server. To set up multiple SACS servers, you'd need to buy the appropriate number of licensed SACS copies.)

Softerm Modular Workgroup from Softronics is designed expressly for this environment. Modular Workgroup is network-wide terminal emulation that runs stand-alone, requires no communications package, and is priced and licensed per gateway.


Things You CAN'T Do with SACS

You can't have more than one person use one modem at the same time. Everyone on the LAN can get to the modem, but only one person can use it at a time. When he's finished, someone else can use it.

You can't put more than one modem on a phone line. Devices to do that are called multiplexers, they're expensive, and they require hardware.

SACS won't create workstations. If SACS is used for remote LAN access, the caller must have a workstation on the LAN to connect to! SACS is not an operating system: it can't create microprocessors out of thin air.


SACS Technical Specifications (Expert SACS)

Memory requirements: 80K

ACS type: IBM ACS (LANACS)

Networks supported: Novell (IPX or NetBIOS), Any NetBIOS network

Max. number of connections: 32 per ACS (hardware dependent)

Max. numbers of SACS per LAN: unlimited (licensed to generate only one SACS from each package)

Maximum transfer rate: 115,200 bps (hardware dependent)

Serial boards supported: DigiBoard (8i recommended), AST, IBM Asynchronous Adapter

Communications programs supported: Softerm PC (IPX or NetBIOS), Softerm Modular (IPX or NetBIOS), Softerm GroupWare (IPX or NetBIOS), ProComm (Network version), Crosstalk (Network version), and others with IBM ACS support

Remote packages supported: PCAnywhere, Carbon Copy, and others

Installation time: 30 minutes (excluding optional hardware)

Operating modes: non-dedicated up to 4 ports, dedicated up to 32 ports


Ordering Information

Softerm Asynchronous Communication Server is now available for $100.00. To order, call Softronics at 800/225-8590 or fax 719/548-1878.



[ Home | Back to Products ]



Softronics

5085 List Drive Colorado Springs, CO 80919 USA SALES (800) 225-8590 OFFICE (719) 593-9540 FAX (719) 548-1878 TECHNICAL ASSISTANCE (719) 593-9550 SOFTRONICS BBS (719) 593-9295 or Telnet to softerm.com EMAIL sales@softronics.com

Softerm is the registered trademark of Softronics, Inc. All products referenced herein are the trademarks or registered trademarks of their respective companies.



Copyright © 1999 by
Softronics, Inc. All rights reserved.
No part of this document may be reproduced without
the express written permission of Softronics, Inc.
Best experienced withMicrosoft Internet Explorer
Click here to start.

 

 

 

 

© 1996 Softerm® ACS product literature by Softronics, Inc. All rights reserved.