Weird Connection Problem

I have two servers: one with Debian 4 on it and one with Microsoft
Windows Server 2003. They are both on the same internet connection, one
number away from each other in IP address. Everyone can connect to both
just fine except for one client. He can connect to the Windows server
but not the Debian server. I had him first try to ping it using the
domain that points to the Debian server. It pulled up the right IP
address but timed out. I then had him ping the IP address. This too
timed out. He has 2 computers in his house and both are doing the same
thing. Nobody else has this problem; they are able to connect to both.
Does anyone have any idea of what could be causing this? Is it
something I setup incorrectly on the Debian Server? I'm not even sure
where to go with this anymore. I appreciate any help and suggestions
you can offer!

Grant wrote:
> I have two servers: one with Debian 4 on it and one with Microsoft
> Windows Server 2003. They are both on the same internet connection, one
> number away from each other in IP address. Everyone can connect to both
> just fine except for one client. He can connect to the Windows server
> but not the Debian server. I had him first try to ping it using the
> domain that points to the Debian server. It pulled up the right IP
> address but timed out. I then had him ping the IP address. This too
> timed out. He has 2 computers in his house and both are doing the same
> thing. Nobody else has this problem; they are able to connect to both.
> Does anyone have any idea of what could be causing this? Is it
> something I setup incorrectly on the Debian Server? I'm not even sure
> where to go with this anymore. I appreciate any help and suggestions
> you can offer!


He has a problem. What distro is he running?

If it is a Ubuntu, it could be the ipv6. Although some folks who don't
tell us the distro they are using might be using an Ubuntu Distro. It
uses a different Ipv6 than most Linux distros. More info here:

> http://www.lockergnome.com/nexus/lin...internet-help/

AHappyCamper wrote:
> Grant wrote:
>> I have two servers: one with Debian 4 on it and one with Microsoft
>> Windows Server 2003. They are both on the same internet connection, one
>> number away from each other in IP address. Everyone can connect to both
>> just fine except for one client. He can connect to the Windows server
>> but not the Debian server. I had him first try to ping it using the
>> domain that points to the Debian server. It pulled up the right IP
>> address but timed out. I then had him ping the IP address. This too
>> timed out. He has 2 computers in his house and both are doing the same
>> thing. Nobody else has this problem; they are able to connect to both.
>> Does anyone have any idea of what could be causing this? Is it
>> something I setup incorrectly on the Debian Server? I'm not even sure
>> where to go with this anymore. I appreciate any help and suggestions
>> you can offer!
>
>
> He has a problem. What distro is he running?
>
> If it is a Ubuntu, it could be the ipv6. Although some folks who don't
> tell us the distro they are using might be using an Ubuntu Distro. It
> uses a different Ipv6 than most Linux distros. More info here:
>
>> http://www.lockergnome.com/nexus/lin...internet-help/
>

He's not running Linux. He is using Windows XP.

Hello,

Grant a écrit :
> I have two servers: one with Debian 4 on it and one with Microsoft
> Windows Server 2003. They are both on the same internet connection, one
> number away from each other in IP address. Everyone can connect to both
> just fine except for one client. He can connect to the Windows server
> but not the Debian server. I had him first try to ping it using the
> domain that points to the Debian server. It pulled up the right IP
> address but timed out. I then had him ping the IP address. This too
> timed out. He has 2 computers in his house and both are doing the same
> thing. Nobody else has this problem; they are able to connect to both.

Can at least other clients ping your Debian server ?

> Does anyone have any idea of what could be causing this? Is it
> something I setup incorrectly on the Debian Server?

It may be a wrong netmask on the Debian server. If the client address
falls in the subnet defined by the wrong netmask, it is unreachable from
the server.

> I'm not even sure where to go with this anymore.

Run a traceroute from the client to the server and vice versa.
Run a packet sniffer on the client and the server while trying to ping
or connect to the server.

Pascal Hambourg wrote:
> Hello,
>
> Grant a écrit :
>> I have two servers: one with Debian 4 on it and one with Microsoft
>> Windows Server 2003. They are both on the same internet connection,
>> one number away from each other in IP address. Everyone can connect
>> to both just fine except for one client. He can connect to the
>> Windows server but not the Debian server. I had him first try to ping
>> it using the domain that points to the Debian server. It pulled up
>> the right IP address but timed out. I then had him ping the IP
>> address. This too timed out. He has 2 computers in his house and
>> both are doing the same thing. Nobody else has this problem; they are
>> able to connect to both.
>
> Can at least other clients ping your Debian server ?
>
>> Does anyone have any idea of what could be causing this? Is it
>> something I setup incorrectly on the Debian Server?
>
> It may be a wrong netmask on the Debian server. If the client address
> falls in the subnet defined by the wrong netmask, it is unreachable from
> the server.
>
>> I'm not even sure where to go with this anymore.
>
> Run a traceroute from the client to the server and vice versa.
> Run a packet sniffer on the client and the server while trying to ping
> or connect to the server.

Yes, others can ping the Debian server.

Can you tell me more about the netmask or point me somewhere where I can
get more information about this. I guess I'm not 100% sure how to set
this in Debian.

Grant a écrit :
>
> Can you tell me more about the netmask or point me somewhere where I can
> get more information about this. I guess I'm not 100% sure how to set
> this in Debian.

Print the contents of the network configuration file
/etc/network/interfaces (if needed, "man interfaces" will tell about the
syntax) and the output of the commands "ifconfig" (or "ip address") and
"route -n" (or "ip route").

Grant wrote:
> AHappyCamper wrote:
>> Grant wrote:
>>> I have two servers: one with Debian 4 on it and one with Microsoft
>>> Windows Server 2003. They are both on the same internet connection, one
>>> number away from each other in IP address. Everyone can connect to both
>>> just fine except for one client. He can connect to the Windows server
>>> but not the Debian server. I had him first try to ping it using the
>>> domain that points to the Debian server. It pulled up the right IP
>>> address but timed out. I then had him ping the IP address. This too
>>> timed out. He has 2 computers in his house and both are doing the same
>>> thing. Nobody else has this problem; they are able to connect to both.
>>> Does anyone have any idea of what could be causing this? Is it
>>> something I setup incorrectly on the Debian Server? I'm not even sure
>>> where to go with this anymore. I appreciate any help and suggestions
>>> you can offer!
>>
>>
>> He has a problem. What distro is he running?
>>
>> If it is a Ubuntu, it could be the ipv6. Although some folks who don't
>> tell us the distro they are using might be using an Ubuntu Distro. It
>> uses a different Ipv6 than most Linux distros. More info here:
>>
>>> http://www.lockergnome.com/nexus/lin...internet-help/
>>>
>>
>
> He's not running Linux. He is using Windows XP.
And, the Samba server and client are both running?
He isn't using the most recent Microsoft updates that reconfigure the
server access defaults?

Still, HE has the problem, not you. Why? Everyone else can access the
servers. He has trouble with one of his machines accessing one of your
servers. The world isn't wrong, one unit is.

That screams out that his config is screwed. Probably by a recent
auto-update from Microsoft that wiped out a config file or item,
replacing it with something broken or different.

Pascal Hambourg wrote:
> Grant a écrit :
>>
>> Can you tell me more about the netmask or point me somewhere where I
>> can get more information about this. I guess I'm not 100% sure how to
>> set this in Debian.
>
> Print the contents of the network configuration file
> /etc/network/interfaces (if needed, "man interfaces" will tell about the
> syntax) and the output of the commands "ifconfig" (or "ip address") and
> "route -n" (or "ip route").

Below is the output you requested:

/etc/network/interfaces

auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 69.129.59.207
netmask 255.0.0.0
gateway 69.129.59.205
pre-up iptables-restore < /etc/iptables.up.rules

auto eth0


ip address:

1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:1a:a0:31:24:74 brd ff:ff:ff:ff:ff:ff
inet 69.129.59.207/8 brd 69.255.255.255 scope global eth0
inet6 fe80::21a:a0ff:fe31:2474/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0



ip route:

69.0.0.0/8 dev eth0 proto kernel scope link src 69.129.59.207
default via 69.129.59.205 dev eth0

AHappyCamper wrote:
> Grant wrote:
>> AHappyCamper wrote:
>>> Grant wrote:
>>>> I have two servers: one with Debian 4 on it and one with Microsoft
>>>> Windows Server 2003. They are both on the same internet connection, one
>>>> number away from each other in IP address. Everyone can connect to both
>>>> just fine except for one client. He can connect to the Windows server
>>>> but not the Debian server. I had him first try to ping it using the
>>>> domain that points to the Debian server. It pulled up the right IP
>>>> address but timed out. I then had him ping the IP address. This too
>>>> timed out. He has 2 computers in his house and both are doing the same
>>>> thing. Nobody else has this problem; they are able to connect to both.
>>>> Does anyone have any idea of what could be causing this? Is it
>>>> something I setup incorrectly on the Debian Server? I'm not even sure
>>>> where to go with this anymore. I appreciate any help and suggestions
>>>> you can offer!
>>>
>>> He has a problem. What distro is he running?
>>>
>>> If it is a Ubuntu, it could be the ipv6. Although some folks who don't
>>> tell us the distro they are using might be using an Ubuntu Distro. It
>>> uses a different Ipv6 than most Linux distros. More info here:
>>>
>>>> http://www.lockergnome.com/nexus/lin...internet-help/
>>>>
>> He's not running Linux. He is using Windows XP.
> And, the Samba server and client are both running?
> He isn't using the most recent Microsoft updates that reconfigure the
> server access defaults?
>
> Still, HE has the problem, not you. Why? Everyone else can access the
> servers. He has trouble with one of his machines accessing one of your
> servers. The world isn't wrong, one unit is.
>
> That screams out that his config is screwed. Probably by a recent
> auto-update from Microsoft that wiped out a config file or item,
> replacing it with something broken or different.
>

Samba is not in use. All the server has on it is Apache and that is
what the Windows XP computer can't access. It can't even ping the
Debian server. But it doesn't have a problem getting into the Windows
2003 Server system.

Grant <(E-Mail Removed)> writes:

>Pascal Hambourg wrote:
>> Grant a écrit :
>>>
>>> Can you tell me more about the netmask or point me somewhere where I
>>> can get more information about this. I guess I'm not 100% sure how to
>>> set this in Debian.
>>
>> Print the contents of the network configuration file
>> /etc/network/interfaces (if needed, "man interfaces" will tell about the
>> syntax) and the output of the commands "ifconfig" (or "ip address") and
>> "route -n" (or "ip route").

>Below is the output you requested:

>/etc/network/interfaces

>auto lo
>iface lo inet loopback

># The primary network interface
>allow-hotplug eth0
>iface eth0 inet static
> address 69.129.59.207
> netmask 255.0.0.0
> gateway 69.129.59.205
> pre-up iptables-restore < /etc/iptables.up.rules

You certainly should not hae that netmask. It should probably be
255.255.255.0. What your says is that all 2^24 addresses which start with
69 are part of your subnet, which I strongly doubt is true.




>auto eth0


>ip address:

>1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
>2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:1a:a0:31:24:74 brd ff:ff:ff:ff:ff:ff
> inet 69.129.59.207/8 brd 69.255.255.255 scope global eth0
> inet6 fe80::21a:a0ff:fe31:2474/64 scope link
> valid_lft forever preferred_lft forever
>3: sit0: <NOARP> mtu 1480 qdisc noop
> link/sit 0.0.0.0 brd 0.0.0.0



>ip route:

>69.0.0.0/8 dev eth0 proto kernel scope link src 69.129.59.207
>default via 69.129.59.205 dev eth0