Diablo® III

1.0.6a and Error 3007?

(Locked)

I still experience the error message when trying to log into America server however if I change to Asia server I have no problem playing D3 just that I have to start all over again. Common! Blizzard get this fix. Not sure any other country experience the same issue or just Australia residence are experiencing this after reading the posts.
Change your DNS to googles
ie. 8.8.8.8 for primary and 8.8.4.4 secondary
Does not work for everyone
Changing the DNS to 8.8.8.8 didn't work. I'm in Canberra. Seems like a long wait till the Aus/NZ ISPs recognise the new US battle.net settings. 3 days and counting with Error 3007. I knew there is a reason I never got into these Online games. Diablo 3 - my first and last RPOG.
AGREE
'Bug Fixes: Fixed an issue that could occur when attempting to upgrade from the Diablo III Starter Edition'

Why did I, or anybody as an owner of the full version of the game, need this update?
This does not make sense, as I have an account in the Americas and it gives me 3007 error only since the patch. I switch to ASIA and all works fine

If it was my ISP it would impact both
Here you go Blizzard. The "more infor" you were looking for. If it helps in any way:

C:\Users\Home>nslookup us.depot.battle.net
Server: UnKnown
Address: 10.1.1.1

Non-authoritative answer:
Name: gs1.wpc.edgecastcdn.net
Address: 68.232.45.253
Aliases: us.depot.battle.net
wpc.758c.att-acdn.net

C:\Users\Home>telnet us.depot.battle.net 1119
Connecting To us.depot.battle.net...Could not open connectio to the host, on port 1119: Connect failed

C:\Users\Home>telnet us.actual.battle.net 1119
<<I get a blank screen, as expected>>

C:\Users\Home>tracert us.depot.battle.net

Tracing route to gs1.wpc.edgecastcdn.net [68.232.45.253]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.1.1.1
2 14 ms 14 ms 14 ms nexthop.act.iinet.net.au [203.215.12.248]
3 15 ms 15 ms 14 ms po2.cbr-tact-bdr1.iinet.net.au [203.215.12.26]
4 18 ms 18 ms 19 ms ge-3-0-2-0.syd-ult-core1.iinet.net.au [203.215.20.8]
5 * * * Request timed out.
6 21 ms 20 ms 21 ms 68.232.45.253

Trace complete.

C:\Users\Home>tracert us.actual.battle.net

Tracing route to us.actual.battle.net [12.130.244.193]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.1.1
2 14 ms 15 ms 14 ms nexthop.act.iinet.net.au [203.215.12.248]
3 15 ms 14 ms 14 ms po2.cbr-tact-bdr2.iinet.net.au [203.215.12.28]
4 19 ms 26 ms 18 ms ge-3-0-2-0.syd-mas-core1.iinet.net.au [203.215.20.34]
5 209 ms 208 ms 209 ms unknown.telstraglobal.net [134.159.130.113]
6 210 ms 211 ms 210 ms i-0-5-0-0.tlot-core01.bx.telstraglobal.net [202.84.140.102]
7 163 ms 163 ms 164 ms i-0-4-0-0.tlot02.bi.telstraglobal.net [202.84.251.238]
8 179 ms 178 ms 178 ms 208.175.201.5
9 178 ms 177 ms 177 ms 208.174.194.66
10 181 ms 183 ms 181 ms cr1.la2ca.ip.att.net [12.123.30.6]
11 178 ms 178 ms 178 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 178 ms 179 ms 179 ms 12-122-254-234.attens.net [12.122.254.234]
13 178 ms 177 ms 177 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
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.
hi guys,tried the 8888 dns thing,im in aus,followed the steps thru to change it but the last step where the windows diagnostic is suppose to check ,it didnt do anything so i could not change it........ did this happen with anyone else? plus side is at least my authenticator still works :)
85 Draenei Priest
0
2 days, can't log in, Blizz get off youre collective !@#$ and do something to correct the issue instead of whining that it's not your problem
Edited by Carlos#1210 on 12/13/2012 4:41 AM PST
Marco, This is what I understand. Your ISP has a list of IP Addresses (numbers) and their corresponding DNS addresses (words like us.depot.battle.net). Blizzard changed the number of their US server. Don't ask me how. I don't know the details. Till your ISP has updated information for this new number in its correspondig DNS record "ET can't call home".

The IP address of the Asian and European server didn't change. So no problem logging in to them.
lol blizzard trying to blame other things for what is CLEARLY there fault. stop making excuses and just fix it.
SAME PROBLEM FROM SYD AUS.

just want to play this game i have a lvl 60 hardcore monk, had no dramas then u give us a patch and everything fails.

WTF
I am in Australia here, STILL getting the Error 3007! Can Blizzard please fix up this 3007 issue? It's been three days that we still can't play the game in the Americas region ......
Am from India and even am getting the same "Error 3007" from the time i downloaded the new patch. its getting more than 48hrs since am facing this problem.
go to control panel click network connections right click your local area connection click properties select internet protocol then click properties go to use dns server (preferred) and enter the numbers 8.8.8.8 and vola should work then :)
12/13/2012 05:17 AMPosted by KINSA1
I am in Australia here, STILL getting the Error 3007! Can Blizzard please fix up this 3007 issue? It's been three days that we still can't play the game in the Americas region ......

go to control panel click network connections right click your local area connection click properties select internet protocol then click properties go to use dns server (preferred) and enter the numbers 8.8.8.8 and vola should work then :)
12/13/2012 04:10 AMPosted by Firewing
Changing the DNS to 8.8.8.8 didn't work. I'm in Canberra. Seems like a long wait till the Aus/NZ ISPs recognise the new US battle.net settings. 3 days and counting with Error 3007. I knew there is a reason I never got into these Online games. Diablo 3 - my first and last RPOG.


go to control panel click network connections right click your local area connection click properties select internet protocol then click properties go to use dns server (preferred) and enter the numbers 8.8.8.8 and vola should work then :)
Same problem, getting 3007 trying to log in.

Was working fine yesterday & patched first go this morning.

I have attempted this several times already and it wont establish the connection at all when I try log in. 3007 3007 3007.

I too am in Australia connecting to US.


go to control panel click network connections right click your local area connection click properties select internet protocol then click properties go to use dns server (preferred) and enter the numbers 8.8.8.8 and vola should work then :)
12/13/2012 04:10 AMPosted by Firewing
Changing the DNS to 8.8.8.8 didn't work. I'm in Canberra. Seems like a long wait till the Aus/NZ ISPs recognise the new US battle.net settings. 3 days and counting with Error 3007. I knew there is a reason I never got into these Online games. Diablo 3 - my first and last RPOG.

Well from Melbourne, it did, if you follow all instructions carefully. Then you after you login, you need to quit D3 and reset DNS to either automatic or previous, if there were any on your system.
Having said that and although I can play again, this stuff up should not have happened in the first place.
12/11/2012 02:03 PMPosted by Livert
Come on Blizzard, please verify there's an issue with Australian logins.


go to control panel click network connections right click your local area connection click properties select internet protocol then click properties go to use dns server (preferred) and enter the numbers 8.8.8.8 and vola should work then :)
This topic is locked.

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]