Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 13
Hi Linux Forums devs, I have a really weird problem. I can connect to my VPS server via SSH fine, and type commands. But it appears my server can't make ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2011
    Posts
    7

    Strange problem: I can SSH to my remote server, but it has no internet


    Hi Linux Forums devs,
    I have a really weird problem.

    I can connect to my VPS server via SSH fine, and type commands. But it appears my server can't make any outgoing connections. I don't have Root access though.

    When I type "wget google.com" it gets stuck on "Resolving google.com".

    I can access my server via HTTP:
    212.150.134.140/~airgamin

    Does anyone know what could be the problem?

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    Sounds a bit like a dns problem.
    On your server: Do you get an ip for google.com with nslookup?
    Code:
    nslookup google.com
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Apr 2011
    Posts
    7
    Thanks for your reply mate!

    This is the response:

    ;; connection timed out; no servers could be reached

  4. #4
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    It is a dns problem.

    Either
    a) there are wrong nameserver defined in /etc/resolv.conf

    b) the nameservers defined in /etc/resolv.conf are down/not reachable.
    Check with ping and host (more convenient than nslookup imho))
    Code:
    ping <NAMESERVER_OF_ETC_RESOLV.CONF>
    host google.com <NAMESERVER_OF_ETC_RESOLV.CONF>
    Alternatively to host you can call nslookup without parameters and set the nameserver manually.


    As you donīt have root, that is pretty much all you can do.
    But you can report what you found out to the sysadmin responsible for that server.
    You must always face the curtain with a bow.

  5. #5
    Just Joined!
    Join Date
    Apr 2011
    Posts
    7
    File content of /etc/resolv.conf

    search localdomain
    nameserver 8.8.8.8
    nameserver 8.8.4.4
    When I try to ping the first nameserver 8.8.8.8 it says:
    ping: icmp open socket: Operation not permitted
    And when I try to nslookup 8.8.8.8 it returns:
    ;; connection timed out; no servers could be reached
    I'm guessing 8.8.8.8 is a default value in the resolv.conf? It's probably an invalid IP.

  6. #6
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    8.8.8.8 and 8.8.4.4 are public dnservers provided by google.
    Free of charge and for everyone.
    How nice of them.
    However, now they know which hosts your server resolves over time.
    In a private environment that translates to (simplified): Your browser history is in their databases.

    But back to topic.
    Both nameserver are
    a) pingable
    b) available
    c) they do their work, aka: resolv hosts

    As your server cannot reach them, you have a network problem.
    Was there a recent firewall and/or routing and/or IP change?

    I am a bit surprised now, that you said you can connect via ssh.
    Do you connect from the internet or from some private network?
    You must always face the curtain with a bow.

  7. #7
    Just Joined!
    Join Date
    Apr 2011
    Posts
    7
    Wow, that is really funny! Google is taking over the world!

    I am connecting via the internet to the SSH, that server is not on my network.

    Also, you can probably connect to it as well by clicking this link:
    Code:
    212.150.134.140/~airgamin/
    The IP hasn't changed at all. As far as firewall/routing, I probably wouldn't know, because I'm just a customer and they don't tell me much. They have bad support and aren't available most of the time.

  8. #8
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    Code:
    traceroute 212.150.134.140
    traceroute to 212.150.134.140 (212.150.134.140), 30 hops max, 60 byte packets
     1  --DELETED--  1.516 ms  2.841 ms  4.293 ms
     2  --DELETED--  10.975 ms  11.410 ms  11.835 ms
     3  --DELETED--  13.569 ms  14.532 ms  15.285 ms
     4  --DELETED--  18.415 ms  20.153 ms  20.793 ms
     5  --DELETED--  46.960 ms  48.126 ms  48.349 ms
     6  ten3-3.brdr1.fra.nv.net.il (80.81.194.47)  31.478 ms  15.226 ms  15.541 ms
     7  10.80.1.1 (10.80.1.1)  15.359 ms  17.365 ms  17.640 ms
    Someone messed up, probably your provider.

    This is traceroute from my place to your ip.
    ( I deleted the hops close to me, as they are not neccesary in that view)

    After 80.81.194.47, the route goes into a private network (10.80.1.1) which is not routeable internetwise.
    That means, your server is not reachable from the internet.


    Both ten3-3.brdr1.fra.nv.net.il and the network with the IP 80.81.194.47 belongs to "Netvision".
    That isn't your provider by any chance?
    Even if not, then your provider is probably a customer of netvision.

    Either way, time to pick up the phone or write an email to them.
    You must always face the curtain with a bow.

  9. #9
    Just Joined!
    Join Date
    Apr 2011
    Posts
    7
    Thanks so much for your insight Irithori!!! I will link my host to this page and explain the problem to them.

    I thought it was a problem with the server configuration, but it's probably a networking issue.

    By provider, do you mean ISP or my hosting provider?

  10. #10
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,356
    You're welcome

    Hosting Provider.
    The guys, who provide/manage your server and its connectivity.
    You must always face the curtain with a bow.

Page 1 of 2 1 2 LastLast

Posting Permissions

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