From owner-freebsd-questions Wed Apr 10 14:45:33 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12180 for questions-outgoing; Wed, 10 Apr 1996 14:45:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA12171 for ; Wed, 10 Apr 1996 14:45:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02501; Wed, 10 Apr 1996 14:43:21 -0700 From: Terry Lambert Message-Id: <199604102143.OAA02501@phaeton.artisoft.com> Subject: Re: Ntalkd To: maint@spike.fa.gau.hu (Maintenance user) Date: Wed, 10 Apr 1996 14:43:20 -0700 (MST) Cc: FreeBSD-questions@FreeBSD.ORG In-Reply-To: from "Maintenance user" at Apr 10, 96 07:54:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We have FreeBSD Stable. We update the sources each week, and compiled a > new kernel about a week ago. Since that the server is unreachable by talk > from the outside world. It still works fine to talk to another user on > the server. We had no changes in the configuration, just the new kernel. > Did anyone run into the same problems? Thanx for your help, The default rules for the firewall code have changed. By default, if the firewall code is active, everything is disallowed unless you have specifically allowed it. This is probably your problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.