Diablo 3, 3G and Error 3007

[Crummy_Gummy]

Hi all

I can't logon to Diablo 3 because of this annoying 3007 error. I'm running 8ta and CellC which both have fairly decent latency. It looks like Diablo is initiating a callback event. I'm wondering if the 3G proxies have anything to do with this callback not completing. It's definitely accepting my username and password as there is an error if I use the wrong password.

Any ideas/success with this? My next plan is to create a socket proxy to my linode, I was wondering if any of you have had a similar problem.

 

[guest2013-1]

Hi all

I can't logon to Diablo 3 because of this annoying 3007 error. I'm running 8ta and CellC which both have fairly decent latency. It looks like Diablo is initiating a callback event. I'm wondering if the 3G proxies have anything to do with this callback not completing. It's definitely accepting my username and password as there is an error if I use the wrong password.

Any ideas/success with this? My next plan is to create a socket proxy to my linode, I was wondering if any of you have had a similar problem.

IMO it's your region. I'm betting you downloaded and applied the new patch, and you're now trying to login to the American server. I says on the launcher that you can't do that until the new patch launches on America/Asia. So check that, and try and login to Europe (if it's that) and see if you get the same error.

Otherwise, a google for only "3007" brings up several results in the top 5 for diablo 3 issues

 

[Crummy_Gummy]

I think your right about it having something to do with a patch. I have however tried EU and America. No dice.

As for google, most of the info is related to connections dropping and contains sage wisdom from Blizzard advising you to disable all security on your PC and router. Not any advice I'd like to use. It dose however point again to the callback which could be a problem on 3G. You'd think it fould fail back to a synchronous connection though.