Results 1 to 4 of 4

Thread: Traceroute

  1. #1
    Join Date
    Dec 2008
    Location
    Sydney, Australia
    Posts
    1,021

    Default Traceroute

    I am trying to figure out while I have timeouts whenever trying to access a particular remote server. Using the traceroute command in Linux, I get nothing but asterisks for all hops, while tracert under Windows from the same machine shows text. All software firewalls are disabled.
    If any network gurus read this, an additional question relating to the problem I'm investigating: I cannot reach a particular website using either https, ping, or tracert (timeouts), yet the rest of the web is fine. Other people can reach that address without a problem. The output of tracert goes all the way through the hops to just before the site in question, then timeouts. Any hints as to what the issue could be much appreciated!
    Günter

    Desk: Tumbleweed, KDE 5, AMD Ryzen 5 3400G, 16Gb, 120Gb SSD, 2 SATA.
    Lap: Thinkpad T430, Tumbleweed, Intel i5, 8Gb, SSD.

  2. #2
    Join Date
    Oct 2008
    Location
    Birmingham. AL
    Posts
    858

    Default Re: Traceroute

    Let's see if someone here can give a more specific answer, but it may be that the default timeouts in Windows are longer. Do a "man traceroute" to determine how to increase the timeouts under Linux.

    As for that one Website being a problem, it's got to be on their end. If you can browse the Web otherwise, and your traceroute is making it to the final hop before stalling, that in and of itself tells you where the problem is.

  3. #3

    Default Re: Traceroute

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Being unable to reach a site via traceroute or ping means ICMP isn't
    allowed at some point, which really doesn't mean much. If you can ping
    google.com or somebody else that does not block ICMP then you're fine on
    that front on your end but a lot of sites block ICMP for one reason or
    another.

    The HTTPS issues is a bit more pressing. Test it with something just
    working at the TCP layer (I assume you've been using your browser thus
    far, which is far more than a TCP utility) such as netcat:

    netcat -zv ipAddresOrDNSOfTheSiteHere 443

    If your output is that the port is 'open' then the issue is your browser.
    If not then get a LAN trace of the same attempt and see if your packets
    make it out (SYN) and if they respond with a SYN/ACK at least at which
    point your box should finish up with an ACK and then the connection is
    established (that's all that the netcat command above does, and then it
    breaks the connection). If that works then netcat should say 'open' and
    if it does not then netcat will usually give a reason why it failed
    (Connection Refused, for example). To get a LAN/packet trace:

    sudo /usr/sbin/tcpdump -s 0 -w /tmp/cap0.cap

    Do your test while that's running, then use Ctrl+C to stop the trace.
    Attach the compressed version of /tmp/cap0.cap here and we'll see what we see.

    Good luck.





    gminnerup wrote:
    > I am trying to figure out while I have timeouts whenever trying to
    > access a particular remote server. Using the traceroute command in
    > Linux, I get nothing but asterisks for all hops, while tracert under
    > Windows from the same machine shows text. All software firewalls are
    > disabled.
    > If any network gurus read this, an additional question relating to the
    > problem I'm investigating: I cannot reach a particular website using
    > either https, ping, or tracert (timeouts), yet the rest of the web is
    > fine. Other people can reach that address without a problem. The output
    > of tracert goes all the way through the hops to just before the site in
    > question, then timeouts. Any hints as to what the issue could be much
    > appreciated!
    >
    >

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.9 (GNU/Linux)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

    iQIcBAEBAgAGBQJKwZ4YAAoJEF+XTK08PnB5+QgQANTZ3ftxE2kXdlOMJq525y63
    H8FGcCoLvwRiopnc3nLsHS61+/Pn/BPCjctP+oZhv4WbjjeIlCSaOfa9tJrUG4Wv
    Fzxvg8JlBFdcAErZI7bgeK2NecJTxiNSvZ9xVagVoRBThdSAYRUnR+4Jt8uQEKL7
    3QGpcuDeTViHfJsa0lkPUcy0salRAluHuIhgSbBUjwvIfGRYEid1LdgLOwUC3T76
    UCWmKnJn349zVXEq3r5oxXDKrw2Y+hIWc3l7ayesJtUjOwUEzLZu9DQOxmt3TBU+
    ajPS1ykbEGzTnu/nOKLD8wNEZW2u1hKwfZ5vnRzeDw8dP3S5J3IjIuyIlbSmXtKu
    Uj+q57S2uoemK8FG3jVsjVOuWPljwpKYnOhT/9QKW01JjXR8G8phaQx1PmkcPsJK
    XFzbB7zaWfiL/RLdZX9Di+bzxPQwmxC6uKlZpwChKupV46xhG7DGX4AVpCgq+EX1
    j2UjAS7iNdGr53GYJbb3Z3OHznrEoG+TR8VxFp+AW7Bcb/2cQO9gM6VzocxzrQiL
    mTIYGrpPqjB7ElBO9VO0qGkF/XxzR/4RGDZJ3O2A8UlfMq9IGFuysGO+1DWs42x/
    neo0P0KcJgvueTUa35U+qdRHjjlsRUsX2ZNlTTZTdRmg87ZYKaNutbVn841dkOFK
    nS9k8NHo4d7E0FYQiczK
    =BeVZ
    -----END PGP SIGNATURE-----

  4. #4
    Join Date
    Dec 2008
    Location
    Sydney, Australia
    Posts
    1,021

    Default Re: Traceroute

    Thanks all, the problem with accessing that website mysteriously resolved itself upon a router reset. No idea why...
    But I'd still like to be able to get traceroute output. I've tried the traceroute command from the command line, and the Gnome network tools, and both only give me asterisks for each hop except the first (to the default gateway), which isn't much use at all.
    Günter

    Desk: Tumbleweed, KDE 5, AMD Ryzen 5 3400G, 16Gb, 120Gb SSD, 2 SATA.
    Lap: Thinkpad T430, Tumbleweed, Intel i5, 8Gb, SSD.

Posting Permissions

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