Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!GRIN1.BITNET!MCGUIRE From: MCGUIRE@GRIN1.BITNET ("The Sysco Kid ", McGuire,Ed) Newsgroups: comp.os.vms Subject: Disallowing logins on Terminal ports Message-ID: <8806280840.AA18197@ucbvax.Berkeley.EDU> Date: 7 Jun 88 16:26:56 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 65 ------------------------------ Begin Reference ------------------------------- Date: Tue, 31 May 88 16:09:59 gmt Received: From NDSUVM1(MAILER) by GRIN1 with Jnet id 0590, for MCGUIRE@GRIN1; Tue, 7 Jun 88 08:55 CDT, by NDSUVM1 (Mailer X1.25) id 0583; Tue, 07 Jun 88 08:53:49 CDT Reply-to: INFO-VAXKL.SRI.COM Sender: "INFO-VAX Discussion"Comments: CROSSNET mail via SMTP@INTERBIT From: SYSMAN%NMSUVM1.BITNET@CUNYVM.CUNY.EDU Subject: Disallowing logins on Terminal ports Comments: To: info-vax@kl.sri.com To: "Ed McGuire (McGuire,Ed)" 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 ------------------------------- End Reference -------------------------------- Mark, It was not clear to me whether your Kermit users are starting on the VAX and connecting to remote systems (outbound), or whether they are starting on remote systems such as microcomputers and connecting to the VAX (inbound). If your Kermit connects are outbound, then you can change the characteristics of the port with the command SET TERMINAL/NOTYPEAHD/PERMANENT. That will stop the looping, because the job controller will no longer check for unsolicited input on the port and start LOGINOUT. If your connects are inbound, then you won't want to do that because your users will be unable to log in. In that case, one VAX solution is to have an operator do SET TERMINAL/TYPEAHD/PERMANENT whenever someone wants to connect, and then SET TERMINAL/NOTYPEAHD/PERMANENT when the connection is broken. This is rather inconvenient, of course. Can you change your communications equipment to do full modem control? If the VAX port is set /MODEM/PERMANENT, then the VAX will use RS-232 control signals as documented in the I/O manual in the section on the terminal driver. I think a side effect of this is that the VAX will ignore all incoming data unless it sees control signals that indicate that a connection is being established. Ed