[comp.dcom.modems] TB+, VMS4.6, DHV-11, MVax_2

efb@suned1.UUCP (Everett F. Batey II) (10/14/88)

Been fighting with this one for a while.  Someone / thing other than my login
attempt is seen as trying to log in when I try to log into my MV_2 via my TB.
Below are the SHOW TERM, and TB+ config.  I am able to control and configure
the TB from my outbound port.  Inbound .. I get User Auth Failure VICE 
Username: ( see below ).  For any ideas or redirection of the following to
anyone you think might have a bright idea, thanks, Ev ..

VAX_$ SHOW TER TXA1
Terminal: _TXA1:      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
   Modem              No Local_echo      Autobaud           No Hangup
   No Brdcstmbx       No DMA             No Altypeahd       Set_speed
   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

The TB+ is set up per _Commands and Registers Reference Manual_ to Table 2-2
for Unattended Answer attached to a DHV-11:

E0 F1 M1 Q0 P V1 X1     Version BA4.00
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=040 S08=002 S09=006
S10=007 S11=070 S12=050 
S45=255 S47=004 S48=000 S49=000
S50=000 S51=004 S52=001 S53=002 S54=003 S55=003 S
... lots of lost numbers ... bad handshaking ...
N0:
OK

Upon reaching the MicroVAX's TB+, sending <cr>, we get the host's one line
message, expecting Username: / Password:, INSTEAD we get _User .. Auth ..
failure_ AND checking our accounting file .. Low and behold _LOGFAIL   USER_
the name of a default account that gets blamed for trying to login when 
DDCMP Async DECNET has trouble restarting.

TO THE EXPERIENCED this MEANS, the SYSMGR SHOULD ???
 
  SET TERM TXA1 /PERM /what /whatelse or 

  Change Some or ALL of
                 S51=4 (9600) .. S52=1 (no ans w/o DTR,..) ..
                 S53=2 (assert DSR and DCD upon valid carrier ) ..
                 S54=3 (disable break to command) ..
                 S55=3 (disable escape) ..
                 S66=1 (Lock ifs speed to S51' setting) ..
                 S67=1 (upon CD assert CTS 200 ms after RTS true) ..
may be bad values for TB+ on a VMS 4.6 MV_2 with DHV-11 serial ifc.

ANY SUGGESTIONS WILL BE WELCOME !!!
-- 
 suned1!efb@elroy.JPL.Nasa.Gov   sun!tsunami!suned1!efb   efbatey@NSWSES.ARPA
    Any statements / opinions made here are mine, alone, not those of the    
    United States, the DoD, the Navy, the Congress, the Judiciary, nor ...