Problem Restated: OPA0 on DS10L



Perhaps I was too terse on first go around, but am having problems
connecting to the OPA0 port. I have CONSOLE set to serial on all my nodes
so the second COM port is OPA0 and the first is TTA0 , as Fred kindly
explained a while back. AlphaServer DS10L 466 MHz running OpenVMS V7.3-1
OS has all the latest patches and the firware is Version 7.1

I ran the following tests below. The only test, which in my estimation was
normal was TEST 2, connecting from an XP1000. It is odd that TEST 1
was not normal, since here we were connecting from one port to the other
on same machine. Now I have used this method of connecting to the
console port from a COM port on W2k using HyperTerm successfully with
Pelicans, Miatas and XP1000s, so I think there is something wrong with
the DS10L serial ports.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXX TEST 1 Loop from the TTA0 to OPA0 XXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

********** FIRST PART **************
NORNS> set host/dte opa0

%REM-I-TOQUIT, connection established

Press Ctrl/\ to quit, Ctrl/@ for command mode

U

%REM-E-PORTRXERR, port receive error
-SYSTEM-W-DATAOVERUN, data overrun
Username: Username: R\
Too many parameters - reenter command with fewer parameters
\R\\
Username:
Username: Password:
Password:
User authorization failure
Username:
Username: tr
Error reading command input
File read error
Data overrun <----------------------- Hangs hit return

Username:

On second attempt

NORNS> set host/dte opa0

%REM-I-TOQUIT, connection established

Press Ctrl/\ to quit, Ctrl/@ for command mode



Username: eading command input
Too many parameters - reenter command with fewer parameters
\COMMAND\
Username:


*********** SECOND PART **************
NORNS> set host/dte opa0
Same beahvior. But on second attempt appeared as expected.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXX TEST 2 Connect from XP1000/xxA0 to DS10L/OPA0 XXXXXXX
KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK


First from TTA0
ODIN> set host/dte tta0


%REM-I-TOQUIT, connection established

Press Ctrl/\ to quit, Ctrl/@ for command mode





Username:


Worked perfectly and fast

ODIN> set host/dte opa0

%REM-I-TOQUIT, connection established

Press Ctrl/\ to quit, Ctrl/@ for command mode



Username:


Ditto

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXX TEST 3 Connect from W2K/COM1 to XP1000/OPA0 XXXXXXX
KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK


In this test using Hyperterm set to 9600-8-N-1 I window is popped
and immediately Username: prompt appears

Username: tom
Password:
$ sho def
SYS$SYSROOT:[SYSEXE]
= SYS$SYSROOT:[SYSEXE]
= SYS$COMMON:[SYSEXE]


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXX TEST 4 Connect from W2K/COM1 to DS10L/TTA0 XXXXXXX
KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK


After a long while it gets the Username: prompt. On second
attempt after removing and reinserting cable it is normal


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXX TEST 5 Connect from W2K/COM1 to DS10L/OPA0 XXXXXXX
KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK

Never connected. I also tried setting OPA0 to NOTYPE connecting
and then changing to TYPE_AHEAD. Also tried opening HyperTerm
and then connecting cable.


I am using standard Null modem cable wired (and tested) as follows

1 ----- 4
2 ----- 3
3 ----- 2
4 ----- 1,6
5 ----- 5
6 ----- 4
7 ----- 8
8 ----- 7

The settings on TTA0 and OPA0 are as follows

NORNS> sho term/full opa0
Terminal: _OPA0: Device_Type: Unknown Owner: No Owner

Input: 9600 LFfill: 0 Width: 80 Parity: None
Output: 9600 CRfill: 0 Page: 24

Terminal Characteristics:
Interactive Echo Type_ahead No Escape
No Hostsync TTsync Lowercase No Tab
Wrap Scope No Remote No Eightbit
Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA No Altypeahd Set_speed
No Commsync Line Editing Overstrike editing No Fallback
No Dialup No Secure server No Disconnect No Pasthru
No Syspassword No SIXEL Graphics No Soft Characters No Printer Port
Numeric Keypad No ANSI_CRT No Regis No Block_mode
No Advanced_video No Edit_mode No DEC_CRT No DEC_CRT2
No DEC_CRT3 No DEC_CRT4 No DEC_CRT5 No Ansi_Color
VMS Style Input
NORNS> sho term/full tta0
Terminal: _TTA0: Device_Type: Unknown Owner: No Owner

Input: 9600 LFfill: 0 Width: 80 Parity: None
Output: 9600 CRfill: 0 Page: 24

Terminal Characteristics:
Interactive Echo Type_ahead No Escape
No Hostsync TTsync Lowercase No Tab
Wrap Scope No Remote No Eightbit
Broadcast No Readsync No Form Fulldup
No Modem No Local_echo Autobaud No Hangup
No Brdcstmbx No DMA No Altypeahd Set_speed
No Commsync Line Editing Overstrike editing No Fallback
No Dialup No Secure server Disconnect No Pasthru
No Syspassword No SIXEL Graphics No Soft Characters No Printer Port
Numeric Keypad No ANSI_CRT No Regis No Block_mode
No Advanced_video No Edit_mode No DEC_CRT No DEC_CRT2
No DEC_CRT3 No DEC_CRT4 No DEC_CRT5 No Ansi_Color
VMS Style Input





.



Relevant Pages

  • RE: I think Ive been hacked...please help!
    ... > connecting within seconds of boot. ... port scanning the machine from the outside ... experience performing incident response activities, ... one will run netstat and see something listening on ...
    (Incidents)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.help_and_support)