From owner-freebsd-questions Sat May 2 20:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12321 for freebsd-questions-outgoing; Sat, 2 May 1998 20:10:04 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12270 for ; Sat, 2 May 1998 20:09:45 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id UAA21521; Sat, 2 May 1998 20:08:28 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Sat, 2 May 1998 20:08:28 -0700 (PDT) From: Doug White Reply-To: Doug White To: Snob Art Genre cc: questions@FreeBSD.ORG Subject: Re: mysterious network problem, continued In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Apr 1998, Snob Art Genre wrote: > Two additional data points, both very interesting: > > 1) Connections from non-FreeBSD machines work fine. Other FreeBSD > machines are unable to connect. > 2) I suspect the problem is in TCP, because IP is working (traceroute > uses it), and the services with problems are all TCP-based. > Traceroute seems to invoke the UDP code by connecting to a > nonexistant port. > > The first point is the more interesting, and I really want to know why > it is. Oh. Try disabling tcp extensions. Are you logging into an Annex, by chance? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message