NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
I just spent $400 on a new Netgear Nighthawk router
I just spent $400 on a new Netgear Nighthawk router only to find out it has the same problem as the old out of service RAX43 router. If it’s a Windows issue, I don’t think MS is too interested in ...
It has been several days without any issues accessing Readyshare after I disabled the Protection Engine feature on my Netgear RS600 router. I am marking this thread as solution found but I would have preferred to keep the Protection Engine enabled. Hopefully, in the future a fix can be found so as to be able to use both Readyshare and Protection Engine at the same time. Thanks to FURRYe38 and the others who helped to narrow down the cause of the issue.
Hellorobmartinez108,
Spending $400 on a new router only to face the same ReadySHARE and admin page access issues is frustrating. If both routers show similar behavior, it could point to a firmware or compatibility issue—possibly with Windows SMB settings. I recommend checking for the latest firmware updates and ensuring SMB 1.0 is enabled in Windows if required. Netgear support should address this, especially since it impacts core router functionality.
Best Regards,
Donna Taylor
Thanks for your reply. I’ve had SMB v1 enabled since before I purchased the new router. So, just for troubleshooting, I disabled SMB v1. Immediately, my connection to readyshare and the admin page was terminated. I got a slightly different error message attached below. This tells me that new Netgear Nighthawk RS600 routers are still using SMB v1. With SMB v1 enabled, I can get temporary access to readyshare. After about 20 minutes, the router drops my connection and that is when I get the error message that my local device is already in use. I did upgrade the new router to the latest firmware before I disabled SMB v1. My only hope now is that before the RS600 goes out of upgrade service, Netgear will fix the firmware so that SMB v1 will no longer be necessary for Windows 11 devices. That is, if it turns out that SMB v1 is causing the connection problems.
Please stick with one discussion thread.
While is it clear that you need to keep SMB 1 enabled, that is NOT the cause of your "device already in use". That is happening because the PC didn't fully close the session when the connection got dropped. So as far as it is concerned, U: is still in use by the old (failed) session.
I gave some advice on your other thread here:
That includes ways to easily access the share without mapping it to a drive letter.
Part of the puzzle here is why the connection is dropping. Some PCs (particularly laptops) will power down their network hardware during periods of inactivity. Is the connection dropping when you are actively using the PC? Or is it happening when you step away for a while?