How to increase your internet connection speed for wow. (a better way)

[JoeWunsch]

Ok.

About 18 months ago I switched servers, and while my old server my latency was always around 150, the new server was always around 250-260, and made playing a pain in the ass because I was not used to this lag delay in casting spells, /following, etc.

I looked online for ways to lower your ping, and found these registry edits.

I did the changes and my ping dropped by over 100. I can verify it was not just a 'visual' change, in that you are just seeing a lower ping number -- because the change was drastic on my end. I was no longer experiencing lag when casting spells resulting in spells not being cast all at once but you see the 5 LB's hit the target all spread out over a few milliseconds.

So I don't know about all these technical reasons on why it wouldn't work, all I can say is I felt and saw a difference in the way my 5 characters played.

[PerzianPenguin]

[s]that would be a viable claim.
if i had a myspace.
The only social networking site i was ever apart of, was Xanga, which i have long left as most of my friends went to myspace.

[/s]Off topic. Did you seriously read the rules? I'm up late, editing your posts cause you didn't read the rules?
-Svpernova09

[TeamGrizzly]

Tried manually editing the registry as taughted in WoW forums and my latency is GREEN for the first time so I can testify that the method works. In terms of gameplay, not much difference though. Maybe I don't feel the effects cos I do not PVP. Anyway, no harm trying. If you do not like it, just delete the additional parameter from registry and revert back to where you started.

[cryinsham]

playing on us servers from Korea and now Germany I can say the tcpack fix does work as far as QoS scheduling i never tried it.

[Los]

But does just the latency number go down, or is the general 'feel' of lag and gameplay actually improving?

[mikekim]

the QoS is not relevant to home networks unless you are running VOIP phones or streaming video for Cameras.

the TCPackfrequency registry change on the other hand does work. I did this a couple of months ago and my latency went from 200-250 to under 50

[zanthor]

TCPAck does help with lowering your PING, it also takes MORE bandwidth creating a higher potential for bottlenecks if you are choked already. (Such as running 5 clients on a low bandwidth provider.)

All said and done PerzianPenguin appears to be posting 80-90% unsubstantiated crap and having people use tools that the average user really shouldn't be screwing with. You jack around in the registry without knowing exactly what you are doing and you can turn your hack attempt into a nice long reload of windows. GPEdit is exactly the same, you can screw things up so bad so fast. None of his advice is coming with a warning of "Hey you may brick your system if you do this wrong..." and it's all sensationalized in his presentation style.

Lose the caps lock.
Post some supporting evidence.
Warn people that these changes may have a negative impact.

Oh, and use the search function... The TCPAck hack has been discussed here at length already.

[Nisch]

[quote='PerzianPenguin',index.php?page=Thread&postI D=198544#post198544]Although DNS pinging works, [/quote]

You're like a spammer pushing out penis enlargement ads.

You say things work without any logical backing.

You need to stop the bullshit.

Pinging (ICMP) and DNS (UDP 53) have nothing to do with your TCP WoW connection.

If it does...........your ISP or your computer sucks.

Also, how are you supposed to give people confidence when you can't even spell "their" correctly?

Someone needs to ban this idiot before he causes someone more harm than good.

Here's a real good example showing the OP doesn't know what the hell he's talking about.

He expects you to mess with your registry and that DNS pinging works when he doesn't even know what NAT is (a fundamental in any networking environment)

[url='http://www.dual-boxing.com/forums/index.php?page=Thread&postID=196636#post196636']Can't get two wow's connected to same server[/url]

[Taliesin]

I also assert that this "fix" does not work as described. The bandwidth allocation for QoS services are only set aside when the network is set up to make use of it. And the purpose of this is actually to improve your performance in most situations even when it is enabled. Unless you're playing on a network with QoS services enabled, then the bandwidth is not touched.

Also consider that you are talking about 20% of the bandwidth of the NIC, not your internet connection, as broadband connections are usually managed by a separate modem or on a host server and not directly inside by your PC. Typical NIC speeds are 10/100 Mbps. Let's assume you are only connected at 10 Mbps. A broadband connection is somewhere between 256 Kbps and 1.5 Mbps. So you're telling me that shaving 2 Mbps off the NIC speed has a significant effect on about .5 Mbps of the remaining 8 Mbps that is largely unused as well? And this is for high-end connection speeds.

The other possibility is that you are playing over dial-up with the modem in your gaming machine, in which case there is no NIC to manage. Besides the fact that QoS should now be disabled and no allocation taking place, the limitations you experience have more to do with connection speed, line quality, and service provider than anything else.

Best case scenario is you are inadvertently disabling other features in your system that may be related to IP management, causing some other unknown affect on system performances. Maybe you boosted IP traffic somehow, but at the cost of what else? I need specifics of what I just disabled in my machine before I start blindly disabling services. Maybe I'm just paranoid....

[Caspian]

Regarding the TCPAck change - not the QoS hack

http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true
(http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true[/url] )
If you set the value to 1, every packet is acknowledged
immediately because there is only one outstanding TCP ACK as a segment is just
received. The value of 0 (zero) is not valid and is treated as the default, 2.
The only time the ACK number is 0 is when a segment is not received and the
host is not going to acknowledge the data.

Formatting - looks better now that is basically quoting myself.