I recently purchased an ASA 5505 for my organisation and i have run into a bit of an issue with the Clientless SSL VPN.
The problem is that port 443 is currently forwarded to our web servers so before purchasing the device i thought i would be able to add mutliple outside interfaces to get around this problem but after receiving the device and talking to cisco (tech wasnt very helpful) it doesnt seem to support 2 interfaces different gateways, and i cant add a second interface that has an IP in the same subnet as the outside interface. The asa doesnt also seem to support secondary ip addresses.
So I am wondering if anyone has any ideas how i can have the Clientless SSL VPN work without changing its port so that users dont have to enter the port every time they go to it.
The problem is that port 443 is currently forwarded to our web servers so before purchasing the device i thought i would be able to add mutliple outside interfaces to get around this problem but after receiving the device and talking to cisco (tech wasnt very helpful) it doesnt seem to support 2 interfaces different gateways, and i cant add a second interface that has an IP in the same subnet as the outside interface. The asa doesnt also seem to support secondary ip addresses.
So I am wondering if anyone has any ideas how i can have the Clientless SSL VPN work without changing its port so that users dont have to enter the port every time they go to it.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 13 Comments.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 13 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.