03-20-2013 08:17 AM
When using port with address of External Gateway on Global protect, 5.0.3 does not accept this.
it is working on 5.0.2
03-20-2013 08:57 AM
why you are using the interface with a port number?
03-20-2013 08:59 AM
Because 443 is busy for some of our customers.And they do not want to change port of the other service.
03-29-2013 12:38 PM
Ok, so you can create a public IP loopback address and then use that as your portal. I agree that it appears to be a bug, but you have a workaround that allows you to upgrade to 5.0.3 (correct?) Thanks
03-29-2013 12:42 PM
03-29-2013 02:05 PM
Ok.. making an assumption here. in 5.0.2, you could have 188.8.131.52:444 as the GW. Instead of configuring your portal to send down 184.108.40.206:444, (in 5.0.3) why not have it continue to send 220.127.116.11 and just ask those new users to add the :444 port number (presuming existing GP users already have 18.104.22.168:444 in their configuration on the GP agent) Would that work. No reason why it should not. Thoughts?
03-29-2013 02:12 PM
Because if you don't write any port it uses 443 as I know.if you write in portal ....45 it will use port 443 by default.
When you connect to portal you do not choose your gateway(if you don't have a license and not configured) it automaticly goes trough the gw configured with 443.
So the problem is not portal , it is gateway.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!