I have spent the past 24 hours attempting to access the STO website from my home network Verizon Fios account. I restored my router, updated the firmware, contacted tech support, and even changed DNS servers in an effort to connect to crypticstudios.com, startrekonline.com, or the STO game servers. I attempted to login using 3 separate network devices. I had assumed that you were experiencing web difficulties until i accessed your website over 3g on my iphone. Today I went to another network location and I am able to access your websites perfectly fine on the same laptop I attempted at my house.
From my home network:
All attempts to Ping cryptic studios websites resulted in a time out, I ran a tracert and when it hopped from cryptic-1.border12.bsn.pnap.net it timed out. I believe that for whatever reason your servers are rejecting my networks request.
Any Idea?? It only affects my home network, and nothing else. However a few days ago, I aws able to log in and access everything just fine. Its very Bizzar.. Fios is blaming it on cryptic..
Same issues as above. Server timeouts 95% of the time, and the other 5% gets ya kicked in less than a minute. WTH is up with this? Hopefully this gets resolved soon. 36 hours and counting now...:eek:
Well I can tell you exactly what your problem is ... FIOS , fact is Verizon is like a little child selling yellow water and calling it lemonaid, with no lemons in sight.
Well now that I got that out of the way, check your router, Verizon will reset it every half hour or so. Did you install any new hardware or security Software?
The problem is though that during the tracert it hops far beyond fios before a problem is encountered. I t goes through alternet etc, then on to the cryptic server where a response is recieved. THEN it times out just after cryptic-1... Its very strange... I put in a ticket with cryptic about it, but it doesn't seem to have made the priority list as of yet... I am kind of irritated that I spent soo much money on this game, being that I can not even log onto the website to check for help. Unless I am not at my house! haha. what a nuissance...
You're right that's the exact thing I'm getting. The funny thing is if you tracert www.champions-online.com it'll stop at the same exact server too.
When I'm at work on Paetch or testing out on my neighbor's wireless and I do a tracert, it never even touches that cryptic-1 server. Something is definitely fishy with that server and why fios is the only thing i've found to hit it.
The only good news is we're not alone. I'm in richmond VA and having this issue. Where are you located?
Also I figured out last night, the ONLY way I can connect at home is to connect to my work VPN first. It's a pain in the butt, super slow but at least I can get on. If you can't get one from your work maybe there is a 3rd party that offers VPNs?
It's a crummy way to do it but at least it's a better workaround than anything Fios or cryptic have offered so far.
I just found a site, Strongvpn dot com and if my work's VPN starts acting too slow, I may give them a shot. Maybe we could get STO to pay for our VPN. yeah right
Now that is very interesting.. I am in Richmond VA as well.. Near midlo tpnk to be more precise, dont stalk me. haha. Perhaps it is a fios issue, can one of you DEVS call fios and complain about this.. It seams to be a very localized issue. Also, I am on the road right now, so if you ever get it to work, let me know... Thanks!
That is weird, I'm right behind johnston willis... That kind of adds credibility to my theory that verizon's DNS servers haven't added the right info yet. We'd probably be hitting the same server. It could still be Cryptic's server having an issue though.... who knows.
I've called twice. I have a new router coming and there is a whitelist request form they had me try. I don't think either one of them will work.
if you call it is VERY important that you only say you're trying to get to the website. They will say they don't support the game at all, so you just have to say just get me to the website and i'll work from there. It's ahuge pain in the rump.
here is the whitelist request form they had me fill out. It's for email of all dang things. Just don't enter any email info, just in the additional info section add www.startrekonline.com and champions-online.com. Hopefully they'll add them but who knows. I kind of doubt it.
Well clearly this is not something that either Verizon nor cryptic is willing to help with. I am not 100% convinced that it is not cryptic still. Were it to be verizon, i imagine the issue would propogate some where other than cryptic-1.yaddayaddayadda.pnap. whatever....
This is the 3rd or so report of issues from FIOS. I've notified our network engineer and will look into it. Can please post the full traceroute so I can send it along?
The ISP I work for sometimes has this issue too... If they pull a new 'block' of IP addresses and you get one some websites do not have that range in their rules so they auto-drop the traffic.
In our case it was most common when we started using 99.x IPs. Many 3rd party websites had to be asked to 'allow' those.
I am currently unable to post the tracert. I am on the road for a few weeks. WackyD33 would you mind posting it when you get home from the office tonight? It is simple to do, from the cmd prompt in windows type tracert startrekonline.com thank you! Be sure to not be accessing it through your vpn.
Yeah I have a ticket with Cryptic but I've gotten 0 help from them. just the old "it's verizon's issue"
Because this screams ISP issue. A trace-route will tell you exactly where the signal is dropping and if it's really the fault of Cryptic, Verizon or one of the tier isp's. Cogent is one of the big ones that have issues with dropped signal areas.
Because this screams ISP issue. A trace-route will tell you exactly where the signal is dropping and if it's really the fault of Cryptic, Verizon or one of the tier isp's. Cogent is one of the big ones that have issues with dropped signal areas.
As stated in the original post.... According to the tracert when it hops FROM cryptic-1.border12.bsn.pnap.net it times out... looks like cryptic's issue to me. Plus it happened after the server update @ cryptic apparently. I am not attempting to sling mud at anyone, just happy that cryptic is looking into it. I had a verizon network tech online yesterday, he said everything should be working from there end. But that may not be the case. Hopefully he will be able to post a tracert tonight.
Not sure if its related but does using a different DNS provider help ? There are quite a few available, I use https://www.dyndns.com/services/dynguide/ and it boosts web access speeds and reliability 100% compared to AT&T's DNS.
Not sure if its related but does using a different DNS provider help ? There are quite a few available, I use https://www.dyndns.com/services/dynguide/ and it boosts web access speeds and reliability 100% compared to AT&T's DNS.
No, a different dns provider will not help with routing issues. It will only help dns resolution issues.
yeah ever since the servers went down Friday evening EST is when I stopped being able to get in. Ithought the servers were just down until Saturday night someone else online told me to check things on my end.
Ok just for reference here is the tracert from work, where I AM able to log in:
1 * * * Request timed out.
2 1 ms 1 ms 1 ms 209.155.252.130
3 * * * Request timed out.
4 266 ms 213 ms 187 ms ge-1-0-0-300.core02.rcmeva01.paetec.net [169.130.100.2]
5 225 ms 200 ms 222 ms so-1-3-0.core02.rlghnc01.paetec.net [169.130.80.218]
6 209 ms 227 ms 238 ms ge-0-1-0.core01.rlghnc01.paetec.net [169.130.81.121]
7 245 ms 211 ms 280 ms 169.130.80.5
8 377 ms 241 ms 255 ms ge-0-3-0.core01.asbnva01.paetec.net [169.130.81.85]
9 213 ms 200 ms 206 ms GigabitEthernet9-2.ar5.DCA3.gblx.net [64.211.110.173]
10 220 ms 206 ms 259 ms te9-1-10G.ar2.DCA3.gblx.net [67.16.135.41]
11 301 ms 330 ms 373 ms 206.111.0.65.ptr.us.xo.net [206.111.0.65]
12 232 ms 263 ms 243 ms te-11-4-0.rar3.washington-dc.us.xo.net [207.88.12.201]
13 * 464 ms 572 ms te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
14 258 ms 256 ms 235 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
15 200 ms 221 ms 230 ms 216.55.4.18
16 280 ms 310 ms 332 ms 208.95.185.174
Not sure if its related but does using a different DNS provider help ? There are quite a few available, I use https://www.dyndns.com/services/dynguide/ and it boosts web access speeds and reliability 100% compared to AT&T's DNS.
I know what you were saying, maybe that cryptic-1 server was not being recognized by DNS. I tried changing the router's DNS settings to what you find on opendns.com (maybe org) and that didn't work either.
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 6 ms L100.RCMDVA-VFTTP-25.verizon-gni.net [98.117.94.1]
3 8 ms 7 ms 7 ms 12-0-4-125.RCMDVA-LCR-01.verizon-gni.net [130.81.140.116]
4 61 ms 12 ms 12 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248]
5 15 ms 14 ms 14 ms 0.so-3-2-0.XT1.DCA6.ALTER.NET [152.63.39.169]
6 27 ms 27 ms 26 ms 0.so-7-1-0.XL3.BOS4.ALTER.NET [152.63.0.209]
7 28 ms 27 ms 28 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 27 ms 27 ms 26 ms internap-gw.customer.alter.net [65.207.236.58]
9 90 ms 219 ms 219 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
10 27 ms 35 ms 34 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
11 * * * Request timed out.
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.
Please try this, run "ping f l 2000 patchserver.crypticstudios.com". This should return something like "Packet needs to be fragmented". Then slowloy lower the number (the 2000) by 50 at a time until you can get a valid ping. Can you let me know what number works, if any?
2 4 ms 5 ms 4 ms L100.RCMDVA-VFTTP-13.verizon-gni.net [96.228.59.
1]
3 5 ms 5 ms 4 ms 9-2-113.RCMDVA-LCR-01.verizon-gni.net [130.81.96
.250]
4 9 ms 9 ms 9 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.28.248]
5 11 ms 12 ms 12 ms 0.so-5-1-0.XT1.DCA5.ALTER.NET [152.63.36.205]
6 24 ms 23 ms 24 ms 0.so-7-1-0.XL3.BOS4.ALTER.NET [152.63.0.209]
7 25 ms 24 ms 24 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 25 ms 25 ms 26 ms internap-gw.customer.alter.net [65.207.236.58]
9 25 ms 24 ms 26 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
10 32 ms 36 ms 34 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
I changed my DNS several times and it didn't help any. It looks like mine may have taken a slightly different route but the end result was at the same cryptic-1 that failed.... much like that one did.. Thanks!
Comments
Well now that I got that out of the way, check your router, Verizon will reset it every half hour or so. Did you install any new hardware or security Software?
J
When I'm at work on Paetch or testing out on my neighbor's wireless and I do a tracert, it never even touches that cryptic-1 server. Something is definitely fishy with that server and why fios is the only thing i've found to hit it.
The only good news is we're not alone. I'm in richmond VA and having this issue. Where are you located?
It's a crummy way to do it but at least it's a better workaround than anything Fios or cryptic have offered so far.
I just found a site, Strongvpn dot com and if my work's VPN starts acting too slow, I may give them a shot. Maybe we could get STO to pay for our VPN. yeah right
if you call it is VERY important that you only say you're trying to get to the website. They will say they don't support the game at all, so you just have to say just get me to the website and i'll work from there. It's ahuge pain in the rump.
here is the whitelist request form they had me fill out. It's for email of all dang things. Just don't enter any email info, just in the additional info section add www.startrekonline.com and champions-online.com. Hopefully they'll add them but who knows. I kind of doubt it.
http://www2.verizon.net/micro/whitelist/request_form.asp?id=member
If all else fails I can say that the VPN solution works but how stupid is that?
Any luck today??
In our case it was most common when we started using 99.x IPs. Many 3rd party websites had to be asked to 'allow' those.
And thank you for looking into it code.
Because this screams ISP issue. A trace-route will tell you exactly where the signal is dropping and if it's really the fault of Cryptic, Verizon or one of the tier isp's. Cogent is one of the big ones that have issues with dropped signal areas.
As stated in the original post.... According to the tracert when it hops FROM cryptic-1.border12.bsn.pnap.net it times out... looks like cryptic's issue to me. Plus it happened after the server update @ cryptic apparently. I am not attempting to sling mud at anyone, just happy that cryptic is looking into it. I had a verizon network tech online yesterday, he said everything should be working from there end. But that may not be the case. Hopefully he will be able to post a tracert tonight.
Sure does, I have not been able to log into the game or the websites from home in days..
No, a different dns provider will not help with routing issues. It will only help dns resolution issues.
Ok just for reference here is the tracert from work, where I AM able to log in:
Tracing route to www.startrekonline.com [208.95.185.174]
over a maximum of 30 hops:
1 * * * Request timed out.
2 1 ms 1 ms 1 ms 209.155.252.130
3 * * * Request timed out.
4 266 ms 213 ms 187 ms ge-1-0-0-300.core02.rcmeva01.paetec.net [169.130.100.2]
5 225 ms 200 ms 222 ms so-1-3-0.core02.rlghnc01.paetec.net [169.130.80.218]
6 209 ms 227 ms 238 ms ge-0-1-0.core01.rlghnc01.paetec.net [169.130.81.121]
7 245 ms 211 ms 280 ms 169.130.80.5
8 377 ms 241 ms 255 ms ge-0-3-0.core01.asbnva01.paetec.net [169.130.81.85]
9 213 ms 200 ms 206 ms GigabitEthernet9-2.ar5.DCA3.gblx.net [64.211.110.173]
10 220 ms 206 ms 259 ms te9-1-10G.ar2.DCA3.gblx.net [67.16.135.41]
11 301 ms 330 ms 373 ms 206.111.0.65.ptr.us.xo.net [206.111.0.65]
12 232 ms 263 ms 243 ms te-11-4-0.rar3.washington-dc.us.xo.net [207.88.12.201]
13 * 464 ms 572 ms te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
14 258 ms 256 ms 235 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
15 200 ms 221 ms 230 ms 216.55.4.18
16 280 ms 310 ms 332 ms 208.95.185.174
Trace complete.
Tracing route to www.startrekonline.com [208.95.185.174]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 6 ms L100.RCMDVA-VFTTP-25.verizon-gni.net [98.117.94.1]
3 8 ms 7 ms 7 ms 12-0-4-125.RCMDVA-LCR-01.verizon-gni.net [130.81.140.116]
4 61 ms 12 ms 12 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248]
5 15 ms 14 ms 14 ms 0.so-3-2-0.XT1.DCA6.ALTER.NET [152.63.39.169]
6 27 ms 27 ms 26 ms 0.so-7-1-0.XL3.BOS4.ALTER.NET [152.63.0.209]
7 28 ms 27 ms 28 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 27 ms 27 ms 26 ms internap-gw.customer.alter.net [65.207.236.58]
9 90 ms 219 ms 219 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
10 27 ms 35 ms 34 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
11 * * * Request timed out.
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.
I know what you were saying, maybe that cryptic-1 server was not being recognized by DNS. I tried changing the router's DNS settings to what you find on opendns.com (maybe org) and that didn't work either.
2 4 ms 5 ms 4 ms L100.RCMDVA-VFTTP-13.verizon-gni.net [96.228.59.
1]
3 5 ms 5 ms 4 ms 9-2-113.RCMDVA-LCR-01.verizon-gni.net [130.81.96
.250]
4 9 ms 9 ms 9 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.28.248]
5 11 ms 12 ms 12 ms 0.so-5-1-0.XT1.DCA5.ALTER.NET [152.63.36.205]
6 24 ms 23 ms 24 ms 0.so-7-1-0.XL3.BOS4.ALTER.NET [152.63.0.209]
7 25 ms 24 ms 24 ms POS6-0.GW5.BOS4.ALTER.NET [152.63.25.69]
8 25 ms 25 ms 26 ms internap-gw.customer.alter.net [65.207.236.58]
9 25 ms 24 ms 26 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
10 32 ms 36 ms 34 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
11 25 ms 25 ms 24 ms 208.95.185.174