Error 3007 with a Dlink DIR-615

Technical Support
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
bump
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)..
I'm having this exact same problem, and my dsl modem is configured to work directly through a router, thus I cannot play at all unless I now buy a new router?
ACK! The frustration!!!
Bump this works for me. Thanks a lot!
Same problem here. I get disconnected every 5 mins and my router is Dlink DIR-615.

PLEASE Blizzard, help us!
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
help my !@# i dis every 5 min
Hi people!
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:

TCP myIP:4104____12.130.244.193:1119
TCP myIP:4105____12.130.245.97:1119

TCP myIP:2356____112.130.244.193:1119
TCP myIP:2357____112.130.245.21:1119

TCP myIP:AAAA____12.130.244.193:1119
TCP myIP:BBBB____12.130.246.86:1119

TCP myIP:CCCC____12.130.244.193:1119
TCP myIP:DDDD____12.130.247.108:1119

So i configured my router with ADVANCED->INBOUND FILTER->ADD INBOUND FILTER RULE = name: battle.net, Remote IP Range: 12.130.244.193-12.130.247.255

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
Hello everyone, I was also experiencing constant disconnects from D3. I am using the Dir-615 router. I flashed the router with dd-wrt(custom firmware) set it up and now I don't lose connection at all. Hope this helps someone.
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.
05/19/2012 05:00 AMPosted by Malanak
Hello everyone, I was also experiencing constant disconnects from D3. I am using the Dir-615 router. I flashed the router with dd-wrt(custom firmware) set it up and now I don't lose connection at all. Hope this helps someone.


Can u explain?
I have been having the 3007 error with a Cisco Linksys E3000 wireless router. It has even extended to WoW.
bump
dd-wrt(custom firmware). this worked for me as well. http://www.dd-wrt.com/site/index
Dd-wrt is my final solution ,it works well .
I reflasheD my d-link dir 615 router.
Hi people!
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:

TCP myIP:4104____12.130.244.193:1119
TCP myIP:4105____12.130.245.97:1119

TCP myIP:2356____112.130.244.193:1119
TCP myIP:2357____112.130.245.21:1119

TCP myIP:AAAA____12.130.244.193:1119
TCP myIP:BBBB____12.130.246.86:1119

TCP myIP:CCCC____12.130.244.193:1119
TCP myIP:DDDD____12.130.247.108:1119

So i configured my router with ADVANCED->INBOUND FILTER->ADD INBOUND FILTER RULE = name: battle.net, Remote IP Range: 12.130.244.193-12.130.247.255

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


Many thanks, that worked perfectly!!!
Hi people!
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:

TCP myIP:4104____12.130.244.193:1119
TCP myIP:4105____12.130.245.97:1119

TCP myIP:2356____112.130.244.193:1119
TCP myIP:2357____112.130.245.21:1119

TCP myIP:AAAA____12.130.244.193:1119
TCP myIP:BBBB____12.130.246.86:1119

TCP myIP:CCCC____12.130.244.193:1119
TCP myIP:DDDD____12.130.247.108:1119

So i configured my router with ADVANCED->INBOUND FILTER->ADD INBOUND FILTER RULE = name: battle.net, Remote IP Range: 12.130.244.193-12.130.247.255

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


this work for me aswell posting this on the tech forum

Join the Conversation

Return to Forum