Solved: RUCKUS Forums - Re: Client disconnections after 200.19.7.11.283 up... - Page 3

seanm · ‎04-15-2026

We have a Ruckus R750 running Unleashed.

Everything was fine with 200.18.7.101.244, then we updated to 200.19.7.11.283 and many people were reporting disconnections and/or unstable connections.

Turning the "force DHCP" option from ON to OFF seems to have fixed it.

Anyone else have this same issue?

Sean

sanjay_kumar · ‎05-05-2026

Hi,

We are able to find the root cause, seems like the dhcp ip address is not updated for more than lease time , the
lease time is set 0, hence the client got kicked off.

This is addressed in 200.19 MR.
ETA is July 6th for now.

View solution in original post

sanjay_kumar · ‎04-22-2026

@username,
Is it possible to share the backup file from 200.18 ? We will try to reproduce by upgrading to 200.19

username · ‎04-23-2026

is there an update on this issue? More people seem to be having the same issues with the most recent unleashed version.

sanjay_kumar · ‎04-23-2026

Hi @username,

We have been trying to reproduce the issue inhouse but not able to so far.
I'm trying to see if I can get remote session to customer setup or atleast get the backup file so that we can check in lab.

Could you please share the backup file so that we can check? If the setup is downgraded, it is still fine.

sanjay_kumar · ‎04-28-2026

Hi @username,

We are able to reproduce the issue in with the backup. We are working on it to find the root cause and fix it.

I will keep you posted.

Wirelessed · ‎04-16-2026

Can confirm force DHCP had to be disabled to maintain wireless connections after the update to 200.19.7.11.283 for R650.

Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to fix it