Maybe this is problem with gateway or DNS servers. You have to check addresses when you have problems with connection.

jimasek wrote

Maybe this is problem with gateway or DNS servers. You have to check addresses when you have problems with connection.

Ok.
I forgot to tell:
The WA5210g is connected as an "extender" (not Range-Extender) to a switchport on another Router and works simply as a AP.
For security reasons the WLAN-Clients get adresses via DHCP from the connected other Router in for example 10.11.12.0/24 with all needed things, as DNS and Gateway.
The AP has an adresse in 192.178.156.0/24. If yopu want to administer this AP you have to connect physically by cord or probably to set an IP in WLAN-NIC manually from that network.

The primary problem is not the connectivity to the web-ui, it is the fact that only this one specific AP (we changed ist meanwhile at the customers place) was broadcasting the SSID of the open wireless network, but every try to connect is refused.

This specific AP is now connected in a test scenario and i wait still for the error to occur.

Leo

Now it is three weeks the Ap was lying near my windows, daily check shows: OK.
=> The effect is not reproducable.

If the phenomen was not depending on the signal or current on the LAN-socket, it disappeared.
So i will flash this AP and give it back into produkction. (with a little sticker in it to identify, in case....)

Closed.
Leo

This will probably solve your problem ... Happened to me ..

Go To SNMP and activate it ... add permissions and reboot ..

Worked for me