Date: Tue, 27 Jan 2004 19:17:38 -0500 From: "George Dew" <gdew@responsenetworking.com> To: <freebsd-bugs@FreeBSD.ORG> Subject: TCP/IP issue Message-ID: <DMECLJPFEIMDDDCMMEMHEELDEFAA.gdew@responsenetworking.com>
next in thread | raw e-mail | index | archive | help
I'm sorry to bother you, but I've tried a lot of places and I'm not sure where to look for the answer. I've done a number of FreeBSD installations over the past two years. I've replaced about 10-20 Windows file servers with FreeBSD running SAMBA. I've also installed a number of FreeBSD servers running MySQL/Apache for web applications. I'm telling you this only so that you know that I'm not a complete novice when it comes to FreeBSD. However, I just did an installation on an older machine that is giving me some problems. The machine has an older motherboard with a sis900 NIC. The sis900 is configured as 192.168.1.10/24, with a default gateway of 192.168.1.1 (identified in /etc/rc.conf). The DNS servers belong to the appropriate ISPs (identified in resolv.conf). There are several Windows workstations on the network starting at 192.168.1.100 - 192.168.1.105 that are receiving dynamic IP addresses from the Linksys router at 192.168.1.1. The problem is this. The BSD box can ping the Windows workstations (W98-Win2K) at 192.168.1.100, 192.168.1.101, 192.168.1.102...and so on, but it cannot pint 192.168.1.1 (the default gateway). What makes it even more strange is that even though the BSD machine can pint 192.168.1.100, the Windows machine (Win2K) at 192.168.1.100 cannot ping the BSD box at 192.168.1.10. Do you have any advice as to where I might be able to find the answer to this? I'd really appreciate any help, and I appreciate your taking the time. Thanks. _____________________________ George Dew Response Networking Inc. 212-539-3000 support@responsenetworking.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DMECLJPFEIMDDDCMMEMHEELDEFAA.gdew>