I'm getting some pretty constant disconnect issues and the forums are intermittantly going down. Anyone else seeing these problems?
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 39 ms 9 ms 17 ms 68.0.128.61
4 14 ms 17 ms 13 ms 70.169.74.200
5 16 ms 21 ms 11 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 28 ms 25 ms 24 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 27 ms 35 ms 27 ms te0-3-0-5.ccr22.lax01.atlas.cogentco.com [154.54.44.133]
8 51 ms 59 ms 63 ms te0-1-0-3.ccr22.iah01.atlas.cogentco.com [154.54.44.253]
9 85 ms 82 ms 81 ms te0-2-0-7.ccr22.atl01.atlas.cogentco.com [66.28.4.89]
10 89 ms 83 ms 82 ms te0-3-0-2.ccr22.dca01.atlas.cogentco.com [154.54.1.122]
11 89 ms 97 ms 89 ms te0-1-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.2.134]
12 95 ms 92 ms 94 ms te0-2-0-6.ccr22.bos01.atlas.cogentco.com [154.54.44.58]
13 * 95 ms 93 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 99 ms 92 ms 102 ms 38.111.40.114
15 96 ms 97 ms 93 ms 208.95.185.41
I'm getting some pretty constant disconnect issues and the forums are intermittantly going down. Anyone else seeing these problems?
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 39 ms 9 ms 17 ms 68.0.128.61
4 14 ms 17 ms 13 ms 70.169.74.200
5 16 ms 21 ms 11 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 28 ms 25 ms 24 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 27 ms 35 ms 27 ms te0-3-0-5.ccr22.lax01.atlas.cogentco.com [154.54.44.133]
8 51 ms 59 ms 63 ms te0-1-0-3.ccr22.iah01.atlas.cogentco.com [154.54.44.253]
9 85 ms 82 ms 81 ms te0-2-0-7.ccr22.atl01.atlas.cogentco.com [66.28.4.89]
10 89 ms 83 ms 82 ms te0-3-0-2.ccr22.dca01.atlas.cogentco.com [154.54.1.122]
11 89 ms 97 ms 89 ms te0-1-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.2.134]
12 95 ms 92 ms 94 ms te0-2-0-6.ccr22.bos01.atlas.cogentco.com [154.54.44.58]
13 * 95 ms 93 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 99 ms 92 ms 102 ms 38.111.40.114
15 96 ms 97 ms 93 ms 208.95.185.41
I've been having lots of connection stability problems over the weekend as well.
Amongst all the other online games I use, the problem here appears to be isolated to STO.
I'm on Telstra in Australia and have not seen this level of conneciton instability for a while.
(Sorry, posted from work. No trace route to cut and paste, however when I ran it on Saturday everything looked normal).
I've been having lots of connection stability problems over the weekend as well.
Amongst all the other online games I use, the problem here appears to be isolated to STO.
I'm on Telstra in Australia and have not seen this level of conneciton instability for a while.
(Sorry, posted from work. No trace route to cut and paste, however when I ran it on Saturday everything looked normal).
I'm having the same problem from Canada. My other online games are fine, yet STO continually d/c's me.
I've been having lots of connection stability problems over the weekend as well.
Amongst all the other online games I use, the problem here appears to be isolated to STO.
I'm on Telstra in Australia and have not seen this level of conneciton instability for a while.
(Sorry, posted from work. No trace route to cut and paste, however when I ran it on Saturday everything looked normal).
I'm not doubting you, but STO behaves like a VPN... no matter where the hiccup is, if it sees one, it'll kick you offline. Your tracert's 2nd hop is to your ISP, and it's timing out.
EDIT: Other games aren't nearly as sensitive to these issues as Cryptic's are. This can be both good and bad.
Trace Route:
Still getting No Server Reponse errors in game and DC's when zoning when I got home from work.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms .
2 27 ms 19 ms 17 ms 172.xx.TRIBBLE.x
3 59 ms 58 ms 57 ms 172.xx.xx.TRIBBLE
4 59 ms 52 ms 51 ms 172.xx.TRIBBLE.xx
5 94 ms 67 ms 71 ms Bundle-Ether11.woo9.Brisbane.telstra.net [203.45.53.241]
6 69 ms 75 ms 71 ms Bundle-Ether2.woo-core1.Brisbane.telstra.net [203.50.44.9]
7 79 ms 80 ms 77 ms Bundle-POS2.chw-core2.Sydney.telstra.net [203.50.6.201]
8 65 ms 75 ms 73 ms Bundle-Ether1.oxf-gw2.Sydney.telstra.net [203.50.6.90]
9 78 ms 81 ms 74 ms TenGigE15-0-0.sydo-core01.Sydney.reach.com [203.50.13.102]
10 67 ms 68 ms 69 ms i-0-5-4-0.sydo-core02.bi.reach.com [202.84.220.189]
11 236 ms 238 ms 226 ms i-0-3-0-0.1wlt-core01.bx.reach.com [202.84.140.222]
12 265 ms 258 ms 256 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
13 263 ms 265 ms 272 ms cogent-peer.eqla01.pr.reach.com [134.159.63.198]
14 245 ms 248 ms 244 ms te0-2-0-2.ccr21.lax01.atlas.cogentco.com [154.54.3.141]
15 305 ms 308 ms 308 ms te0-2-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.241]
16 324 ms 323 ms 330 ms te0-2-0-2.ccr21.atl01.atlas.cogentco.com [154.54.42.210]
17 319 ms 319 ms 318 ms te0-2-0-3.ccr21.dca01.atlas.cogentco.com [154.54.24.9]
18 324 ms 326 ms 329 ms te0-1-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.1.234]
19 319 ms 313 ms 325 ms te0-0-0-1.ccr22.bos01.atlas.cogentco.com [154.54.25.114]
20 315 ms 321 ms 326 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
21 336 ms 344 ms 360 ms 38.111.40.114
22 303 ms 292 ms 292 ms patchserver.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 8 ms 6 ms ash-bb1-geth0-2-1.telia.net [65.19.100.113]
3 10 ms 9 ms 9 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
4 11 ms 12 ms 12 ms 64.15.2.61
5 21 ms 11 ms 8 ms 64.15.2.178
6 30 ms 31 ms 30 ms te8-7.ccr01.jfk04.atlas.cogentco.com [154.54.11.
249]
7 34 ms 34 ms 31 ms 154.54.47.25
8 39 ms 38 ms 37 ms te0-4-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.44.66]
9 36 ms 37 ms 38 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 31 ms 18 ms 19 ms 38.111.40.114
11 16 ms 15 ms 18 ms 208.95.185.41
reaching the servers is not the problem. did you ever leave a ping running with 1MB Packages while you are playing. Interesting is that when the delay is going up towards 1000+ ms then the connection normally drops real fast.
I hear you...the problem for us (the end users) is, what can we do about it??? I'm basically stuck living with constant disconnects. I have 2 chars up to Captain since about 2 weeks prior to Season 4 to now. It gets frustrating. I've updated all my drivers, opened ports on my router and enabled port forwarding to my computer...none of which has helped my situation. I don't know what else to do. To add to the frustration, I have a ticket open with support and not even a brief reply to acknowledge they received it and let me know they are working on it. Patch after patch they say they're addressing networking issues and I haven't seen a difference in performance. And the cherry on top is that prior to Season 4 I took my 1st Char from Ensign to Captain without many DC's at all...I don't believe this issue is on my side.
Cest la vie, I'll plod along as I've been doing, dealing with the dc's. It beats going back to WOW!
I tried find the problem. A think that problem is there:
border11.te8-1-bbnet2.bsn.pnap.net (63.251.128.104) 118.375 ms 118.347 ms *
cryptic-3.border11.bsn.pnap.net (216.52.61.78) 126.518 ms 126.550 ms 126.545 ms
- i check lines and this is the place whitch make the problem and i'm still disconnect.
I heard from Support regarding my ticket. So far they have had me adjust settings in my firewall, and virus protection software to allow STO through both. They also had me change my client options to use the US proxy server. The first changes have not helped, after adjusting the firewall and virus protection software, I experienced disconnects as I have been since the release of season 4. The load times for login and entering instances seemed faster to me, so there was some little improvement. I have not played since changing the proxy server option. I'll test it tonight and post again.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 8 ms 6 ms ash-bb1-geth0-2-1.telia.net [65.19.100.113]
3 10 ms 9 ms 9 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
4 11 ms 12 ms 12 ms 64.15.2.61
5 21 ms 11 ms 8 ms 64.15.2.178
6 30 ms 31 ms 30 ms te8-7.ccr01.jfk04.atlas.cogentco.com [154.54.11.
249]
7 34 ms 34 ms 31 ms 154.54.47.25
8 39 ms 38 ms 37 ms te0-4-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.44.66]
9 36 ms 37 ms 38 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 31 ms 18 ms 19 ms 38.111.40.114
11 16 ms 15 ms 18 ms 208.95.185.41
I don't believe I said Old Republic was never going to have these issues. If you look closely, I said I don't believe they will have such issues after over a year past their release date. Cryptic isn't doing all that great resolving these DC issues as evidenced by the number of posts complaining about DC's.
I noticed the first hop immediately...I don't know what IP address that is; but it does seem logical to me that that timed out result is at the heart of my issue. Do you think that is my gateway/router?
I don't believe I said Old Republic was never going to have these issues. If you look closely, I said I don't believe they will have such issues after over a year past their release date. Cryptic isn't doing all that great resolving these DC issues as evidenced by the number of posts complaining about DC's.
I noticed the first hop immediately...I don't know what IP address that is; but it does seem logical to me that that timed out result is at the heart of my issue. Do you think that is my gateway/router?
Yep. The first hop on my tracrts have been my router. If there is an issue with your connection, it appears as though your router is not handling network traffic properly (unfortunately).
Just a follow-up; this time-out is a known issue with D-Link routers. It isn't really timing out and D-Link has released firmware upgrade to address this in the past. Unfortunately for me, they have not released such a firmware upgrade for my router to date...
I have modified my Firewall and Virus protection settings and I played several huors last night with only 1 DC. That ocurred when loading an instance beaming down to a planet; I think my issues are solved and Cryptic support has been awesome since replying to my ticket.
I think I've seen at least half a dozen people with atlas.cogentco.com in their trace routes... I have no idea how this can be dealt with, unless said server is on Cryptic property, though.
Comments
This appears to be at your ISP's end...
Amongst all the other online games I use, the problem here appears to be isolated to STO.
I'm on Telstra in Australia and have not seen this level of conneciton instability for a while.
(Sorry, posted from work. No trace route to cut and paste, however when I ran it on Saturday everything looked normal).
I'm having the same problem from Canada. My other online games are fine, yet STO continually d/c's me.
I'm not doubting you, but STO behaves like a VPN... no matter where the hiccup is, if it sees one, it'll kick you offline. Your tracert's 2nd hop is to your ISP, and it's timing out.
EDIT: Other games aren't nearly as sensitive to these issues as Cryptic's are. This can be both good and bad.
Still getting No Server Reponse errors in game and DC's when zoning when I got home from work.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms .
2 27 ms 19 ms 17 ms 172.xx.TRIBBLE.x
3 59 ms 58 ms 57 ms 172.xx.xx.TRIBBLE
4 59 ms 52 ms 51 ms 172.xx.TRIBBLE.xx
5 94 ms 67 ms 71 ms Bundle-Ether11.woo9.Brisbane.telstra.net [203.45.53.241]
6 69 ms 75 ms 71 ms Bundle-Ether2.woo-core1.Brisbane.telstra.net [203.50.44.9]
7 79 ms 80 ms 77 ms Bundle-POS2.chw-core2.Sydney.telstra.net [203.50.6.201]
8 65 ms 75 ms 73 ms Bundle-Ether1.oxf-gw2.Sydney.telstra.net [203.50.6.90]
9 78 ms 81 ms 74 ms TenGigE15-0-0.sydo-core01.Sydney.reach.com [203.50.13.102]
10 67 ms 68 ms 69 ms i-0-5-4-0.sydo-core02.bi.reach.com [202.84.220.189]
11 236 ms 238 ms 226 ms i-0-3-0-0.1wlt-core01.bx.reach.com [202.84.140.222]
12 265 ms 258 ms 256 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
13 263 ms 265 ms 272 ms cogent-peer.eqla01.pr.reach.com [134.159.63.198]
14 245 ms 248 ms 244 ms te0-2-0-2.ccr21.lax01.atlas.cogentco.com [154.54.3.141]
15 305 ms 308 ms 308 ms te0-2-0-3.ccr21.iah01.atlas.cogentco.com [154.54.44.241]
16 324 ms 323 ms 330 ms te0-2-0-2.ccr21.atl01.atlas.cogentco.com [154.54.42.210]
17 319 ms 319 ms 318 ms te0-2-0-3.ccr21.dca01.atlas.cogentco.com [154.54.24.9]
18 324 ms 326 ms 329 ms te0-1-0-7.ccr21.jfk02.atlas.cogentco.com [154.54.1.234]
19 319 ms 313 ms 325 ms te0-0-0-1.ccr22.bos01.atlas.cogentco.com [154.54.25.114]
20 315 ms 321 ms 326 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
21 336 ms 344 ms 360 ms 38.111.40.114
22 303 ms 292 ms 292 ms patchserver.crypticstudios.com [208.95.185.41]
Trace complete.
Tracert:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jay>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 6 ms 8 ms 6 ms ash-bb1-geth0-2-1.telia.net [65.19.100.113]
3 10 ms 9 ms 9 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
4 11 ms 12 ms 12 ms 64.15.2.61
5 21 ms 11 ms 8 ms 64.15.2.178
6 30 ms 31 ms 30 ms te8-7.ccr01.jfk04.atlas.cogentco.com [154.54.11.
249]
7 34 ms 34 ms 31 ms 154.54.47.25
8 39 ms 38 ms 37 ms te0-4-0-3.ccr22.bos01.atlas.cogentco.com [154.54
.44.66]
9 36 ms 37 ms 38 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 31 ms 18 ms 19 ms 38.111.40.114
11 16 ms 15 ms 18 ms 208.95.185.41
Trace complete.
Nettest:
contacting nettest server..
Local IP: 24.190.3.140
Ping: 16.4 msec
Port: 80: 1584 KB/sec 53 KB/sec 1668 KB/sec 500
Port: 80: 1626 KB/sec 52 KB/sec 1711 KB/sec 500
Port: 443: 1502 KB/sec 55 KB/sec 1590 KB/sec 500
Port: 443: 1315 KB/sec 53 KB/sec 1390 KB/sec 500
Port: 7255: 1363 KB/sec 54 KB/sec 1443 KB/sec 500
Port: 7255: 1457 KB/sec 53 KB/sec 1544 KB/sec 500
Port: 7003: 1455 KB/sec 52 KB/sec 1542 KB/sec 500
Port: 7003: 1453 KB/sec 53 KB/sec 1537 KB/sec 500
Port: 7202: 1465 KB/sec 52 KB/sec 1549 KB/sec 500
Port: 7202: 1464 KB/sec 59 KB/sec 1549 KB/sec 500
Port: 7499: 1427 KB/sec 55 KB/sec 1511 KB/sec 500
Port: 7499: 1467 KB/sec 52 KB/sec 1551 KB/sec 500
Port: 80: 1645 KB/sec 47 KB/sec 1732 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
Don't despair, The Old Republic will be out by the end of the year and all of this will be a bad memory...
Cest la vie, I'll plod along as I've been doing, dealing with the dc's. It beats going back to WOW!
Same here. Only my STO game is gone FUBAR.. All my other games work just fine. I even could play old Diablo 2 on battle.net just fine lol
border11.te8-1-bbnet2.bsn.pnap.net (63.251.128.104) 118.375 ms 118.347 ms *
cryptic-3.border11.bsn.pnap.net (216.52.61.78) 126.518 ms 126.550 ms 126.545 ms
- i check lines and this is the place whitch make the problem and i'm still disconnect.
Repair it
For the record, it appears to be an issue even getting through your router. Check the first hop.
As for The Old Republic never going to have these issues: You're setting yourself up for a major disappointment if you believe that.
I noticed the first hop immediately...I don't know what IP address that is; but it does seem logical to me that that timed out result is at the heart of my issue. Do you think that is my gateway/router?
Yep. The first hop on my tracrts have been my router. If there is an issue with your connection, it appears as though your router is not handling network traffic properly (unfortunately).
I have modified my Firewall and Virus protection settings and I played several huors last night with only 1 DC. That ocurred when loading an instance beaming down to a planet; I think my issues are solved and Cryptic support has been awesome since replying to my ticket.