- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: EX6200v2 constant disconnects after firmware 1.0.1.64
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
EX6200v2 constant disconnects after firmware 1.0.1.64
Hi all,
EX6200v2 use it as access point.
After upgrade to firmware 1.0.1.64 i get constant disconnects from wireless
Tested with iphone x samsungs s8 and laptops drop are happening every 5 to 10 minutes.
Anyone else has the same issue?
Any document for rolling back the firmware to last version that worked great.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: EX6200v2 constant disconnects after firmware 1.0.1.64
Hi @lkitsos,
You can use the below link for downgrading firmware. Did you tried modifying wireless channel regarding this issue? Is it happening on both 2.4 and 5GHz bands? Did you performed a reset and reconfigured it back as AP after firmware upgrade?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: EX6200v2 constant disconnects after firmware 1.0.1.64
Hi @lkitsos,
Use this link https://kb.netgear.com/000038837/EX6200v2-Firmware-Version-1-0-1-50 for firmware downgrade.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: EX6200v2 constant disconnects after firmware 1.0.1.64
Sorry for taking so long to reply.
After a lot of upgrades and downgrades the most stable firmware is the
- Firmware Version: V1.0.1.40
Dont have drops and the are not disconnects from the mobile devices and laptops and tablets.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: EX6200v2 constant disconnects after firmware 1.0.1.64
Just as an additional datapoint, I've been having this issue as well, but it started with the firmware included with the device, which I believe was V1.0.1.50, and it persisted after upgrading to V1.0.1.64. I'm currently testing V1.0.1.40.