From: kak@hico2.UUCP (Kris A. Kugel)
Newsgroups: comp.sys.3b1,comp.sys.att,comp.unix.wizards
Subject: Problems with STARLAN uucp link
Summary: rejection after login when connecting with starlan
Keywords: starlan 3B1 uucp HDB BNU 7300 unixpc
Date: 13 Apr 92 03:26:11 GMT
Reply-To: kak@hico2.westmark.com
Followup-To: comp.sys.3b1
Organization: High Country Software

I don't understand this: I hook up starlan, and my machines can't
connect with uucp, but it breaks AFTER the successful login,
and only over the starlan, not over a RS232 link.

One especially annoying aspect is that the successful
login through starlan keeps the uucp from dropping down to
the next uucp link, an existing (and working) RS232 link,
so the remote machine never connects on demand.  Now, I
could stick with just the RS232 link, but that kinda defeats
the whole purpose of installing starlan.

I'd think it'd have something to do with the Permissions file,
but I've checked out about every reasonable combination I can
think of, including the one shown below.  The reluctant machine
is not running the default 3B1 HDB uucp, but still . . . .

From uulog -s hico3:
uucpadm hico3  (4/12-23:10:51,4939,0) FAILED (BAD LOGIN/MACHINE COMBINATION)

Could somebody with a better knowledge of the baroque
workings of uucp take a look at the following output from
/usr/lib/uucp/Uutry -r -x9, and tell me what you think
I need to do to fix this problem? 

mchFind called (hico2)
list (rmail) num = 1
list (/) num = 1
list (/) num = 1
list (ALL) num = 1
_Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands ALL
chdir(/usr/spool/uucp/hico2)
conn(hico2)
Device Type STARLAN_NAU wanted
ProtoStr = eg
Internal caller type STARLAN
slancall: entered
slancall: flds: hico2
slancall: dev: STARLAN_NAU
slancall: open ret 6
slancall: connecting to name hico2.serve
set interface STARLAN
processdev: calling setdevcfg(uucico, STARLAN_NAU)
gdial(pc_uucp) called
chat: TCGETA failed, errno 22
expect: ("")
got it
sendthem (NLPS:000:001:102^@<NO CR>)
getto ret 6
expect: (ogin:)
login:got it
sendthem (LOGIN_NAME^M)
expect: (word:)
Password:got it
sendthem (LOGIN_PASSWORD^M)
imsg >^PShere=hico2^@Login Successful: System=hico2
omsg "Shico3 -Q0 -x9"
imsg >^PRLOGIN^@msg-RLOGIN
HANDSHAKE FAILED: REMOTE REJECT AFTER LOGIN
exit code 101
Conversation Complete: Status FAILED

TM_cnt: 0


I tried messing around with Permissions, on the off-chance
that maybe it had something to do with starlan user id's,
but that still fails with "REMOTE REJECT AFTER LOGIN".

from /usr/lib/uucp/Permissions:

# MACHINE=hico3:hicntry \
# LOGNAME=uuhico:net SENDFILES=yes REQUEST=yes READ=/ WRITE=/ COMMANDS=ALL \
# VALIDATE=hico3:hicntry

MACHINE=hico3:hicntry \
	SENDFILES=yes REQUEST=yes READ=/ WRITE=/ COMMANDS=ALL

LOGNAME=UUCP_LOGNAME:net:other SENDFILES=yes REQUEST=yes \
	READ=/ WRITE=/ COMMANDS=ALL 


I don't have a clue on this one.  Any thoughts from out there?

                               Kris A. Kugel
                             ( 908 ) 842-2707
                          uunet!westmark!hico2!kak
                        {daver,ditka,zorch}!hico2!kak
                      internet: kak@hico2.westmark.com
Newsgroups: comp.sys.3b1