I have a wireless network that is using a 5508 WLC (running 18.104.22.168), and AIR-LAP1142N-A-K9. My users are having trust domain relationship issues with their laptops when connected to WiFi. I have isolated this problem to WiFi by connecting the Laptops directly with a LAN cable and they do not have this issue. I think this has something to do with AP isolation but am not sure. Does anyone have any clue what could be causing this?
Solved! Go to Solution.
Can you explain a bit more about what the "trust domain relationship issue" is ?
The end result of a wireless association is that the client session is in RUN state and its traffic is fed into a VLAN (for central switching), or in the case of FlexConnect, the traffic breaks out of the AP onto a VLAN on the attached switch. There should be no impact for the upper layers (AD domain or otherwise). If you are plugging users into a switch port then you may not be making a fair comparison, unless you can prove that they ended up on the same VLAN.
One VLAN to rule them all!!! Nice ... let's park that discussion. FlexConnect is just an alternative to Central Switching when the controller is central, but APs are spread over various geographic locations - the traffic stays local.
Can you still please explain what this "domain trust issue" is?
Ok, when a computer connected to wifi trys to logon with thier user account they get "The trust relationship between this workstation and the primary domain failed." Though if I take and cable computer in they can log on just fine. This only happens with the newer model APs in the room, not the where the older models are.
I'm pretty sure I don't, as I didn't change anything to the setup of the Wi-Fi other than adding new accessp Here's another interesting little tidbit to add to this. My wireless devices cannot print from my cable to printers. So if I plug the wireless devices in to cabling they can print just fine.
Yes they are all on same VLAN. Its not any of those. The APs should let this all work. The old ones I replaced didn't have this issue. Only thing I can think of is it has to do with the APs. Only change to network was the new APs.