Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
I been going through the forms and one of the main reasons why 3007 error occurs is because of their Dlink DIR-615 router. To resolve this problem I disconnected the wireless router and DIRECTLY connected the Ethernet cable to my computer. By doing this I had no error at all and was able to play Diablo 3 for hours. However, can someone please teach me how to fix this problem by using Dlink DIR-615 router? I simply cant disconnect this router for my own use. Thank you.
Blizzard support help me out please
I tried everything with my DLink DIR-615, and even with the newest firmware wasn't able to not get the 3007 error.
I finally dug my netgear WGR-614 out of the closet, and hooked it up, and my wife and i have been happily slaying demons without disconnectes ever sense (about 11 hours of play time on the new router)..
The only way i guess to fix it now its to keep connected to you modem directly otherwise then that youre gonna be disconected every 5 min, i got same trouble with my D link 615, i wish they gonna fix that soon cause i cannot have wireless in my house when i play directly with the modem
I want to share my solution for a Dlink DIR 615 C2
I don't know anything about networking but reading a lot of information in the forum gave me some conclusion.
First of all, I didn't want to enable DMZ (FIREWALL SETTINGS) because some people said that is unsafe.
Second, when i activate Endpoint Independent option for TCP Endpoint Filtering i saw in the netstat a lot of suspects processes that i didn't like.
Also, i discovered with the netstat command the following connections when i was playing Diablo III:
So i configured my router with ADVANCED->INBOUND FILTER->ADD INBOUND FILTER RULE = name: battle.net, Remote IP Range: 184.108.40.206-220.127.116.11
ADVANCED->FIREWALL SETTINGS->NAT ENDPOINT FILTERING = Default setting (UDP Endpoint Filtering: Address Restricted, TCP Endpoint Filtering: Port And Address Restricted)
And then in ADVANCED->PORT FORWARDING = name: Diablo III.exe, TCP: 80,1020-5000, UDP: 1119,6881-6999. Schedule: Always, Inbound Filter: battle.net
and the game just worked fine!
by the way... The Support Center needs to update the link http://us.battle.net/support/en/article/firewall-configuration-for-blizzard-games with the true TCP PORTS config.
I don't know if the problem is with the battle.net server that opens random ports with different IPs or we need to open all the possible ports that use the battle.net server xD
Sorry for my poor english
Edited by spaceGhost#1188 on 5/19/2012 4:32 AM PDT
I had endless disconnects after 1-2 minutes gameplay, using a Thomson speedtouch modem and a D link Dir 615 wireless.
After reading about others experience, I just ditched the wireless modem and it runs absolutely fine through the speedtouch no disconnects all night.
Guess the wife just doesnt get to use her laptop.
Can u explain?
Many thanks, that worked perfectly!!!
this work for me aswell posting this on the tech forum
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.