Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
Waited the 10 minutes... Only for the game to crash again before I could login...
Guess what... Now trying to login on the Asian Server gives me the 3003 Error!
Spoke too soon, now I'm queueing again with no ETA of when I can log in.
Might just give up and get some sleep.
Edited by Ungrimm#6416 on 5/22/2012 5:59 AM PDT
THIS error SUCKS! I have played Diablo 3 fine since launch but my brother who bought the game a couple days ago has not been able to play more than 20 minutes before getting this error 3003. This doesnt make sense at all. Hes tried all the solutions of port fowarding and disabling firewall etc etc. His computer is literally a metre away from mine and hes is getting the error and im not.....MAKES NO SENSE
Blizz really need to fix this asap
I have been reading all the posts on error 3003 and the only thing that makes me happy about the whole thing is reading the f(*&en funny posts from you guys. I agree, they should make it offline available, like the second one.... and bring back the cows :( I miss the cows.. Moo moo moo moo?
If you tried to setup non-original Diablo, you are changing hosts file (C:\Windows\System32\drivers\etc). Check this file. You can see there eu.battle.net/bla bla 127.0.0.1 this mean if you want to connect eu.battle.net/bla bla go to the 127.0.0.1 ip address. And this ip addres your microsof local loopback address. I think you are taking this problem cause of this. You need to delete this inputs from hosts file. After that you can try to access again.
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.