Hi there,
I've set up a Virtual Server on a 60D for Load Balancing purposes. That works fine so far, but creating a virtual IP with port forwarding mapped to the Virtual Server doesn't...
Configuring the port forwarding to one of the real servers instead of the virtual server works just fine though.
The setup with some imaginary IPs for illustration purposes:
Virtual Server: 192.168.1.10 Real Server #1: 192.168.1.11 Real Server #2: 192.168.1.12 Virtual IP VIP_1: 123.45.67.89 --> 192.168.1.10(TCP: 30001 --> 30000) | Interface: wan1 Virtual IP VIP_2: 123.45.67.89 --> 192.168.1.12(TCP: 30002 --> 30000) | Interface: wan1
"telnet 123.45.67.89 30002" succesfully establishes a connection. But "telnet 123.45.67.89 30001" times out. So VIP_2 works just fine, VIP_1 doesn't.
Any ideas how I could debug this or what the issue might be?
Or is this scenario simply not supported? Would there be any workarounds in that case?
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Why don't you create another virtual server with the public IP and the same real servers? Or did you already test this and it didn't work?
I'm facing the same problem but i couldn't manage to fix it ! can you share the configuration for it to understand your solution ?
i posted already about it here "https://forum.fortinet.com/tm.aspx?tree=true&m=176776"
Thanks
Does telnet directly to the IP of the virtual server work?
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1732 | |
1106 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.