Jump to content

YetiGBR1

Members
 View Profile  See their activity

  • Posts

    63

  • Joined

  • Donations

    0.00 USD 

 Content Type 

Posts posted by YetiGBR1

  2. Posted · Edited by YetiGBR1
    Typo error

    Hi Zarg,

     

    The "Supposed Influx" is not what you think according to my inside source they a ghost or undropped connections by the server login/connection system and this appears to have been getting more frequent since before Christmas from what I've seen.

     

    I'm sure Zackerman or Kyp could confirm this.

  3. Posted · Edited by YetiGBR1

    Having established it is not client/server related and is infact an "internet infrastructure Issue" I have resorted to running a single client and dealing with the inconvinience until it apperars to become more stable. I would like to give a Massive Thankyou to all that have looked into the issues on my/our behalf.

    All the best,

    YetiGBR the insane. :wacko:

  5. Posted · Edited by YetiGBR1

    Has the DNS entry canged for sunrise.net-7.org? from sunrise.net-7.org [38.130.197.232] to 141.8.225.226 reason I ask just crashed and did a tracert again and this came back:

    Date/Time 29th Dec 2016 @ 11:05am GMT (approx -+ or - 2-3 mins)

    C:\>tracert sunrise.net7.org

    Tracing route to sunrise.net7.org [141.8.225.226]
    over a maximum of 30 hops:

      1    17 ms    21 ms    21 ms  10.213.80.1
      2   186 ms    23 ms    23 ms  midd-core-2b-xe-203-0.network.virginmedia.net [62.252.68.185]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5   135 ms    57 ms    51 ms  ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158]
      6    48 ms    50 ms    60 ms  TenGE13-2.br02.ams01.pccwbtn.net [80.249.209.37]
      7   174 ms   211 ms   175 ms  HundredGE0-3-0-0.br04.dal01.pccwbtn.net [63.223.32.66]
      8   336 ms   224 ms   181 ms  datafoundry.te0-1-0-8.br04.dal01.pccwbtn.net [63.218.23.119]
      9   184 ms   655 ms   361 ms  209-99-48-54.fwd.datafoundry.com [209.99.48.54]
     10   177 ms   168 ms   168 ms  141.8.225.226

    Trace complete.

  6. Posted

    Further update client is "awaiting Master HandOff" : 00:07 GMT 29th Dec 2016

    C:\>tracert sunrise.net-7.org

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1    22 ms    18 ms    61 ms  10.213.80.1
      2    49 ms    22 ms    34 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5    28 ms    21 ms    21 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    30 ms    28 ms    31 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8    96 ms   712 ms   191 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9   133 ms   105 ms   100 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   100 ms   103 ms    97 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   180 ms   144 ms   418 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   149 ms   152 ms   149 ms  sunrise.net-7.org [38.130.197.232]
     16   516 ms   159 ms   148 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

  7. Posted

    Update (after falling asleep at the kb) time: 20:43 GMT

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1    12 ms    22 ms    21 ms  10.213.80.1
      2    22 ms    23 ms    23 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5    26 ms    28 ms    57 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    34 ms   219 ms   125 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8    96 ms   104 ms   105 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9   358 ms   103 ms   104 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   104 ms   103 ms   102 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   147 ms   176 ms   190 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   268 ms   159 ms   178 ms  sunrise.net-7.org [38.130.197.232]
     16   150 ms   145 ms   138 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

    Gating and lost connection to server, error msg was "Server failed to respond to sector handover"

  8. Posted · Edited by YetiGBR1
    Added extra info

    Hi Kyp,

     

    Just saw your post and ran another TRaceRT for you at 18:38 GMT

    C:\>tracert sunrise.net-7.org

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1    12 ms    20 ms    18 ms  10.213.80.1
      2    20 ms    34 ms    19 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5   143 ms    22 ms    22 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    61 ms    42 ms    34 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8   232 ms   108 ms   109 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9   105 ms   104 ms   103 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   120 ms   109 ms   110 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   141 ms   152 ms   296 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   792 ms   149 ms   160 ms  sunrise.net-7.org [38.130.197.232]
     16   149 ms   139 ms   139 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

    Looks better than before and I have been logged in on 2 clients with no drops/CTD etc for almost 40 minutes.

    Reran the TraceRT again at 18:46 GMT:

    C:\>tracert sunrise.net-7.org

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1    12 ms   288 ms    20 ms  10.213.80.1
      2    17 ms    16 ms    17 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5    18 ms    22 ms   110 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    29 ms    92 ms    29 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8    99 ms   103 ms   121 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9    93 ms    94 ms   243 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   415 ms   221 ms   343 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   148 ms   145 ms   163 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   147 ms   156 ms   405 ms  sunrise.net-7.org [38.130.197.232]
     16   158 ms   140 ms   145 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

  9. Posted

    Just ran another one:

    C:\>tracert sunrise.net-7.org

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1     6 ms    17 ms    18 ms  10.213.80.1
      2    12 ms    13 ms    13 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5    58 ms    21 ms    21 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    29 ms    29 ms    29 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8    95 ms   103 ms   343 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9   100 ms    98 ms    97 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   173 ms   144 ms   103 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   151 ms   152 ms   161 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15  2660 ms   170 ms   154 ms  sunrise.net-7.org [38.130.197.232]
     16   344 ms   145 ms   140 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

  10. Posted · Edited by YetiGBR1
    Added TraceRT info

    Hi Kyp,

    Many thanks for the update, I figured it may be beyond the scope of the game as there was some really big lag times on the USA backbone. If I get a chance to sort out a isolated laptop I'll run several WireShark scans and see IF I can identify the offending router/switch.

    Many thanks again and keep up the awesome work you and the team do.

    YetiGBR the Insane :-)

    C:\>tracert sunrise.net-7.org

    Tracing route to sunrise.net-7.org [38.130.197.232]
    over a maximum of 30 hops:

      1    16 ms    26 ms    21 ms  10.213.80.1
      2    33 ms    20 ms    34 ms  midd-core-2a-xe-133-0.network.virginmedia.net [62.252.68.169]
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5   133 ms    34 ms    47 ms  nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
      6    42 ms    36 ms    49 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
      7     *        *        *     Request timed out.
      8   779 ms   118 ms    98 ms  us-nyc01b-rd2-ae9-0.aorta.net [84.116.140.170]
      9   216 ms   157 ms   149 ms  us-nyc01b-ri2-ae3-0.aorta.net [84.116.137.194]
     10   126 ms   103 ms   108 ms  lag-5.ear3.NewYork1.Level3.net [4.68.72.9]
     11     *        *        *     Request timed out.
     12   148 ms   165 ms   170 ms  HAMPTON-ROA.ear1.Miami1.Level3.net [4.30.20.86]
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15   146 ms   376 ms   284 ms  sunrise.net-7.org [38.130.197.232]
     16   157 ms   139 ms   144 ms  sunrise.net-7.org [38.130.197.232]

    Trace complete.

  11. Posted

    Still having the same issues only it is more frequent AND happening to more of my clients (between 3-4) at any time. The freezes / lock-ups happen randomly over the 1-8 clients on separate PC's. I have checked my ISP for known issues but they were resolved before Christmas, I have noticed that there was significant lag on the USA core backbone routers when doing a "Tracert" to sunrise server.

    It has now gotten to a point for me where it is not playable nor enjoyable, I used to tolerate the "ODD" hiccup but not every 10-30 minutes that is just plain unrealistic. I know you guys have worked tirelessly and professionally to bring us this EMU and keep it working let alone patched with content (Awesome job, please keep it up) but PLEASE, PLEASE sort these issues out :-)

    Apologies for the whine, just utterly gutted I cannot play the BEST game atm.

    Running Windows 7 Pro and Windows 10 Home and Pro on PC's all fully patched.

    I have done all the usual checks for viruses/Trojans/hacks etc on the network at my location and they are all clean.

  12. Posted · Edited by YetiGBR1
    spelling mistake + Adding extra info

    I too have been experiencing this "feature" and it 1st appeared late on Sunday evening GMT and has gotten worse post Tuesdays server Maintenance Reboot. It's now at a point that one can only play solo and not Multi-Box/Multi-client for fear of dying or locking up in a raid etc. Something changed server side of that I am sure in fact its similar to what has previously been described in the forms when you had a Visual Studio C code conflict or something. I applaud your efforts as Dev's and GM's tirelessly giving your time to make our free time enjoyable. Please fix before Christmas if possible.

     

    Running Win7 Pro and Win 10 Home and Pro (all 64bit) on clients

    All the best,

    The UK's ONLY YetiGBR :)

×
×
  • Create New...