Meraki

Stach53 · ‎Nov 23 2019

We're all Win10 but being x-manufacturing, I understand the need to retain old OSs. Still wish they would allow both user name types. It doesn't take much to confuse the end users when you have different naming conventions at password time.

Stach53 · ‎Nov 22 2019

UPN will not work with older clients like W98 and prior. Maybe it's for backward compatibility but W98?? Thanks for the input JD.

Stach53 · ‎Nov 22 2019

It is using Active Directory authentication.

Stach53 · ‎Nov 22 2019

Community Members I have been unable to use UPN (User Principal Name) when entering credentials for Win10 client VPN. The AD connected PCs accept UPN without issue but client VPN requires sAMAccountName. Basically, client VPN requires this format Domain\Username But any other connection to the DC can use the Username@DomainName format. Has anyone else experienced this and if so were you able to fix it? Best Regards, Stach53

Meraki

Community

About Stach53

Stach53

Community Record

Badges

Re: MX65 Client VPN with UPN

Re: MX65 Client VPN with UPN

Re: MX65 Client VPN with UPN

MX65 Client VPN with UPN

Re: MX65 Client VPN with UPN