Diablo® III

AUSSIE PLAYERS 12/12 3007 cant log in ?

07:20 Darwin - No love all morning here either.
Pingzapper is one of those tunnelling programs which use proxy connections to stabilize your connections or sometimes get past blocked ports.

I was tunnelling through their Los Angeles servers. But like I said, can now get in just using vanilla game client.


lots of ppl from China got banned for using this kind of proxy program.
This is getting annoying. In Melb, ISP iinet & no joy. Tried changing enSG to enUS in the launcher but then I've got a 2.5G download. (not going to happen)

I would gladly give up all my characters & items for a Aust/NZ server. (based in Aust)
this is the only online only game I play and this sort of thing seems to happen too often. is this commen or does this sort or down time happen in other on line games too. or are blizz just kinda useless?
LOL never going to happen man would cost the too much money, as you can tell they don't give 2 F#$%s about the people playing in the Oceanic Region
MVP - Diablo III
View profile
The Americas server ip is 12.129.209.68 could someone try doing a trace route(https://us.battle.net/support/en/article/performing-a-traceroute) and seeing if it times out before hitting the blizz servers? and post it here.

Note that it should timeout once it starts hitting the blizz servers as it is hitting there firewall.

For example mine is:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 23 ms 24 ms lns20.bne4.internode.on.net [150.101.180.143]
3 25 ms 23 ms 24 ms te0-1-0.cor2.bne4.internode.on.net [150.101.180.146]
4 196 ms 197 ms 195 ms te3-0-0.bdr1.syd6.internode.on.net [150.101.183.5]
5 196 ms 196 ms 196 ms pos1-0-0.bdr1.lax1.internode.on.net [203.16.213.190]
6 196 ms 196 ms 246 ms xe-7-0-3.edge2.LosAngeles9.Level3.net [4.53.230.45]
7 232 ms 227 ms 230 ms 192.205.37.145
8 205 ms 207 ms 207 ms cr1.la2ca.ip.att.net [12.122.128.102]
9 204 ms 202 ms 203 ms gar20.la2ca.ip.att.net [12.122.128.181]
10 204 ms 203 ms 204 ms 12-122-254-234.attens.net [12.122.254.234]
11 204 ms 204 ms 204 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
________________________________________________
Twitter: @Narull | ANZ Diablo III MVP
http://us.battle.net/d3/en/forum/topic/6490399005 - Narull's Hardcore Challenge.
There not spelling mistakes, Im speaking 'Ye Old English'
12/11/2012 01:49 PMPosted by samelight
lots of ppl from China got banned for using this kind of proxy program.


I doubt it. From what I gather they still make a normal connection to Blizz servers. I used it only to get by my University blocking Blizz server ports earlier in the year. So once I get past my own network restrictions it behaves as a normal connection.

Also as I mentioned I don't use it anymore and can connect fine without it.
Come on Blizzard pull your finger out and fix this issue!!
12/11/2012 01:53 PMPosted by LordVik
this is the only online only game I play and this sort of thing seems to happen too often. is this commen or does this sort or down time happen in other on line games too. or are blizz just kinda useless?

no they jsut dont give a sh*t about it thats all... u guys will get used to it
Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 14 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 35 ms 37 ms 37 ms lo0.melbras18.mel.iprimus.net.au [202.138.4.81]

3 36 ms 41 ms 37 ms mel0710.mel.iprimus.net.au [203.134.26.177]
4 35 ms 36 ms 37 ms 50.123-134-203.network.mel.iprimus.net.au [203.1
34.123.50]
5 53 ms 52 ms 52 ms xe-3-1-0.csr01.syd.iprimus.net.au [203.134.2.201
]
6 51 ms 50 ms 50 ms irb-5.bsr01.equ.iprimus.net.au [210.50.143.163]

7 188 ms 187 ms 190 ms xe-0-3-0.bsr01.sjc.iprimus.net.au [203.134.2.138
]
8 190 ms 189 ms 190 ms xe-5-3-0.sjc12.ip4.tinet.net [173.241.128.13]
9 * 364 ms * as7018.ip4.tinet.net [77.67.78.94]
10 203 ms 205 ms 204 ms cr1.sffca.ip.att.net [12.122.86.198]
11 200 ms 203 ms 204 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 201 ms 201 ms 200 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 202 ms 201 ms 202 ms 12-122-254-234.attens.net [12.122.254.234]
14 213 ms 212 ms 212 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
15 * * * Request timed out.
...repeat...
30 * * * Request timed out.

Trace complete.

There's your problem :)
Edited by Elthiriul#1239 on 12/11/2012 1:57 PM PST
Here got a solution: For guz with 3007: Try to change ur dns
3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007

So it patched fine @ 6:30 this morning. I have been trying to log in since and the result every time without question is 3007.

This error is occurring when establishing the connection to battlenet during the log in phase.

Game was working fine yesterday, today's new patch = can't play :'(.

3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007 3007
In Newcastle here on Americas .Had a patch update and now get a #3007 on attempting to connect to server. Also on Telstra
Edited by Tingtang#6279 on 12/11/2012 2:03 PM PST
12/11/2012 01:57 PMPosted by Shawshank
Here got a solution: For guz with 3007: Try to change ur dns

how ?
Here's mine if it's any help.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms reshub-vlan-191.anu.edu.au [150.203.192.1]
2 <1 ms <1 ms <1 ms huxhub-ge-x-x.anu.edu.au [150.203.201.97]
3 <1 ms <1 ms <1 ms huxbdr-te-2-1.anu.edu.au [150.203.201.6]
4 137 ms 2 ms 200 ms tengigabitethernet2-2.er1.anu.cpe.aarnet.net.au [182.255.118.9]
5 <1 ms <1 ms <1 ms ge-2-0-0.bb1.b.cbr.aarnet.net.au [202.158.201.81]
6 4 ms 4 ms 4 ms so-0-1-0.bb1.b.syd.aarnet.net.au [202.158.194.29]
7 155 ms 154 ms 154 ms so-3-0-0.bb1.a.lax.aarnet.net.au [202.158.194.158]
8 157 ms 157 ms 163 ms 10.ge-9-3-8.er2.lax112.us.above.net [64.124.200.233]
9 157 ms 157 ms 157 ms xe-0-1-0.cr2.lax112.us.above.net [64.125.30.250]
10 157 ms 157 ms 176 ms xe-8-0-0.mpr1.lax12.us.above.net [64.125.30.30]
11 * * * Request timed out.
12 161 ms 161 ms 162 ms cr1.la2ca.ip.att.net [12.123.30.18]
13 158 ms 157 ms 157 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 158 ms 262 ms 158 ms 12-122-254-238.attens.net [12.122.254.238]
15 158 ms 158 ms 158 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
Change it to what??
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 16 ms 16 ms 172.18.113.45
3 15 ms 16 ms 15 ms 172.18.73.50
4 24 ms 24 ms 23 ms 172.18.243.101
5 25 ms 23 ms 23 ms bundle-ether13.wel33.perth.telstra.net [110.142.
134.201]
6 18 ms 19 ms 19 ms bundle-ether1.wel-core3.perth.telstra.net [203.5
0.6.137]
7 51 ms 48 ms 59 ms bundle-ether7.fli-core1.adelaide.telstra.net [20
3.50.11.18]
8 68 ms 59 ms 60 ms bundle-ether9.win-core1.melbourne.telstra.net [2
03.50.11.91]
9 79 ms 86 ms 83 ms bundle-ether12.ken-core4.sydney.telstra.net [203
.50.11.12]
10 74 ms 75 ms 78 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50
.6.29]
11 73 ms 73 ms 73 ms tengigabitethernet11-0.sydp-core02.sydney.reach.
com [203.50.13.86]
12 220 ms 220 ms 220 ms i-0-4-2-0.paix-core01.bx.telstraglobal.net [202.
84.140.157]
13 221 ms 304 ms 221 ms i-0-0-0-1.paix02.bi.telstraglobal.net [202.84.25
1.74]
14 221 ms 221 ms 221 ms 206.24.240.149
15 222 ms 222 ms 222 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.20
6.58]
16 246 ms 223 ms 223 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.2
03.22]
17 225 ms 225 ms 225 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
18 269 ms 268 ms 268 ms cr1.sffca.ip.att.net [12.122.137.126]
19 268 ms 266 ms 267 ms cr1.la2ca.ip.att.net [12.122.3.122]
20 264 ms 263 ms 263 ms gar20.la2ca.ip.att.net [12.122.128.181]
21 265 ms 264 ms 287 ms 12-122-254-234.attens.net [12.122.254.234]
22 267 ms 267 ms 266 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
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.

edit Changing DNS server to 8.8.8.8 fixed the problem for me
Edited by Juicebox#6602 on 12/11/2012 2:58 PM PST
I logged on earlier (about half an hour ago in tasmania) with no problems.

Just so you know.


What ISP you with mate? SO far yet to see someone else on node like me.

Really weird that I can login on both clients but others can't. I'd get one of my friends to try my account on there net but they are all sleeping...damn people who sleep.
________________________________________________
Twitter: @Narull | ANZ Diablo III MVP
http://us.battle.net/d3/en/forum/topic/6490399005 - Narull's Hardcore Challenge.
There not spelling mistakes, Im speaking 'Ye Old English'


Dodo which uses telstra i believe. But it was working fine.
Changed my DNS to use google servers 8.8.8.8
Flushed the cache and now on
ya, is the !@#$en DNS,google it and change it to Google Public DNS then u can login
This topic has reached its post limit. You may no longer post or reply to posts for this topic.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]