Windows server vpn client for mac3/3/2023 We would like to gain more control over which client machines can connect to the VPN endpoint PS: Ideally, we would like to keep using Windows 2016 Server RAS as it enables us to use stock networks settings on client machines compared to e.g. Because of my limited knowledge, I'm not even sure stock Windows 2016 Server RAS/VPN will allow us to restrict which client machine are allowed to connect.Ĭan someone please help me assemble this puzzle? Thanks! That is move away from using a shared secret for machine authentication.įor now, I don't know whether we can/should keep using LT2P or whether we should move to IKEv2. And machine authentication uses a shared secret.įrom there, we would like to gain more control over which client machines can connect to the VPN endpoint. User identification uses Windows AD login/password. We're currently running Windows 2016 Server RAS/VPN server and we have Windows, macOS and Linux clients that connect to the VPN endpoint with L2TP over IPSec. ![]() ![]() I quite don't know where to start so I'll describe the needs in hope someone can help me figure out the building blocks that need to be assembled.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |