Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Network question

  • 13-11-2004 12:58am
    #1
    jabaroon
    Registered Users, Registered Users 2 Posts: 668 ✭✭✭


    Hi All,

    I am having intermittent problems connecting to my Ireland.com pop3 server through my netsource DSL connection. I suspect that the problem is a network issue with the netsource/their provider routing. When I do a tracert to pop3.ireland.com, I get:

    1 2 ms 2 ms 1 ms my.router [192.168.1.1]
    2 23 ms 22 ms 22 ms rt004dub.netsource.ie [213.79.63.254]
    3 25 ms 23 ms 24 ms rt001kil.netsource.ie [212.17.32.101]
    4 22 ms 23 ms 25 ms 64.215.182.205
    5 115 ms 109 ms 109 ms so1-2-0-2488M.ar1.DCA3.gblx.net [67.17.67.53]
    6 113 ms 225 ms 110 ms 206.111.0.21
    7 112 ms 110 ms 114 ms p5-0-0.RAR1.Washington-DC.us.xo.net [65.106.3.13
    8 304 ms 306 ms 306 ms p1-0-0.RAR1.SanJose-CA.us.xo.net [65.106.0.38]
    9 322 ms 306 ms 306 ms p0-0-0d0.RAR2.SanJose-CA.us.xo.net [65.106.1.62]
    10 187 ms 186 ms 185 ms p14-0.DCR1.DC-Fremont-CA.us.xo.net [65.106.2.178
    11 354 ms 184 ms 327 ms 205.158.60.162.ptr.us.xo.net [205.158.60.162]
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.

    Can anyone else out there who is using netsource try running "tracert pop3.ireland.com" and let me know if you get similar results?....also if others are using non-netsource provider, can you do same?...

    I am assuming that by virtue of the route being able to be traced to us.xo.net, that the problem is with their routing tables (or something similar) and nothing at all to do with my local configuration. Any network experts able to shed any light for me / care to comment!!?
    Thanks,
    Jab


Comments

  • #2
    tribble
    Closed Accounts Posts: 1,478 ✭✭✭tribble


    Tracing route to pop2.pr.outblaze.com [205.158.62.73] over a maximum of 30 hops: 1 2021 ms 3 ms 3 ms rfc1918.space.should.not.be.used.on.publicips [192.168.2.1] 2 25 ms 22 ms 23 ms rt004dub.netsource.ie [213.79.63.254] 3 253 ms 257 ms 46 ms rt001kil.netsource.ie [212.17.32.101] 4 25 ms 25 ms 27 ms 64.215.182.205 5 111 ms 110 ms 113 ms so1-2-0-2488M.ar1.DCA3.gblx.net [67.17.67.53] 6 113 ms 111 ms 113 ms p4-2.IR1.Ashburn-VA.us.xo.net [206.111.0.137] 7 111 ms 112 ms 114 ms p5-0-0.RAR1.Washington-DC.us.xo.net [65.106.3.133] 8 187 ms 188 ms 187 ms p1-0-0.RAR1.SanJose-CA.us.xo.net [65.106.0.38] 9 191 ms 184 ms 185 ms p0-0-0d0.RAR2.SanJose-CA.us.xo.net [65.106.1.62] 10 186 ms 216 ms 343 ms p15-0.DCR1.DC-Fremont-CA.us.xo.net [65.106.2.154] 11 294 ms 186 ms 196 ms 205.158.60.162.ptr.us.xo.net [205.158.60.162] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.


  • #3
    MrPinK
    Closed Accounts Posts: 1,502 ✭✭✭MrPinK


    jabaroon wrote:
    I am assuming that by virtue of the route being able to be traced to us.xo.net, that the problem is with their routing tables (or something similar) and nothing at all to do with my local configuration.
    No, just because you can't trace to it doesn't mean your packets aren't getting routed to their destination. The other hosts on the route probably have incoming ICMP packets (which ping uses) blocked for security reasons. If you telnet to pop3.ireland.com on port 110 you should be able to connect to it. I can from my netsource connection anyway. Dosen't seem to be any network problem along the route.


Advertisement