test content
What is the Arc Client?
Install Arc

Problem connecting from Verizon! Tech Please READ ASAP!

SystemSystem Member, NoReporting Posts: 178,019 Arc User
I just spent 45min on the phone with verizon before they handed me off to you guys. here is the issue:

Cannot connect to startrekonline.com, and the launcher cannot ether. Same problem on other computers, including my friends who also uses verizon fios at another residence. when i ping startrekonline.com, it says this:


C:\Users\Brett>ping www.startrekonline.com

Pinging www.startrekonline.com [208.95.185.44] with 32 bytes of data:
Reply from 152.63.113.189: TTL expired in transit.
Reply from 152.63.113.189: TTL expired in transit.
Reply from 152.63.113.189: TTL expired in transit.
Reply from 152.63.113.189: TTL expired in transit.

Ping statistics for 208.95.185.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Brett>

When i do a tracert, i get this:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Brett>tracert www.startrekonline.com

Tracing route to www.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.1
2 6 ms 7 ms 7 ms L100.LSANCA-VFTTP-37.verizon-gni.net [71.189.228
.1]
3 6 ms 7 ms 6 ms 9-1-737.LSANCA-LCR-07.verizon-gni.net [130.81.58
.248]
4 8 ms 6 ms 7 ms so-5-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.29.140]
5 7 ms 7 ms 10 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6 10 ms 7 ms 9 ms 0.ae3.BR3.LAX15.ALTER.NET [152.63.113.185]
7 8 ms 10 ms 10 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
8 6 ms 7 ms 7 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
9 8 ms 10 ms 9 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
10 6 ms 7 ms 10 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
11 10 ms 9 ms 10 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
12 43 ms 7 ms 7 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
13 8 ms 10 ms 9 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
14 6 ms 6 ms 7 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
15 8 ms 9 ms 9 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
16 8 ms 10 ms 9 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
17 8 ms 10 ms 9 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
18 8 ms 10 ms 9 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
19 8 ms 10 ms 8 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
20 10 ms 9 ms 6 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
21 10 ms 8 ms 10 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
22 9 ms 9 ms 10 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
23 11 ms 10 ms 9 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
24 8 ms 10 ms 9 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
25 10 ms 9 ms 10 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
26 6 ms 9 ms 10 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
27 9 ms 9 ms 17 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
28 8 ms 9 ms 10 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
29 9 ms 9 ms 10 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
30 6 ms 10 ms 7 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]

Trace complete.

C:\Users\Brett>

Verizon says it is on your guys end and I am supposed to contact you, but I cannot find a support phone number. STO was working fine earlier today, and i have not experienced this problem before. Yes i have rebooted my router
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    I also have verizon fios and mine or my friends computer cannot log onto the website or the game.. its like the sto server for my area is down. I'm in tthe souther california. Everything works fine but sto site and game.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    Wild guess but your problem could be at LAX15.ALTER.NET, just a wild stab in the um light. Generally should still be Verizon that's supposed to take care of this, as they should be able to route you around it at the very least. At any rate, seems LAX15.ALTER.NET has no idea where STO is and both think the other knows, so infinitely bouncing back and forth till you get your timeout.

    Though if you want a quick fix, a proxy might work.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    ::bump::

    just happened to me earlier today and cant figure it out without a proxy and i really don't want to have to do that.

    UPDATE:

    Here is part of my trace-route..it's definitely two bad DNS servers:


    5 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 60.000 ms 100.000 ms 30.000 ms
    6 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 30.000 ms 25.000 ms
    7 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    8 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 30.000 ms 60.000 ms
    9 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    10 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 30.000 ms 30.000 ms
    11 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    12 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 35.000 ms 30.000 ms 30.000 ms
    13 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    14 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 30.000 ms 30.000 ms
    15 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 75.000 ms 25.000 ms 30.000 ms
    16 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 35.000 ms 30.000 ms
    17 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 35.000 ms 30.000 ms 35.000 ms
    18 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 25.000 ms 30.000 ms
    19 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 45.000 ms 30.000 ms 30.000 ms
    20 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 35.000 ms 45.000 ms 130.000 ms
    21 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 30.000 ms 35.000 ms
    22 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 35.000 ms 25.000 ms 45.000 ms
    23 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 40.000 ms 30.000 ms
    24 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 30.000 ms 35.000 ms
    25 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 30.000 ms 85.000 ms
    26 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 30.000 ms 25.000 ms
    27 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 50.000 ms 35.000 ms
    28 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 30.000 ms 30.000 ms
    29 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 55.000 ms 30.000 ms 30.000 ms
    30 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 70.000 ms 35.000 ms 30.000 ms
    31 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    32 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 60.000 ms 45.000 ms
    33 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 35.000 ms 30.000 ms
    34 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 35.000 ms 30.000 ms
    35 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 110.000 ms 25.000 ms 25.000 ms
    36 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 95.000 ms 40.000 ms
    37 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 35.000 ms 35.000 ms 35.000 ms
    38 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 40.000 ms 45.000 ms 35.000 ms
    39 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 50.000 ms 30.000 ms 25.000 ms
    40 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 55.000 ms 55.000 ms 30.000 ms
    41 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 30.000 ms 35.000 ms
    42 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 75.000 ms 25.000 ms
    43 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 85.000 ms 25.000 ms
    44 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 35.000 ms 30.000 ms 35.000 ms
    45 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 55.000 ms 25.000 ms 30.000 ms
    46 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 30.000 ms 25.000 ms 30.000 ms
    47 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 25.000 ms 30.000 ms
    48 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 25.000 ms 35.000 ms 45.000 ms
    49 0.ae3.BR3.LAX15.ALTER.NET (152.63.113.185) 30.000 ms 35.000 ms 25.000 ms
    50 0.ae3.XL3.LAX15.ALTER.NET (152.63.113.186) 35.000 ms 30.000 ms 30.000 ms
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    i woke up this morning and all is working well again... so maybe they fix the problem
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    I had this very same issue last night. This morning i logged on and downloaded the patch, went to work, and when I came home at 4pm pst the same thing happened again. Waiting to see if it connects eventually.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2010
    Verizon just wanted to make you go away. That's a routing loop and it's definitely their problem. It is equally certain that the callcentre monkeys that you talk to have absolutely no authority to do anything about it. You cannot do anything to fix this sort of problem.
Sign In or Register to comment.