I have 2 PCs in same home network and want them both to play Diablo on b.net. I have mastered how to set up port forwarding with one pc, but when I try to set up for both the modem gives an error about a conflict. I can get it to work by connecting one pc to b.net, creating a game, switching the port forwarding rule to the second pc and then connecting it - but what a pain. Any tips on how to achieve the goal?

перенаправление портов нужно, чтобы к вам могли присоединиться
для обычный игры достаточно открыть порты в операционной системе
зачем вам на двух компах хостить?

I want to use both PCs so my son and I can play on bnet with others. Thanks.

See my post https://www.gog.com/forum/diablo/cannot_connect_to_bnet_after_successfully_portfowarding/post12 ; report back if you need more help.

For local-only games (which your follow-post said you don't want in general, but maybe sometimes you will): avoid battle.net, use one of the local connection methods like IPX.

If you want to play obth of you in bnet you will need to use another connexion maybe you an share your 3g 4g connexion from your phone that will work. Connecting to battlenet from the same ip will just bug the connexion.

this happens in every single blizzard game

This is only true if you configured your network incorrectly. My post linked above explains how to do it properly.

Im not sure if it is possible to connect 2 computers on the same network to battle.net or not. It may be possible if you use the traditional method as described in the following article (much easier for me to read and follow than a forum thread) on one computer and then use the UPnP method mentioned within the article on another computer. Let me know if you can get it to work...

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

It is possible. I've done it. I've posted how to do it. At least one person has successfully done it using my instructions, and reported back on his success. (Others may have done it without reporting back.) That guide has more wrong than right. I would not recommend it to anyone.

- Disabling IPv6 is irrelevant. The game automatically uses IPv4.
- Forwarding TCP ports has never been required for Diablo. This particular bit of misinformation took hold somewhere and has been repeated extensively.
- Forwarding ports other than 6112 holds a tiny grain of truth, but is mostly wrong too. This was born of the need to forward non-6112 ports to port 6112 on secondary systems. It was never correct to forward more than one port to any one system.

Well pardon me for trying to help out... I posted a link to a guide I personally have had success with, works without a hitch... nice attitude btw... A+

I appreciate that you want to help, but you start off with "I don't know if it works" when I just described, in great detail in the linked post, exactly how to make it work.

I didn't say the guide you linked cannot work. I said it was more wrong than right and that I would not recommend it to anyone. To use a car analogy, jaywalking across a freeway can get you to the other side, and maybe even safely. It's still a bad idea and I wouldn't recommend it to anyone.

I mean, I personally cannot even follow your guide and as you said, it requires an enterprise grade router... regardless, having both options here is for the better. I know the guide I posted works (I personally used it myself). If other users have had success with that linked guide then all the better.

Just because the guide works for you, it doesn't mean it will work for everyone Kougun.

For example, neither guide will work for me, because there's my ISP's NAT in the way. It needs to be portforwarded along with my own router, but the end user normally cannot access ISP's NAT, so the port forwarding has to be done from the ISP's side. After contacting the ISP, someone else has already set up the port forwarding for port 6112, and the only solution the ISP offered was port forwarding a different port (useless) or purchasing a static IP.

Not everyone can simply configure ports and play. In my eyes, this is a serious issue that GOG should have resolved (alone or together with Blizzard) prior to this release.

Paying extra money for a yearly plan with static IP just to be able to connect to an outdated battle net service, and just because some idiot thought it was a good idea to disable the JOIN GAME button. Forget it.

Most people probably cannot follow it without some supporting materials, but the point of the guide was to describe exactly what is required, in a way that can be readily translated to any applicable router. My exact words were "Low end consumer home routers may not be flexible enough to let you do the right thing", and I picked that phrasing deliberately. You don't need an enterprise grade router. You don't even need anything particularly powerful. You just need a system where the software is not needlessly crippled. A Raspberry Pi is probably powerful enough to do this.