WoW #114 Error

Technical Support
Prev 1 2 3 4 10 Next
ISP: Telstra
Router: Technicolor TG587n v3
OS: Win8 x64
Server: Barthilas, Bloodlust (12.129.209.68)
C:\Users\Ben>tracert 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 18 ms 98 ms 99 ms 10.0.0.138
2 20 ms 19 ms 19 ms 172.18.112.65
3 21 ms 22 ms 21 ms 172.18.93.138
4 20 ms 21 ms 23 ms 172.18.239.101
5 24 ms 22 ms 23 ms bundle-ether10.ken39.sydney.telstra.net [203.45.
17.17]
6 25 ms 22 ms 23 ms bundle-ether6.ken-core4.sydney.telstra.net [203.
50.6.145]
7 29 ms 23 ms 23 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50
.6.29]
8 27 ms 19 ms 20 ms tengigabitethernet2-0.sydp-core02.sydney.reach.c
om [203.50.13.50]
9 157 ms 158 ms 157 ms i-0-4-0-0.paix-core01.bx.telstraglobal.net [202.
84.140.37]
10 157 ms 158 ms 157 ms i-0-0-0-0.paix02.bi.telstraglobal.net [202.84.25
1.70]
11 159 ms 160 ms 161 ms 206.24.240.149
12 192 ms 192 ms 192 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.2
00.197]
13 191 ms 191 ms 191 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.2
03.22]
14 173 ms 172 ms 171 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
15 172 ms 174 ms 173 ms cr1.sffca.ip.att.net [12.122.137.122]
16 181 ms 178 ms 177 ms cr1.la2ca.ip.att.net [12.122.3.122]
17 170 ms 170 ms 170 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 170 ms 170 ms 170 ms 12-122-254-234.attens.net [12.122.254.234]
19 171 ms 172 ms 171 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
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.

Trace complete.


Yahoo for comparison
C:\Users\Ben>tracert yahoo.com

Tracing route to yahoo.com [206.190.36.45]
over a maximum of 30 hops:

1 52 ms 98 ms 98 ms 10.0.0.138
2 20 ms 26 ms 20 ms 172.18.112.65
3 19 ms 20 ms 19 ms 172.18.93.138
4 29 ms 22 ms 23 ms 172.18.239.101
5 26 ms 23 ms 23 ms bundle-ether10.ken39.sydney.telstra.net [203.45.
17.17]
6 29 ms 23 ms 23 ms bundle-ether6.ken-core4.sydney.telstra.net [203.
50.6.145]
7 21 ms 22 ms 19 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50
.6.29]
8 33 ms 20 ms 20 ms 203.50.13.114
9 157 ms 165 ms 157 ms i-0-1-0-0.paix-core01.bx.telstraglobal.net [202.
84.140.117]
10 158 ms 159 ms 159 ms i-0-0-0-2.paix02.bi.telstraglobal.net [202.84.25
1.101]
11 * * * Request timed out.
12 183 ms 183 ms 183 ms ae-7.pat2.dnx.yahoo.com [216.115.96.115]
13 195 ms 228 ms 214 ms ae-5.pat2.gqb.yahoo.com [216.115.101.197]
14 258 ms 259 ms 245 ms ae-1.msr2.gq1.yahoo.com [66.196.67.3]
15 229 ms 230 ms 229 ms xe-5-0-0.clr2-a-gdc.gq1.yahoo.com [67.195.0.23]

16 184 ms 181 ms 194 ms et-18-25.fab2-1-gdc.gq1.yahoo.com [98.137.31.170
]
17 216 ms 231 ms 216 ms po-13.bas1-7-prd.gq1.yahoo.com [206.190.32.21]
18 243 ms 196 ms 243 ms ir1.fp.vip.gq1.yahoo.com [206.190.36.45]

Trace complete.


Troubleshooting performed:
Repaired WoW
Deleted Blizzard Entertainment folder from C:\ProgramData
Reset modem to default settings + released/renewed + flushed DNS cache
Sacrificed a goat
Entered Google DNS servers into Win8 LAN adapter settings + released/renewed + flushed DNS cache
Removed B.net authenticator from account

Note:

This is affecting both SC2 and WoW on my PC.
My wife is able to connect to WoW on Barth on her Macbook
sigh ... this happened last time and had to wait for a few days ... tried all of the above to no prevail .. need this to be fixed please .. i rang my isp and there is no problems with my connection it has been tested etc ..

my stepson plays on the laptop with same connection but wireless and he has no problems .. so i cant see how this is isp ><
same issue with me, when will it be fixed?
Same here, added Authenticator today and can no longer log on due to 114.
Having the same issue - no fixes (DNS changes/flushing, cache deletion, running as admin etc) are working.
First attempt to play after adding authenticator.
My mum can access her's just fine. Same location, Same ISP (same internet account), Same server.
DNS change dont work for me, as well as deleting folders, run in 32bit. is a new computer and using the same ISP, i can log on from my old laptop which i have been playing on for quite a while.
bump, tf goin on up in here
ISP: Telstra
Location: Australia, Brisbane
Realm: Jubei'thos 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 22 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 25 ms 23 ms 23 ms 172.18.213.11
3 24 ms 23 ms 23 ms 172.18.70.142
4 33 ms 34 ms 23 ms 172.18.241.233
5 25 ms 33 ms 24 ms bundle-ether10.cha47.brisbane.telstra.net [110.142.226.9]
6 25 ms 26 ms 23 ms bundle-ether4.cha-core4.brisbane.telstra.net [203.50.11.50]
7 39 ms 47 ms 46 ms bundle-ether11.ken-core4.sydney.telstra.net [203.50.11.72]
8 46 ms 47 ms 47 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 38 ms 37 ms 38 ms tengigabitethernet0-x.sydp-core02.sydney.reach.com [203.50.13.70]
10 177 ms 175 ms 176 ms i-0-4-2-0.paix-core01.bx.telstraglobal.net [202.84.140.157]
11 181 ms 179 ms 177 ms i-0-0-0-1.paix02.bi.telstraglobal.net [202.84.251.74]
12 180 ms 179 ms 179 ms 206.24.240.149
13 227 ms 264 ms 225 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 211 ms 210 ms 210 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 195 ms 196 ms 194 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 197 ms 193 ms 192 ms cr1.sffca.ip.att.net [12.122.137.126]
17 191 ms 190 ms 192 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 188 ms 187 ms 187 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 197 ms 190 ms 190 ms 12-122-254-238.attens.net [12.122.254.238]
20 197 ms 196 ms 196 ms 12.129.193.254
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.

Trace complete.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.1.254
2 14 ms 13 ms 14 ms lo5000.bras6.adl1.adnap.net.au [122.49.191.20]
3 13 ms 13 ms 13 ms g3-16.cor1.adl1.adnap.net.au [219.90.143.193]
4 13 ms 13 ms 14 ms te4-1.cor2.adl1.adnap.net.au [219.90.143.246]
5 14 ms 13 ms 13 ms vlan444.o5rxc76f000.optus.net.au [59.154.56.1]
6 193 ms 193 ms 192 ms 67.17.192.141
7 198 ms 198 ms 201 ms 192.205.34.65
8 199 ms 199 ms 199 ms cr1.la2ca.ip.att.net [12.122.128.98]
9 193 ms 193 ms 193 ms gar20.la2ca.ip.att.net [12.122.128.181]
10 195 ms 195 ms 194 ms 12-122-254-238.attens.net [12.122.254.238]
11 198 ms 198 ms 198 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
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.

Trace complete.

Have tried all the work arounds but no change.

Problem has come after I formatted computer and re-installed WoW. It was fine before I did that. We have 2 other computers here running WoW (different account to me) through the same internet and have no problems with either of those. Can even log into my account on them but keep getting the 114 error when I try on this computer.
same here ~

but i can play on Puplic Test Server and Starter Edition..... ??!?!?!?!?!?

there is no problem in Puplic Test Server and Starter Edition.

problem of route ???
ISP: OptusNet
Location: Australia, Sydney
Realm: Frostmourne (Battlegroup Bloodlust 12.129.209.68)

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 2 ms 1 ms 2 ms c211-30-101-185.rivrw2.nsw.optusnet.com.au [211.30.101.185]
2 36 ms 34 ms 32 ms 10.63.0.1
3 23 ms 17 ms 26 ms riv3-ge4-0-1.gw.optusnet.com.au [198.142.192.25]
4 45 ms 40 ms 23 ms mas3-ge2-0.gw.optusnet.com.au [211.29.126.105]
5 171 ms 171 ms 173 ms 203.208.174.85
6 167 ms 198 ms 167 ms xe-3-1-0.lax30.ip4.tinet.net [216.221.157.149]
7 169 ms 167 ms 162 ms as7018.lax30.ip4.tinet.net [77.67.79.174]
8 186 ms 180 ms 195 ms cr2.la2ca.ip.att.net [12.123.30.190]
9 179 ms 174 ms 319 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 198 ms 212 ms 186 ms 12.122.251.190
11 165 ms 164 ms 167 ms 206.16.68.46
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.

Trace complete.
Doing what blue post said about the DNS change worked for me.
Essentially, anyone that has installed something relative to WoW gets this error.

Many people (like myself) have just finished installing the game and when they try log on, get the #114 Error. Funny enough, its also only subject to those in the oceanic region; Australia, New Zealand, Indonesia, Singapore, Malaysia.

I have also tried installing through original discs. Did not work either.

Though there are 'work arounds', I do not have the energy or drive to change all of my computers settings. Blizzard should assure that the standard issued programs like the launcher should work properly without having the user change and waste time on 'work arounds'.
Well I just got the game back after a few months break and waited around 4 - 5 hours to transfer the game from my friends computer (works perfectly on his laptop) and than I try on my PC and it doesn't work? Go figure? Has anyone seen any blue posts on ho to fix this without messing around with your DNS or any ETA on the fixes?
*ISP - Pakistan Telecommunication Company Limited (PTCL)
*Location - Pakistan, Lahore
*Realm connect to - Darkspear
*tracer route -
1 192.168.0.1 (192.168.0.1) 29.369 ms 0.785 ms 0.719 ms
2 * * *
3 10.0.235.22 (10.0.235.22) 128.568 ms 1083.198 ms 1128.048 ms
4 182.184.23.97 (182.184.23.97) 972.102 ms 739.754 ms 467.764 ms
5 10.1.1.10 (10.1.1.10) 245.170 ms 612.059 ms 1127.048 ms
6 203.99.170.145 (203.99.170.145) 688.113 ms 1671.700 ms 1191.949 ms
7 static-10ge-khi275-po1-pe01.pie.net.pk (221.120.251.157) 944.064 ms 1104.763 ms 819.872 ms
8 static.khi77.pie.net.pk (202.125.128.170) 936.053 ms 583.543 ms 496.697 ms
9 * *
ISP: iprimus
Location: Australia, Barongarook, Victoria
Realm: Dath'Remar

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 13 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 31 ms 31 ms 30 ms 77.178.dsl.mel.iprimus.net.au [202.138.4.77]
3 32 ms 31 ms 31 ms mel0111.mel.iprimus.net.au [203.134.26.150]
4 31 ms 31 ms 31 ms 51.123-134-203.network.mel.iprimus.net.au [203.134.123.51]
5 44 ms 43 ms 43 ms xe-0-2-0.csr01.equ.iprimus.net.au [203.134.2.229]
6 44 ms 42 ms 43 ms irb-4.bsr01.equ.iprimus.net.au [203.134.67.163]
7 181 ms 180 ms 180 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138]
8 184 ms 217 ms 182 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
9 183 ms 183 ms 183 ms as7018.ip4.tinet.net [77.67.78.94]
10 200 ms 199 ms 200 ms cr1.sffca.ip.att.net [12.122.86.198]
11 204 ms 198 ms 199 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 196 ms 249 ms 195 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 197 ms 197 ms 196 ms 12-122-254-234.attens.net [12.122.254.234]
14 368 ms 207 ms 208 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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
Internode, vic, aus.
new os (windows 8), fresh wow install, error 114 - can log in other computers on same network and access wow - no issues - just the new one doesn't want to know. It has spent over 24 hours now downloading "patch" and says is playable.................
It was working perfectly until got windows 8 so am not sure if on our end in the settings somewhere or on blizz end / isp problem - lets connect on this computer just fine, but nothing has been changed on this one.
Hmm i got it working.

I changed both my IP4 and IP6
IPV4- 8.8.8.8/4.4.4.4
IPV6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844

Then went into CMD and ran a release/renew and a dns flush..

Press windows "R" and then type in "cmd" in the run.exe box

In the command prompt type in the below
ipconfig /release
ipconfig /renew
ipconfig /flushdns

try wow now.. worked for me


Thankyou so much Letthiswork!

I followed your instructions exactly and in addition deleted:

C:\ProgramData\Battle.net
C:\ProgramData\Battle.netBlizzard Entertainment

It then had a bit of a think about it and finally asked me for my authenticator upon login instead of #114!@ rejecting me.
my friend and I have both got this issue , and after following all the different ideas listed,
and going through the support ticket system all i can say is they dont know what is the cause or how to fix it. what will happen is we will loose game time.

Join the Conversation

Return to Forum