Controllerless Networks

Hi all,

 

I've got some wireless laptops that need to authenticate against our AD. Since the users don't have a wireless connection at logon, they can not authenticate and logon...

 

I tried this: http://www4.uwm.edu/technology/authenticated/wifi/uwm/upload/Windows8-2.pdf

 

But this doesn't seem to work.
Sometimes when the user has already a profile on the laptop, he can log on, but no GPO's or scripts are pushed to the client.
When I try to make a wifi connection when I'm logged in, no problem...

Once I have a connection and I log off and then reconnect as another user, everything works fine.

Reboot or shutdown gives a problem...

 

I've tried to add a computergroup to the NPS, but this doesn't work either. (or I'm doing it wrong)

I've got Aruba 105 IAP's, with Radius configured and working.

 

Does anybody have an idea?

Kindest regards,

 

Stijn

Step #16 in that document should be User OR Computer Authentication.

---

@cjoseph wrote:

Step #16 in that document should be User OR Computer Authentication.

---

I also tried that from the first time but no success...

It is only one of the things that need to be in place for this to work: We need to see the entire failed message on the radius server when the computer attempts to authenticate to know what is not working.

---

@cjoseph wrote:
It is only one of the things that need to be in place for this to work: We need to see the entire failed message on the radius server when the computer attempts to authenticate to know what is not working.

---

I was looking in the eventlogs but can not find the failed loginattempts.
It only shows when it was succesfull... Can i create another filter or where do I have to look? (Server 2012)
On the Aruba VC it says that the credentials have been refused by the radius server.

 

Regards,

 

Stijn

Check the logs in the Event viewer under Custom Views > Server Roles > Network Policy Server

 

 

Strange...

There is not 1 eventid: 6273?

On the server eventlogs all I see are succesfull logins...

 

Very strange

 

Here's what the eventlog says when it's succesfull: see att.

 

 

Usually when you are doing single sign-on, you want to leave the "Automatically use my Windows logon name and password" checked because it will use those credentials to authenticate you to the network before contacting AD.

---

@cappalli wrote:

Usually when you are doing single sign-on, you want to leave the "Automatically use my Windows logon name and password" checked because it will use those credentials to authenticate you to the network before contacting AD.

---

I know, and that's how i want to use it.
But when i disable that, it gives me an extra set of textfields to fill in the credentials for the Wifi. That way when you enter the (same)credentials it shows you that it is trying to connect to the Wireless network prior to loging on to the network.

 

When you check the box you mention, it just geives me a logon error...

 

Stijn

After you make the change, do you reboot? Sometimes the logon session becomes cached.

Yes, I do a reboot...
We know it makes a difference.