Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: Can't ping server

  1. #11
    Join Date
    Sep 2008
    Location
    England
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Can't ping server

    Mango works!

    Code:
    rhys@Orange:~$ ssh 'rhys@192.168.1.72'
    ssh_exchange_identification: Connection closed by remote host
    Code:
    rhys@Mango:~$ ssh 'rhys@192.168.1.72'
    rhys@192.168.1.72's password: 
    Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.5.0-30-generic x86_64)
    
     * Documentation:  https://help.ubuntu.com/
    
      System information as of Tue May 21 23:17:39 BST 2013
    
      System load:    0.5                 Processes:           177
      Usage of /home: 43.9% of 415.83GB   Users logged in:     1
      Memory usage:   45%                 IP address for eth0: 192.168.1.72
      Swap usage:     0%
    
      Graph this data and manage this system at https://landscape.canonical.com/
    
    1 package can be updated.
    0 updates are security updates.
    
    You have new mail.
    Last login: Tue May 21 19:27:06 2013 from mango.local

  2. #12
    Join Date
    Nov 2009
    Location
    Mataro, Spain
    Beans
    13,782
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Can't ping server

    Are all three machines on the same 192.168.1.x subnet? They would need to be on the same subnet to communicate with .72.

    I noticed tomato has only one network interface, and it has the private IP of .72 configured on it. So I guess the public IP seen earlier is the IP of your internet router.

    If all the machines are on your private LAN they should be able to communicate between themselves with the private IPs. Also, you might need to have a dns set up so that they can communicate by name.

    Since communication between orange and tomato doesn't work with the private IPs I assume you might have a configuration issue (not in the same subnet) or connectivity issue (not connected in the same LAN).
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit

  3. #13
    Join Date
    Sep 2008
    Location
    England
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Can't ping server

    Yes indeed they are;
    Mango 192.168.1.158
    Tomato 192.168.1.72
    Orange 192.168.1.14

    They are all connected via a router not a switch Orange is on the wifi and Mango and Tomato are on the Ethernet.

    I'm not at home to check what my routers IP is but that makes sense.

    What configuration files should I be checking; I've double checked the /etc/network/interfaces /etc/ssh/sshd_config /etc/ssh/ssh_config
    These all look the same on all 3 computers.

    I might try changing them all back to static and forwarding the MAC address on my router to the machines, to see if that will work, is one method better than the other?

  4. #14
    Join Date
    Nov 2009
    Location
    Mataro, Spain
    Beans
    13,782
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Can't ping server

    The IP setup should be static for servers, in /etc/network/interfaces. For desktop (client) machines it's not really important whether the IP is static or dynamic.

    In the LAN the machines should be able to communicate without problems between themselves. It's really weird the ping is not working between some machines, as there doesn't seem to be firewall involved.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit

  5. #15
    Join Date
    Sep 2011
    Location
    Behind you!
    Beans
    668
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Can't ping server

    If your configuration is assumed to be correct, you need to look at the hardware. The network cable or port that the cable is plugged into (either on the server or the network hub)

    You need to ping www.google.com from each machine to make sure each machine is resolving an external friendly name and then has the ability to communicate with it.

    If that fails on any machine, that machine's config or access to the Internet/network is hampered in some way.

    When pinging internal devices, only use the IP address to avoid bringing in DNS issues as well (for example, when you pinged "tomato" one time, it resolved an external IP...most-likely a web site)

    If the Internet test failed, you then need to ping your gateway/router (192.168.1.1 in this case).

    LHammonds

  6. #16
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Can't ping server

    I usually use this order when troubleshooting connectivity issues:

    1. ping different host on same subnet (internal only)
    2. ping gateway (router)
    3. ping external site (google)

    Depending on which test fails, it gives you a place to start.
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  7. #17
    Join Date
    Sep 2008
    Location
    England
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Can't ping server

    Orange - 192.168.1.14

    Ping OK on 192.168.1.158 (Mango), 192.168.1.1, www.google.co.uk
    Ping unsuccessful on 192.168.1.72 (Tomato)

    Code:
    rhys@Orange:~$ ping 192.168.1.72
    PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
    ^C
    --- 192.168.1.72 ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 3024ms
    
    rhys@Orange:~$ ping 192.168.1.158
    PING 192.168.1.158 (192.168.1.158) 56(84) bytes of data.
    64 bytes from 192.168.1.158: icmp_req=1 ttl=64 time=3.85 ms
    64 bytes from 192.168.1.158: icmp_req=2 ttl=64 time=1.88 ms
    64 bytes from 192.168.1.158: icmp_req=3 ttl=64 time=2.10 ms
    ^C
    --- 192.168.1.158 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 1.884/2.611/3.850/0.882 ms
    rhys@Orange:~$ ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=2.37 ms
    64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=1.78 ms
    64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1.88 ms
    64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=10.8 ms
    ^C
    --- 192.168.1.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3005ms
    rtt min/avg/max/mdev = 1.787/4.227/10.869/3.841 ms
    rhys@Orange:~$ ping www.google.co.uk
    PING www.google.co.uk (173.194.67.94) 56(84) bytes of data.
    64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=1 ttl=45 time=18.7 ms
    64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=2 ttl=45 time=18.4 ms
    64 bytes from wi-in-f94.1e100.net (173.194.67.94): icmp_req=3 ttl=45 time=18.2 ms
    ^C
    --- www.google.co.uk ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 18.218/18.477/18.769/0.251 ms

    Mango - 192.168.1.158

    Ping OK on 192.168.1.14 (Orange), 192.168.1.1, www.google.co.uk
    Ping unsuccessful on 192.168.1.72 (Tomato)

    Code:
    rhys@Mango:~$ ping 192.168.1.14
    PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data.
    64 bytes from 192.168.1.14: icmp_req=1 ttl=64 time=1.62 ms
    64 bytes from 192.168.1.14: icmp_req=2 ttl=64 time=2.13 ms
    64 bytes from 192.168.1.14: icmp_req=3 ttl=64 time=1.82 ms
    ^C
    --- 192.168.1.14 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2001ms
    rtt min/avg/max/mdev = 1.623/1.862/2.139/0.215 ms
    rhys@Mango:~$ ping 192.168.1.72
    PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
    ^C
    --- 192.168.1.72 ping statistics ---
    3 packets transmitted, 0 received, 100% packet loss, time 2015ms
    
    rhys@Mango:~$ ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.499 ms
    64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.433 ms
    64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.418 ms
    64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.431 ms
    64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.423 ms
    ^C
    --- 192.168.1.1 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4000ms
    rtt min/avg/max/mdev = 0.418/0.440/0.499/0.039 ms
    rhys@Mango:~$ ping www.google.co.uk
    PING www.google.co.uk (173.194.41.95) 56(84) bytes of data.
    64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=1 ttl=53 time=11.3 ms
    64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=2 ttl=53 time=11.3 ms
    64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=3 ttl=53 time=11.2 ms
    64 bytes from lhr08s01-in-f31.1e100.net (173.194.41.95): icmp_req=4 ttl=53 time=11.3 ms
    ^C
    --- www.google.co.uk ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 11.280/11.332/11.376/0.040 ms

    Tomato - 192.168.1.72

    Ping OK on 192.168.1.14 (Orange) 192.168.1.158 (Mango), 192.168.1.1, 173.194.41.95 (www.google.co.uk)
    Ping unsuccessful on 192.168.1.72 (Tomato), www.google.co.uk

    Code:
    rhys@Tomato:~$ ping 192.168.1.14
    PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data.
    64 bytes from 192.168.1.14: icmp_req=1 ttl=64 time=1.31 ms
    64 bytes from 192.168.1.14: icmp_req=2 ttl=64 time=1.47 ms
    64 bytes from 192.168.1.14: icmp_req=3 ttl=64 time=1.93 ms
    ^C
    --- 192.168.1.14 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 1.313/1.571/1.932/0.266 ms
    rhys@Tomato:~$ ping 192.168.1.158
    PING 192.168.1.158 (192.168.1.158) 56(84) bytes of data.
    64 bytes from 192.168.1.158: icmp_req=1 ttl=64 time=0.181 ms
    64 bytes from 192.168.1.158: icmp_req=2 ttl=64 time=0.191 ms
    64 bytes from 192.168.1.158: icmp_req=3 ttl=64 time=0.187 ms
    ^C
    --- 192.168.1.158 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 1999ms
    rtt min/avg/max/mdev = 0.181/0.186/0.191/0.011 ms
    rhys@Tomato:~$ ping 192.168.1.72
    PING 192.168.1.72 (192.168.1.72) 56(84) bytes of data.
    ^C
    --- 192.168.1.72 ping statistics ---
    2 packets transmitted, 0 received, 100% packet loss, time 1006ms
    
    rhys@Tomato:~$ ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.496 ms
    64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.443 ms
    64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.439 ms
    64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.450 ms
    ^C
    --- 192.168.1.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3000ms
    rtt min/avg/max/mdev = 0.439/0.457/0.496/0.022 ms
    rhys@Tomato:~$ ping www.google.co.uk
    ping: unknown host www.google.co.uk
    rhys@Tomato:~$ ping 173.194.41.95
    PING 173.194.41.95 (173.194.41.95) 56(84) bytes of data.
    64 bytes from 173.194.41.95: icmp_req=1 ttl=53 time=11.3 ms
    64 bytes from 173.194.41.95: icmp_req=2 ttl=53 time=11.1 ms
    64 bytes from 173.194.41.95: icmp_req=3 ttl=53 time=11.1 ms
    64 bytes from 173.194.41.95: icmp_req=4 ttl=53 time=11.4 ms
    ^C
    --- 173.194.41.95 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 11.161/11.273/11.435/0.174 ms
    I'm curious to know why there's a DNS issue on Tomato for external domains, would this be a good place to start?

    EDIT:
    Just as a side note, I have restarted my router and disconnected all cables and blown out any dust (just incase) and reconnected everything.
    Last edited by AmbiguousOutlier; May 23rd, 2013 at 06:32 PM.

  8. #18
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Can't ping server

    Compare the network configuration of the working machines to the broken one and see what the difference is.

    Pay particular attention to the contents of /etc/resolv.conf
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

  9. #19
    Join Date
    Sep 2008
    Location
    England
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Can't ping server

    Outputs of;
    /etc/resolv.conf
    /etc/network/interfaces
    /etc/hosts

    respectively

    Mango - not sure what these addresses are, I can ping them, google suggests they are something to do with openvpn which I do use but not on mango, only tomato and orange.

    Code:
    # domain dummy.net
    nameserver 208.67.222.222
    nameserver 208.67.220.220
    Code:
    # interfaces(5) file used by ifup(8) and ifdown(8)
    auto lo
    iface lo inet loopback
    Code:
    127.0.0.1       localhost
    127.0.1.1       Mango
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters

    Orange

    Code:
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 127.0.1.1
    search default
    Code:
    # interfaces(5) file used by ifup(8) and ifdown(8)
    auto lo
    iface lo inet loopback
    Code:
    127.0.0.1       localhost
    127.0.1.1       orange
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters

    Tomato
    Code:
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    Code:
    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    auto eth0
    iface eth0 inet static
            address 192.168.1.72
            netmask 255.255.255.0
            broadcast 192.168.1.255
            gateway 192.168.1.1
    Code:
    127.0.0.1       localhost
    127.0.1.1       Tomato
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    What do you suggest?

  10. #20
    Join Date
    Oct 2009
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: Can't ping server

    Yeah, no DNS servers. You could add this to /etc/network/interfaces under the gateway.

    Code:
            # dns-* options are implemented by the resolvconf package, if installed
            dns-nameservers 208.67.222.222
    Restart networking or reboot and it should be fine.
    Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide

    Tomorrow's an illusion and yesterday's a dream, today is a solution...

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •