Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!NMSUVM1.BITNET!SYSMAN
From: SYSMAN@NMSUVM1.BITNET
Newsgroups: comp.os.vms
Subject: Disallowing logins on Terminal ports
Message-ID: <8806030250.AA28914@ucbvax.Berkeley.EDU>
Date: 31 May 88 16:09:59 GMT
Article-I.D.: ucbvax.8806030250.AA28914
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

Date: 31 May 88, 15:56:13 GMT
From: Mark Nichols              (505) 646-4183       SYSMAN   at NMSUVM1
To:   INFO-VAX at KL.SRI.COM


We have a problem concerning terminal ports and the NIU's used to
connect to the campus network. Whenever the NIU times out and goes to
the idle state the Vax interprets the response from the NIU as a login
attempt and prompts for a password. The NIU screams back "Invalid Response"
or something like that. The Vax of course kicks back "User Authorization
Failure" to which the NIU responds again with another error message. And
off it goes .... with the Vax and the NIU ping-ponging error messages
messages back and forth and the console spitting out all kinds of access
violation messages.

Is there a way to disable logins on a specific port while still
allowing a user to connect to the port via kermit to go through the
NIU and onto the network? We have tried all sorts of things with the
NIU and it seems doing something from the Vax end is more feasable.


Thanks for _ANY_ help at all.

Mark Nichols
Systems Programmer
New Mexico State University