todd@ivucsb.UUCP (Todd Day) (01/28/89)
I am trying to establish a uucp connection between a Mac II and a UNIXPC. It is a direct 19200 serial line. My UNIXPC can establish a uucico with the Mac, but the Mac can't initiate a uucico session itself. Running uucico on the Mac with -x9 produces: [gets the line] [logs in ok] imsg> [some numbers] Shere=ivucsb [...] valid sys Shere = ivucsb imsg> [...] RLOGIN [...] 0-RLOGIN [the Mac then proceeds to close the connection, gives 07 as some code, and then exits with 0] On my UNIXPC, in /usr/spool/uucp/LOGFILE, I get an error message about BAD LOGIN/MACHINE NAME. I've tried just about everything I can think of. The UNIXPC has no problem logging into the Mac and getting uucico to run. Thanks for your help. Todd Day | ..!apple!comdesign!ivucsb!todd | todd@ivucsb.UUCP
cspencer@spdcc.COM (Cliff Spencer) (01/30/89)
In article <496@ivucsb.UUCP> todd@ivucsb.UUCP (Todd Day) writes: >On my UNIXPC, in /usr/spool/uucp/LOGFILE, I get an >error message about BAD LOGIN/MACHINE NAME. > >I've tried just about everything I can think of. The UNIXPC >has no problem logging into the Mac and getting uucico to run. Does the PC have an entry for the Mac in L.sys? This could be of the form Mac Never Are you sure that the system name the Mac provides is the same name that the PC expects to see? -cliff
ebd@cup.portal.com (Elliot B Dierksen) (02/02/89)
Todd Days writes: > I am trying to establish a uucp connection between a Mac II and > a UNIXPC. It is a direct 19200 serial line. My UNIXPC can > establish a uucico with the Mac, but the Mac can't initiate a > uucico session itself. [some of explanation of problem deleted] > On my UNIXPC, in /usr/spool/uucp/LOGFILE, I get an > error message about BAD LOGIN/MACHINE NAME. The problem is (I am pretty sure!) that the logname that the MAC is using is not in the USERFILE. if that is not the case, check the order in which the lognames appear in your passwd files. uucico establishes the logname of the caller in a strange way. first it takes the UID number assigned by login from the logname keyed by the user, then it looks for the first logname that matches that UID number. case in point if your passwd file had these entries in this order: uucpadm::6:5:UUCP:/usr/spool/uucppublic:/usr/lib/uucico nuucp::6:5:UUCP:/usr/spool/uucppublic:/usr/lib/uucico uucico would try and use uucpadm as the logname, and if it were not in USERFILE, it would give you the BAD LOGIN message you described. when i encountered this problem, it was because one of the machines i UUCP with sorted its passwd file and blew uucico's mind! check out the things i mentioned there. if that is not the problem, send me some e-mail. i'm a battle-scarred veteran of the different machine uucp connectivity war!! Good Luck! Elliot Dierksen ebd@cup.portal.com