Remote Access Issue - R9.0 and Up - Failed to Communicate

[jokermia]

We have a customer who recently switched VPN access software, and since then we've lost remote access to all R9.0 and up systems. Instead, we get the dreaded "Failed to Communicate" error. Is this a security issue related to R9.0 and above? Ports, settings, etc? If so, is there a resolution? As an FYI, nothing has changed other than the VPN. Thank you in advance for any help.

 

[Bolinious]

This is why I have an old desktop sitting at the site. I just remote to it to do changes. One of my clients also has VM pro which is running on this same system for the files, etc.. for their complicated queue.

And yes, I was warned about RDP and potentially having issues, but we use screenconnect to get to the computer.

As for your specific issue, it does look like the VPN is only allowing certain ports to communicate which would be what is causing your errors. What specific VPN software is in use now. that might assist in figuring out a fix.

 

[jokermia]

The VPN software is Palo Alto Prisma, thanks - should have included that in the post.

 

[jokermia]

Bumping this to see if anyone knows what security measures would prevent remote access to a customer site on Palo Alto remote access software, or what ports need to be open on the switch for R9 and above

 

[Ekster]

For remote access of the IPO, you need these ports

22

80

411

443

7070

7071

7443

7444

8443

9443

50790 - 50814

ICMP to Avaya system needs to be allowed too

 

[nnaarrnn]

My guess is that your VPN client credentials (username) don't permit access to the vLAN the IPO is on. Have whoever manages that Palo Alto fix that and I'm sure you'll be fine.