3. November 2020 at 1:18 #53422
On ThinOS 8.6_511, our WiFi connected 5070’s with PCoIP will, after a number of hours (give or take 5 hours), seemingly stop using their WLAN default gateway. WiFi remains connected, but there is no communication with devices outside their own subnet.
I can manually go into “Network Setup > General” and under “Network Interface as the Default Gateway” select “WLAN – Wireless Network Connection”. This instantly restores communication to devices that need the gateway (non-Layer 2 traffic). I have not found a WMS setting or INI parameter for this setting.
To make matters worse, this selection does NOT survive a reboot on 8.6_511. The system will go back to ENET as the network interface gateway. Our users end up just rebooting the thin client every 5-10 hours to connect back to their RDP session.
Downgrading to 8.6_027 seems to have resolved the issue. (Our 5070’s on 8.6_111 also don’t seem to have a problem FWIW.) Furthermore, the WLAN gateway setting on 8.6_027 survives a reboot. Personally, I think this setting should be greyed out when ENET is disconnected. (Who would want to use their disconnected ethernet NIC as their default gateway?)
I will be reporting to Dell tomorrow. I just wanted to give a heads up to anyone experiencing similar issues.3. November 2020 at 10:45 #53427ConfGenKeymaster
- Total Post: 11270
- Jedi Master
Please keep us updated on this one.
CG3. November 2020 at 15:50 #53431
I’m facing the same issue with my Wyse 5470 enterprise laptops with ThinOS 8.6_511.
I want the WLAN to be the default gateway, but the system can’t remind this.
Each time I return to the network setup, the ENET is the default gateway.
I was relieved to find this post as I started to go crazy with this…
I downgrade firmware to 8.6_303 but still the same issue… and unfortunately, that’s the factory fimware of my 5470 laptops (I tried a factory reset as well).
I can’t find any older firmware for the 5470 laptop on the Dell Support website.
A WMS setting or INI parameter would be great to bypass this a least.
3. November 2020 at 17:36 #53435
- This reply was modified 6 months, 1 week ago by vinz.
Quick point of clarification:
On 511, the WLAN setting not only doesn’t survive a reboot, it doesn’t even survive closing out of the network config screen. After selecting the WLAN radio button and clicking OK, when you immediately re-open network setup, ENET will be selected again.
Also, no WiFi problems on any of our terminals since downgrading the firmware yesterday.3. November 2020 at 17:54 #53436
I see a handful of older versions for your 5470 on Dell’s site.
Select the raw image item, then it should expand and show an option for “older versions” to download. 8.6_108 is the oldest for that model I see available.3. November 2020 at 18:46 #53437
Update: I called Dell to report the issue. They said engineering wouldn’t accept the report until I provided logs on 511 and then downgraded to 412 and tried that as well.
I said sorry, but I’m not Dell’s personal QA. I understand their reasons for having their process that requires logs, but my report was basically a courtesy and an FYI, not to solve a problem impacting our production. My company won’t pay me to work in our lab testing firmware we don’t actually need to run the business. Since we are fine on the old firmware, I have no incentive to do their testing.
I would encourage anyone else having this problem to call in and report it. They indicated no other customers have said anything about this issue – not surprising since the firmware is relatively new. So maybe a large number of complaints would be enough motivation to get engineering to investigate, sans logs.4. November 2020 at 13:32 #53439
@lionelhuts : Thanks, I feel stupid to not have seen the “older versions” option !
I will try older firmwares and keep you informed4. November 2020 at 14:47 #53441
After trying the firmware 8.6_206, same problem…
Then I downgrade to 8.6_204, and now it works ! The WLAN Default Gateway is still there after closing the network setup screen, an event after a reboot.
So 4 newer firmwares (8.6_206, 303, 412, 511) and this bug is still there ??
(altough I didn’t try the 8.6_412, but I don’t think it works)
I’m amazed that Dell doesn’t know this problem so far !4. November 2020 at 22:29 #53442
- You must be logged in to reply to this topic.