Issues connecting

I setup a simple Debian server (v4) with Apache 2 and BIND DNS on a
static IP address. I can access the website from my computer which is
on another static IP address one number off. One other system that is
offsite can also access the website but no one else can. Can't even
ping the server. What makes it more interesting is I have a Windows
server on another static IP, same internet connection and everyone can
access it. Anyone have any ideas of what I may missing here for the
Debian server that is preventing the access to it? BIND is the DNS
server for domains pointing to both the Debian and Windows but
everything seems to be working fine for the Windows server so I think
I can rule out BIND being setup wrong.

Thanks for your help!

On Mon, 22 Oct 2007 05:05:11 +0000, grantroelofs rearranged some electrons
to say:

> I setup a simple Debian server (v4) with Apache 2 and BIND DNS on a
> static IP address. I can access the website from my computer which is
> on another static IP address one number off. One other system that is
> offsite can also access the website but no one else can. Can't even
> ping the server. What makes it more interesting is I have a Windows
> server on another static IP, same internet connection and everyone can
> access it. Anyone have any ideas of what I may missing here for the
> Debian server that is preventing the access to it? BIND is the DNS
> server for domains pointing to both the Debian and Windows but
> everything seems to be working fine for the Windows server so I think I
> can rule out BIND being setup wrong.
>
> Thanks for your help!

Sounds like a routing problem. How are you routing your incoming traffic?

david wrote:
> On Mon, 22 Oct 2007 05:05:11 +0000, grantroelofs rearranged some electrons
> to say:
>
>> I setup a simple Debian server (v4) with Apache 2 and BIND DNS on a
>> static IP address. I can access the website from my computer which is
>> on another static IP address one number off. One other system that is
>> offsite can also access the website but no one else can. Can't even
>> ping the server. What makes it more interesting is I have a Windows
>> server on another static IP, same internet connection and everyone can
>> access it. Anyone have any ideas of what I may missing here for the
>> Debian server that is preventing the access to it? BIND is the DNS
>> server for domains pointing to both the Debian and Windows but
>> everything seems to be working fine for the Windows server so I think I
>> can rule out BIND being setup wrong.
>>
>> Thanks for your help!
>
> Sounds like a routing problem. How are you routing your incoming traffic?

By routing, are you referring to my firewall? I'm using iptables. My
output is the following:

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

As you can see, I haven't really set it up yet.

Grant wrote:
> david wrote:
>
>> On Mon, 22 Oct 2007 05:05:11 +0000, grantroelofs rearranged some
>> electrons
>> to say:
>>
>>> I setup a simple Debian server (v4) with Apache 2 and BIND DNS on a
>>> static IP address. I can access the website from my computer which is
>>> on another static IP address one number off. One other system that is
>>> offsite can also access the website but no one else can. Can't even
>>> ping the server. What makes it more interesting is I have a Windows
>>> server on another static IP, same internet connection and everyone can
>>> access it. Anyone have any ideas of what I may missing here for the
>>> Debian server that is preventing the access to it? BIND is the DNS
>>> server for domains pointing to both the Debian and Windows but
>>> everything seems to be working fine for the Windows server so I think I
>>> can rule out BIND being setup wrong.
>>>
>>> Thanks for your help!
>>
>>
>> Sounds like a routing problem. How are you routing your incoming
>> traffic?
>
>
> By routing, are you referring to my firewall? I'm using iptables. My
> output is the following:
>
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
>
> As you can see, I haven't really set it up yet.

No - post the output of:

route -n

Additionally, post the output of:

ifconfig -a

--

Tauno Voipio
tauno voipio (at) iki fi