From owner-freebsd-current Tue Feb 3 12:06:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24331 for current-outgoing; Tue, 3 Feb 1998 12:06:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24294 for ; Tue, 3 Feb 1998 12:06:51 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA09191; Tue, 3 Feb 1998 15:06:34 -0500 (EST) Date: Tue, 3 Feb 1998 15:06:33 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Scot W. Hetzel" cc: freebsd-current@FreeBSD.ORG Subject: Re: current.freebsd.org unable to connect In-Reply-To: <00ec01bd30d9$43e59dc0$c3e0d9cf@admin.westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" You should make sure that your machine's reverse lookup is happening OK. The snap server seems to tend toward the "super-paranoid". It nukes mismatches and things that just aren't reversed... Charles Sprickman spork@super-g.com ---- "I'm not a prophet or a stone-age man Just a mortal with potential of a superman I'm living on" -DB On Tue, 3 Feb 1998, Scot W. Hetzel wrote: > I tried to connect to the SNAP shot server yesterday and today, and was > unable to get a connection. > > The error I am getting back is: > > 421 Service not available, remote server has closed connection > > Is there a problem with the SNAP shot servers? > > Thanks, > > Scot >