Tele2 - Connection issues

From reports received back from our Network team and Partners, who have informed us that they have been closely monitoring traffic since work was completed on the 14th of October. They have been unable to identify any specific network issues, which would connect the recent reports made in the following thread with the original reported issue:

http://forums.wow-europe.com/thread.html?topicId=6104970537&sid=1

Following the last few pages of that thread it has become difficult to continue to collect information that would be helpful to any ongoing investigation. For that reason we would request that players who are still reporting latency or general connection problems specific to the previously reported thread, to use this newly created thread to provide us with the following requested information.

We will need the information generated from the following commands (Tracert and pathping):

When you are playing the game, press Alt Tab, You may want to switch to windowed mode to make it easier to get back to the desktop.

- Click the Start button and select the Run option from the menu
- Type in cmd in the command text box then press Enter.
- Type the following into the command window that appears: netstat -n -p tcp -b | more
you will see a line like this one (depending on World Of Warcraft):

TCP XXX.XX.XX.XX:XXXX YY.YYY.YYY.YY:3724 ESTABLISHED 4476 [WoW.exe]

The IP address that is indicated by Xs is your IP address, this is not needed, so do not post this.

The information that is important however is the one indicated by Y's on the example above, this is the IP address of the server you are playing on.

Now we need some information on your connection, in the same command window, type in:

tracert YY.YYY.YYY.YY > C:\tracert.txt

Once that file has finished and saved itself to the harddisk, we will now need to run the PathPing command.

The steps are quite similar and we will be using the same IP address that we discovered earlier. With the command window open, type the following

pathping YY.YYY.YYY.YY > C:\pathping.txt

Once you have produced both files , copy and paste the contents of the tracert.txt and pathping.txt into this thread so we can further troubleshoot this matter.

Q u o t e:

2 days ago I got a call from Tele2 stating that they couldn't find anything at their end. What worries me is that the guy also said that they basically got no response to their questions directed to Blizzard.

He also confirmed that Tele2 didn't change anything for those few days when it actually was working. (Because they were still waiting for response from Blizzard)

Please get back to Tele2 with whatever info they need! And also try to figure out why it works when connecting via hidden24.com

The fact that it's basically impossible to get through to Billing Support via phone trying to get a free character transfer to a working realm doesn't really much either. :-(

That would be interesting, if they got no response from Blizzard where they in direct contact with our network team and partners if they had any questions regarding the reported issues.

It should be noted that the initial issue that was reported a few weeks ago was solved, if there are still issues then, these issues are not likely related or are a completely new issue.

Once again as I mentioned in my first post, out network team and partners can see nothing that would explain the issues reported.

Q u o t e:


Have you taken into concideration that we are able to play with VPN services like Hidden24.com ?

Something is wrong with the traffic from Tele 2 ISP -> ...xxx.. -> Blizz servers
Where Tele 2 ISP -> VPN -> ..xxx.. -> Blizz servers works..

That would be because your using alternate routing outside that which your provider gives, Blizzard does not have any control over this routing.

Q u o t e:
Talked to Tele2 again now and they are getting more and more phone calls about this problem, they still say the problem is on Blizzards side because all tracerts time out right after they leave the Tele2 servers and connects to Blizzard. I was thinking about calling Blizz support but I have a feeling they will say it's not their fault either...

Q u o t e:
10 34 ms 35 ms 35 ms ffm-bb1-link.telia.net [213.248.64.42]
11 41 ms 42 ms 42 ms prs-bb1-link.telia.net [80.91.248.69]
12 46 ms 45 ms 45 ms prs-b4-link.telia.net [213.248.65.222]
13 51 ms 46 ms 50 ms prs-nant-ks51-link.telia.net [80.91.249.66]

It is perfectly normal that the traceroute will end at the 13th hop (using the traceroute posted after your post). For security reasons all data from that point on is blocked.

Q u o t e:
problem is at blizzard partner telia, just ask them to fix the problem again, like last time..

There are no problems with our partners this has been checked and verified on more than one occasion. These reported issues are not down to any part of the network or hardware within our control.

Q u o t e:
Another traceroute that i got yesterday when talking whit the Tele2 techsupport.



Sp†rar v„g till eu.argentdawn.com [208.112.127.100]

”ver h”gst 30 hopp:



1 <10 ms <10 ms <10 ms

2 33 ms 7 ms 25 ms c213-100-104-1.swipnet.se [213.100.104.1]

3 35 ms 45 ms 48 ms vst90.vlan990.swip.net [130.244.32.145]

4 21 ms 38 ms 24 ms vst-core-1.gigabiteth1-1s20.swip.net [130.244.205.209]

5 30 ms 51 ms 30 ms vst-core-2.pos4-0.swip.net [130.244.39.46]

6 16 ms 13 ms 39 ms lba2-core-1.pos3-3.swip.net [130.244.194.9]

7 38 ms 45 ms 36 ms bck-core-1.pos5-0-0.swip.net [130.244.218.162]

8 27 ms 38 ms 48 ms gbg-core-1.gigabiteth5-0-0.swip.net [130.244.218.181]

9 56 ms 33 ms 61 ms ams17-core-1.pos6-0-0.swip.net [130.244.205.150]

10 51 ms 54 ms 76 ms ams16-core-1.gigabiteth4-0-0.swip.net [130.244.205.165]

11 34 ms 46 ms 50 ms TenGE13-2.br02.ams01.pccwbtn.net [195.69.145.37]

12 120 ms 123 ms 121 ms safesecureweb.ge2-6.br01.phl02.pccwbtn.net [63.218.31.2]

13 170 ms 201 ms 257 ms ded2.dc3.hostmysite.net [67.59.145.10]

14 139 ms 121 ms 130 ms eu.argentdawn.com [208.112.127.100]



Sp†rning utf”rd.

getting big latency at jump 12

Your not tracing to a valid Blizzard IP address, eu.argentdawn.com is not going to run a trace route to Argent Dawn.

http://www.all-nettools.com/toolbox/smart-whois.php

208.112.127.100
208.112.0.0 - 208.112.127.255
HostMySite
650 Pencader Drive
Newark, DE
US

Q u o t e:


Stop focusing on details and solve the frickin problem already. You have lots of threads with numerous trace routes, start using them and act like you get payed.. (Not targeted to you personally. Atleast you post us answers which is more then anyone else at Blizz is doing. Or so it seems.)

I will focus on details if the information posted is wrong, That is part of my job.

Q u o t e:
A week or so ago technical support advised me to contact billing support to check for the possibility to get a free transfer to a server that works. After a couple of days trying to get through to billing support I finally succeeded... only to find out the only way to get a free transfer to a working realm is to nag in the forums. So here it is:

PLEASE GIVE US THE POSSIBILITY TO TRANSFER OUR CHARACTERS TO WORKING REALMS WHILE YOU SORT THIS OUT!!!

It should be free and we shouldn't suffer any cooldowns because when you have managed to solve this we want to get back to our friends and play with them.

Free transfers are only ever offered on realms that have a persistently high player population, transfers are offered to elevate the queues, they are not offered for any other reasons.

Once again, our network team and partners have found no issues within our network, that would explain the reports we have seen on the forums.

Hi,

Where still actively investigating all reports, though we are not seeing as many contacts about this as we where a few weeks ago.

Feedback from out network team and partners, who are in contact with Tele2 mention that some changes have been made that should have improved the situation.

If your still reporting latency/connection problems then please continue to post all the required information to further help those investigations.

Q u o t e:
Guys stop posting tracerts, they show absolutely nothing out of the ordinary.

To the contrary, tracerts and pathping results are very helpful no matter if they show no obvious issues. Please continue to provide the information requested.

Hi Tillian,

Posting e-mails you have received from a Blizzard employee is against the forum rules, I have edited your post to remove it.

Note that if you have any questions about that e-mail, that you should reply back for further assistance.

Splithoof -- Try providing more information about your connection, I'm unable to find any information posted by this character.

http://forums.wow-europe.com/thread.html?topicId=6425543892&sid=1&pageNo=1#0

Q u o t e:
I'm starting to consider this my daily quest. Can I get goldz for it?

TRACERT:
Sp†rar v„g till 80-239-181-79.customer.teliacarrier.com [80.239.181.79]
”ver h”gst 30 hopp:
1 <10 ms <10 ms <10 ms vood.lan [192.168.1.1]
2 563 ms 714 ms 647 ms c213-100-198-1.swipnet.se [213.100.198.1]
3 649 ms 682 ms 652 ms kst80.ge1-2s507.swip.net [130.244.29.237]
4 397 ms 294 ms 376 ms kst-ncore-2.gigabiteth1-1.swip.net [130.244.206.73]
5 515 ms 435 ms 369 ms avk-ncore-2.tengigabiteth2-1.swip.net [130.244.52.114]
6 690 ms 722 ms 745 ms avk-ncore-1.tengigabiteth2-2.swip.net [130.244.52.118]
7 466 ms 483 ms 567 ms avk-core-1.gigabiteth9-0-0.swip.net [130.244.52.121]
8 587 ms 588 ms 714 ms s-b1-link.telia.net [213.248.101.121]
9 646 ms 656 ms 676 ms s-bb2-link.telia.net [80.91.252.126]
10 639 ms 762 ms 641 ms ffm-bb2-link.telia.net [80.91.251.147]
11 754 ms 801 ms 764 ms prs-bb2-link.telia.net [80.91.249.47]
12 766 ms 791 ms 757 ms prs-b4-link.telia.net [213.248.65.226]
13 831 ms 427 ms 352 ms prs-nant-ks51-link.telia.net [80.91.249.66]
14 * * * Beg„ran gjorde timeout.
15 * * * Beg„ran gjorde timeout.
16 * * * Beg„ran gjorde timeout.
17 * * * Beg„ran gjorde timeout.
18 * * * Beg„ran gjorde timeout.
19 * * * Beg„ran gjorde timeout.
20 * * * Beg„ran gjorde timeout.
21 * * * Beg„ran gjorde timeout.
22 * * * Beg„ran gjorde timeout.
23 * * * Beg„ran gjorde timeout.
24 * * * Beg„ran gjorde timeout.
25 * * * Beg„ran gjorde timeout.
26 * * * Beg„ran gjorde timeout.
27 * * * Beg„ran gjorde timeout.
28 * * * Beg„ran gjorde timeout.
29 * * * Beg„ran gjorde timeout.
30 * * * Beg„ran gjorde timeout.
Sp†rning utf”rd.

PATHPING:
Sp†rar v„g till 80-239-181-79.customer.teliacarrier.com [80.239.181.79]
”ver h”gst 30 hopp:
0 blinken [192.168.1.2]
1 vood.lan [192.168.1.1]
2 c213-100-198-1.swipnet.se [213.100.198.1]
3 kst80.ge1-2s507.swip.net [130.244.29.237]
4 kst-ncore-2.gigabiteth1-1.swip.net [130.244.206.73]
5 avk-ncore-2.tengigabiteth2-1.swip.net [130.244.52.114]
6 avk-ncore-1.tengigabiteth2-2.swip.net [130.244.52.118]
7 avk-core-1.gigabiteth9-0-0.swip.net [130.244.52.121]
8 s-b1-link.telia.net [213.248.101.121]
9 s-bb2-link.telia.net [80.91.252.126]
10 ffm-bb2-link.telia.net [80.91.251.147]
11 prs-bb2-link.telia.net [80.91.248.61]
12 prs-b4-link.telia.net [213.248.65.226]
13 prs-nant-ks51-link.telia.net [80.91.249.66]
14 * * *
Statistik f”r 350 sekunder ber„knas...
K„lla hit Denna nod/l„nk
Hopp Tid f”rl/skic= % f”rl/skic= % Adress
0 blinken [192.168.1.2]
0/ 100 = 0 % |
1 0 ms 0/ 100 = 0 % 0/ 100 = 0 % vood.lan [192.168.1.1]
0/ 100 = 0 % |
2 572 ms 0/ 100 = 0 % 0/ 100 = 0 % c213-100-198-1.swipnet.se [213.100.198.1]
0/ 100 = 0 % |
3 611 ms 2/ 100 = 2 % 2/ 100 = 2 % kst80.ge1-2s507.swip.net [130.244.29.237]
0/ 100 = 0 % |
4 617 ms 1/ 100 = 1 % 1/ 100 = 1 % kst-ncore-2.gigabiteth1-1.swip.net [130.244.206.73]
0/ 100 = 0 % |
5 620 ms 0/ 100 = 0 % 0/ 100 = 0 % avk-ncore-2.tengigabiteth2-1.swip.net [130.244.52.114]
0/ 100 = 0 % |
6 620 ms 0/ 100 = 0 % 0/ 100 = 0 % avk-ncore-1.tengigabiteth2-2.swip.net [130.244.52.118]
0/ 100 = 0 % |
7 609 ms 3/ 100 = 3 % 3/ 100 = 3 % avk-core-1.gigabiteth9-0-0.swip.net [130.244.52.121]
0/ 100 = 0 % |
8 617 ms 0/ 100 = 0 % 0/ 100 = 0 % s-b1-link.telia.net [213.248.101.121]
0/ 100 = 0 % |
9 627 ms 1/ 100 = 1 % 1/ 100 = 1 % s-bb2-link.telia.net [80.91.252.126]
0/ 100 = 0 % |
10 647 ms 1/ 100 = 1 % 1/ 100 = 1 % ffm-bb2-link.telia.net [80.91.251.147]
0/ 100 = 0 % |
11 644 ms 0/ 100 = 0 % 0/ 100 = 0 % prs-bb2-link.telia.net [80.91.248.61]
100/ 100 =100 % |
12 --- 100/ 100 =100 % 0/ 100 = 0 % prs-b4-link.telia.net [213.248.65.226]
0/ 100 = 0 % |
13 --- 100/ 100 =100 % 0/ 100 = 0 % prs-nant-ks51-link.telia.net [80.91.249.66]
0/ 100 = 0 % |
14 --- 100/ 100 =100 % 0/ 100 = 0 % blinken [0.0.0.0]
Sp†rning utf”rd.

Your traceroute looks a little broken, could you try rebooting your modem/router and try and perform the tracert again.

Hi,

I am going to lock this thread, to avoid it been dragged upto the top since the issue at hand has since been resolved.

If you are encountering high latency then please use our weekly latency thread, else create a new thread detailing your problem.