GlobalProtect portal corrupt.

Reply
Highlighted
L2 Linker

GlobalProtect portal corrupt.

Running an 2050 Active Passive HA pair.

Yesterday I noticed that I couldn't login with the Globalprotect client. After some investigation I noticed that I could log in on the Globalprotect Portal web page, but after the login the page which offers the client downloads would not show up and the connection was reset after a timeout of ~30 seconds.

I suspended the active node, when the other node was active I could access the portal page and the client login was also working again. I rebooted the box with the portal page problem, but the login still doesn't work when I make this node active again.

Is there a way to reset the Globalprotect page one this device.

I'm running Panos 4.1.6, should I try "reinstall" in the software page?

Thanks


Accepted Solutions
Highlighted
L2 Linker

Re: GlobalProtect portal corrupt.

Thanks for your answer, but this doesn't change anything.

Edit:

Ok ,I think I narrowed the problem down to a DNS problem, I changed dns and service route for the dns, now that I rolled back this changes I have it back working.

Somehow the LDAP query to our AD for the users seems to get broken by this change, not sure why though. The changes seemed correct to me.

Edit2:

Found it, because I changed the service route, security policy rules where wrong/missing for accessing the LDAP.

View solution in original post


All Replies
Highlighted
L5 Sessionator

Re: GlobalProtect portal corrupt.

If you are sure that the config has not changed.Try restarting the process slvpn-web-server process which serves web-pages for GP.

CLI command:

> debug software restart sslvpn-web-server

-Ameya

Highlighted
L2 Linker

Re: GlobalProtect portal corrupt.

Thanks for your answer, but this doesn't change anything.

Edit:

Ok ,I think I narrowed the problem down to a DNS problem, I changed dns and service route for the dns, now that I rolled back this changes I have it back working.

Somehow the LDAP query to our AD for the users seems to get broken by this change, not sure why though. The changes seemed correct to me.

Edit2:

Found it, because I changed the service route, security policy rules where wrong/missing for accessing the LDAP.

View solution in original post

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 Live Community as a whole!

The Live Community thanks you for your participation!