Add firewall guide (in case of comms error)

Installation.md

@@ -3,6 +3,7 @@
 * [**Windows**](https://github.com/tidusjar/Ombi/wiki/Installation#windows)
     * [NSSM Service](https://github.com/tidusjar/Ombi/wiki/Installation#install-as-a-service-with-nssm)
     * [Windows Task Scheduler Service](https://github.com/tidusjar/Ombi/wiki/Installation#install-as-a-service-with-windows-task-scheduler)
+    * [Allowing Ombi through your firewall](https://github.com/tidusjar/Ombi/wiki/Installation#windows-firewall)
 * [**Linux**](https://github.com/tidusjar/Ombi/wiki/Installation#linux-systems)
     * [Apt Repo](https://github.com/tidusjar/Ombi/wiki/Installation#apt-repo-the-easy-way-only-debian-based-distros)
     * [Manual Install (all distro's)](https://github.com/tidusjar/Ombi/wiki/Installation#manual-install-the-less-easy-way-all-distros)
@@ -75,6 +76,16 @@ As an alternative to NSSM, you can use Task Scheduler to run `Ombi.exe` as if yo
 
 [How to WITH PICTURES!](https://imgur.com/a/oXEWW8z)
 
+### Windows Firewall
+To add a port forward in Windows Firewall, you have a few options.<br>
+Note that this is not the preferred method of access, and a [Reverse Proxy](https://github.com/tidusjar/Ombi/wiki/Reverse-Proxy-Examples) is recommended instead.<br>
+Replace the port in the below commands with your own port if you're running a different port than the default.<br>
+
+**Command Prompt**<br>
+`netsh advfirewall firewall add rule name="Ombi" dir=in action=allow protocol=TCP localport=5000`  
+
+**Powershell**<br>
+`New-NetFirewallRule -DisplayName 'Ombi' -Direction Inbound -Action Allow -Protocol TCP -LocalPort @('5000')`
 ***
 
 # Linux systems