Nethserver and Guacamole are installed and working perfectly fine when accessed directly by ip address. When done port forwarding, I am able to see nethserver welcome page, but when I do http://192.168.1.149/guacamole, I am hetting This site can’t be reached 192.168.1.149 took too long to respond. Please Help.
Server: Windows2016
ISP has assigned the ip address of 192.168.1.149(server) behind their firewall, and I have a public IP that is getting forwarded to it(all ports). My dhcp/firewall server IP address is 192.168.2.1(its a vm on the server) , and nethserver\Guacamole is installed on ip address 192.168.2.2(also a vm on the server). Port forwarding is happening on the windows server with the ip address 192.168.1.149(server).
You don’t state it, but I assume your Windows 2016 server is running Hyper-V to run your VMs.
You also don’t state which port(s) are being forwarded.
Also missing is the info from where are you testing? Internally, from the Windows server GUI?
Or are you actualling trying to use an internal LAN IP from the Internet, eg via a Smartphone Hotspot to test? (Internal LAN IPs do NOT work over the Internet!).
Thanks a lot. Looks like I am making some progress. I was not forwarding port 443. I am able to get guacamole on http://192.168.1.149/guacamole(earlier I wasnt). Its still not working from the external IP address. I think its an issue with http vs https as the browser keeps trying to connect vis https, and not http. I am out of my league here. Any ideas on what to try next?
yes, to test it, I pointed a domain to the public ip address and I can access it with http:// (its just nethserver welcome page)but not with https://, even though the SSL is in place. In either case, I am unable to get to guacamole.
Well, since it’s working from the “LAN” side, I’d say it’s either an issue with your ISP / Port Forwarding / Firewall / Windows 2016, but not with NethServer.
I do know quite a few firewalls, but as you haven’t provided any info on yours (The VM, not Windows 2016) I can’t provide any hints…
The next issue is that this is not a Windows support forum, nor one for unnamed firewalls.