From owner-freebsd-questions@FreeBSD.ORG Mon Nov 10 18:39:06 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD0A416A4CF for ; Mon, 10 Nov 2003 18:39:06 -0800 (PST) Received: from lsh142.siteprotect.com (lsh142.siteprotect.com [66.113.130.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39C8443FB1 for ; Mon, 10 Nov 2003 18:39:05 -0800 (PST) (envelope-from you@aredumb.com) Received: (from aredumb@localhost) by lsh142.siteprotect.com (8.11.6/8.11.6) id hAB2d4r23341 for freebsd-questions@freebsd.org; Mon, 10 Nov 2003 20:39:04 -0600 Date: Mon, 10 Nov 2003 18:39:04 -0800 From: you@aredumb.com (Will Yardley) To: Message-ID: <20031111023904.GB19869@aredumb.com> Mail-Followup-To: you@aredumb.com (Will Yardley), References: <20031111021649.GA17409@aredumb.com> <002801c3a7fa$c35cd750$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002801c3a7fa$c35cd750$1200a8c0@gsicomp.on.ca> User-Agent: Mutt/1.4i Subject: Re: problems with FreeBSD telnet client X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 02:39:06 -0000 Matthew Emmerton wrote: > > When I telnet to a Cisco device from a FreeBSD machine, I get this > > error: > > > > jazz% telnet somerouterorswitch > > Password: Kerberos: No default realm defined for Kerberos! > > > > Assuming you don't use Kerberos, is there a way to make the telnet > > client not attempt to use it to authenticate? > I have a feeling that this is coming from the telnet server (ie, the Cisco > box), since no such text shows up in the FreeBSD telnet client sources our > our Kerberos-[45] libraries. (4-STABLE, cvsup'd just a few minutes ago.) > > Perhaps the Cisco box has Kerberos support, and since it senses that the > FreeBSD telnet client is Kerberos-aware, it spews out this warning to notify > you of the server misconfiguration? Yeah - I was guessing that that was the problem. I was hoping there was a way to get the telnet client not to try to use Kerberos, but sounds like "-K" may be the closest thing to that. Checked out some of the options at: http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_command_summary_chapter09186a00800880ac.html but don't see anything that will help.