From: bill@twg.bc.ca (Bill Irwin)
Subject: Solution to: Trouble configuring UUCP on TCP/IP
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Reply-To: bill@twg.bc.ca (Bill Irwin)
Organization: The Westrheim Group, Vancouver, B.C., Canada
Date: Mon, 4 Jan 1993 09:55:42 GMT
Keywords: sco uucp tcp/ip
Precedence: bulk


bill@twg.bc.ca (Bill Irwin) writes:

: unilabs!chare@uunet.UU.NET (Chris Hare) writes:

: : In article <2808@twg.bc.ca> bill@twg.bc.ca (Bill Irwin) writes:
: : >
: : >I am having trouble configuring UUCP to use the TCP/IP network as
: : >its "device".  I have two systems, both running SCO UNIX 3.2.4,

: : I went through this recently.  this is what you need to do.

: : In Devices, create an entry which reads

: : TCP TCP,e     -       Any     TCP     540

: : Note:  this instructs uucp to use the 'e' protocol, and to connect on port
: : 540.

: I have the uucico accessing the TCP device now, but it is failing
: after the password is given to the remote system.  Following is a
: portion of the -x9 log:

: mchFind called (SystemB)
[stuff deleted]
: sendthem (^M)
: expect: (gin:)
: login:got it
: sendthem (systema^M)
: expect: (word:)
:  Password:got it
: sendthem (password^M)
: msg > Login incorrect.^Jimsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg >imsg

: The ">imsg" stuff keeps going and going until the log is is over
: 700Kb in size.  Then it fails.  I have seen this type of output
: on a normal modem connection before, but can't recall what it is
: a symptom of.

Actually, this was the uutry log produced after I changed the
entry in "/etc/inetd.conf" from "/etc/uucpd" to
"/usr/lib/uucp/uucpd".  There seemed to be another uucpd on the
system and it seemed to get me a little further along in the
dialogue.  The original uucpd was producing a "user unknown"
message right after the login name was given and before a
password was even checked.  This is the right uucpd to use, which
was pointed out to me by belal@sco.com.  The one in usr/lib/uucp
was released with the UNIX runtime in error and was compiled from
an earlier version of the source, with the wrong development
environment.

The mystery is solved.  It seems that the Systems file entry chat
script that was used when a modem was being used to connect was
producing my "user unknown" message.  Here are the two entries
that I have used to fix the problem:

#SystemB Any TCP,e  Any - --gin:--gin:--gin:-BREAK-ogin:-BREAK-ogin: systema word: foobar
SystemB Any TCP,e  Any - gin: systema word: foobar

The first one was being used until today, when I was mailed an
extract from the SCO "How to" database that showed the greatly
simplified chat script.  I decided to take a shot in the dark and
see if the BREAK (which I never saw being sent in the uutry log)
was causing the trouble.  The second entry worked fine, first
try.

I am now going to test the first entry by just removing the BREAK
portion of the entry, to see if it is the syntax of the script
that causes the problem, or the BREAK.

I would like to thank the following people who responded and
helped in this solution:

fenner@cs.psu.edu (Bill)
belal@sco.com (Bela)
chare@unilabs.org (Chris Hare)
fitz@wang.com
giles@promed.com.au (Giles Lean)
udo@umonk.GUN.de (Udo Monk)
-- 
Bill Irwin    -       The Westrheim Group     -    Vancouver, BC, Canada
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
uunet!twg!bill            (604) 431-9600 (voice) |     Your Computer  
bill@twg.bc.ca            (604) 430-4329 (fax)   |    Systems Partner
Newsgroups: comp.protocols.tcp-ip