Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 25 replies
  • Subscribers 3 subscribers
  • Views 11620 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Battle.Net Beta Launcher

IngoPohlschneider
Hello
did anyone make it to setup the UTM to allow the Battle.Net Beta Launcher to successfully install?

I allowed the ports mentioned in the following port outgoing.

https://eu.battle.net/support/en/article/firewall-proxy-router-and-port-configuration

Didn't work. I can see some ACK RSTs get getting Default Dropped.

The Beta Launcher Installer is stuck at "Updating Beta Launcher" and doesn't go any further

Any advice would be nice [:)]


This thread was automatically locked due to age.
Parents
  • 0
    The difference is that the .100 has a second NIC that is disabled by default, but directly connected to the Router. So it can - on demand - work around the ASG [;)]

    So I guess game-play is not a problem, only updates / client install/download are.

    But since I do not want to got the .100-way for every update I'd like to find out what is the reason with the UTM in between [:)]
Reply
  • 0
    The difference is that the .100 has a second NIC that is disabled by default, but directly connected to the Router. So it can - on demand - work around the ASG [;)]

    So I guess game-play is not a problem, only updates / client install/download are.

    But since I do not want to got the .100-way for every update I'd like to find out what is the reason with the UTM in between [:)]
Children
No Data