Jump to content

Recommended Posts

Posted

Hi there

 

Usual stuff on the first day back from half term.

 

Four teacher laptops refuse to connect to the school network Meru wireless. They did connect before half term perfectly.

 

I have done everything. Updated drivers, rolled back drivers, taken the laptops out of AD and back, released and renewed uninstalled and re-installed etc etc.

 

They will connect to my phone so I can't see that it's the card at fault.

 

Other laptops in the school are fine.

 

Anybody - any clues would be appreciated.

 

J

Posted
Random idea but you haven't run out of IP Addresses have you? we had this happen before, resulted in us kicking a lot of the BYOD devices off the network to make room.
Posted (edited)

have you inadvertantly blocked the MAC addresses?

 

couple things you could try

 

- try spoofing the MAC address by changing the physical address option (not always called this) on the network interface properties.

- remove your wirekess ssid from the laptop and reconnecting

- in cmd

netsh int ip reset c:\resetlog.txt
netsh winsock reset

Edited by dapaulio
Posted

Have tried the above and not made a difference.

We have a Meru controller that is giving a 802.1x authentication failure which i presume is the problem, but unfortunately I cannot seem to find a solution around it.

Anyone have any other suggestions?

Posted

Yes it is. It picks it from the NTP server. All other GPOs and other network policies apply correctly when connected through physical cable.

Have also taken the laptop off the domain and tested and get the same problem.

It seems to be just a few laptops in the network, most devices seem to be able to connect to the wireless.

Posted
Expired certificates on controller or server or laptop?

Permanent license on controller which is active

if its just 4 being daft id guess the laptops but might be worth checking the server etc

Posted
Is the Meru controller acting as the RADIUS server or is it talking to a Windows server hosting that role? I'd have those logs open and then attempt to connect a couple of times with a known-bad laptop to see if it can be a bit more verbose.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...