gsg0384@uxa.cso.uiuc.edu (01/28/89)
Hi,
I have a problem:
The modem process program for Domain/IX 9.5.1 (probably the same for
the OS 10.1 also) which reads as `siologin_modem' (? I do not remember
the name correctly) issues the following prompt which is quite different
from standard UNIX prompt:
AEGIS-DOMAIN/IX Kernel, revision 9.5.1 ...(the dial-in date time etc) ...
Enter line access code:
Now it should stop and wait till I enter the code. However, nineteen out
of twenty, it shows the following screen:
AEGIS-DOMAIN/IX Kernel, revision 9.5.1 ...(the dial-in date time etc) ...
Enter line access code:
Invalid line access code.
Enter line access code:
You are out of chance. Too bad... good by
And then clicking sound from my modem showing "NO CARRIER".
It makes me really mad. The machine does not give me a chance actually.
I read the modem manual (Smartmodem 1200) thoroughly, and did some trick
on the host's modem so that Apollo DN580 may give me a second chance
showing the same long message prompt again. (Ignore-DTR setting adjust)
This time, nine out of 10 cases, the 'siologin_modem' process
dies before issuing the second showing of the above message. Then I
have to wait about 15 minutes till the scheduler of the OS revives the
'siologin_modem' process. Argggg...
I asked the administrator (he calls himself "The Lord") to increase the
number of chance making DN580 issue "Enter line access code:" more than
twice. He said that the number of chance is programed in binary code
and there is nothing he can do about it.
The usual UNIX siologin_modem or _dialin or whatever process does not
ask the line access code as Apollo does. I won't complain about that
if Apollo does what is supposed to do. We have one DN580, three 3000s,
one 660, and one DSP160. The same thing happened on 3000s, 660 as well
as 580.
Has anyone had the same experience ever?
Is there any get-around trick?
Does DOMAIN/OS 10 show the same prompt message when dialed in?
Pleas HELP ME. HELP...
Hugh gsg0384@uxa.cso.uiuc.edu
song@uispg.csl.uiuc.edulray@uxh.cso.uiuc.edu (01/31/89)
Hey! And here I thought I was the Apollo Lord at the UIUC! :-) In the configuration file for siomonit, rip out the "-dialin." The resulting login prompt will be much closer to (though not exactly) what you want and expect. At SR10 and above, you can use getty, which I hear fixes problems like the one you are experiencing with modems, as well as integrating the UNIX stuff in, but having not tried it, I cannot say for certain. Leland Ray lray@civilgate.ce.uiuc.edu (217) 333-3821
dbfunk@ICAEN.UIOWA.EDU (David B. Funk) (01/31/89)
In posting <133000001@uxa.cso.uiuc.edu>, Hugh (gsg0384@uxa.cso.uiuc.edu) says: > I have a problem: > ... > Now it should stop and wait till I enter the code. However, nineteen out > of twenty, it shows the following screen: > > AEGIS-DOMAIN/IX Kernel, revision 9.5.1 ...(the dial-in date time etc) ... > Enter line access code: > Invalid line access code. > Enter line access code: > You are out of chance. Too bad... good by Your problem is that the siologin process sees "return" characters before it sees your attempt to type in the line access code. As the line access code read is not echoed, you don't see the characters its receiving. You are probably having 1 of 2 possible problems: 1) When dialing in with your modem, do NOT hit the "return" key until after you see the "Enter line access code:" prompt. Any "returns" that you hit after the remote modem has answered the phone and before the prompt is issued, will be saved. Then the siologin process will see these saved-up "returns" and think that you are giving it a null line access code. It may take several seconds between the time that the remote modem answers the phone and the display of the prompt. During this time resist temptation to bang on the "return" key, you'll only cause this problem to arise. IE when calling in, give the command to your modem to dial the phone (EX: ATDT12345678 ) then take your hands off the keyboard of your terminal and WAIT. Don't even touch the keyboard until AFTER the "Enter line access code:" prompt appears. Yes, I know that on many other computer systems you have to dial in and then hit the "return" key several times to get a "login" prompt. Not so for Apollo, this will only cause your problem. If you are using a PC and some kind of terminal emulation program to dial your modem, check the progam to make sure that it's not doing something like this. 2) If the preceding description is not true (you've followed the directions and it still bombs you out), then the Apollo is seeing characters from the answering modem before it sees them from you. If the answering modem on the Apollo end is emitting some kind of text to the Apollo when it picks up the phone (such as a result code like "connect 1200") then the siologin process will think that this is a bogus line access code and bomb out. Have the Apollo administrator check the modem to see if it is emitting some text when a user calles in. Many "smart" modems have lots of configuration parameters, which if not all set correctly can cause things like this to happen. One way to check this, disconnect the answering modem from the Apollo and connect it to a terminal. Make a call to it and watch the terminal screen. If at all possible, put the terinal in a mode that will cause it to display control characters as well as regular ones. Even a bare "cr" characer at this time will cause this problem. A variation on this problem is caused by phone line noise, not a modem setup problem. If the answering modem "hears" enough noise on the line, after it answers the phone and before it locks onto your modem's carrier, then it may spit out garbage characters. The monitoring terminal trick will also detect this problem. This problem is real tough to fix, you may have to try different modems at the Apollo end. Dave Funk
dbfunk@ICAEN.UIOWA.EDU (David B. Funk) (02/01/89)
WRT posting <18300002@uxh.cso.uiuc.edu> from Leland Ray <lray@civilgate.ce.uiuc.edu> about the siologin problem from <133000001@uxa.cso.uiuc.edu> > In the configuration file for siomonit, rip out the "-dialin." The > resulting login prompt will be much closer to (though not exactly) > what you want and expect. Yes, this will cure the problem of being bombed out by line access code entry failures, but it will introduce a new set of problems if you really have a modem connected to the Apollo. You will lose the modem control action of the DTR/DCD lines. When a modem is connected to an Apollo and the "-dialin" attribute is set in the "siomonit_file" then the DTR & DCD lines are used to control the connection. The Apollo will assert DTR, which is a "go-ahead" signal to the modem. When the modem detects a caller's carrier it asserts DCD, this tells the Apollo to initiate a login sequence. (This is why you don't need to bang on the "return" key.) If the user gives a "logout" command, then the Apollo drops DTR as part of its logging out process. When the modem sees DTR drop, it "hangs up the phone" and breaks the connection. If the user just hangs up the phone, with out giving a "logout", the modem drops DCD. When the Apollo sees this change, it gives the user's shell a stop fault to make it exit, freeing the port for the next user to login. Without "-dialin", if a user's call gets disconnected (due to a hangup or noise on the line) the login shell is still left active. Then the next user to call in will be connected to the previous user's shell. The ideal answer would be to provide DTR/DCD modem control without the line access code checking. The current version... STOP THE PRESSES!!!!! I've just found what you're looking for!! There is an undocumented option to siologin called "-access_retry" that lets you set the number of tries that you get to enter the line access code. This option must be followed by a number to set the try count on a "-dialin" line, in the "siomonit_file". An example of its use would be: -repeat /dev/sio1 -dialin -access_retry 10 -n siologin_1 /com/sh This would give you 10 chances to enter the line access code before it bombed you out. If you give it a value of zero, it will not ask for the line access code at all, just go directly to the "Please log in:" prompt. However, be aware that you have only 2 chances to give it your login ID & password before it bombs you out. So if you have the spurious "return" problem, that I mentioned in my previous posting, you'll be no better off. In that case you'll want as many tries as you need to eat up the garbage characters. Dave Funk