topic Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f in Unleashed

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

seanm — Wed, 15 Apr 2026 17:15:44 GMT

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

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

Imran_ruckus — Wed, 15 Apr 2026 18:29:00 GMT

Hi @seanm

Greetings!!!

Thank you for reaching out to the RUCKUS Community Forums and for the detailed explanation, that is very helpful.

We appreciate your patience and understanding as we work to resolve the issues you are experiencing with your RUCKUS Unleashed.

Based on the information provided, it appears that you are seeing client disconnections after latest Unleashed upgrade.

The “Force DHCP” feature can interfere with normal DHCP renewals, especially when using an external DHCP server.
Disabling it allows clients to communicate directly with the DHCP server, which is why stability improves.
This looks like a behavior change in newer firmware rather than a network issue.

Recommendations:

Keep Force DHCP = OFF unless there is a specific requirement
Monitor client behavior after the change to confirm stability
If the issue reappears, reviewing DHCP server logs can provide additional insight
Test with latest patch (if newer than 200.19.7.11.283 comes out)

Hope that helps.

Thank you again for your patience.

If your issue has been addressed, please click the Kudos button and mark the responses as an Accepted Solutions.

Best regards,

Imran Sanadi

RUCKUS | Community Forums Support

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

gritech — Wed, 15 Apr 2026 18:49:22 GMT

Possibly related? I didn't try turning off force DHCP during troubleshooting.

https://community.ruckuswireless.com/t5/Unleashed/200-19-7-11-283-Chromebook-Issues/td-p/113239

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Thu, 16 Apr 2026 01:40:16 GMT

Hi @gritech,

Have you tried disabling "Wifi 6/7 on the SSID under Advance >> Radio Control and check?

Regards,
Sanjay Kumar

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Thu, 16 Apr 2026 01:41:56 GMT

@seanm,

Could you please share the details of the clients (Client model, version, you have which are facing the issue?
We can try to check this internally.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

gritech — Thu, 16 Apr 2026 13:34:49 GMT

Yes, with inconsistent results that I documented in my original thread.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

username — Thu, 16 Apr 2026 21:09:14 GMT

I have tried updating to 200.19 twice in the last month. Both times, I have had constant wifi problems on my IPhone. Rolling back immediately everything went back to working with no issues. I am running all r750s. Exact same issue has you, think its specific to the r750s.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

username — Thu, 16 Apr 2026 21:11:12 GMT

I have the exact same issue. Running all r750s. Both times I upgraded I instantly had wifi problems, especially on my IPhone. Rolling back to previous version immediately fixed all the issues.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

Wirelessed — Fri, 17 Apr 2026 01:38:14 GMT

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

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Fri, 17 Apr 2026 03:12:17 GMT

HI @username,
Could you please share the below details so that we can check:
Client model
Version.
SSID Details (Type, Encryption, Authentication, WPA2 or WPA3)

Or It would be great if anyone can share the config backup file (Using Private message option) which will help us to find the root cause.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

username — Sun, 19 Apr 2026 02:28:11 GMT

Running all r750s.

Right now I rolled back to 200.18.7.101.244 since that has given me no problems.

2.4GHZ and 5GHZ network on same wifi network. AM: Open, EM: WPA2

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Thu, 23 Apr 2026 02:34:02 GMT

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

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

username — Thu, 23 Apr 2026 20:55:25 GMT

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

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Fri, 24 Apr 2026 01:55:11 GMT

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.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

gritech — Mon, 27 Apr 2026 17:23:17 GMT

seanm - and others,

What is the status of your SONOS compatibility setting? I've found that even on 200.17 having this setting off intermittently, but regularly, delays DHCP responses long enough for a forced disconnect.

Re: Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to f

sanjay_kumar — Wed, 29 Apr 2026 03:38:23 GMT

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.