New A6200 doesn't connect after restart.

I've gotten to second or third level tech support on this. They gave me a "debug" driver that seems to solve the problem. Unfortunately, its not released, and does not include the full software implementation. They sent me the latter several times, and it never worked (same issue with having to reset the usb port every reboot). They left me with the impression that they really did not know what issue was causing the problem, and it was just random luck that the "debug driver) worked.

My experience with netgear is that when their stuff works, its absolutely great. The new R7000 router is a case in point. If, however, you need tech support, may the lord have mercy on your soul. I've never had a good experience with them.

My mistake Sorry, I didn't see that info in the entire thread and I assumed (My Bad) that anyone purchasing the A6200 would had expected to connect above 300 which requires a USB3. System Requirements Available USB 1.1 or USB 2.0 slot Data throughput may also be limited by the product’s interface, e.g. to less than 480 Mbps for a USB 2.0 interface. The product description at best is Quite lame for what it doesn't say.

the problem is on using a usb 2.0 port

Check your USB3 port drivers for a update. Some USB3 ports do not work correctly until PC is completely booted up which might be causing the problem. I've seen this on two PC's so far.

I use a wireless key board on a desktop and it will not let me into Bios setup by hitting Delete Key when booting PC using USB3 port. It does however work when using USB2 port. After boot up the usb3 works fine. If I didn't try to enter Bios setup I never would had notice it.

When trying to use a usb3 port to reimage a different PC the image files are not found when drive is in USB3 but are found using USB2. The drive is a USB3 device which does work when PC is running Win 7. The backup image was written to it using WIN 7 backup.

May or may not be the problem but interesting anyway.

All,

You must register this issue with Netgear Support.
They have no idea that there is an issue with this f/w and therefore will not fix it.

Please please register now!!!!!!!!!!!!!!!!!!!!!!!!!!

Downgrading to .18 worked for me as well. Unfortunately, I now lose beamforming. Drag. Any idea when netgear will update their "new" driver to work? Any idea when they will actually train their tech support folks so that they can respond intelligently when folks call/email/post about these "known" bugs?

Its september, and I'm having the same problem. Unfortunately, when I try to download the down level driver, its an empty file. There is no .18 to install. Argh. At least this is a known issue. Apparently, not to netgear tech support though. I called once, and he was clueless, I used their online tech support form, and they were equallly clueless.

Its september, and I'm having the same problem. Unfortunately, when I try to download the down level driver, its an empty file. There is no .18 to install. Argh. At least this is a known issue. Apparently, not to netgear tech support though. I called once, and he was clueless, I used their online tech support form, and they were equallly clueless.

Thanks for the info, my computer was offline for a while but dropping the version back down to 1.0.0.18 looks like it has done the goods. In case anyone was wondering I was on 1.0.0.26 and it had the reboot issue.

Fuby wrote:
Backed down to 1.0.0.8 and it did find it on reoot..will see how this goes and hope the next version remembers to add it back in..

oops...meant 1.0.0.18... atill working fine on reboots..