HP3000-L Archives

March 1999, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Wed, 17 Mar 1999 12:07:51 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Nick Demos <[log in to unmask]> wrote:


<snip>

>Guys, I might be wrong here, but I believe the bottom line is:
>
>Hardware:
>
>1.  A modem card will support EITHER modems or direct connect
>terminals (or PC's).
>2.  A direct connect card only supports terminals (or PC's)
>
>Software  The appropriate Ldev's must be specified correctly in
>SYSGEN and/or
>          NMMGR.
>
>That is how I think it works.


For the most part that is true. A direct connect port will support a modem
under the "right" conditions. Mainly the modem has to be configured to
assume DSR and DTR (and maybe a few others that I don't remember off the top
of my head) are always active and use a 2-3, 3-2, 7-7 cable.

Of course, just because you can hook up a modem in this fashion doesn't mean
you should. There are serious security implications to this setup.
Primarily, if the modem and DTC do not communicate the fact that the CD
dropped, the session won't be aborted. This leaves the possibility that the
next user to connect to the modem will be logged on in the middle of another
user's session (maybe MANAGER.SYS?) without any security checks. I would
only consider this option if I were using a modem with an on-board
username/password scheme that you must authorize through before it connects
you through to the system.

ATOM RSS1 RSS2