UUCP from 4.2BSD->AT&T 3B2

[Ron Thielen]

We have been scratching our heads over this one for a while.  Any help would
be greatly appreciated.

I am attempting to establish a UUCP connection between my Pyramid and an AT&T
3B2-400.  When we call the 3B2, uucico fires up on their side and identifies
their system properly.  It then sends LOGIN where my system is expecting OK.
My system then gives up with HANDSHAKE FAILED.  I know of at least one 4.2BSD
VAX experiencing the exact same problem with a different 3B2.

The 3B2 doesn't have a source license, and my System V source doesn't give me
a clue.  We experience the same problem whether running uucico from the 4.2BSD
universe or the System V universe on the Pyramid.

Here's a script of our conversation.


ucb root 1 cd /usr/lib/uucp
ucb root 2 uucico -r1 -x9 -spaladin&
[1] 1159
ucb root 3 uucp sphinx (1/9-17:44-1159) DEBUG (ENABLED)
finds called
getto called
call: no. paladin for sys paladin
Using ACU to call
Dialing T(PHONE#)
Using hayes
dc - /dev/ttyi47
\015\012OK\015\012\015\012CONNECThayes ok
login called
wanted ogin: \015\012\015\012remote login:got that
send (USERID)
wanted assword:  pcd\015\012Password:got that
send (PASSWORD)
uucp paladin (1/9-17:45-1159) SUCCEEDED (call to paladin )
imsg >\015\012UNIX System V Release 2.0.4 3B2 Version 2\015\012paladin\015\012Copyright (c) 1984 AT&T\015\012All Rights Reserved\015\012\020<
Shere=paladin\000imsg >\020<
RLOGIN\000msg-RLOGIN
uucp paladin (1/9-17:45-1159) HANDSHAKE FAILED (LOGIN)
Hanging up fd = 7
exit code 0

[1]    Done                 uucico -r1 -x9 -spaladin