I did the port forward and tried all the fixes, it's still not working.

One day this will be easier to fix. :(

I have the same issue as everyone described here and I've tried all these "fixes" but haven't had any luck yet.

I have also tried all the things people sayed, but nothing is working for me on Win7. Hoppe that a patch will come and fix it, so i can play with my friends.

actually i think i am also behind ISP router, i don't have a static IP, my public ip is behind some ISP NAT without dedicated line. i know this because i tried Dynamic DNS service and it didnt work because my ISP assigns a private WAN IP address instead of public IP..

but i am able to go on battle.net with that trick of canceling out and selecting any other option like IPX or Modem, cancel and enter battle.net again, most of the time i don't get the red message again and can create/joing games.

also i never portforwarded on my router, so it's strange indeed. maybe it's an ipv6 issue.

From what I hear it is an ipv6 issue. Sometimes your ISP can make it ipv4 but mine wouldn't so I am unable to host games unless the vpn works for that too

Hello everyone!
I'm getting same error as topic starter and some people here. I followed Blizzard firewall configuration manual, I forwarded 6112-6119 on my router, I even tried that weird "go to battle.net, get error message, go to another option or main menu, and then return to battle.net" solution. I contacted my network provider, and they said "we are not blocking TCP/UDP on port 6112-6119, go contact to developer".

And nothing works for me.

Waiting for GOG team members' answer to call of those who have same problem.

Regards.

Yes, your ISP is not blocking these ports, but they are also not redirecting these ports to your computer. That's the issue.

Diablo server doesn't tell the router "sup, Router! I'm sending this packet to Ice_Haron's computer, third one from the left", so the router doesn't know where to send the packets for Diablo. Thus, the 6112 error. Your ISP can configure their NAT to send data from ports 6112-6119 to a specific IP address that's used by your PC. Some ISPs charge money for that. And in case the ports ARE already in use (by someone else who uses the same ISP), most ISPs will tell you to pay for a static IP, so you can either pay more or use Hamachi to play LAN.

You don't need for static IP address. You can port forward to dynamic IP addresses just fine. But when the DHCP decides that it's time to give you a different IP, it will stop working.

There's also no need for port forwarding due to the thing called DMZ or DMZ Host. When active, your router will send everything to the specified IP address, so it basically acts like port forwarding, but for ALL ports at once.

Also, last time we talked about this, you told me that you DID port forward, so that's that.

---

To summarize, there is no single guide that you can follow and it will work. The setup is dependent on EACH PERSON's ISP's physical NETWORK layout, so the requirements will be different for everyone.
The thing about clicking a different option in the menu is total bullshit and has no effect on the network settings whatsoever.

I would also like to remind people that if you do get the error and are able to connect into the battle.net chat hub, if you leave and go back into the main menu and start battle.net again you might be able to connect as normal if you have followed the instructions people have posted here.
This might also take a few tries.

DMZ seems a bit drastic, for most users portfoward work then no need to DMZ. i would rather suggest playing via Hamachi if you can't port forward rather than DMZ. i also never said you or anyone need static IP.

well it's not bullshit if it works. and it worked for some others as well, not sure what is up with that though. the red error goes away the 2nd time.

anyways that was a while ago. since i followed FreshMeat's Windows Firewall guide and portforwarded (despite port scanners still reporting it's closed), the red error never appears anymore. i would suggest anyone with the problem try this first, if not look at Hamchi for playing online.

https://www.tapatalk.com/groups/freshmeatbutchery/portforwarding-guide-old-tristram-forums-t10.html

I had quite a bit of difficulty getting diablo to work on battle.net. This guide is the best I have found to date and following all the steps has allowed me to host on battle.net once again.

https://d1legit.com/2019/03/31/diablo-1-hosting-on-battle-net-port-forwarding-guide/

I finally got it working. After following everyone's instructions it still wasn't working. Then I found someone mentioned a reboot. That did it.

What is your computer that PC crom the fairly odd parents thats a milk crate monitor and a hamster powering it?

HELLO!! I may have just cracked the code lol..Once in GOGGALAXY open the normal Diablo (NOT THE DIABLO CLASSIC). Open Multiplayer and then create a game in Local Area Network. When you start the game your PC should have a additional check to see if you want to allow the game to proceed. After saying yes and creating a game close Diablo. Go open Diablo Classic and run Battlenet from Multiplayer. At this point I was able to connect but it says my connections slow and I will only be able to chat not join games. I went back and then reopened Battlenet and my character. I AM NOW ABLE TO CREATE AND JOIN GAMES but unfortunately I see no games available. Idk if me trying to patch Battlenet a few times before trying all of the above had anything to do with my success.I hope this helps someone else

For those who TRIED EVERYTHING (as I did). If you really did that, there is one thing remaining - your Internet Provider. As soon as I changed it, I connected to b-net and was able to join games.

If you have to change your internet provider to play a game, then I'd risk saying there's something wrong with the game :D