I setup cisco wireless controller 2500 connecting 2 Aironet APs, with windows 2008 NPS as radius server (server certificate installed), via
[WPA2][Auth(802.1X)], MAC Filtering
Now I have domain computer (laptop) connected to SSID which provides direct to the LAN dhcp server. That means my notebook got same ip range as when it connected to LAN.
The user used cached domain logon info to logon the computer, then the wireless profile started to connect with radius server which has User group policy.
Problem is the notebook (logon as normal domain user) browse \\"domain name" or any \\hostname will take 10 mins or more to pop up with "enter network password" or sometimes "The specified netwrok name is no longer avail"...
However ever if I simply \\192.168.2.x which is the host's ip address, I got list of share folders instantly.
And when I disable the wireless and connect to the LAN cable, I had no problem to browse any shared folders.
Is there any setting in wireless controller block anything? I did not configure anything on APs.
Help please as it had hold me several days of work.
I dont think its the WLC. The WLC is a extension of the wired network. But it telling that it looks like something is going on.
A few things of interest
Is your DNS valid when you connect to the wireless also what wireless supplicant are you using ?
Problem fixed. Because I setup the 192.168.2.x as "virtual interface", which totally confused the WLC.
So what the hell the virtual interface is used?
The virtual interface should be 22.214.171.124
The controller typically uses this interface for web redirect when using the web splash page (web auth).
The controller also uses 126.96.36.199 as a virtual proxy for the actual DHCP server (if configured)
Just to add, it can be any ip address, just not an ip address that is routable internally in your network.
Sent from my iPhone
In the olden days 188.8.131.52 IP was not made public, but now you can see this IP address in the internet, hence it is not advisable to use that for the virtual network.
Preferrably you can assign an IP in the 192.0.2.* range
To add to the virtual 184.108.40.206 IP address drama
Since 220.127.116.11 was given to someone. If you had a wieless user and they went to that specific web site that resloved to 18.104.22.168, the user would not get directed to that web site. The WLC would see 22.214.171.124 as a connected route, thus you would hit the WLC.
So how do I Create the other vans on the controller? Do you have a link to some documentation that explains how to do that.
Sent from Cisco Technical Support iPad App
Tony not sure I follow.. Did you mean to repond to another thread?
If i setup dhcp pools on WLC for wlans, what is the dhcp server address for wlan interfaces? the management ip or virtual interf 126.96.36.199?
Internal dhcp configured on the wlc, you will always use the management ip address for the primary dhcp on the interface.
Sent from my iPhone