Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!howland.erols.net!news.sprintlink.net!news-peer.sprintlink.net!uunet!in2.uu.net!204.97.220.6!earth.superlink.net!stardot.com!hhui From: hhui@stardot.com (Hui-Hui Hu) Newsgroups: comp.unix.bsd.freebsd.misc Subject: kerberos woes - can't figure out what is not kerberized Date: 29 Dec 1996 10:17:33 GMT Organization: Stardot Networks Ltd Lines: 18 Message-ID: <5a5gft$7gp@earth.superlink.net> NNTP-Posting-Host: lucidity.stardot.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33075 Hi, I'm running a kerberosIV system on FreeBSD 2.2-ALPHA and commands such as rlogin can't figure out if the remote system is not kerberized, thus causing timeouts unless I say rlogin -K remotehost. bad computer. Actually, come to think of it, the only time it does display the message "warning: remote host does not support kerberos" is when the non-kerberized host's realm is already defined in my realms file. if the realm is undefined, it will time out. I know these details are sketchy but has anyone else experienced the same problem? what am I doing wrong? thanks. -- Tung-Hui Hu. Hacker. Arc Four. hhui@arcfour.com. Accounts I have gotten killed because they junkmailed me: 11