EDIT: Please close this thread, the issue has been solved.
Okay, this is getting ridiculous. On for an hour and literally disconnected every 5 minutes. I timed it. Messages not getting sent to chat, whiplash every ten or fifteen minutes that is so bad I think I'm gonna be sick from how much and how fast it moves; but when I did a tracert to "patchserver.crypticstudios.com" like it said to on the support FAQ, the times are well under 180ms (highest was 142ms, and I only got that once out of 10 tracerts). Plus, this ONLY happens at night (when I'm actually able to play), but it runs fine during the day (when I DON'T have time to play). And it's been like this for several weeks. What the hell is going on? I'm in southern BC, Canada on a High Speed Extreme Cable connection, and I've already done tests with my ISP; it's not them. I am running Windows 7, 2GB RAM, 2.5Ghz Dual Core processor, and a 512MB GeForce 210 HD video card. I've tried setting video setting to as low as they can go; it's not that, either.
UPDATE: I just found out that when I had my ISP send a tech a couple weeks ago, he put a filter on the wiring outside; that might be slowing my speeds. I'm going to see if they can take it off and hope that fixes it. If not I'll edit this post with any new info, including Nettest tool results.
Usually cycling problems (only occuring at certain times of the dya) is an indication of traffic shapping as ISP applys different shapping rules during peak times.
Since you are in canada I assuming you are using Shaw which if you search the net you will find articles that shaw does traffic shape. Run the nettest both during when you have and don't have problems . If the results are difffernt then you may be being affected by shapping. (as the nettest server is not the game server so would not be affect by player load.)
Also there been a major routing problem couple of days ago that affected all traffic out of canada that the rerouting to fix may still be affect you a little (secondary routes of lower qualltiy)
Yo, usually filters help filter out 'noise' on the line and don't effect the speed too much.
What I would suggest doing is, before you launch the game, go to Start -> Run type in cmd and then OK. In the black box type in ping patchserver.crypticstudios.com -t and let it run while you play the game. This will send tiny query packets to their server so you can see if you're totally losing your internet connection at these times. Also, are you on wireless or a network cable?
Yo, usually filters help filter out 'noise' on the line and don't effect the speed too much.
What I would suggest doing is, before you launch the game, go to Start -> Run type in cmd and then OK. In the black box type in ping patchserver.crypticstudios.com -t and let it run while you play the game. This will send tiny query packets to their server so you can see if you're totally losing your internet connection at these times. Also, are you on wireless or a network cable?
Thanks for the help, and i don't mean to sound ****ed at you directly, but I already did that tracert test; I used to work in internet technical support, I know nearly all the troubleshooting tricks. And I already said I was on cable, my router is not a wireless one and I have tried bypassing the router entirely with no change in the results.
I've been running the nettest several times and noticing no difference; it's the same no matter what time of day it is, all the pings that should be around 500kb/s are no higher than 45kb/s, and averaging about 28kb/s.
This might be totally unrelated, but that happened to me once when I first bought World of Warcraft. Long story short, turned out my routers firmware needed to be upgraded. After that, I could play WoW more than 2 min without it timing out on me. Like I said, might be unrelated but perhaps checking your router's firmware might help.
This might be totally unrelated, but that happened to me once when I first bought World of Warcraft. Long story short, turned out my routers firmware needed to be upgraded. After that, I could play WoW more than 2 min without it timing out on me. Like I said, might be unrelated but perhaps checking your router's firmware might help.
Already tried bypassing the router entirely and get the same results.
Does anyone actually read the posts? I've said that 3 times now.
results in teh 20-50 range on the nettest is not good something definately affecting the connection. (from experience need at less 200 in columns 1and 3 and 14 in colummn 2 for reliable play.)
What was the ping time listed after the ip and was the reading on ports 80 and 443 the same as 7000-7500 ports.
Thanks for the help, and i don't mean to sound ****ed at you directly, but I already did that tracert test; I used to work in internet technical support, I know nearly all the troubleshooting tricks. And I already said I was on cable, my router is not a wireless one and I have tried bypassing the router entirely with no change in the results.
I've been running the nettest several times and noticing no difference; it's the same no matter what time of day it is, all the pings that should be around 500kb/s are no higher than 45kb/s, and averaging about 28kb/s.
I didn't say to do a tracert. I asked to do a constant ping to google.com or some other site to see if you're totally losing internet access during these periods. The reason I ask you to do this (btw, I'm a Tech Support guy too and I have A+ certification as well as several years of experiece) is because it MIGHT be your network controller in your computer. Losing packets like that can be a sign that it is starting to fail.
I didn't say to do a tracert. I asked to do a constant ping to google.com or some other site to see if you're totally losing internet access during these periods. The reason I ask you to do this (btw, I'm a Tech Support guy too and I have A+ certification as well as several years of experiece) is because it MIGHT be your network controller in your computer. Losing packets like that can be a sign that it is starting to fail.
Ah, I see. I tried it earlier, but I don't recall anything out of the ordinary. I'll run it again. I'm pretty doubtful that the network controller is going already, this comp is only about 4 months old, at most, as far as I know.
ok, in the following results, I've edited out my personal IP.
Here's the results from 2 of my nettest runs:
Pinging www.l.google.com [74.125.53.99] with 32 bytes of data:
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=36ms TTL=53
Reply from 74.125.53.99: bytes=32 time=50ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=33ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=29ms TTL=53
Reply from 74.125.53.99: bytes=32 time=49ms TTL=53
Reply from 74.125.53.99: bytes=32 time=37ms TTL=53
Reply from 74.125.53.99: bytes=32 time=52ms TTL=53
Reply from 74.125.53.99: bytes=32 time=40ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=51ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=45ms TTL=53
Reply from 74.125.53.99: bytes=32 time=52ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=23ms TTL=53
Reply from 74.125.53.99: bytes=32 time=42ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=43ms TTL=53
Reply from 74.125.53.99: bytes=32 time=23ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=38ms TTL=53
Reply from 74.125.53.99: bytes=32 time=38ms TTL=53
Ping statistics for 74.125.53.99:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 52ms, Average = 31ms
Pinging patchserver.crypticstudios.com [208.95.184.25] with 32 bytes of data:
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=106ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=99ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=109ms TTL=115
Reply from 208.95.184.25: bytes=32 time=97ms TTL=115
Reply from 208.95.184.25: bytes=32 time=97ms TTL=115
Reply from 208.95.184.25: bytes=32 time=94ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=104ms TTL=115
Reply from 208.95.184.25: bytes=32 time=87ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=95ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=100ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=95ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=92ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=93ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Request timed out.
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=101ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=92ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Ping statistics for 208.95.184.25:
Packets: Sent = 41, Received = 40, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 109ms, Average = 92ms
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
3 28 ms 9 ms 23 ms rd1cs-ge1-2-1.ok.shawcable.net [64.59.168.66]
4 20 ms 27 ms 19 ms rc2so-tge0-15-5-0-2.cg.shawcable.net [66.163.77.213]
5 37 ms 35 ms 59 ms rc1nr-pos0-8-5-0.wp.shawcable.net [66.163.76.86]
6 38 ms 36 ms 35 ms rc1sc-ge2-0.wp.shawcable.net [66.163.73.173]
7 61 ms 79 ms 63 ms rc1sh-pos1-0-0.mt.shawcable.net [66.163.77.170]
8 72 ms 74 ms 73 ms rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154]
9 90 ms 78 ms 82 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.185]
10 90 ms 79 ms 79 ms cr2-cr1.nym009.internap.net [66.79.146.198]
11 82 ms 88 ms 88 ms bsn006-nym009-9-cr1.bsn006.internap.net [66.79.158.9]
12 88 ms 86 ms 104 ms bsn004-bsn006-792-mpr1.bsn004.internap.net [66.79.145.34]
13 109 ms 90 ms 118 ms border12.te7-1-bbnet1.bsn.pnap.net [63.251.128.42]
14 90 ms 90 ms 104 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
15 96 ms 88 ms 91 ms patchserver.crypticstudios.com [208.95.184.25]
Tracing route to www.l.google.com [74.125.53.103]
over a maximum of 30 hops:
3 10 ms 26 ms 11 ms rd1cs-ge1-2-1.ok.shawcable.net [64.59.168.66]
4 26 ms 16 ms 18 ms rc2bb-tge0-1-2-0.vc.shawcable.net [66.163.77.218]
5 15 ms 27 ms 14 ms rc2wh-tge0-15-1-0.vc.shawcable.net [66.163.69.121]
6 32 ms 23 ms 19 ms rc2wt-pos7-0.wa.shawcable.net [66.163.76.154]
7 98 ms 38 ms 33 ms 74.125.48.233
8 51 ms 21 ms 21 ms 209.85.249.32
9 24 ms 23 ms 25 ms 216.239.46.208
10 34 ms 25 ms 39 ms 209.85.250.146
11 70 ms 26 ms 39 ms 216.239.48.165
12 28 ms 27 ms 28 ms 72.14.232.6
13 27 ms 28 ms 27 ms pw-in-f103.1e100.net [74.125.53.103]
Hmm... maybe I didn't explain myself well... I do that sometimes
Start the ping test to google.com before you start the game and let it run all the while you are running the game so you can see if you totally lost Internet connection when you get kicked out of game. It will say 'timed out' if it did. This will help narrow it down to ISP or your own hardware (NIC or router)...
Hmm... maybe I didn't explain myself well... I do that sometimes
Start the ping test to google.com before you start the game and let it run all the while you are running the game so you can see if you totally lost Internet connection when you get kicked out of game. It will say 'timed out' if it did. This will help narrow it down to ISP or your own hardware (NIC or router)...
Ah, I see what you mean now; that is a good idea. I can try, but I don't know how good it will work right now; the command prompt only keeps a set # of lines worth of information. It's been a while and I don't recall how to get it to save a log of the ping results, so I'm not sure how to see if any of the lines that are gone were a timeout or not. If you happen to know the command, I'd really appreciate it ^_^
Ok, to day has been the worst one yet; NOW it doesn't even kick me out, it just said "Retrieving character list" for almost 10 MINUTES, 4 times in a row! THEN when I DID get in (only twice out of the 5 attempts over 40 minutes) I was in for about a minute and a half before it kicked me out AGAIN! Luckilly I had been running the ping constantly while it was doing this, but the results can't be posted as the forums say it makes the post to frikkin long, even by itself. At the least, here's the statistics and the nettest I did just after the first attempt to log in failed miserably:
Ping statistics for 208.95.184.25:
Packets: Sent = 606, Received = 603, Lost = 3 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 283ms, Average = 103ms
I'm getting sick and tired of this, and am considering canceling my account until they can get there heads out of their asses. I can't even make a frikkin support ticket about this, for cryin' out loud!! What the :mad: is the point of having a page on the site for creating new tickets if it doesn't have any way of letting you create new tickets!!!
When these problems started weeks ago, it was my ISP having issues. I'd run the tests with the router, bypassed the router, then with the router. After the ISP fixed what was causing it at their end, I was a complete and utter idiot and kept running the tests with the router in the equation, thinking "I've already bypassed the router, I know that`s not an issue", thinking this was an extension of the old issue.
So the short is my router is hooped and I'm an idiot.
I want to sincerely apologize for my rudeness, especially to Cryptic; it was uncalled for and I will not let my frustration get the better of me again.
For what it is worth, I had the same problem a few months ago.
Kept getting consistent disco's and seemed to be fairly regular (every 5-20 min). Turns out that it was crappy wiring at the telephone line box at the house and the outlet I use (I have AT&T DSL).
Basically the phone guy switched the DSL portion to the line 2 of the house and put some filters on it, Not had a problem since.
When these problems started weeks ago, it was my ISP having issues. I'd run the tests with the router, bypassed the router, then with the router. After the ISP fixed what was causing it at their end, I was a complete and utter idiot and kept running the tests with the router in the equation, thinking "I've already bypassed the router, I know that`s not an issue", thinking this was an extension of the old issue.
So the short is my router is hooped and I'm an idiot.
I want to sincerely apologize for my rudeness, especially to Cryptic; it was uncalled for and I will not let my frustration get the better of me again.
Glad to hear you got it fixed man
Don't feel bad about not being able to figure it out... if you could solve all the computer problems you had then people like me and the Cryptic IT Support people would be out of work
Okay, it looks like the new router is not fixing the issue...
I've been searching the forums for a while, trying to find a solution to the constant lag and disconnects I've been getting on a daily basis for several weeks now.
I've replaced my router.
I've had my ISP send technicians.
I've done hours and hours of troubleshooting on my PC with both my ISP and my computer manufacturer.
Nothing is working.
Today I was noticing several dozen threads on the forums with several people in each one, all having the same issues. And all living on the west coast of North America. After looking at the domains of the hops with high pings and dropped packets, I've started to see a distinct trend. It just hit me that all the problems seem to be almost entirely on systems owned by some company called InterNAP; I did a google search and found 2 things: internap.net and pnap.net are both owned by InterNAP, and 2) STO is NOT the only game suffering from the same issues with InterNAP; WoW and others are having the same problems. And it's all people on the west coast, such as BC, Washington, etc.
Is InterNAP the real cause of our woes? How do we fix the problems that are being caused by InterNAP, if it IS their systems interfering? Cryptic can't do anything because it's not their servers, and I'm not sure my ISP can do anything because it's outside their network. So what do we do? InterNAP seems to be causing a HUGE issue for hundreds of MMO players across the west coast of North America, and it seems they ahve been for months.
Comments
Since you are in canada I assuming you are using Shaw which if you search the net you will find articles that shaw does traffic shape. Run the nettest both during when you have and don't have problems . If the results are difffernt then you may be being affected by shapping. (as the nettest server is not the game server so would not be affect by player load.)
Also there been a major routing problem couple of days ago that affected all traffic out of canada that the rerouting to fix may still be affect you a little (secondary routes of lower qualltiy)
What I would suggest doing is, before you launch the game, go to Start -> Run type in cmd and then OK. In the black box type in ping patchserver.crypticstudios.com -t and let it run while you play the game. This will send tiny query packets to their server so you can see if you're totally losing your internet connection at these times. Also, are you on wireless or a network cable?
Thanks for the help, and i don't mean to sound ****ed at you directly, but I already did that tracert test; I used to work in internet technical support, I know nearly all the troubleshooting tricks. And I already said I was on cable, my router is not a wireless one and I have tried bypassing the router entirely with no change in the results.
I've been running the nettest several times and noticing no difference; it's the same no matter what time of day it is, all the pings that should be around 500kb/s are no higher than 45kb/s, and averaging about 28kb/s.
Already tried bypassing the router entirely and get the same results.
Does anyone actually read the posts? I've said that 3 times now.
What was the ping time listed after the ip and was the reading on ports 80 and 443 the same as 7000-7500 ports.
I didn't say to do a tracert. I asked to do a constant ping to google.com or some other site to see if you're totally losing internet access during these periods. The reason I ask you to do this (btw, I'm a Tech Support guy too
Ah, I see. I tried it earlier, but I don't recall anything out of the ordinary. I'll run it again. I'm pretty doubtful that the network controller is going already, this comp is only about 4 months old, at most, as far as I know.
ok, in the following results, I've edited out my personal IP.
Here's the results from 2 of my nettest runs:
contacting nettest server..
Ping: 93.8 msec
Port: 80: 68 KB/sec 3 KB/sec 72 KB/sec 500
Port: 80: 63 KB/sec 3 KB/sec 67 KB/sec 500
Port: 443: 69 KB/sec 4 KB/sec 75 KB/sec 500
Port: 443: 60 KB/sec 3 KB/sec 66 KB/sec 500
Port: 7255: 8 KB/sec 1 KB/sec 10 KB/sec 500
Port: 7255: 44 KB/sec 3 KB/sec 48 KB/sec 500
Port: 7003: 52 KB/sec 5 KB/sec 56 KB/sec 500
Port: 7003: timed out
Port: 7202: 54 KB/sec 3 KB/sec 58 KB/sec 500
Port: 7202: 27 KB/sec 2 KB/sec 30 KB/sec 500
Port: 7499: 55 KB/sec 3 KB/sec 60 KB/sec 500
Port: 7499: 48 KB/sec 3 KB/sec 52 KB/sec 500
Port: 80: 73 KB/sec 3 KB/sec 78 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
contacting nettest server..
Ping: 93.8 msec
Port: 80: 94 KB/sec 4 KB/sec 99 KB/sec 500
Port: 80: 69 KB/sec 3 KB/sec 73 KB/sec 500
Port: 443: 64 KB/sec 3 KB/sec 69 KB/sec 500
Port: 443: 67 KB/sec 3 KB/sec 71 KB/sec 500
Port: 7255: 87 KB/sec 4 KB/sec 93 KB/sec 500
Port: 7255: 69 KB/sec 3 KB/sec 73 KB/sec 500
Port: 7003: 66 KB/sec 3 KB/sec 73 KB/sec 500
Port: 7003: 67 KB/sec 3 KB/sec 75 KB/sec 500
Port: 7202: 66 KB/sec 3 KB/sec 71 KB/sec 500
Port: 7202: 74 KB/sec 3 KB/sec 80 KB/sec 500
Port: 7499: 71 KB/sec 3 KB/sec 76 KB/sec 500
Port: 7499: 62 KB/sec 3 KB/sec 66 KB/sec 500
Port: 80: 56 KB/sec 3 KB/sec 59 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 1 KB/sec
hit return to exit
And here's a ping I did to Google with -t:
C:\Users\rentacenter>ping www.google.com -t
Pinging www.l.google.com [74.125.53.99] with 32 bytes of data:
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=36ms TTL=53
Reply from 74.125.53.99: bytes=32 time=50ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=33ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=29ms TTL=53
Reply from 74.125.53.99: bytes=32 time=49ms TTL=53
Reply from 74.125.53.99: bytes=32 time=37ms TTL=53
Reply from 74.125.53.99: bytes=32 time=52ms TTL=53
Reply from 74.125.53.99: bytes=32 time=40ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=51ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=45ms TTL=53
Reply from 74.125.53.99: bytes=32 time=52ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=23ms TTL=53
Reply from 74.125.53.99: bytes=32 time=42ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=24ms TTL=53
Reply from 74.125.53.99: bytes=32 time=43ms TTL=53
Reply from 74.125.53.99: bytes=32 time=23ms TTL=53
Reply from 74.125.53.99: bytes=32 time=27ms TTL=53
Reply from 74.125.53.99: bytes=32 time=25ms TTL=53
Reply from 74.125.53.99: bytes=32 time=26ms TTL=53
Reply from 74.125.53.99: bytes=32 time=38ms TTL=53
Reply from 74.125.53.99: bytes=32 time=38ms TTL=53
Ping statistics for 74.125.53.99:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 52ms, Average = 31ms
And to the patchserver:
C:\Users\rentacenter>ping patchserver.crypticstudios.com -t
Pinging patchserver.crypticstudios.com [208.95.184.25] with 32 bytes of data:
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=106ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=99ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=109ms TTL=115
Reply from 208.95.184.25: bytes=32 time=97ms TTL=115
Reply from 208.95.184.25: bytes=32 time=97ms TTL=115
Reply from 208.95.184.25: bytes=32 time=94ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=104ms TTL=115
Reply from 208.95.184.25: bytes=32 time=87ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=95ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=100ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=95ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=92ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=93ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=91ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Request timed out.
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=90ms TTL=115
Reply from 208.95.184.25: bytes=32 time=101ms TTL=115
Reply from 208.95.184.25: bytes=32 time=89ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Reply from 208.95.184.25: bytes=32 time=92ms TTL=115
Reply from 208.95.184.25: bytes=32 time=88ms TTL=115
Ping statistics for 208.95.184.25:
Packets: Sent = 41, Received = 40, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 109ms, Average = 92ms
Hope this helps.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\rentacenter>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
3 28 ms 9 ms 23 ms rd1cs-ge1-2-1.ok.shawcable.net [64.59.168.66]
4 20 ms 27 ms 19 ms rc2so-tge0-15-5-0-2.cg.shawcable.net [66.163.77.213]
5 37 ms 35 ms 59 ms rc1nr-pos0-8-5-0.wp.shawcable.net [66.163.76.86]
6 38 ms 36 ms 35 ms rc1sc-ge2-0.wp.shawcable.net [66.163.73.173]
7 61 ms 79 ms 63 ms rc1sh-pos1-0-0.mt.shawcable.net [66.163.77.170]
8 72 ms 74 ms 73 ms rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.154]
9 90 ms 78 ms 82 ms cr2-nyiix-peer.nym009.internap.net [198.32.160.185]
10 90 ms 79 ms 79 ms cr2-cr1.nym009.internap.net [66.79.146.198]
11 82 ms 88 ms 88 ms bsn006-nym009-9-cr1.bsn006.internap.net [66.79.158.9]
12 88 ms 86 ms 104 ms bsn004-bsn006-792-mpr1.bsn004.internap.net [66.79.145.34]
13 109 ms 90 ms 118 ms border12.te7-1-bbnet1.bsn.pnap.net [63.251.128.42]
14 90 ms 90 ms 104 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
15 96 ms 88 ms 91 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
C:\Users\rentacenter>tracert www.google.com
Tracing route to www.l.google.com [74.125.53.103]
over a maximum of 30 hops:
3 10 ms 26 ms 11 ms rd1cs-ge1-2-1.ok.shawcable.net [64.59.168.66]
4 26 ms 16 ms 18 ms rc2bb-tge0-1-2-0.vc.shawcable.net [66.163.77.218]
5 15 ms 27 ms 14 ms rc2wh-tge0-15-1-0.vc.shawcable.net [66.163.69.121]
6 32 ms 23 ms 19 ms rc2wt-pos7-0.wa.shawcable.net [66.163.76.154]
7 98 ms 38 ms 33 ms 74.125.48.233
8 51 ms 21 ms 21 ms 209.85.249.32
9 24 ms 23 ms 25 ms 216.239.46.208
10 34 ms 25 ms 39 ms 209.85.250.146
11 70 ms 26 ms 39 ms 216.239.48.165
12 28 ms 27 ms 28 ms 72.14.232.6
13 27 ms 28 ms 27 ms pw-in-f103.1e100.net [74.125.53.103]
Trace complete.
Start the ping test to google.com before you start the game and let it run all the while you are running the game so you can see if you totally lost Internet connection when you get kicked out of game. It will say 'timed out' if it did. This will help narrow it down to ISP or your own hardware (NIC or router)...
Ah, I see what you mean now; that is a good idea. I can try, but I don't know how good it will work right now; the command prompt only keeps a set # of lines worth of information. It's been a while and I don't recall how to get it to save a log of the ping results, so I'm not sure how to see if any of the lines that are gone were a timeout or not. If you happen to know the command, I'd really appreciate it ^_^
I'm getting sick and tired of this, and am considering canceling my account until they can get there heads out of their asses. I can't even make a frikkin support ticket about this, for cryin' out loud!! What the :mad: is the point of having a page on the site for creating new tickets if it doesn't have any way of letting you create new tickets!!!
I want to sincerely apologize for my rudeness, especially to Cryptic; it was uncalled for and I will not let my frustration get the better of me again.
Kept getting consistent disco's and seemed to be fairly regular (every 5-20 min). Turns out that it was crappy wiring at the telephone line box at the house and the outlet I use (I have AT&T DSL).
Basically the phone guy switched the DSL portion to the line 2 of the house and put some filters on it, Not had a problem since.
Glad to hear you got it fixed man
Don't feel bad about not being able to figure it out... if you could solve all the computer problems you had then people like me and the Cryptic IT Support people would be out of work
I've been searching the forums for a while, trying to find a solution to the constant lag and disconnects I've been getting on a daily basis for several weeks now.
Nothing is working.
Today I was noticing several dozen threads on the forums with several people in each one, all having the same issues. And all living on the west coast of North America. After looking at the domains of the hops with high pings and dropped packets, I've started to see a distinct trend. It just hit me that all the problems seem to be almost entirely on systems owned by some company called InterNAP; I did a google search and found 2 things: internap.net and pnap.net are both owned by InterNAP, and 2) STO is NOT the only game suffering from the same issues with InterNAP; WoW and others are having the same problems. And it's all people on the west coast, such as BC, Washington, etc.
Is InterNAP the real cause of our woes? How do we fix the problems that are being caused by InterNAP, if it IS their systems interfering? Cryptic can't do anything because it's not their servers, and I'm not sure my ISP can do anything because it's outside their network. So what do we do? InterNAP seems to be causing a HUGE issue for hundreds of MMO players across the west coast of North America, and it seems they ahve been for months.
So who's job is it to fix it?