Another bug for 5.0.3

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Another bug for 5.0.3

L6 Presenter

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


L4 Transporter


why you are using the interface with a port number?

Because 443 is busy for some of our customers.And they do not want to change port of the other service.

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

No you cannot use this with (Bridge mode Modem)ppoe interface.PaloAlto does not support this.

But for other layer3 interface yes you can use loopback.

Also there is a document for that

Ok.. making an assumption here.  in 5.0.2, you could have as the GW. Instead of configuring your portal to send down, (in 5.0.3) why not have it continue to send and just ask those new users to add the :444 port number (presuming existing GP users already have in their configuration on the GP agent) Would that work.  No reason why it should not.  Thoughts?

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.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!