ppp on OpenVMS AlphaServer hardware port for remote gui access

From: Jim Strehlow (JimStrehlow_at_data911.com)
Date: 10/11/03 

Date: 10 Oct 2003 21:42:05 -0700

Problem:
We need help in configuring a PPP TCP/IP connection so that developers
can run
a Windows-based database GUI browser through a modem connection to a
TTA0:
or TTB0: port on an OpenVMS AlphaServer
if it is possible and you have already done it.

Background:
When a database is on a remote Windows server:
 - developers currently can use Microsoft DialUp Networking (no
endorsement)
 to connect to the Windows server, then

 - run Quest Software's Toad (unintentional plug) gui database browser
software
 to make a connection to the remote database on Windows.

When a database is on an AlphaServer:
 - developers only have a modem connection to an AlphaServer
TTA0:/TTB0: port
   for interactive logins
 - developers are limited to the SQL*Plus command line prompt
 - developers want to use a GUI database browser such as Quest Toad

Strategy:
We have software running on an OpenVMS AlphaServer acting as host
using
Compaq TCP/IP Services (UCX) for OpenVMS Alpha v5.1 and v5.3 ECO 2 on
OpenVMS.

The Compaq TCP/IP Services for OpenVMS Management manual
section 3.2.1.3 Setting Up an Asynchronous Port
specifically suggests SET TERMINAL TTA0: as part of a solution;

but we have not yet been able to get an end-to-end solution to work.
The manual intermixes sections for OpenVMS hosts with OpenVMS clients
and does not supply explicit modem AT commands (if any are needed.)

>From an earlier posting on this forum we learned:
  - if we want to run PPP through a terminal server, then we should
install
    a PPP-aware terminal server.

  - if we use a PPP-aware terminal server, then the dialup can be made
    to look just like any Windows dialup networking setup.

We have some sites that do not need (nor want footprint space for) a
terminal server. For such sites we would like to establish direct PPP
dialin without having to purchase an additional PPP-aware terminal
server. We would like to be able to use one of the direct Alpha
hardware ports – TTA0: or TTB0: - for PPP dialins.

Is that possible without having to add additional hardware? After all,
Windows servers support dialup networking out of the box without
having to add any hardware beyond possibly an external modem.

We are asking the OpenVMS forum for any guidance that members can
offer.
Even if you feel that you can provide only a partial solution,
your contribution could be very helpful to get us started.

In particular, the following would be helpful from OpenVMS system
managers who have established successful PPP connections to an OpenVMS
host using TTA0/TTB0 ports:

 * specific modem models and matching AT commands for those models to
store into the modem's NVRAM for the PPP line.

 * specific "one time" or background OpenVMS and UCX/TCPIP commands
used to set up the PPP machinery.
   That should support the possibility of just using the OpenVMS
system essentially as a dialup router to make TCP/IP connections to
other hosts on the OpenVMS Server's network.

 * does the port have to be dedicated to PPP purposes only, or can it
be
   converted into a PPP session after logging onto the AlphaServer as
a normal
   interactive user?

 * commands that would be typed into the initial DCL interactive
session to convert it into a PPP TCP/IP connection.

 * sample Windows scripts that could be used to automate the dialin
for Windows users unfamilair with OpenVMS or DCL.

 * we have some developers who are familiar only with Windows Dialup
Networking and not with OpenVMS or DCL. The ideal PPP dialin would be
configurable such that, to an end Windows user, the PPP dialin would
just appear as just as an additional Dialup Networking Windows entry.
We would provide supporting scripts to facilitate based upon your
help.

(Please try to only copy the section "problem" from this posting in
your response so that most of your posting will contain new
information. Thank you.)

Thank you in advance.

JimStrehlow@Data911.com
Alameda, CA, USA

Relevant Pages

  • Re: PlatformNotSupportedException with Sql Server 2000 sp3a
    ... > The project is well configured to deploy the soft on the mobile computer. ... >> Post the connection string. ... >>> I having a Sql Server 2000 on windows Xp and i have to use a Symbol MC ... >>> connected on a the database located on Windows Xp's computer. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: connection options to yukon
    ... If these are asp.net apps connecting to the database, ... If you use TLS you can increase the security of your SQL ... > Windows auth can lead to trojan operations as the application using SSPI ... >> Connection pooling does not depend on what method you choose to connect - ...
    (microsoft.public.dotnet.framework.adonet)
  • DSNLess connection
    ... I have a computer with Windows 98 on which I have set it up as a Personal ... Web Server and I am running/testing a small Access database. ... I am confused as to which connection I should be using. ... Microsoft JET Database Engine error '80040e4d' ...
    (microsoft.public.inetserver.asp.db)
  • Re: MSDE and ASP.NET/ADO.NET
    ... If you want to use windows authentication, ... > Server Explorer window in Visual Studio, ... > connection to the database, and checking the properties, ...
    (microsoft.public.sqlserver.msde)
  • Re: Youll never guess what HP advertised
    ... Oracle on VMS user base's priority has been trying to get recent ... We have some customers who insist on Oracle on a Windows box. ... Oracle on OpenVMS to go with our OpenVMS background server ... Our Windows desktop applications communicate with the database and our ...
    (comp.os.vms)