802.1x on a wired network

Soldato
Joined
8 Nov 2002
Posts
9,128
Location
NW London
Having a play with 802.1x security at the moment and there's one thing I'm not sure about.

With both eap-tls or peap, you get no network connectivity until the user logs on and is authenticated. If that's the case, if you deploy software via a computer GPO, would these always fail, as they usually happen during startup (before the login screen comes up)? I also assume that any computer GPOs would only get applied during the usual GP refresh periods.

Is there any method (without resorting to very proprietary protocols) that just authenticates the computer account to allow connectivity, ie. turn on computer as long as computer credentials/certificate authenticate, network connectivity is allowed, so even if nobody logs on there is network connectivity.
 
No idea how it was setup but at my previous work we had it setup so that the machine had a cert and when the machine booted up it authenticated with the network, rather than it being user based. So it can be done, and don't think it was particularly hard to setup.
 
I believe there's also ways to dump unauthenticated users onto a different network (VLAN). So you can provide certain connectivity (AV updates, AD connectivity for GPO) to users without authenticating them. Never implemented it myself, but have seen network designs which do exactly that.
 
I believe there's also ways to dump unauthenticated users onto a different network (VLAN). So you can provide certain connectivity (AV updates, AD connectivity for GPO) to users without authenticating them. Never implemented it myself, but have seen network designs which do exactly that.

Yeah that will be something we set up in the future, hopeully with NAP health checking added into the mix.
 
hmm, i've probably still got my configs for when we implemented this. We used the computer certs to put machines into diff vlans. Shall try and dig out the configs...
 
Back
Top Bottom