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 A_Swope
A_Swope
Just browsing
Member since May 23, 2023
Jul 28 2023
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Jul 28 2023
5:46 AM
@BlakeRichardson: We have nothing pushing option 12, but perhaps he does at home? @Brash: No, the two names are "Davids-MacBook-Pro.local" and "Davids-MBP.lan"
... View more
Jul 27 2023
1:27 PM
I don't care how the client show up on the Meraki dashboard. I am trying to figure out why the hostname on the client itself changes when he connects to the Meraki via AnyConnect, and changes back when he disconnects.
... View more
Jul 27 2023
1:23 PM
First screenshot shows his local hostname to be Davids-MacBook-Pro.local when connected to VPN. When he disconnects, the hostname changes to Davids-MBP.lan. We have no idea where the second value is coming from. This is not AV related, other than the AV console is how I discovered this weirdness.
... View more
Jul 27 2023
8:13 AM
I can see his client in the list, but there's no mention anywhere on his connection or his details page of this mystery hostname that VPN gives to his computer when he connects.
... View more
Jul 27 2023
7:50 AM
Neither the when-connected nor when-disconnected hostname is in the client list. I don't think it's coming from there.
... View more
Jul 27 2023
6:42 AM
Our AV management software lists by hostname, and we are getting duplicates for our Mac users. We've traced it down to this: when a Mac user connects to AnyConnect, something is dynamically changing the computer's hostname. See below of before and after disconnecting. However the local hostname settings in the UI remain constant regardless of his VPN connction status: How do we get the hostname to stay static?
... View more
Labels:
- Labels:
-
Client VPN
May 23 2023
2:25 PM
I know this is old, but here's another vote to allow rules to be disabled. My rep convinced me to "upgrade" from ASA-5525 due to them reaching EOL. These MXs are not nearly as feature rich. Cannot NAT across internal ports, cannot disable rules, no test (apply) then commit pattern. On the other hand, traffic analysis is MUCH better. My two mfu use cases: testing a new rule; confirming an old rule is no longer needed.
... View more
© 2024 Cisco Systems, Inc.
