From owner-freebsd-stable Fri Dec 21 9:16:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 12C9437B419 for ; Fri, 21 Dec 2001 09:16:15 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id fBLHGBd17784; Fri, 21 Dec 2001 09:16:11 -0800 (PST) Message-Id: <200112211716.fBLHGBd17784@ptavv.es.net> To: Rob Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: X xauth problems with DHCP- maybe FBSD settings issue In-reply-to: Your message of "Fri, 21 Dec 2001 08:31:25 PST." <3C2363DD.FCA4EF5C@pythonemproject.com> Date: Fri, 21 Dec 2001 09:16:11 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rob, My condolences on the loss of your @Home service. The old @Home node names are not used by ATTBI, so the name you are specifying fails to translate to an IP address and xauth gets upset. The fix is probably to add the name of your system (and I would strongly urge you to re-name it) to /etc/hosts. That seems to have done the trick for me. 192.168.168.100 pikes.es.net pikes You can create the unix socket because it is a truly a named socket and there is no issue with associating it with an IP address. (Also, note that there is no attbi.com name on my system. That was my choice since ATTBI does not seem interested in properly configuring DNS.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message