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

Cant connect to this IP with Esat.

  • 10-09-2004 5:59pm
    #1
    Nemesis
    Registered Users, Registered Users 2 Posts: 659 ✭✭✭


    Last night as I went to join [rD]'s DoD server ( 195.149.21.33 )the server did not appear on my fav lists.
    It said server does not respond.
    Earlier that day I had played on it.
    Every other server in my list responded.

    I tried a different ISP (OceanFree) and connected no problem.

    I thought this was strange that with one ISP (Esat) I cant connect to the server and with Oceanfree I could.

    Here are the Tracert's of both ISP's to [rD]'s DoD server..:

    Using Oceanfree

    C:\Documents and Settings\Nemesis>tracert 195.149.21.33

    Tracing route to 195.149.21.33 over a maximum of 30 hops

    1 33 ms 34 ms 33 ms ts002.bmt.esat.net [193.95.142.233]
    2 33 ms 33 ms 33 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
    3 34 ms 33 ms 33 ms ge1-0.core001.bmt.esat.net [193.95.140.17]
    4 53 ms 33 ms 33 ms pos3-0.core001.cwt.esat.net [193.95.131.41]
    5 45 ms 45 ms 45 ms pos2-0.br001.ldn.esat.net [193.95.131.14]
    6 45 ms 46 ms 46 ms lon1-9.nildram.net [195.66.224.59]
    7 46 ms 45 ms 45 ms jolt-gw.nildram.net [195.149.20.126]
    8 50 ms 50 ms 50 ms 195.149.21.33

    Trace complete.


    Using Esat-anytime my main account.

    C:\Documents and Settings\Nemesis>tracert 195.149.21.33

    Tracing route to 195.149.21.33 over a maximum of 30 hops

    1 30 ms 30 ms 30 ms ts523.cwt.esat.net [193.95.136.201]
    2 31 ms 30 ms 31 ms vlan500.rt501.cwt.esat.net [193.95.136.124]
    3 31 ms 32 ms 31 ms vlan53.rt002.cwt.esat-x.com [193.95.130.153]
    4 30 ms 30 ms 30 ms ge1-0.core001.cwt.esat.net [193.95.129.17]
    5 43 ms 42 ms 43 ms pos2-0.br001.ldn.esat.net [193.95.131.14]
    6 43 ms 42 ms 43 ms lon1-9.nildram.net [195.66.224.59]
    7 * * * Request timed out.
    8 * * * Request timed out.

    So whats going on here folks?

    have Esat barred people from Seeing this ip?.

    DemonBaby.


Comments

  • #2
    dahamsta
    Banned (with Prison Access) Posts: 16,659 ✭✭✭✭dahamsta


    Nemesis wrote:
    6 43 ms 42 ms 43 ms lon1-9.nildram.net [195.66.224.59]
    7 * * * Request timed out.
    Your trace is stopping at or after Nildram, not Esat. Unless Nildram is owned by BT?

    adam


  • #3
    rash
    Registered Users, Registered Users 2 Posts: 306 ✭✭rash


    the router 195.149.20.126 may not have a route back to the Esat subnet that you're on.
    Contact Esat Support, they should follow up with the remote ISP


Advertisement