Merge pull request #191 from zerotier/laduke/190-windows

Laduke/190 windows

docs/faq-windows.md

@@ -37,6 +37,10 @@ If the purpose of your ZeroTier network is solely remoting into office workstati
 [Client Isolation Rules](./faq-rules.md#client-isolation) and [RDP Only Rules](./faq-rules.md#remote-desktop-only-rdp-only)
 :::
 
+### System Service Not Reachable by UI
+
+[System Service Not Reachable by UI](./windows-service-unreachable)
+
 ### Resolving `Port Error` {#port-error}
 
 If you're seeing `PORT ERROR` on Windows, it's likely that the driver did not get installed correctly for some reason.  To fix this, navigate to

docs/windows-service-unreachable.md

@@ -26,3 +26,21 @@ ZeroTier should now be reachable by the UI client when you restart it.
 ## Why does this happen?
 
 Not entirely sure. IP helper service is a windows service that provides tunneling for IPv6 over IPv4. IP helper grabs 9993 before ZeroTier can. The issue persists through reboots. In the resource monitor, you can see which ports are bound to which services. IP helper is the culprit.
+
+Do you use Docker or WSL and ZeroTier? One of those might be reserving the port in IP Helper.
+
+Try this in a Admin Powershell
+
+```sh
+netsh interface portproxy show all
+```
+
+is 9993 in the results?
+
+Try to delete the entry
+
+```sh
+netsh interface portproxy delete help
+```
+
+Or try killing Docker or WSL and see if the problem goes away. [Let us know](https://discuss.zerotier.com/c/community-support/8) what you find out.

sidebars.js

@@ -170,7 +170,7 @@ module.exports = {
             description: 'ZeroTier on Windows',
             slug: '/windows',
           },
-          items: ['faq-windows', 'chocolatey', 'winget', 'windows-lan-game', 'windows-unknown-node-id']
+          items: ['faq-windows', 'chocolatey', 'winget', 'windows-lan-game', 'windows-unknown-node-id', 'windows-service-unreachable']
         },
         /* ANDROID */
         {