Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About IT_Tropolis
About IT_Tropolis
Community Record
20
Posts
4
Kudos
2
Solutions
Badges
2 weeks ago
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 Client VPN.
... View more
2 weeks ago
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 connected to Client VPN to print to a Fiery print server that is connected to a large Canon copier/printer. Thank you, Bob H.
... View more
Labels:
- Labels:
-
Client VPN
-
Other
Mar 27 2024
6:00 PM
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. his home router to use different subnet.
... View more
Mar 27 2024
4:57 PM
Hi @PhilipDAth : 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 occurs. Thank you, Bob H.
... View more
Mar 27 2024
4:54 PM
Hi @alemabrahao : 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 the same device/laptop, he can ping the DC no problems. Thank you, Bob
... View more
Mar 27 2024
4:18 PM
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 other servers. This behavior just started a few days ago. When he is in the office on the LAN with the same device, a Windows 11 laptop, it connects to the DC successfully. Thanks so much for any insights! Bob H.
... View more
Labels:
- Labels:
-
Client VPN
Sep 21 2023
1:10 PM
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.
... View more
Feb 11 2023
9:40 PM
Does Meraki have a solution to turn-off the alerts in this case? It's not an issue as this is how the Synology handles NIC Teaming so I just want to stop the alerts from the Meraki.
... View more
Aug 3 2022
12:18 PM
3 Kudos
The Dell Optimization program causes this issue. Uninstalling the program resolves the issue.
... View more
Jul 28 2022
3:05 PM
MX is running 16.16.1. I just sch. it to upgrade to 16.16.4 overnight.
... View more
Jul 28 2022
12:48 PM
Yes, Windows 10. No, not AnyConnect, rather Windows 10 native L2TP VPN client/connection. After VPN connects, user gets assigned a Client VPN IP just like all Client VPN users. The IP does not conflict with her assigned local IP from her wireless router.
... View more
Jul 28 2022
9:41 AM
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 remote device but same issue. Tried different physical location/different ISP connection from remote device but same issue. Updated device drivers & BIOS (Dell laptop) but same issue. Anybody else experience this issue before? Thank you, Bob H.
... View more
Labels:
- Labels:
-
Client VPN
Aug 5 2021
8:29 AM
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 connect after re-discover. SSID 2 still allowing connections (different VLAN). Enabled SSID 3 and it's allowing connections. Any ideas why SSID 1 would just all of a sudden disallow connections? Thank you, Bob H.
... View more
Labels:
- Labels:
-
Other
Jul 2 2021
4:30 PM
This issue is back. I've seen it in (3) different Windows 10 Build 19042 devices in the last two days. I guess using rasphone.pbk is a workaround but hopefully Microsoft will fix it soon. Is Cisco putting pressure on Microsoft to fix it?
... View more
Jul 2 2021
4:24 PM
This issue is back. I've seen it in (3) different Windows 10 Build 19042 devices in the last two days. Is Cisco putting pressure on Microsoft to fix it???
... View more
Jul 2 2021
3:33 PM
Hi Jason: Did you ever find a solution to this issue? I've seen this on (3) devices in the past 2 days. Thanks, Bob H.
... View more
Jul 2 2021
2:29 PM
I just started seeing this issue again, on (3) different Windows 10 computers in the past 2 days. All 3 are Windows 10 Build 19042 but that may be a coincidence. VPN working then all of a sudden it won't connect. Authication method set to General Authentication. Changing it to Username and Password caused the Adapter settings to have the Security tab option for protocols greyed out so neither PAP nor CHAP are checked. Fixing the Adapter settings resets the VPN authentication from Username and Password to General, and round and round we go. Was their ever a fix for this issue besides using a 3rd party VPN s/w, i.e. did MS fix it?
... View more
Oct 30 2020
12:06 PM
Hi @GreenMan Is there a way to workaround/cfg. for this scenario to work, i.e. for Client VPN users to be able to access LAN resources when coincidentally their outside LAN subnet from which they're connecting is same as the office LAN subnet? Thank you!
... View more
Oct 30 2020
11:48 AM
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 IPs on the LAN. Split tunneling is NOT cfg. and they can connect to Internet sites, and those sites see their public IP as the office IP, not their home ISP public IP. If user physically takes same MacOS machine to a Starbucks or another house it works as expected, i.e. they can RDP to their machine at the office and they can connect/open the Intranet site. At location w/issue, they have Frontier FIOS w/an ARRIS NVG468MQ router. It uses 192.168.254/24 network. The office coincidentally uses the same LAN subnet 192.168.254/24. Is this the cause? Thanks for any insights!
... View more
Jun 2 2020
11:29 AM
1 Kudo
Hi: I have numerous users working remotely on MacOS devices connecting to a web site hosted behind an MX84. I've configured the MX84 with a 1:1 NAT rule allowing their public IP. It's been working with months without an issues. As of yesterday, they can no longer connect, i.e. https://MyWebsiteBehindMX84.com returns error page: Server is unavailable now. Please try again later or contact your administrator. Their public IP has not changed and we verified another non-MacOS device on their LAN can connect. I'm thinking a MacOS update may have caused this issue, perhaps something to do with IPv6? Any insights are greatly appreciated! Thank you, Bob H.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 614 | 2 weeks ago | |
| 4050 | Aug 3 2022 12:18 PM |
My Top Kudoed Posts
© 2024 Cisco Systems, Inc.
