bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) (07/28/89)
Hi folks, I am having all kinds of problems trying to establish a UUCP
link with a BSD machine that runs old-style UUCP. I am running XENIX
2.3.1 HoneyDanBer UUCP. Basically nothing is getting across. Is
there some kind of problem with trying to UUCP between old-style and HDB?
Sorry to ask such a neophyte question, but this is my first attempt at
this. Thanks in advance.
--Carmen
--
Carmen Maria Hardina, University of Hawaii at Manoa...
UUCP: {uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!bt455s39
ARPA: uhccux!bt455s39@nosc.MIL BITNET: bt455s39@uhccux
INET: bt455s39@uhccux.UHCC.HAWAII.EDU <-- It may work.davidsen@sungod.crd.ge.com (William Davidsen) (07/31/89)
In article <4443@uhccux.uhcc.hawaii.edu> bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) writes: | Hi folks, I am having all kinds of problems trying to establish a UUCP | link with a BSD machine that runs old-style UUCP. I am running XENIX | 2.3.1 HoneyDanBer UUCP. Basically nothing is getting across. Is | there some kind of problem with trying to UUCP between old-style and HDB? If the BSD site is calling you they need to set no parity. To do this they include P_NULL in the L.sys dialog. Have them look it up, but that's probably the problem if they're calling you. If they're getting logged in but can't do things it's almost certainly your Systems file being too restrictive for their site. good luck! bill davidsen (davidsen@crdos1.crd.GE.COM) {uunet | philabs}!crdgw1!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me
tony@oha.UUCP (Tony Olekshy) (08/01/89)
In message <4443@uhccux.uhcc.hawaii.edu>, bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) writes: > > I am having all kinds of problems trying to establish a UUCP > link with a BSD machine that runs old-style UUCP. I am running XENIX > 2.3.1 HoneyDanBer UUCP. Basically nothing is getting across... 1) Get a copy of O'Reilly & Associates' Nutshell Handbook entitled ``Managing uucp and Usenet, +1 617 527 4210 (I have 0 affiliation with them). 2) Read the manual page on the `cu' program and use it for the following tests: - Get your modem to dial a number. You can do things like (Hayes eg.) ATDT... directly in cu. If you modem looks dead, it could be the wiring (see Handbook). - Get your modem to *exchange* carriers (whistles) with the other modem. This may require fiddling with /etc/ttys and /etc/gettydefs. You may need to send other initialization commands to the modem (AT&X4, for example, see your modem manuals) for this to work, but not usually. I had trouble with one system 'till I took out all the cr*p from the manual except ATZ, and bingo! - Get a login, password, and uucico prompt from the other system. This may require fiddling with cu flags. The cu program passes ~%break and ^D through to the other end. Make a note of how you get through. 3) Use the Nutshell Handbook to set up the uucp files at each end. The experiments you conducted in step 2 should be sufficient *if you keep your notes in order*. Then uucico with the -x 9 option to debug the uucico protocol. This has always worked for me, although it can take some creative fiddling to accomplish each step. This way though, at least you know when you are making progress through the steps, and I hate feeling that my efforts are being futile. > Sorry to ask such a neophyte question, but this is my first attempt at this. And a well asked question at that. I know my experience is limited here, and I'm sure I've missed some things. But hey, it's Usenet, someone will fill us in. Yours, etc., Tony Olekshy (...!alberta!oha!tony or tony@oha.UUCP).