Prisma Acess Agent EPM issue

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

Prisma Acess Agent EPM issue

L2 Linker

I have a PAA agent installed onto a Windows machine and when the vpn tunnel is down the EPM status is up and working but as soon as we bring the vpn tunnel up the EPM status goes down indicating a SSL handshake failed, now ive eliminated DNS issue with/without tunnel, all good, ive disabled dencryption of any *.gpcoudservice.com traffic within prisma, and also done testing with the forwarding profile to ensure  *.gpcoudservice.com also goes direct and not down VPN tunnel from agent. One thing to note according to the documentation, and on other customers deployments the PAA domain should be <company-name>.epm.gpcloudservice.com, now for my tenant the domain suffix is .lab.gpcloudservice and not .epm, this is a demo tenant so not sure if this is correct.  Has anybody seen this before

Thanks

0 REPLIES 0
  • 90 Views
  • 0 replies
  • 0 Likes
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!