cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1977
Views
5
Helpful
6
Replies

Mobility Express access from wireless connection fails 8-6-101-0

gp1200x
Level 2
Level 2

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 

1 Accepted Solution

Accepted Solutions

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

View solution in original post

6 Replies 6

Hi

Take a look on the management tab at "Management via wireless"

 

 

 

-If I helped you somehow, please, rate it as useful.-

There is no Management via wireless that we can find on any screen. Any idea where exactly it is? This is Mobility Express 8.6.101.0

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.-

 

 

Nope...none of our laptops can access the management from the wireless....if the controller is in the same subnet...I can access other controllers in other subnets though. The controller knows I am on wireless and it appears to prevent access to it once my WAPs are configured with multiple wlans and trunks....downgrading a unit to see if this just started with newer code since I used to run 8.3.133 and don't recall having issues.

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.-

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

Review Cisco Networking for a $25 gift card