![]() I was able to get this resolved / working. We have a large traveling workforce that doesn't always get GPO updates in a timely manner because they are off the domain most of the time. I'd like to avoid having to push out a GPO to get this going. I think this is a certificate issue on the windows end stations, but i am not sure how to fix this. Logging Results: Accounting information was written to the local log file. Network Policy Server granted access to a user.įully Qualified Account Name: DOMAIN\user.nameĬalled Station Identifier: E2-CB-AC-B5-5B-0A:SSID NAMEĬalling Station Identifier: 80-B0-3D-7F-EA-EA There are never any reject or denied message in NPS logging (see below) NPS doesn't give any useful output, and I know its validating accounts since iPhones and Mac OSX computers are able to get onto the wireless network. The thumbprint matches a cert issued by a trusted AD intermediate CA, user acceptsģ) Immediately get a prompt "Can't connect to this network" Our workstation environment consists of almost exclusively Windows 10 PC's and they all seem to do the same thing when a user tries to connect to wifi in the building:ġ) Get prompted to authenticate (check "use my windows user account" or manually type in AD creds)Ģ) Windows prompts about the certificate. Macs and Apple IOS devices can successfully authenticate against AD using RADIUS, but only after they "Trust" the AD CS certificate used on our Domain. So, i've gone through much of what you've already outlined and get the same interesting behavior. ![]() The "Conditions" allow the proper AD user groups to authenticate ex: DOMAIN\Domain Users The right certificate is selected under the NPS Policy > Constraints Tab > Microsoft: Protected EAP (PEAP) options > Edit Protected PEAP Properties One thing I wanted to mention is to be sure that your NPS Network Policy is configured per the Meraki Documentation for 802.1X authentication (in addition to having your RADIUS Clients portion configured) since I found it needed both in order to test from the Meraki Dashboard. So I can sympathize with your struggles, I'm dealing with almost the same thing. Interesting to read your post, i'm in pretty much the same boat. I get pretty much the same error logged when trying to connect from my laptop. The NPS Account log shows this when I click the Test button: I had been running 2012 R2 but decided to wipe it and install 2016 afresh as though maybe RADIUS worked better!). I have Accounting enabled on the Windows Server (which is now a DC running Server 2016. No matter what I try though, I can't get my phone or laptop to connect, nor get the Test function to succeed from the SSID > Radius Servers section. You'll need this later.Okay so I've spent several DAYS on this and seem to be getting nowhere I'm starting to get fairly frustrated having followed numerous guides exactly. Make note of the name of this PC under How to connect to this PC. When you're ready, select Start > Settings > System > Remote Desktop, and turn on Enable Remote Desktop. To check this, go to Start > Settings > System > About and look for Edition. For info on how to get Windows 10 Pro, go to Upgrade Windows 10 Home to Windows 10 Pro. ![]() Select the remote PC name that you added, and then wait for the connection to complete. On your Windows, Android, or iOS device: Open the Remote Desktop app (available for free from Microsoft Store, Google Play, and the Mac App Store), and add the name of the PC that you want to connect to (from Step 1). In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect. On your local Windows PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection. ![]() ![]() Use Remote Desktop to connect to the PC you set up: Make note of the name of this PC under PC name. Then, under System, select Remote Desktop, set Remote Desktop to On, and then select Confirm. When you're ready, select Start, and open Settings. Then, under System, select About, and under Windows specifications, look for Edition. For info on how to get Windows 11 Pro, go to Upgrade Windows Home to Windows Pro. To check this, select Start, and open Settings. Set up the PC you want to connect to so it allows remote connections: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |