From SecureW2:
The issue is noticed when the RADIUS server cert is signed by AddTrust External
CA Root (Cross signed by USERTrust RSA Certification Authority) and with the
recent windows 10 update. We are looking into this and should be able to
provide you an update.
Ryan Turner
Senior
We had a cert issue a few years back. Our intermediate cert authority got a
root cert of their own and it started getting deployed with major operating
systems. Devices that had the new root cert wouldn't use the old root cert, so
server validation failed. I don’t see how reinstalling the
On 07/30/2018 11:22 AM, Turner, Ryan H wrote:
> We aren't running your method, but we also haven't heard of any mass scale
> issues (doesn't mean there isn't). What did SecureW2 say?
They are telling us that it's an issue with our cert stack, which I'm having a
hard time believing.
We have a
We aren't running your method, but we also haven't heard of any mass scale
issues (doesn't mean there isn't). What did SecureW2 say?
Ryan Turner
Senior Manager, Networking
The University of North Carolina at Chapel Hill
+1 919 445 0113 Office
+1 919 274 7926 Mobile
r...@unc.edu
Good morning everyone -
We here at Penn have recently come across a strange issue with Windows 10 and
our new JoinNow installation.
The run down goes like this:
1) Connect to onboarding SSID
2) Run JoinNow
3) Authentication Loop on Windows 10
Doing some research into it, there are a
Not familiar with your setup or Meraki, but in NPS you can define a Radius
client at a subnetie. 192.168.1.0/24. Then define more specific Connection
Request Policies and Network policies. Don’t worry, NPS is smart enough to
match on the most specific radius client.
Client1 –
