NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
I have been having crazy problems with Readyshare
I have been having crazy problems with Readyshare, I have changed the WINS and added the unsafe SMB1 leaving my system looking unsafe.
I have found that when I open the credential manager from Cont...
If you open the Credentials manager you can show the windows credentials then make the password change required, you'll see READYSHARE as a generic credential, change the password within that and voila you'll be able to use your Readyshare drives, works for both the USB cable attachments correctly.
So that is the solution to the problem caused by not being able to access your drives.It's nothing to do with adding old broken network solutions like SMB 1.0 or WINS, as long as your network is set correctly it should operate succesfully.
For some reason Windows reset that credential, for a reason I cannot understand (you'd have to talk to the programmer of that routine, good luck with that lol).
So I appear to have found a complete solution to that problem... hoorah for me!
Nighthawk R8000P
Firmware Version
V1.4.1.68_1.3.28
Open Control Panel in Windows 11; hit windows key and r type "Control Panel" and it will open the only control panel in windows change your view to your choice and open Credentials Manager, from that chose windows credentials and you can make the necessary changes using that.
That has given me access, once again, to my NAS readyshare drives attached to Windows 11.
I have Edition Windows 11 Pro Insider Preview
Version 22H2
Installed on 3/16/2023
OS build 23403.1001
Experience Windows Feature Experience Pack 1000.22647.1000.0
I can then remove access to the unsafe SMB1 and secure my system again while gaining access to my attached devices, I have 2 drives attached, one from a Nexstar MX Dual 3.5" SATA drive enclosure and one from an old drive encased and attached using USB 3.0 cable.
The Netgear Nighthawk has a very useful 2 USB ports, one a 2.0 and one a 3.0 version
I have a lot of storage for backups, movies, and family storage usage so require my drives to be accessible online using my home network, this is why I chose the Netgear router so I have access to my storage when I'm not running windows on a computer, that can save me a lot of hassle and running costs, but it has to work all the time without me having a heart attack when, for no known reason, it stops working!
Since I posted this problem I've only had this error occur on 3 more separate occasions, no system changes were made and nothing changed on my pc except the loss of service to my NAS.
I use the old firmware versions because I assign IP addresses manually for my equipment, so I know the address of my printers and TV's etc. so I can make them work more reliably.
I have spoken to Netgear about the problem of not being able to assign fixed IP's using their newer firmware, they are aware of it and still haven't fixed it, to my knowledge, I'd have to try it on each new version and I don't have the patience to function as their tester and my support has, naturally finished.
222Graham222 wrote:
Open Control Panel in Windows 11; hit windows key and r type "Control Panel" and it will open the only control panel in windows change your view to your choice and open Credentials Manager, from that chose windows credentials and you can make the necessary changes using that.
What are those necessary changes?
If you open the Credentials manager you can show the windows credentials then make the password change required, you'll see READYSHARE as a generic credential, change the password within that and voila you'll be able to use your Readyshare drives, works for both the USB cable attachments correctly.
So that is the solution to the problem caused by not being able to access your drives.It's nothing to do with adding old broken network solutions like SMB 1.0 or WINS, as long as your network is set correctly it should operate succesfully.
For some reason Windows reset that credential, for a reason I cannot understand (you'd have to talk to the programmer of that routine, good luck with that lol).
So I appear to have found a complete solution to that problem... hoorah for me!
Oh no. Not another place to have to mess around!
I see where you mean.
222Graham222 wrote:
It's nothing to do with adding old broken network solutions like SMB 1.0 or WINS, as long as your network is set correctly it should operate succesfully.
It would be interesting to see if other people can use that route rather than messing with SMB. Maybe I'll grit my teeth and see if it works here.