Entanet users and WoW

Paste the complete output when you try to ping that domain - is your machine at least getting as far as resolving the name to an IP, or is it the DNS request that's timing out?

Teki187 said:
Can a router firmware upgrade break port forwarding?
Click to expand...

It could, but unless you're running a server you don't need to forward ports for WoW.

traceroute and ping packets
Click to expand...

There's no such thing - they both use ICMP.
 
tolien said:
Paste the complete output when you try to ping that domain - is your machine at least getting as far as resolving the name to an IP, or is it the DNS request that's timing out?



It could, but unless you're running a server you don't need to forward ports for WoW.



There's no such thing - they both use ICMP.
Click to expand...

Hey, thanks for replying.

Pinging eu.logon.worldofwarcraft.com [80.239.178.113] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.239.178.113:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

---------------------------------------------------------------

Tracing route to eu.logon.worldofwarcraft.com [80.239.178.113]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 50 ms 22 ms 25 ms spruce.dsl.enta.net [84.45.242.72]
3 22 ms 23 ms 23 ms vlan4001.global-switch.dsl.enta.net [84.45.242.6
5]
4 23 ms 24 ms 23 ms gi3-8.telehouse-east.dsl.enta.net [84.45.242.50]

5 23 ms 23 ms 23 ms te5-2.telehouse-east.core.enta.net [62.249.192.1
21]
6 23 ms 24 ms 23 ms te5-1.telecity-hex.core.enta.net [87.127.236.102
]
7 22 ms 24 ms 23 ms ldn-tch-i2-link.telia.net [213.248.84.109]
8 23 ms 24 ms 23 ms ldn-tch-i1-link.telia.net [80.91.250.217]
9 24 ms 23 ms 23 ms ldn-b1-link.telia.net [80.91.250.209]
10 24 ms 23 ms 25 ms ldn-bb1-link.telia.net [80.91.248.90]
11 30 ms 30 ms 31 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
12 32 ms 31 ms 31 ms prs-b1-link.telia.net [80.91.250.253]
13 32 ms 31 ms 31 ms prs-tc-i1-link-telia.net [80.91.250.30]
14 * * * Request timed out.

14-30 hops is the same.
 
I believe it is normal for it to timeout at this point, check the wow forums it is explained on there, i would post there for support and see if there is any issues.
 
I think we have concluded that other providers are having issues with WOW and pluging into the modem is not going to help matters.
 
Macca said:
I believe it is normal for it to timeout at this point, check the wow forums it is explained on there, i would post there for support and see if there is any issues.
Click to expand...

I've already contacted them and they tell me to email tech support which i did 5 days ago. No reply.

I'm not connected wireless, im already directly into the router.

Other people are also having issues the same as me.

I just want to make sure its no my router.
 
I know at least one use entanet user (UKFSN) who has no problems playing WoW and your tracert looks fine - yes it times out after hop 14 but that's because subsequent hops don't respond to ping requests.

Do an ipconfig /flushdns and see if that makes any difference.
 
Fixed it.

Basically the service rules on my router where blocking everything wow after i upgraded the firmware.

After i deleted them, i loaded up wow fine.
 
You must log in or register to reply here.
Back
Top Bottom