I did that before i even change ip addresses to make sure but there's no conflict on IP. Anyway i replaced my router with another one and all works perfectly.
On Tue, May 7, 2013 at 2:12 PM, Karl E. Jorgensen <karl.jorgen...@nice.com> wrote: > On Fri, May 03, 2013 at 11:05:13PM +0100, s0lid wrote: >> Hi, >> >> Im having an unsual issue with my debian 6.0.7 server. This is a fresh >> install >> and i set the IP settings to DHCP. It get the IP from my >> router(192.168.1.1), I >> tried to ping the router IP but it doesn't reply i tried to ping a computers >> it >> replies fine, I don't know what's going on here this is the first time i had >> an >> issue with debian in terms of network. The router is accessible and can be >> ping >> from my laptop. >> >> ---from my laptop--- >> >> $ ping 192.168.1.1 >> PING 192.168.1.1 (192.168.1.1): 56 data bytes >> 64 bytes from 192.168.1.1: icmp_seq=0 ttl=254 time=2.623 ms >> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=254 time=1.000 ms >> >> $ ping 192.168.1.200 >> PING 192.168.1.200 (192.168.1.200): 56 data bytes >> 64 bytes from 192.168.1.200: icmp_seq=0 ttl=128 time=5.701 ms >> 64 bytes from 192.168.1.200: icmp_seq=1 ttl=128 time=2.320 ms >> >> >> ---from debian server--- >> root@debian:~# ping 192.168.1.1 >> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. >> >> PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. >> 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=40.5 ms >> 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=1.96 ms >> 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=2.08 ms >> ^C >> --- 192.168.1.2 ping statistics --- >> 3 packets transmitted, 3 received, 0% packet loss, time 2003ms >> rtt min/avg/max/mdev = 1.967/14.861/40.532/18.152 ms >> >> >> >> I don't know if there's an issue with TTL or even if it's related at all. I >> also run arp from the debian server and it can see the router's >> IP(192.168.1.1) >> >> root@debian:~# arp -a >> ? (192.168.1.1) at 40:4a:03:d6:ac:a9 [ether] on eth1 >> ? (192.168.1.101) at e0:f8:47:1e:a0:a6 [ether] on eth1 >> ? (192.168.1.105) at 08:00:27:b3:86:01 [ether] on eth1 >> ? (192.168.1.200) at 00:16:b6:1e:01:a0 [ether] on eth1 > > Although you got the IP address via DHCP, it is still possible that > you have an IP collision - which could also give these symptoms, as > different servers will have different ideas of IP/MAC mappings on the > local network. To make things complicated, it often changes over time > too, as caches and cache expirations are in effect. > > There's a couple of ways you can diagnose this: The easiest is to > remove your "suspected faulty" box from the network (unplug network > cable physically), and check whether the IP address still responds to > pings. If it does, then something else has that IP address. > > To futher diagnose, this, you could manually change the IP address of > the debian server to an IP address you know for sure to be free. > > Hope this helps > -- > Karl E. Jorgensen > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130507061253.GA16935@hawking > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANZ3Tp0=pjefx+fsq=e-fj_+tuijcp413igza61+chgn9o+...@mail.gmail.com
