DNS connection between building movements is not possible

[CCC3]

Both buildings use the same WLC,
You are using the same user band.

But if you move around the building, the wireless is automatically connected
Unable to connect to the internal network server.

In my opinion, communication with DNS server is not working well.

As a temporary measure, if you delete the SSID and log in again, it will be normal.

What's the problem?

[Scott Fella]

Well, on part is, does the device get an ip address and does that device also get a valid DNS server list? If yes, then it does seem like the DNS is not working as expected.  You should not be able to reach a server for an example, then roam, and not reach that server again.  You make sure that the device is not changing ip's? Also if you are using FlexConnect with local switching, you must make sure that the ap's trunk port are all configured properly of else, you will have a blackhole. You should identify the area and ap that are problems and take a closer look at everything.  Also can be an ap connected to a switch that is not forwarding the vlan to your core.

You should always provide the controller model, version, ap and any debugs.

[kiwonkwon8969]

The WLC is 5520, and the Version is 8.10.183.0.

There are 9115,2802,2702 different ap models.

The ap mode is used as local.

[Scott Fella]

Well... since you are using local mode, then I don't see why the issue would be with the wireless.  If the device stays connected and roams around, and you never loos connection, then it might just bean issue with the device or reachability to DNS.  I don't think you have to forget the SSID, you probably can turn off and on the wireless or reboot the device and it would work again.  If you have multiple ports in LAG, check to see if there is an issue with one of the links. You can also run a netsh wlan show wlanreports on a windows device and take a look at previous connections and errors.

[Leo Laohoo]

---

@kiwonkwon8969 wrote:
There are 9115,2802,2702 different ap models.

---

Is the issue affecting when the wireless client(s) is/are connected to 2800 & 9115?