From owner-freebsd-questions Wed Feb 20 9:13: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from out4.mx.nwbl.wi.voyager.net (out4.mx.nwbl.wi.voyager.net [169.207.1.77]) by hub.freebsd.org (Postfix) with ESMTP id 654A237B400 for ; Wed, 20 Feb 2002 09:13:02 -0800 (PST) Received: from shell.core.com (IDENT:2525@shell.core.com [169.207.1.89]) by out4.mx.nwbl.wi.voyager.net (8.11.1/8.11.4/1.7) with ESMTP id g1KHD1532392; Wed, 20 Feb 2002 11:13:01 -0600 (CST) Received: from localhost (raiden@localhost) by shell.core.com (8.11.6/8.11.6/1.3) with ESMTP id g1KHCux05026; Wed, 20 Feb 2002 11:12:56 -0600 (CST) Date: Wed, 20 Feb 2002 11:12:56 -0600 (CST) From: Steven Lake X-X-Sender: raiden@shell.core.com To: Patrick Soltani Cc: freebsd-questions@freebsd.org Subject: Resolved!!: Strange Networking problem In-Reply-To: <3DBB075EEB95944492E127F2B9A96FAF0CE112@ultra-exchange.UltraDNS.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a word out to everyone who helped out. After wracking my brain for a long number of hours I finally found the solution. I did some testing on the DSL router that was giving me all of the heartaches and troubles with our remove fbsd server and after taking it aside and threatening it with greavous harm, it behaved. :) Actually I had to bounce it twice, run a reset on it, then force all fresh settings into it and it's back and playing happy again. Again, thanks everyone for helping me solve this. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message