Re: Weird Connection Problem

Pascal Hambourg wrote:
Grant a écrit :

/etc/network/interfaces
[...]
iface eth0 inet static
address 69.129.59.207
netmask 255.0.0.0
[...]

As Unruh said (and I suspected), it is likely that the netmask 255.0.0.0 is wrong. It leads your box to consider that any host with an address starting with 69 (or whatever is the real number) is in le local network. If such a host is actually not in the local network, it is unreachable from your box.

Check the netmask with your network administrator or you ISP, or on the Windows server which seems to have the right netmask. Then correct /etc/network/interfaces and reload it with the following command :

# update-rc.d networking restart

That was the problem. I corrected the netmask and now the client can access the Debian server. Thank you everyone for helping figure this out.

.

Relevant Pages

  • arp errors,
    ... inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ... arplookup 168.186.1.19 failed: host is not on local network ...
    (freebsd-questions)
  • find ALL reachable IP addresses in a switch?
    ... local network, given an interface that is ... Since we changed the configuration using w3m, ... could have gotten the MAC address right away, ... different network (with a different netmask, ...
    (comp.os.linux.networking)
  • Re: Gateway in a different net
    ... local network address space as determined by your IP and netmask. ... you have to pass through a gateway. ... Most likely you have your netmask set wrong. ... but should let you talk to that router. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Weird Connection Problem
    ... As Unruh said, it is likely that the netmask 255.0.0.0 is wrong. ... It leads your box to consider that any host with an address starting with 69 is in le local network. ...
    (comp.os.linux.networking)
  • Re: CIDR notation in hosts.allow?
    ... If I use CIDR notation to restrict to my local network, ... If I change to a netmask, ...
    (linux.redhat)