01-02-2018 09:32 AM - edited 07-05-2021 08:02 AM
I don't recall having this issue before but I upgraded several ME sites to the latest code.
I can access the controller from the local wired subnet without any issues. If I access the wireless subnet that places the laptop on the corporate network lan (same network lan as the wireless controller address) I can no longer manage or access the wireless controller. Still works with an lan address but no longer from a wireless address in the same exact subnet. Any ideas if there is a setting somewhere preventing this? Not a show stopper but an real inconvenience! Thanks
Solved! Go to Solution.
01-02-2018 04:10 PM
Backleveled code on all ME subnet setups and problem is gone....code level 8.6.101.0 is bad and prevents management via wireless. Looked a the access point info and it has it enabled on them using the CLI so the bug appears to be in their new code release. Using 8.5.110.0 until they come out with a newer version that works. 8.5.110.0 does not have the issue and allows management through the wireless connection on the same subnet as the controller.
Closing
01-02-2018 11:55 AM
Hi
Take a look on the management tab at "Management via wireless"
-If I helped you somehow, please, rate it as useful.-
01-02-2018 12:08 PM
01-02-2018 12:21 PM - edited 01-02-2018 01:32 PM
Sorry, I didn't read it right, though it was WLC. Mobility Express first setup is done via wireless so this limitations shouldn't exist.
Is it possible the firewall on your machine is preventing you to access via WiFi?
-If I helped you somehow, please, rate it as useful.-
01-02-2018 12:40 PM
01-02-2018 01:34 PM
That's an idea. WLC block by default access via wireless and thus need to be permitted but ME is different as the first setup can be done via wireless.
Good luck.
-If I helped you somehow, please, rate it as useful.-
01-02-2018 04:10 PM
Backleveled code on all ME subnet setups and problem is gone....code level 8.6.101.0 is bad and prevents management via wireless. Looked a the access point info and it has it enabled on them using the CLI so the bug appears to be in their new code release. Using 8.5.110.0 until they come out with a newer version that works. 8.5.110.0 does not have the issue and allows management through the wireless connection on the same subnet as the controller.
Closing
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide