Increasing issues with World of warcraft

Started by Nova, May 07, 2008, 19:56:35

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Nova

Up until 3 weeks ago I pretty much had perfect service from IDNet, but like one or two others, during peak times now I am starting to suffer the very beginnings of the same signs that the connection is suffering somewhere "outside" the local network, there's -definitely- nothing wrong with the SNR and so forth, the router is all happy and there's no issues with browsing or downloads. However from around 18:00-21:00 each night now I am starting to get a "choppy" response from the warcraft server.

Tracing route to host-73.wow-europe.com [80.239.179.73]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    18 ms    17 ms    17 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    18 ms    22 ms    18 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    19 ms    19 ms    17 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    18 ms    18 ms    21 ms  ae-12-51.car2.London1.Level3.net [4.68.116.16]
  6    18 ms    20 ms    23 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    19 ms    19 ms    18 ms  ldn-bb2-link.telia.net [80.91.254.21]
  8    62 ms    60 ms    61 ms  prs-bb1-link.telia.net [80.91.254.209]
  9    60 ms    59 ms    57 ms  prs-b1-link.telia.net [80.91.250.249]
10    29 ms    27 ms    27 ms  prs-tc-i1-link-telia.net [80.91.250.30]

.. beyond this point obviously there is no response since blizzards own firewalls kick in. The last time this happened was Nildram and eventually it got so unstable I had to switch ISP, something I really do NOT want to do because IDnet's service overall has been incredibly top notch. However given I raid and do all the endgame stuff, an unstable connection is a killer, and not something I can tolerate.

Nova

Niall

I saw those problems with Nildram a while ago too, but that was Telia, not Nildrams fault. I'm currently seeing the same thing on Hellscream (my mate is paying for the account and I occasionally log in to see what's new; nothing :D).

There's a kind of intermittent lag on there, and I've also been losing connection to realms when using portals/teleports. You can hear the sound load instantly, then it hangs as it hasn't loaded the area from the server. I gave up in the end.

My downloads are fine, and I don't really play online games anymore other than that, so I couldn't tell you if it's across the board.
Flickr Deviant art
Art is not a handicraft, it is the transmission of feeling the artist has experienced.
Leo Tolstoy

Sebby

I'm not a gamer and so I never look at pings. What I'd suggest is you send support an email with the tracert and they can investigate, whoever might be at fault. :)

Nova

Quote from: Niall on May 07, 2008, 20:57:25
I saw those problems with Nildram a while ago too, but that was Telia, not Nildrams fault. I'm currently seeing the same thing on Hellscream (my mate is paying for the account and I occasionally log in to see what's new; nothing :D).

There's a kind of intermittent lag on there, and I've also been losing connection to realms when using portals/teleports. You can hear the sound load instantly, then it hangs as it hasn't loaded the area from the server. I gave up in the end.

My downloads are fine, and I don't really play online games anymore other than that, so I couldn't tell you if it's across the board.

Mm, I'm pretty certain it was one of the peering points or bridges that went to pot, but Nildram could never sort it out and thus they lost a mass of customers because WoW, like or not, is the most popular game about at present. But if the same issues crop up here, then one has to start looking at the hops up to the blizzard firewall (hop 11 comes back blank) and try to figure out which one is going screwy.

Nova

Rik

As Sebby says, collect some traces and let IDNet have them. I've known them change their routing to get round this sort of issue on an external network.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nova

Hm.. been testing addons and just about everything else, but it seems like when the connection is stressed in any way on warcraft (through raids and such) it just collapses. It's been fine up to three weeks ago or so, not sure what's changed.

Nova

netn00b

i have to agree Nova.

ever since idnet had the 'saturday afternoon' problem some weeks ago the pings / lag has been getting steadily worse.

since today's issues i'm basically unable to play at all and keep getting d/c. 

Lance

#7
Welcome to the forum, netn00b! Have a welcome karma!

Could you both post some pings and tracerts please?

netn00b - you say you are getting disconnects. Is that from the game server or the whole internet? Todays issues would only effect you if you had to 'log on' to your broadband (ie reboot the router or if you use a modem). They would not affect general stability or pings.

edit: here are my pings to idnet with interleaving on...

C:\Users\Lance>ping idnet.net -n 10

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 35ms, Average = 29ms
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

netn00b

thanks lance.

well i get bad lag on warcraft.  then if its really bad it disconnects me and i simply re log into the game.

so not sure precisely about 'the whole internet'...

my router is only on when we're using the net, and turned off at all other times.

today i had rebooted router 15 times ?  to no effect.

i then had to call idnet who got me to change my router settings from gw5 to dsl4 if that means anything to anyone....

will try ping and tracert when i work out how to run them and save and paste them here !

Lance

By the whole internet, I simply meant your connection. The chances are that from what you say it is only the server disconnecting you.

With a router, I would normally recommend that you leave it on 24/7, with the exception being if there are thunderstorms nearby or if you are going away. This should offer better stability.

Changing from gw5 to dsl4 is the way you get routed through to IDNet, and relates more to the physical way things are routed. Sometimes one realm can perform better than others, but I suspect that they tried changing it to see if that would get the BT servers to wake up and log you in.

To run a ping and tracert, go to Start | Run and then type cmd -in the command prompt which comes up, type ping (or tracert) followed by the ip address of the game server you are trying to play on. You can copy the output by right clicking and selecting Mark and then highlighting the area you want to copy. Once you have highlighted press the enter key and then you can paste it into the reply box in the normal way.

Hope this helps.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Welcome, netn00b. :karma:

I would recommend letting IDNet know about these problems. This is something that isn't going to be to do with your setup, and if they're not informed, they can't look into the issue. :)

Lance

But it could be the server he is playing on, hence asking for the tracerts and pings!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

It could be, and IDNet will be able to confirm either way. :)

Rik

That's the first time I've seen someone moved from GW5 to DSL4...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nova

These are the EU blizzard WoW datacenters and their appropriate IP ranges:

* Frankfurt: 80.239.232.x, 80.239.233.x
* Frankfurt 2: 80.239.148.x, 80.239.149.x
* Paris: 80.239.178.x, 80.239.179.x
* Paris 2: 80.239.181.x
* Paris 3: 80.239.184.x, 80.239.185.x
* Hamburg: 213.248.122.x, 213.248.123.x

If netnoob's one is on the Paris datacenter (like mine) , we might have our first clue as to what the issue is.

Nova

Rik

Which Paris centre are you on, Nova, or can it be any of them. As Paris is a peering point for IDNet, it may well be a good clue.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nova


shazzy

It's probably Telia.  Always had problems when peered through Telia as far as games or mmorpgs are concerned.


Niall

This problem has mysteriously cleared up about 2 days ago for me. Now I don't have the freezing problem, and nothing at my end has changed :)
Flickr Deviant art
Art is not a handicraft, it is the transmission of feeling the artist has experienced.
Leo Tolstoy

netn00b

Quote from: Rik on May 15, 2008, 08:32:39
That's the first time I've seen someone moved from GW5 to DSL4...
does this mean something good or bad as to why i was moved ?



still getting wow problems.  it was at the point yesterday that every few minutes i would momentarily freeze for 1/2 seconds before continuing moving.

i will try to find out which of the wow datacentres i am linking to and try a tracert.


Rik

Neither, really. The older accounts are on the DSL4 realm, the new ones are on GW5. I'm sure the switch was made just to eliminate any possibility of an issue within IDNet. I can actually login in on either realm but have never noticed a difference, tbh.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

netn00b

if i change the details back in the router login/settings screen will it still work ?

cos checking wow out just now at lunchtime i am finiding the lag and 1/2 sec freezes are worse than ever :(

Rik

Probably, it depends whether they moved you or, as in my case, gave you access rights on both realms (it allows me to check if an issue is reported here).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

netn00b

#23
from looking it appears i'm connecting to 80.239.185.37.


ran a tracert....

Tracing route to 80-239-185-37.customer.teliacarrier.com [80.239.185.37]
over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  192.168.0.1
  2    33 ms    33 ms    32 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3     *       33 ms    32 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    33 ms    35 ms    35 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    34 ms     *       39 ms  ae-12-55.car2.London1.Level3.net [4.68.116.144]

  6    34 ms    33 ms    36 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    35 ms    35 ms    35 ms  ldn-bb2-link.telia.net [80.91.250.238]
  8    72 ms    70 ms    68 ms  prs-bb2-link.telia.net [80.91.254.211]
  9    68 ms    72 ms    74 ms  prs-b1-link.telia.net [80.91.250.253]
10    43 ms    43 ms    41 ms  prs-rosy-s50.telia.net [80.91.251.90]
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.


netn00b

that was with wow closed down btw.....