This is no exageration, I can not stay connected to the game for more than 30 seconds depending on the time of day. In every thread about this problem that I have read (and there are A LOT), everyone who replies seems to put the blame on the poster's end and denies any problem at Cryptic's end. Well could someone please enlighten me as to how the following is an indication that the problem is at my end of the connection. If I seem short tempered, it's purely out of frustration. I seem to have the problem between 9pm and 1am central time but not from 4pm to 6pm. At the earlier time I seem to have a flawless connection.
The following was collected at about 9:30pm after a long series of disconnects and looks no different from data collected at earlier times.
PLEASE help. I'm not sure what I'm looking at but these seem like decent times and data rates.
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 6 ms 8 ms 73.209.136.1
3 7 ms 8 ms 11 ms ge-3-25-ur01.strack.tx.houston.comcast.net [68.85.250.209]
4 10 ms 10 ms 8 ms te-8-2-ar01.bearcreek.tx.houston.comcast.net [68.85.244.61]
5 9 ms 10 ms 9 ms po-12-ar01.royalton.tx.houston.comcast.net [68.85.244.50]
6 10 ms 9 ms 15 ms 68.85.245.253
7 9 ms 8 ms 10 ms 68.85.245.158
8 14 ms 14 ms 12 ms po-17-ar02.greenspoint.tx.houston.comcast.net [68.85.244.130]
9 26 ms 25 ms 28 ms 68.86.90.149
10 19 ms 18 ms 20 ms pos-0-2-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.150]
11 18 ms 18 ms 18 ms 208.175.175.97
12 21 ms 20 ms 17 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.204.146]
13 21 ms 18 ms 17 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
14 63 ms 62 ms 61 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.102]
15 62 ms 63 ms 62 ms er1-te-1-0-1.NewYork.savvis.net [204.70.197.5]
16 64 ms 62 ms 71 ms 208.173.129.62
17 64 ms 62 ms 61 ms border2.po1-20g-bbnet1.nym008.pnap.net [216.52.95.3]
18 69 ms 67 ms 67 ms mpr2.te7-3.bsn004-nym008.phi.pnap.net [216.52.93.222]
19 67 ms 67 ms 68 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
20 68 ms 67 ms 71 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
21 70 ms 71 ms 69 ms patchserver.crypticstudios.com [208.95.184.25]
From the cycling of the problem during certain times does seem to indicate a traffic shappping problem but your test results apear to indicate no problems on the prots tested (although the game uses 7000-7500, I think the nettest checks the most comman used of those ports)
what type is your connection network card, router, modem type of isp connection ect.
personally I have played the game 5-6 hour straight at a time without a single disconnet since closed beta. where if is was just a straight cryptic problem then I and everyone on at the same time would have the problem.
I've done a little more testing and checking over the past couple of days and I'm getting no where. My ISP is Comcast (I know, some of you are going to tell me that whatever they told me is a lie). They assure me that they are not shaping and implimenting any sort of traffic controls on 7000-7500. The techs that I have spoken to all tell me that the modem is reporting that it is opperating correctly, and I had them send a refresh signal to my modem. I have removed my wireless router from the system and plugged the modem directly into my network port on my desktop. None of ths has solved the problem.
A few tests that I've done involve when I login and how long I stay logged in for, and I have noticed something potentially interesting. I usually have no problem logging in and staying connected in the early evening hours of 4 - 8pm central time. My problem seems to be from 9pm - 12 or 1am. So I got home from work and logged in at 5pm last night. Instead of logging off for dinner and family time I left the game running, checking on it from time to time to avoid any sort of boot after inactivity. When I returned to the computer to actually play at 9:30, I had not lost connect to the server, I had not been booted, and I was able to play until I logged out at 11pm. After logging out at 11, I logged right back in. Guess what happened ... yep, disconnected every 30 seconds to 5 minutes. It would seem that if I can log in early enough then I don't have a problem, but if I try to login after a certain time then there is no hope of staying connected.
I realize that one data point says nothing, but it does seem very odd to me that it how long I'm able to stay connected depends on when the connection was intiated. Comcast says the signal and lines are good, Cryptic says thing on ther end are good, and I'm caught in the middle. I'll be testing this again over the next few days. I understand that if Cryptic was have a huge problem then more people wout be suffering from this. But a good number of people are having these issues, so maybe Cryptic has a small problem that is affecting a small number of people.
When you eliminate the obvious, whatever is left has to be true.
while it may not be a solution and for all i know you may have done it.
but i updated and then reninstalled an older driver for the on-board network connection. seems now i dont get this issue (although mne was not as frequent, my on-board nic would drop out often).
just a thought, and dont kow why it works now, but i a simply chalking it up to driver issue on my behalf since the revert worked for me.
I have updated most drivers, as common practice suggests, but I did not do anything with the oft forgotten NIC driver. Mine is an onboard network card but I have a couple of old PCI cards still sitting around somewhere. Tonight I will try disabling the onboard NIC and plugging one of these older cards and see what happens.
This is no exageration, I can not stay connected to the game for more than 30 seconds depending on the time of day. In every thread about this problem that I have read (and there are A LOT), everyone who replies seems to put the blame on the poster's end and denies any problem at Cryptic's end. Well could someone please enlighten me as to how the following is an indication that the problem is at my end of the connection. If I seem short tempered, it's purely out of frustration. I seem to have the problem between 9pm and 1am central time but not from 4pm to 6pm. At the earlier time I seem to have a flawless connection.
.
i posted many times and still got ignored. how do you think i feel?
I have updated most drivers, as common practice suggests, but I did not do anything with the oft forgotten NIC driver. Mine is an onboard network card but I have a couple of old PCI cards still sitting around somewhere. Tonight I will try disabling the onboard NIC and plugging one of these older cards and see what happens.
Thanks for the suggestion.
i actually did both...the seperate NIC and the on-board.
the NIC is not bad, but really i have stuck with the on-board more.
so to cover: i did both, and after this, i dont have the issues.
p.s. - you can update the onboard NIC drivers as well...and ou dont need to do a bios update for it. On most baords i should say - before i step further into that hole...lol
I'm having a slightly different problem where I try to download the patch and then my internet connnection disconnects repeatedly. The only common thread to these disconnections is that I just started running the download client.
I'm almost afraid to say it for fear of jinxing everything, but I think I have finally fixed my problem. Thanks to Sir James for reminding me to tinker with the NIC drivers.
I've been running STO under Windows 7, using the drivers that are installed with Win 7. I downloaded an older version of the NIC driver (don't recall the version number, but it was a 2008 release). I was able to play for three straight hours last night, during my biggest problem time, without so much as a "SERVER NOT RESPONDING" warning during zone changes.
It appears that STO was having trouble with my Windows 7 network driver. I really hope this helps someone else who might be having the same problem.
Something else that occurs to me for other who might be running into his problem. The driver that I rolled back to (from the default Win7 driver) was of course downloaded directly from the manufacturer's website. It is my understanding that most of the drivers that shipped with Win7 were submitted by the respective hardware manufacturers, but in my case the network driver installed by Windows was generic. If "un-updating" your network card drivers doesn't fix your connection problem, consider looking for other generic drivers that may not be optimized for your hardware.
Comments
what type is your connection network card, router, modem type of isp connection ect.
personally I have played the game 5-6 hour straight at a time without a single disconnet since closed beta. where if is was just a straight cryptic problem then I and everyone on at the same time would have the problem.
so need to gather all information
A few tests that I've done involve when I login and how long I stay logged in for, and I have noticed something potentially interesting. I usually have no problem logging in and staying connected in the early evening hours of 4 - 8pm central time. My problem seems to be from 9pm - 12 or 1am. So I got home from work and logged in at 5pm last night. Instead of logging off for dinner and family time I left the game running, checking on it from time to time to avoid any sort of boot after inactivity. When I returned to the computer to actually play at 9:30, I had not lost connect to the server, I had not been booted, and I was able to play until I logged out at 11pm. After logging out at 11, I logged right back in. Guess what happened ... yep, disconnected every 30 seconds to 5 minutes. It would seem that if I can log in early enough then I don't have a problem, but if I try to login after a certain time then there is no hope of staying connected.
I realize that one data point says nothing, but it does seem very odd to me that it how long I'm able to stay connected depends on when the connection was intiated. Comcast says the signal and lines are good, Cryptic says thing on ther end are good, and I'm caught in the middle. I'll be testing this again over the next few days. I understand that if Cryptic was have a huge problem then more people wout be suffering from this. But a good number of people are having these issues, so maybe Cryptic has a small problem that is affecting a small number of people.
When you eliminate the obvious, whatever is left has to be true.
but i updated and then reninstalled an older driver for the on-board network connection. seems now i dont get this issue (although mne was not as frequent, my on-board nic would drop out often).
just a thought, and dont kow why it works now, but i a simply chalking it up to driver issue on my behalf since the revert worked for me.
Thanks for the suggestion.
i posted many times and still got ignored. how do you think i feel?
i actually did both...the seperate NIC and the on-board.
the NIC is not bad, but really i have stuck with the on-board more.
so to cover: i did both, and after this, i dont have the issues.
p.s. - you can update the onboard NIC drivers as well...and ou dont need to do a bios update for it. On most baords i should say - before i step further into that hole...lol
that way we don't have to fight with uk people for connection.
Don't run it during off peak times or when you dont have a problem, as it wont provide an accurate reading.
(You may have to run it in vista/xp compatability mode if youa re running windows 7)
I'm almost afraid to say it for fear of jinxing everything, but I think I have finally fixed my problem. Thanks to Sir James for reminding me to tinker with the NIC drivers.
I've been running STO under Windows 7, using the drivers that are installed with Win 7. I downloaded an older version of the NIC driver (don't recall the version number, but it was a 2008 release). I was able to play for three straight hours last night, during my biggest problem time, without so much as a "SERVER NOT RESPONDING" warning during zone changes.
It appears that STO was having trouble with my Windows 7 network driver. I really hope this helps someone else who might be having the same problem.