it does work here. battle.net has a setting: allow multiple instances of this application or something.

after that. just click BOTH on launch game at the same time;)

Thank you for helping!

I get this error message after loading Aster and starting Battle.net Launcher:

are you starting the battle.net application in a sandbox? that doesnt work.

No, I am starting it normal. Putting in 'multiple instances of the client' makes it so we don't have to do that, right?

I did read that I might have to log into a different Windows account. Could that be the reason? Both accounts are logged into the same Windows user (we have our own Battle.net accounts).

probably:) i use two different accounts.

i am curious to know if playing destiny 2 in co-op will work on your pc. i am getting network disconnected errors.

Nope. I got the error message again even after making the new Windows account. Sigh...

Okay I think I finally got it working.

The thing was that you AREN'T supposed to use a static IP. I had one set up through Aster and that was causing some conflictions, I guess.

Hi, Seems you got it working? My battle.net launches fine, but when launching the same game in the second workstation, the button is faded out and says the game is running(which is appearently not, it detects the game running on another workstation). Could you please help me out? 🙂

Hey now I'm having that problem, too lol...

If you launch them at the same time, one account logs in but the other tells you to login the game through Battle.net launcher (which it already is).

Does anyone know how to get around this?

So no one got this to work with Destiny 2?

So no one got this to work with Destiny 2?

I1m having same problem, is not possible to open Battle.net with other IP, in same PC.

I made it work some time ago using loopback adapter (and sharing internet with it) and portfowarding port 3097 for both ips. The game needs 2 ips, one for each work station, since aster dont let u fix one ip for each workstation (dunno why i tested myself) you need execute the game with default options on aster ( extended settings ) for workstation 1 and log on game, close battle net and agent.exe. Then go on extended settings and set the loop back adapter on workstation 2, soon u hit save the new ip will be active on both worksations even on 1, but since u pre launched it with old ip it does the trick. Im just not sure if i had 2 folders of destiny 2, im pretty sure was just one.

The thing is u need 2 ips because you cant use same port for 2 destiny accounts, you get a error if you invite the both workstations to same squad.

I made all bizz game work, on aster v 2.23 but it was tricky. Soon we get a aster update to let you trully fix one ip for each workstation everything will be solved.

I made it work some time ago using loopback adapter (and sharing internet with it) and portfowarding port 3097 for both ips. The game needs 2 ips, one for each work station, since aster dont let u fix one ip for each workstation (dunno why i tested myself) you need execute the game with default options on aster ( extended settings ) for workstation 1 and log on game, close battle net and agent.exe. Then go on extended settings and set the loop back adapter on workstation 2, soon u hit save the new ip will be active on both worksations even on 1, but since u pre launched it with old ip it does the trick. Im just not sure if i had 2 folders of destiny 2, im pretty sure was just one.

The thing is u need 2 ips because you cant use same port for 2 destiny accounts, you get a error if you invite the both workstations to same squad.

I made all bizz game work, on aster v 2.23 but it was tricky. Soon we get a aster update to let you trully fix one ip for each workstation everything will be solved.

could you make a step by step guide?
i've tried here and every time i try to join the other player the game crashes

Yah im testing the new version a easier way so that i can do a step by step.

For now the rule number one. never ever touch aster extended settings. let them rest at default forever.
Just made it work disabling loopback adapter, launching destiny on workstation 1 and going in game options confirming the ports and forwarding.
Then open battlenet launcher (another account) on workstation 2, enable loopback adapter launch the game, go in options confirm the new port and fowarding it, then workstation 1 can invite to fireteam.

ps: you need to share your internet adapter with loopback adapter so that it get the ip 192.168.137.1, set blizzard app to autoclose on game launch.

my trial ended, soon a get a new license i do a stepbystep.