Results 1 to 10 of 23

Thread: Chrome - Establishing Secure Connection

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Administrator
    Al's Avatar
    Join Date
    May 18th, 2011
    Location
    Chapel Hill, NC
    Posts
    6,753

    Re: Chrome - Establishing Secure Connection

    Microsoft Windows [Version 10.0.18363.959]
    (c) 2019 Microsoft Corporation. All rights reserved.

    tracert stat.free-dc.org

    Tracing route to stat.free-dc.org [23.217.138.110]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
    2 3 ms 2 ms 2 ms 104-185-76-1.lightspeed.rlghnc.sbcglobal.net [104.185.76.1]
    3 * * * Request timed out.
    4 20 ms 12 ms 12 ms 12.123.152.74
    5 13 ms 16 ms 16 ms wswdc21crs.ip.att.net [12.122.2.190]
    6 12 ms 14 ms 14 ms wswdc401igs.ip.att.net [12.122.113.37]
    7 13 ms 13 ms 19 ms 192.205.37.54
    8 74 ms 74 ms 74 ms ae-67.r05.asbnva02.us.bb.gin.ntt.net [129.250.5.153]
    9 18 ms 20 ms 18 ms ae-10.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
    10 70 ms 67 ms 68 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
    11 70 ms 70 ms 87 ms ae-0.a02.snjsca04.us.bb.gin.ntt.net [129.250.2.3]
    12 69 ms 75 ms 73 ms ae-7.akamai.snjsca04.us.bb.gin.ntt.net [130.94.195.14]
    13 68 ms 67 ms 68 ms a23-217-138-110.deploy.static.akamaitechnologies.com [23.217.138.110]

    Trace complete.


    ....and then coming back here her laptop started getting the same secure connection message and lag, though not as bad.



  2. #2
    Advisor - Stateside Division
    Bok's Avatar
    Join Date
    October 14th, 2010
    Location
    Wake Forest, NC
    Posts
    1,211

    Re: Chrome - Establishing Secure Connection

    stat.free-dc.org should be stats.free-dc.org

    Quote Originally Posted by Al View Post
    Microsoft Windows [Version 10.0.18363.959]
    (c) 2019 Microsoft Corporation. All rights reserved.

    tracert stat.free-dc.org

    Tracing route to stat.free-dc.org [23.217.138.110]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
    2 3 ms 2 ms 2 ms 104-185-76-1.lightspeed.rlghnc.sbcglobal.net [104.185.76.1]
    3 * * * Request timed out.
    4 20 ms 12 ms 12 ms 12.123.152.74
    5 13 ms 16 ms 16 ms wswdc21crs.ip.att.net [12.122.2.190]
    6 12 ms 14 ms 14 ms wswdc401igs.ip.att.net [12.122.113.37]
    7 13 ms 13 ms 19 ms 192.205.37.54
    8 74 ms 74 ms 74 ms ae-67.r05.asbnva02.us.bb.gin.ntt.net [129.250.5.153]
    9 18 ms 20 ms 18 ms ae-10.r24.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
    10 70 ms 67 ms 68 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
    11 70 ms 70 ms 87 ms ae-0.a02.snjsca04.us.bb.gin.ntt.net [129.250.2.3]
    12 69 ms 75 ms 73 ms ae-7.akamai.snjsca04.us.bb.gin.ntt.net [130.94.195.14]
    13 68 ms 67 ms 68 ms a23-217-138-110.deploy.static.akamaitechnologies.com [23.217.138.110]

    Trace complete.


    ....and then coming back here her laptop started getting the same secure connection message and lag, though not as bad.

Posting Permissions

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