Posted March 13, 2019
I've opened up ports 6112-6119 TCP & UDP, plus 3724 TCP on my Firewall.
Still, nothing, Any help?
there may be already an entry, but "Allow another app" anyway and browse to GOG folder's Diablo.exe
benhun1
New User
Registered: Jul 2014
From United States
I've opened up ports 6112-6119 TCP & UDP, plus 3724 TCP on my Firewall.
Still, nothing, Any help?
there may be already an entry, but "Allow another app" anyway and browse to GOG folder's Diablo.exe
Anders_Jenbo
New User
Registered: Mar 2019
From Denmark
Posted March 21, 2019
I'd suggest contacting the official Battle.net support since it's directly related to the Battle.net functionality.
https://github.com/diasurgical/devilutionX/releases
SpaceBass
New User
Registered: Mar 2019
From United States
Posted March 23, 2019
Just to have out there. Try closing any other Blizzard games or launchers on your network.
My brother could not get into BNet because our Father had the Blizzard App open on his computer (the Blizz website mentions it using 6112).
Also, as svfn said. The easiest and surest method to get Diablo through your firewall is to add the Diablo.exe and ensure private is checked. Turning your firewall off doesn't always work. In my case it has never worked.
Along with that, make sure you have your network set to Private and NOT Public. When your network is set as Public your firewall uses an entirely different profile regarding inbound/outbound rules. This caused us issues when trying out LAN play.
Try checking if you have DMZ enabled on your outer. I have read routers check Port Forwards first, but DMZ has always jacked up my Port Forwards. If you don't know what DMZ is you most likely don't have it enabled, so no worries x)
-Spooky
My brother could not get into BNet because our Father had the Blizzard App open on his computer (the Blizz website mentions it using 6112).
Also, as svfn said. The easiest and surest method to get Diablo through your firewall is to add the Diablo.exe and ensure private is checked. Turning your firewall off doesn't always work. In my case it has never worked.
Along with that, make sure you have your network set to Private and NOT Public. When your network is set as Public your firewall uses an entirely different profile regarding inbound/outbound rules. This caused us issues when trying out LAN play.
Try checking if you have DMZ enabled on your outer. I have read routers check Port Forwards first, but DMZ has always jacked up my Port Forwards. If you don't know what DMZ is you most likely don't have it enabled, so no worries x)
-Spooky
Post edited March 23, 2019 by SpaceBass
lifeIsWorthless
lifeIsWorthless
Registered: Feb 2014
From Canada
Posted September 18, 2019
Hi People.
I had the same problem - Diablo can chat but not play games.
I tried allowing Diablo through firewall - failed.
I found it's not Diablo you should care about - it's BNUpdate.exe.
Create an inbound rule for it and you're good to go.
Or at least it worked for me - maybe work for you too.
Good luck playing this wonderful classic !
I had the same problem - Diablo can chat but not play games.
I tried allowing Diablo through firewall - failed.
I found it's not Diablo you should care about - it's BNUpdate.exe.
Create an inbound rule for it and you're good to go.
Or at least it worked for me - maybe work for you too.
Good luck playing this wonderful classic !
.Astral.
New User
Registered: Mar 2019
From United States
Posted October 14, 2019
I followed this guide and it worked for me:
https://d1legit.com/2019/03/31/diablo-1-hosting-on-battle-net-port-forwarding-guide/
https://d1legit.com/2019/03/31/diablo-1-hosting-on-battle-net-port-forwarding-guide/