title: Artemis running on WSL2 not accessible from Windows
body: <p>This is a specific question. I am running an Artemis MQ service on WSL2. I would like to access the service from an app running on the Windows side, but I got the following exception:</p>
  <pre><code>Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
  </code></pre>
  <p>When I run both Artemis and the app on the same &quot;side&quot; (both on WSL or both on Windows, but not at the same time), they work correctly.</p>
  <p>Before I installed artemis on WSL, the app running on Linux was able to access the MQ on Windows, so my guess is the problem connected to Artemis being installed on both platform. (However, I checked and no service is running automatically.) Because artemis is not &quot;installed&quot;, but unzipped and a broker is created, uninstalling is not possible.</p>
  <p>Any idea where the two install is interfering each other?</p>
  <p>Note: The web console is also unavailable:</p>
  <p><a href="https://i.stack.imgur.com/UgLOV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/UgLOV.png" alt="enter image description here" /></a></p>
  <p><strong>UPDATE 1</strong></p>
  <p>Some more information:</p>
  <p>I tried to find out any port issue (changed the ports, for example), and to find any reference about port forwarding, but the only info I've found (on the official WSL FAQ), that the ports are shared and we can't talk about forwarding, because they are technically the same (that's why the two instances are conflicting when starting at the same time).</p>
  <p>Also, the fact, that earlier (when there were only the Win version installed) I was able to access the Windows version from WSL, indicates some strange behavior other than a port forwarding issue. (And my collegues use this setup (Win -&gt; WSL) at the moment without problem.)</p>
  <p>I've even uninstalled (deleted, because Artemis is simply unzipped, not installed) the Windows version, but it didn't solve the problem.</p>