375 replies to this topic

[NocturnalBeast]

Ping was mostly good tonight when using VPN, shot up to 600+ when dropping without. I did have a couple server disconnects when launching though.

[LordSkippy]

Ed Steele, on 05 February 2015 - 12:53 AM, said:

Ping was mostly good tonight when using VPN, shot up to 600+ when dropping without. I did have a couple server disconnects when launching though.

I played without the VPN last night, and my pings were back to what they were before the server move throughout my gaming time. However, I did stop playing at 8:30 Central, and the worse throttling seemed to start a little later than that. Still saw an improvement from 110s to 80s pings. Hopefully thinks did go to pot, and returned to bad throttling, after I stopped playing. Will have to see how tonight goes.

[SoggyGorilla]

it appears the problem has been resolved for the moment, i never went beyond 85 ping for the last 12 hours.

[Clit Beastwood]

I was called by someone from TWC yesterday, they're looking into the issue but due to an established process, they *have* to start by sending someone out. He said it's not going to be a standard truck roll, they want to come out and check line levels, confirm I've got clean grounds, etc. At least from my perspective, from what I can pull from the modem itself, my line levels and noise haven't changed since it was installed. I'm going to try to get a day off of work so I can be home for the on-site testing. I initially protested the home visit, as we've been there, done that and it resolved nothing and we can see exactly where the throttling occurs... He replied that (which, unfortunately many of us can relate to) there's a process, and skipping steps won't help anyone involved.

As an aside, I *did* ask the tech that came out last if those levels were ok because they were at the very upper limit of reasonable as per the modem manufacturer's documentation, and he said it's fine/normal. I purchased another motorola sb6183 (I noticed that on my gigabit LAN, just pinging the TWC issued modem had pings in the 10-15ms range, with a 24" cat6 cable plugged into a broadcom netextreme card in my desktop) and it was unable to sync after being left on all night. According to the modem logs, excessive noise is preventing sync. That's all well and good, as even with the original TWC issued modem I could use servers *anywhere* else without similar issues. All I can recommend is to continue reporting issues to TWC. I *did* have some success posting on the dslreports TWC support forum - Kin3ticX, since you're in my area (ish) maybe you should post there too.

I did try and play last night, my ping was still higher than usual (in the low-mid 100's without vpn) and I got no DC's, less rubberbanding, but hit registry still feels "off". Hitreg from home *used* to feel like testing grounds, but these days its nowhere close.

I am glad that this time around someone at TW seems to be taking me seriously - in the past I'd been hung up on, promised callbacks that never happened, etc. - the rep I'm working with now seems a little more invested in actually helping, so that's a very positive change. I'd upgrade my status from "flabbergasted" to "cautiously optimistic".

P.S. I really just wanted to type the word "flabbergasted" - try it, it's fun.

Edited by Fierostetz, 05 February 2015 - 08:58 AM.

[NocturnalBeast]

I had contacted PingZapper support regarding adding a game profile for MWO and this was their response:

"Hi there


We have tried supporting Mechwarrior in the past, however we could not get it to work since the game seems to not support proxy servers. In any case, we will try some more testing."

Jon, maybe you could contact PingZapper and help them out with this, if you have time?

Edited by Ed Steele, 05 February 2015 - 09:01 AM.

[Clit Beastwood]

Ed Steele, on 05 February 2015 - 09:01 AM, said:

I had contacted PingZapper support regarding adding a game profile for MWO and this was their response:

"Hi there


We have tried supporting Mechwarrior in the past, however we could not get it to work since the game seems to not support proxy servers. In any case, we will try some more testing."

Jon, maybe you could contact PingZapper and help them out with this, if you have time?

Hey Ed, check my screenshots, they show you how to set it up for MWO - it's pretty easy. The pingzapper dudes won't make a profile for it until they can consistently guarantee that it's going to resolve issues, which they cannot do at this time. It makes sense - if need be I can throw together a guide. Let me know

[Kin3ticX]

Fierostetz, on 05 February 2015 - 08:55 AM, said:

I was called by someone from TWC yesterday, they're looking into the issue but due to an established process, they *have* to start by sending someone out. He said it's not going to be a standard truck roll, they want to come out and check line levels, confirm I've got clean grounds, etc. At least from my perspective, from what I can pull from the modem itself, my line levels and noise haven't changed since it was installed. I'm going to try to get a day off of work so I can be home for the on-site testing. I initially protested the home visit, as we've been there, done that and it resolved nothing and we can see exactly where the throttling occurs... He replied that (which, unfortunately many of us can relate to) there's a process, and skipping steps won't help anyone involved.

As an aside, I *did* ask the tech that came out last if those levels were ok because they were at the very upper limit of reasonable as per the modem manufacturer's documentation, and he said it's fine/normal. I purchased another motorola sb6183 (I noticed that on my gigabit LAN, just pinging the TWC issued modem had pings in the 10-15ms range, with a 24" cat6 cable plugged into a broadcom netextreme card in my desktop) and it was unable to sync after being left on all night. According to the modem logs, excessive noise is preventing sync. That's all well and good, as even with the original TWC issued modem I could use servers *anywhere* else without similar issues. All I can recommend is to continue reporting issues to TWC. I *did* have some success posting on the dslreports TWC support forum - Kin3ticX, since you're in my area (ish) maybe you should post there too.

I did try and play last night, my ping was still higher than usual (in the low-mid 100's without vpn) and I got no DC's, less rubberbanding, but hit registry still feels "off". Hitreg from home *used* to feel like testing grounds, but these days its nowhere close.

I am glad that this time around someone at TW seems to be taking me seriously - in the past I'd been hung up on, promised callbacks that never happened, etc. - the rep I'm working with now seems a little more invested in actually helping, so that's a very positive change. I'd upgrade my status from "flabbergasted" to "cautiously optimistic".

P.S. I really just wanted to type the word "flabbergasted" - try it, it's fun.

I will think about it. Not crazy about another cable guy coming out.

Interesting development though, seems almost like the peers may be blaming TWC for this problem. I mean, obviously the last three months has been wasted on this with a stupid blame game.

However, basic troubleshooting logic screws with sending out a truck. I had this problem with my old modem. I had the cable guy here a month ago and he said my lines were super duper. The problem only happens between 5-11ish PST.

Edited by Kin3ticX, 05 February 2015 - 10:00 AM.

[Clit Beastwood]

Kin3ticX, on 05 February 2015 - 09:56 AM, said:

I will think about it. Not crazy about another cable guy coming out.

Interesting development though, seems almost like the peers may be blaming TWC for this problem. I mean, obviously the last three months has been wasted on this with a stupid blame game.

However, basic troubleshooting logic screws with sending out a truck. I had this problem with my old modem. I had the cable guy here a month ago and he said my lines were super duper. The problem only happens between 5-11ish PST.

Oh, I'm with you - but when he said "there's a process, if we don't send someone out there first, the process won't get started" - I've worked at companies with that type of bureaucratic required process. Every journey starts with a step, if they're saying this is the step I need to start with, there's not much sense in resisting. I wasn't told "there's no issue", so that's new. I dunno, the guy on the phone sounded legitimately interested in solving the problem - I haven't gotten that feeling in quite a while. Like I said, cautiously optimistic - not that a home visit is going to fix anything, but optimistic that they're at least listening to me

[NocturnalBeast]

Fierostetz, on 05 February 2015 - 09:06 AM, said:

Hey Ed, check my screenshots, they show you how to set it up for MWO - it's pretty easy. The pingzapper dudes won't make a profile for it until they can consistently guarantee that it's going to resolve issues, which they cannot do at this time. It makes sense - if need be I can throw together a guide. Let me know

Thanks, but I have PingZapper setup pretty much the way you do already. My problem is that PingZapper works well once in a while, but I get intermittent server disconnects.

[Clit Beastwood]

Ed Steele, on 05 February 2015 - 10:21 AM, said:

Thanks, but I have PingZapper setup pretty much the way you do already. My problem is that PingZapper works well once in a while, but I get intermittent server disconnects.

Pretty sure that's just the chicago servers - from a bit of googling it looks like those are the most popular ones - if I connect through another area I get no DC's.

[Jon Cunningham]

Ed Steele, on 05 February 2015 - 09:01 AM, said:

I had contacted PingZapper support regarding adding a game profile for MWO and this was their response: "Hi there We have tried supporting Mechwarrior in the past, however we could not get it to work since the game seems to not support proxy servers. In any case, we will try some more testing." Jon, maybe you could contact PingZapper and help them out with this, if you have time?

Sure.

[Clit Beastwood]

The one I'd really like to see working is WTFast - they said they've tried and were waiting on something from PGI - sounded like BS.. WTFast has a better network infrastructure and logging, but it dc's when shifting from mechlab to drops.

Edited by Fierostetz, 05 February 2015 - 10:50 AM.

[Jon Cunningham]

Kin3ticX, on 05 February 2015 - 09:56 AM, said:

I will think about it. Not crazy about another cable guy coming out. Interesting development though, seems almost like the peers may be blaming TWC for this problem. I mean, obviously the last three months has been wasted on this with a stupid blame game. However, basic troubleshooting logic screws with sending out a truck. I had this problem with my old modem. I had the cable guy here a month ago and he said my lines were super duper. The problem only happens between 5-11ish PST.

Yeah, the majority of people with this issue do not appear to have defective modems. We've encountered a few defective ones, here and there.

Fierostetz, on 05 February 2015 - 10:50 AM, said:

The one I'd really like to see working is WTFast - they said they've tried and were waiting on something from PGI - sounded like BS.. WTFast has a better network infrastructure and logging, but it dc's when shifting from mechlab to drops.

They've never contacted me. Shoot me contact details and I'll talk with them about it.

[NocturnalBeast]

Jon Cunningham, on 05 February 2015 - 10:37 AM, said:

Sure.

Thanks, good to see that you are on top of it!

[Vanos]

Thank you Jon for continuning to fight for this help. and Thank you MW for logging in to your TWC Forums and posting on my thread for our own support.

[Vanos]

Trying to multiquote reply, Thank you to Jon Cunningham for his efforts from this end working with TWC.
Second Thank you to folks responding on my thread about an open TWC Forums Link on page 11 on their end.

[Kin3ticX]

Jon Cunningham, on 05 February 2015 - 10:53 AM, said:

Yeah, the majority of people with this issue do not appear to have defective modems. We've encountered a few defective ones, here and there.

Regarding the ping spikes on the local network to the new TWC modems, Arris TG16xx etc.. I talked to a computer science buff friend of mine who also received the "upgrade" modem. He told me it appears these new modems have a single general processor that controls both the modem and the router/switch/wireless. So anything that taxes the processor hits the packet queue and blips as a high ping. Cost savings at its best I guess.

Edited by Kin3ticX, 05 February 2015 - 11:17 AM.

[NocturnalBeast]

Kin3ticX, on 05 February 2015 - 11:15 AM, said:

Regarding the ping spikes on the local network to the new TWC modems, Arris TG16xx etc.. I talked to a computer science buff friend of mine who also received the "upgrade" modem. He told me it appears these new modems have a single general processor that controls both the modem and the router/switch/wireless. So anything that taxes the processor hits the packet queue and blips as a high ping. Cost savings at its best I guess.

Hmm, I have been looking for an excuse to buy a new router.

[Clit Beastwood]

My spiffy new SB6183 has been plugged into my cable and trying to sync for hours now. It's reporting that my line levels are too weak to bind a channel. Plug in the arris TGblahblah and it syncs within 90 seconds. :sigh: technology

Kin3ticX - its true, the same processor is used for both - I'd recommend bridging it and using your own router (tip - have TWC put it in bridge mode instead of doing it yourself, I don't know why but there's a noticeable difference between the two). That being said, that much latency going 24" isn't a good sign.

[Kin3ticX]

Fierostetz, on 05 February 2015 - 11:51 AM, said:

My spiffy new SB6183 has been plugged into my cable and trying to sync for hours now. It's reporting that my line levels are too weak to bind a channel. Plug in the arris TGblahblah and it syncs within 90 seconds. :sigh: technology

Kin3ticX - its true, the same processor is used for both - I'd recommend bridging it and using your own router (tip - have TWC put it in bridge mode instead of doing it yourself, I don't know why but there's a noticeable difference between the two). That being said, that much latency going 24" isn't a good sign.

Bridge mode and NAT mode seemed to do the same thing. I forgot to had the part that the reason we get a 5ms ping to these suckers vs a 1ms ping to a traditional router/switch is akin to setting up an old computer with two network cards as a router. The extra software layers and non specialized hardware add more latency.

Edited by Kin3ticX, 05 February 2015 - 12:11 PM.