Thomas, Most wildcard certificates that I have encountered do NOT include the domain, only subdomains. In other words "something.mydomain.com" would work but not simply "domain.com". I know you tried the actual CN, but perhaps some component is having an issue with the asterisk. If you wanted to make another test, you could try using a server name which is similar to something.mydomain.com.
Jim L. On Mar 3, 2013, at 7:41 AM, Thomas Simmons <twsn...@gmail.com> wrote: > On Sun, Mar 3, 2013 at 6:41 AM, Phil Mayers <p.may...@imperial.ac.uk> wrote: > When you enable "validate...", what are you entering as the server name? I'm > not sure wildcard certs work with eap under windows. > > Hello Phil, > > Initially, I unchecked "Connect to these servers" and left this field empty - > this is what I did with the self-signed cert that worked. I also tried > *.mydomain.com (the CN) and domain.com. I can purchase a standard cert to > verify this is the problem. > > Thomas Simmons <twsn...@gmail.com> wrote: > > >Hello All, > > > >I'm trying to get my setup working with a GoDaddy-issued wildcard > >certificate (I understand self-signed is recommended). I don't > >understand > >why this is not working and appreciate any input. What I have found so > >far: > > > >Everything works with self-signed certs. With the CA cert imported, > >"Validate server certificate" is not required. > >Everything works with GoDaddy certs on Android. > >Everything works with GoDaddy certs and "Validate ..." unchecked. > > -- > Sent from my mobile device, please excuse brevity and typos. > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
