World of Warcraft®

This did not work for me. just sayin.

Worked for me, for a while...


Now i am trying to do my BGs with 3k ms which sucks hard, though i giggle when noobs still can't kill me with a 1 - 3 second delay. :p

when i do this, the first command says element not found, the seconed one says the file name, directory name, or volume label syntax is incorrect

netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=900 store=persistent

element not found. Ideas?

netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=900 store=persistent

element not found. Ideas?

Means you've not put in the right connection name.

netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=900 store=persistent

element not found. Ideas?

Go into your router itself.

type this into your internet bar and hit enter

192.168.1.1

Login is normally admin, and the password is normally admin or password.

Ok once in, on the left side of the screen u will have a list of things to click on and options.

Look for WAN Setup, chance the MTU Size(in bytes) from 1500, down to 900. click apply.


Done.

Spoke to soon bout the fix :< WoW worked for 2 days with no lag then BOOM its back again :(

24/07/2011 12:38Posted by Thalgalad

People should avoid this, its not upto us as end users to go messing with settings to clean up someone elses incompetance.

We have listed it as a possible work-around until the issue itself is resolved. Should you not wish to use it, please contact your ISP for further advice.

You have listed it as a possible workaround.
Okay, so when this issue gets resolved, which it will eventually. All these people that have no clue what theyve changed, with this command, may get issues because of this command.

Do you not see the problem with this? You're going to give yourselves a headache trying to fix a problem you created by letting people who have no buisness messing with settings they dont understand do so because they're desperate to play wow because YOU said it was okay to do so.

The issue will get fixed eventually, people shouldnt go messing with this. No sorry, People that dont know what they're messing with and dont know how to reverse it, shouldnt be messing with it, and you as a blue shouldnt be saying:

24/07/2011 12:38Posted by Thalgalad

We have listed it as a possible work-around until the issue itself is resolved

Because what if this command prompt causes an issue when the actual issue gets resolved? People will come back here with their pitch forks and torches burning, and all you'll say is "you did it at your own risk"

People, dont mess with cmd prompt unless your savvy enough to know what your messing with, its just common sense. I know your all desperate to play, but you may only give yourselves issues down the line.

24/07/2011 13:55Posted by Végeta

We have listed it as a possible work-around until the issue itself is resolved. Should you not wish to use it, please contact your ISP for further advice.

You have listed it as a possible workaround.
Okay, so when this issue gets resolved, which it will eventually. All these people that have no clue what theyve changed, with this command, may get issues because of this command.

Do you not see the problem with this? You're going to give yourselves a headache trying to fix a problem you created by letting people who have no buisness messing with settings they dont understand do so because they're desperate to play wow because YOU said it was okay to do so.

The issue will get fixed eventually, people shouldnt go messing with this. No sorry, People that dont know what they're messing with and dont know how to reverse it, shouldnt be messing with it, and you as a blue shouldnt be saying:

24/07/2011 12:38Posted by Thalgalad

We have listed it as a possible work-around until the issue itself is resolved

Because what if this command prompt causes an issue when the actual issue gets resolved? People will come back here with their pitch forks and torches burning, and all you'll say is "you did it at your own risk"

People, dont mess with cmd prompt unless your savvy enough to know what your messing with, its just common sense. I know your all desperate to play, but you may only give yourselves issues down the line. <span class="underline"/>

I told them how to reset it in the OP
I told them then to use it at their own risk.
:> MFW You didn't read the OP.

Fingers crossed...i think it's worked....either way THANK YOU!!!!! *big squishy hug*

D: mfw people are asking why what they type doesnt work because they have no clue what they're copy pasta'ing into cmd, not realising its because of the quotation marks.

All im promoting is people that have no idea at all about what they're doing not do it. The issue will get resolved in its own time.

If they dont have the sense to realise why it wont work -->

netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=900 store=persistent

element not found. Ideas?

Means you've not put in the right connection name.

They probably shouldnt be messing with it in the first place.

I read your OP, i personally know how to reset it, but do you think people having trouble getting it to work simply because they fail to understand what they are doing, will know straight away how to reverse it?
I dont.
All im saying is this, be careful with what you're doing people, we're all desperate to play, but if you dont know what it is your doing, then dont do it, you may just give yourselves another headache when it does get fixed.

22/07/2011 10:04Posted by Spersky

To reset this, re-type the line that worked for you and replace the "900" with "1500"

Taken directly from my OP.
/conversation

Just spoke with Virgin media, its true what others are saying, 27th of July is fix date they confirmed problem is at their end, but its due to blizzard also that this problem has occurred. I have got myself 15 compo as there are 2 of us that play wow in my house. call them up complain and you will get between £10-£15 off your next bill :)

Its not much but pays at least for one months wow :)

For the people that are having problems getting this to work try this....

Windows 7/Vista ONLY

1. Goto your start menu, click on all programs then accessories
2. RIGHT CLICK on command prompt and run as administrator. (If u cant run as admin then it wont work)
3. Type or copy/paste this command into comand prompt :-
netsh interface ipv4 show subinterfaces

This should give you something like this :-

MTU MediaSenseState Bytes In Bytes Out Interface
------- --------------- --------- --------- -------------
4294967295 1 0 13487914 Loopback Pseudo-Interface 1
1500 1 3734493902 282497358 Local Area Connection 2

The bottom line tells you your current MTU, 1500 in this example, and the name of your connection that you want to change, which is Local Area Connection 2 in this case. This is what you need to type EXACTLY into the next command.


4. Now type:-
netsh interface ipv4 set subinterface "?????????" mtu=900 store=persistent

Just replace the question marks with the name of your connection you found out from step 3

And thats it, windows 7 users can just exit wow and resart the game.. I dont know about vista tho, that might require a reboot

I am following the XP fix what MTU do i set for it? cause it says something about not setting it below 1400 and i don't wanna risk it xD

Thank you Very much for this Much appreciated mate, Typical virgin messed up again, Time to switch providers now But this fix did work :) Down from 3k ms to 30 :)

www.reducethelag.com

30 day free trial. Works perfect, gone from 4.6k ms to 60.

24/07/2011 14:28Posted by Lightguardoo

I am following the XP fix what MTU do i set for it? cause it says something about not setting it below 1400 and i don't wanna risk it xD

900 worked fine on my wife's XP machine.

Is there a fix for Windows Vista or not?

netsh interface ipv4 set subinterface "Local Area Connection" mtu=900 store=persistent

Yep, worked for me, went from 800/1500 down to 30/30... many thanks to the OP!

:)