From owner-freebsd-questions Thu Nov 8 5:33: 5 2001 Delivered-To: freebsd-questions@freebsd.org Received: from squid.tznet.com (squid.tznet.com [66.170.64.7]) by hub.freebsd.org (Postfix) with ESMTP id ABC8F37B418 for ; Thu, 8 Nov 2001 05:33:02 -0800 (PST) Received: from localhost (tech@localhost) by squid.tznet.com (8.11.2/8.11.2) with ESMTP id fA8DVI914276 for ; Thu, 8 Nov 2001 07:31:18 -0600 (CST) Date: Thu, 8 Nov 2001 07:31:18 -0600 (CST) From: Scott Pilz To: freebsd-questions@freebsd.org Subject: arplookup failed 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 I've seen many posts on freebsd-questions but no answers that have helped me with this problem. We have recently obtained a new block of address space (66.170.64.1/20). I run around 8-10 FreeBSD machines in the office, every one has the same problem .. . They are on the 66.170.64.x block, netmask of 255.255.255.0. Upon trying to ping another machine -- NT lets say, that has the address of 66.170.68.x, or 65.x, etc. will issue the following error: /kernel: arplookup 66.170.xx.xxx failed: host not on local network. Now, there MUST be a way to easily fix this. I'm sure it's just a configuration problem, please advise. Thanks. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message