screwy network/dmz problem

Jerry Bell jbell at stelesys.com
Mon Apr 4 17:11:28 PDT 2005


The first thing I would check is that it's the BSD box that you are
actually pinging.  I'd try unplugging it and trying the ping again from
the IIS box.  Barring that, I would double and triple check the network
mask on the BSD box.  Also, make sure you don't have some screwy firewall
rules on the BSD server that prevent outbound pings.
Next, look at the output of 'netstat -rn'
You should see entries for the default gateway as well as your local
network.  If all looks good there, check your arp table with arp -a.  If
you don't see anything there, it's probably a layer 1 or 2 problem
(cabling/vlan).
There are many many possibilities for what could be wrong, but it's hard
for us to say.  Let us know what you find on those tests.

Jerry
http://www.syslog.org

> here in our office we have a firewall running Firewall-1 (it is
> administered remotely from another office in another country). It is set
> up with a dmz so I can host a web server (which is running IIS), but it
> works. I am now adding another web server, running Apache/FreeBSD. Problem
> is the FBSD box does not ping anything. The IIS box can ping the FBSD box
> and get a response from it. I have used the same network settings on the
> FBSD box that are on the IIS box, changing only the ipaddress. I don't
> understand why the FBSD box only responds with network not found when
> trying to ping anything. Now the IIS box is not a member of any network,
> it is it's own workgroup called DMZ. Is the problem that the FBSD box
> needs to be a member of the workgroup DMZ? And if so, how do I get it
> there?
>
> Regards,
> Chip
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>




More information about the freebsd-questions mailing list