Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi:I'd like to know if Talos still blocks the EFI Fiery printing protocol over Client VPN with no way to allow. Thus, I cannot update an MX past 15.44 firmware version because many users in the network use the Fiery Command WorkStation s/w when conn...
Hi:I have a client where the Domain Controller (Windows Server 2016) is refusing connections when he is logged into the Client VPN. He gets error, "The account is not authorized to log in from this station." He cannot even ping the DC. He can ping ot...
Hi:One user connecting to MX64 Client VPN loses Internet access after connecting.Dashboard does show user as connected to Client VPN.Other users connecting to same MX appliance with Client VPN do not have issue.Tried wireless & wired connections from...
Hi:MX68W. This morning users came into office and all of a sudden cannot connect to SSID 1. All users/clients affected.Tried renaming the SSID but still cannot connect. Tried forgetting the wireless network on a Windows 10 client but still cannot ...
Hi:User has MacOS machine. User connects to Client VPN successfully. They obtain Client VPN IP address and I can ping their IP. But they cannot RDP to their computer on the LAN via IP address or connect to the LAN Intranet. They cannot even ping ...
Update: I've updated firmware to version that uses NBAR and Talos, kept the Layer 7 rule denying all peer-to-peer traffic, and confirmed that printing is not denied from the Fiery Command Workstation s/w to Fiery printer when user is connected to Cl...
Think I figured out the issue though I haven't been able to test the resolution yet as I don't have access to cfg. the user's home router. His home network is using same subnet as office subnet, which will cause conflicts I believe. Plan to re-cfg....
Hi @Philip D'Ath :His account in AD does not have a login restriction. If he's in the office, on the LAN, with the same device/laptop, he can ping the DC and access domain resources, no problems. It's only when he's on the Client VPN this issue occ...
Hi @alessandrodematos :That article is not relevant because the user can connect to the Client VPN without any issues. The issue is that after connecting to the Client VPN, he gets blocked from access the DC. If he's in the office, on the LAN, with...
Is this issue w/Ventura and L2TP Client VPN connections resolved? One of my users has a MacBook running Ventura ver. 13.5 and is having a problem connecting to the Meraki Client VPN.
