Login failure uucp RH7.3 to SCO5.0.6
Murray Hooper
log from debug on linux box
uucico outhouse - (2002-10-07 14:30:44.65 5606) Calling system outhouse
(port TCP)
uucico outhouse - (2002-10-07 14:30:44.66 5606) DEBUG: fcsend: Writing sleep
sleep "\r"
uucico outhouse - (2002-10-07 14:30:46.69 5606) DEBUG: icexpect: Looking for
5 "ogin:"
uucico outhouse - (2002-10-07 14:30:46.69 5606) DEBUG: icexpect: Got
"login:" (found it)
uucico outhouse - (2002-10-07 14:30:46.69 5606) DEBUG: fcsend: Writing
"u_id\r"
uucico outhouse - (2002-10-07 14:30:46.69 5606) DEBUG: icexpect: Looking for
5 "word:"
uucico outhouse - (2002-10-07 14:30:46.69 5606) DEBUG: icexpect: Got "
Password:" (found it)
uucico outhouse - (2002-10-07 14:30:46.70 5606) DEBUG: fcsend: Writing
"password\r"
uucico outhouse - (2002-10-07 14:30:46.70 5606) DEBUG: zget_uucp_cmd: Got "
Login incorrect.\nuucico outhouse - (2002-10-07 14:30:47.61 5606) ERROR:
Line disconnected
" (error)
password & login are correct and several SCO OS5 boxes connect in to server
via uucp over TCP, but linux box doesn't want to. Any suggestions about
what to look at/for?
thanx
murray
Bill Campbell
>Hi Folks:
>
>log from debug on linux box
>
>uucico outhouse - (2002-10-07 14:30:46.70 5606) DEBUG: zget_uucp_cmd: Got "
>Login incorrect.\nuucico outhouse - (2002-10-07 14:30:47.61 5606) ERROR:
>Line disconnected
>
>password & login are correct and several SCO OS5 boxes connect in to server
>via uucp over TCP, but linux box doesn't want to. Any suggestions about
>what to look at/for?
I suspect that you're running into a parity mismatch, but it's
been at least four years since I did uucp into a standard 3.2v5.xxx
system, as we either switched to Taylor uucp on SCO or to Linux
systems for most of our uucp traffic. I remember that there were
some special setup parameters on SCO systems necessary to talk to
old SunOS boxen that did 7bit even parity instead of 8-bit none.
It would require some digging through old archives for me to get
the details, but perhaps this will get you started in the right
direction.
The chat sequence I have on one of our Linux systems that calls
an SCO OpenServer system does have some delays in it which may
also help. Here are the chat specs on our Taylor uucp sys file:
chat-timeout 120
chat "" \r ogin:-BREAK-ogin:-BREAK-ogin: \ducamco ssword: \dxxxxxx
Bill
--
INTERNET: bi...@Celestial.COM Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
Instead of giving money to found colleges to promote learning, why don't
they pass a constitutional amendment prohibiting anybody from learning
anything? If it works as good as the Prohibition one did, why, in five
years we would have the smartest race of people on earth.
-- The Best of Will Rogers
Jurr
This is what I have on my RH box in /etc/uucp/sys
called-login nuucp
myname fil9700
time Any
port type tcp
system comm
address 10.1.1.47
commands ALL
local-send /
remote-send /
local-receive /
remote-receive /
chat ogin: \L word: \P
call-login nuucp
call-password password
connecting to an sco 505 system
works like a buzz.
Jurriaan Aaftink
Network Admin
Brilmij Groep BV