Dameize said:
randomnumbershere.customer.teliacarrier.com: portnumber
This is just a temporary DNS label your ISP attaches to your router/modem when it assigns you an IP address. I'm not sure what you are looking at, it could be something called Network Address Translation that the router is doing for your WoWclient.
To try to isolate the problem...
Go
here for US, or
here for EU. Find the IP address of your WoW server. If yours isn't listed, you'll have to do some Googling to find it.
Then
* open up a shell: Start -> Run -> "cmd.exe"
* type "tracert YOUR_WOW_SERVERS_IP_ADDRESS" into the command window
* You will get back output that looks like the following
C:\>tracert 1.2.3.4
Tracing route to 1.2.3.4 over a maximum of 30 hops
1 1 ms 1 ms 1 ms CampusFW.localnet [192.168.1.3]
2 9 ms 7 ms 7 ms somegateway.com
3 8 ms 9 ms 7 ms mumblefoo.com
4 9 ms 9 ms 9 ms 96-45.mumblety.com
5 9 ms 9 ms 10 ms edr.hughesnet.com
6 9 ms 9 ms 9 ms 1-5-4-65.rogers.com
7 10 ms 9 ms 9 ms bbn.butterfly.com
8 39 ms 9 ms 10 ms 6-1-0.edge.denmark.net
9 10 ms 9 ms 10 ms 4-90.edge2.london.net
10 11 ms 11 ms 9 ms edg3-90.nyny.com
11 48 ms 49 ms 51 ms cr2.att.net
12 49 ms 51 ms 51 ms cr1.verizon.net
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * ^C
What you get back is a hop count in the first column, and the round-trip time are the next three columns (it takes three samples and shows each to you discretely), and the name of the machine it is communicating with. As you can see in this phony example, the jump to the AT&T network injects considerably more delay in Hop 11.
At some point you will start seeing 'Request timed out'. This is because your packet has finally hit the Bliz network, and they will not allow the 'traceroute' command through. It can be a security problem, because people can discover things about your network that they shouldn't know. When you start to see '*' in the lines, just hit Control-C to stop the 'traceroute', you've got everything you need to know--Bliz isn't going to be the cause of your lag.
You should see <15ms or so for the first 5-10 hops, then it may jump up to 50-70ms range. If you see 100s of milliseconds, there's where your problem starts.
My guess is your going to have a significant delay before even getting through your local router (Hop1, the CampusFW in the phony example). This means the problem is being caused by some machine (maybe not the one running your WoWclient/HB setup), inside your house. If that is the case, you'll have to figure that out for yourself if your router is incapable of showing statistics.
Analyzing network traffic is not easy to do. There are heavy-duty, open source tools that will look at every packet that crosses the network like
Wireshark. I suggest you go do a lot of reading and Googling to pursue your problem. This is the wrong forum to be discussing this type of thing. Instead, try
DSLReports--that's what they live for.
cheers,
CJ