Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About DrakeKammer
Community Record
7
Posts
4
Kudos
0
Solutions
Badges
Feb 29 2024
7:10 AM
Solved. Thank you. Added routes to azure network gateway for the highest numbered VLAN and 6.X.X.X
... View more
Feb 29 2024
7:10 AM
Added routes to azure network gateway for the highest numbered VLAN and 6.X.X.X
... View more
Feb 26 2024
12:36 PM
2 Kudos
one of the first things I tried after seeing the server 2019 bug.
... View more
Feb 26 2024
12:35 PM
2 Kudos
Might be on to something. Yes I can ping VLAN 300 from the on-prem, but not from the azure vm. I can ping other on-prem devices. But it doesn't appear I can talk to VLAN300.
... View more
Feb 26 2024
12:17 PM
So since the original Radius server was on-prem, VLAN priority didn't matter? As it currently stands, using the on-prem radius server, our highest VLAN is 300, and the VLAN where the on-prem Radius server lives is on VLAN 1. That's why I'm somewhat confused. But since we're moving to a S2S tunnel for radius, it needs to be in the highest VLAN possible? Where as on-prem it didn't matter?
... View more
Feb 26 2024
9:01 AM
What if VLAN 10 isn't where the Radius server lives, but rather VLAN 1.
... View more
Feb 26 2024
7:19 AM
We've migrated the on-prem Active Directory environment to azure and have an existing VPN pipeline. We're struggling to get Meraki to send the requests over the S2S VPN. We're using the NPS azure vm private ip within the meraki portal. We thought since there was an existing VPN connection, that we could just spin up a new NPS/DC and change Meraki to forward the request to the azure vm via the S2S vpn. I have event logs of on-prem devices talking to azure resources over the S2S, but cannot get the radius request to flow, or so it seems. Any layers or breaking points to look into? I don't have good log files as of yet.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 1568 | |
| 2 | 1568 |
© 2024 Cisco Systems, Inc.
