Hello, I got a weird issue with my XG105w:
I have set up several VLans as follows:
Vlan1: 192.168.16.0/24
Vlan10: 192.168.10.0/24
Vlan20: 172.16.16.0/24
Vlan30: 10.16.16.0 / 24
Vlan40: 10.0.0.0/24
My local servers (domain controller active directory, file server, RDS server, WDS server, server for our ERP etc ...) are in Vlan1. I have set up rules in the firewall of the xg105w so that the vlan1 communicates with all the Vlans except the vlan20 and 40, and I have also made rules in the other direction, that all the Vlans with the exception of the Vlans 20 and 40 communicate with the Vlan1. Until then all is well, I ping well from one Vlan to the other etc ...
The issue is on my web servers. If I am in the Vlan10 and I type https://DNSName of my IIS server, It displays the page with the certificate error, like always, but when i decide to continue, it dispays a 502 bad gateway error and i do not access it, but if I type https://IPAddress I access it well. On the other hand, if I am in the Vlan1, https://DNSName works well. I do not understand how this is possible, since if I ping the DNS name of the server, this resolves me the corresponding IP address and in windows explorer \\DNSName works for the shares.... It's just web traffic that does work from one Vlan to the other, yet in my firewall rules I've allowed ALL traffic from one vlan to another.
The problem occurs only from vlan to vlan and from VPN to VLan, because if I create a firewall rule that redirects port 443 coming from the WAN to my server in LAN, it works well.
Thank you for your help.
This thread was automatically locked due to age.
