NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
W0lfd
Sep 14, 2016Initiate
ReadySHARE Windows 10 + KB3189866
Windows 10 cumulative update KB3189866 breaks readyshare. :smileysurprised:
Uninstall it if you can't access your readyshare folder.
- Sep 25, 2016
Problem solved.
The solution below absolutely worked for me!
The one thing to say is that when you create the Windows Credential - you must enter a user name and password, and...
1. I had to configure readyshare itself to allow read and write access to a username - i selected admin.
2. The windows credential required the router username "admin" and the password for admin. I tried my windows username and password, and i was able to connect to map the drive, but not open the contents of it. With admin and the password, i was able to get it to work!
>Found a solution:
>go into user account in control panel
>if you're in windows 10 select manage your credentials this will open 2 options
>web credentials and windows credentials
>head to windows credentials and add a new windows credential
>enter the location of the drive \\readyshare on the first line
>your windows user name in the second line
>your windows password in the third line
>and you're done, you should see the drive under network and be able to access it as before
>good luck
Hooch80
Sep 19, 2016Tutor
I have the exact same problem.
1. \\readyshare DOES NOT WORK - it results in "A specified logon session does not exist. It may already have been terminated."
2. HTTP access works
3. FTP access works
4. Creating a network share from the HTTP web site DOES NOT WORK
Any answers yet?
Hooch80
Sep 25, 2016Tutor
Problem solved.
The solution below absolutely worked for me!
The one thing to say is that when you create the Windows Credential - you must enter a user name and password, and...
1. I had to configure readyshare itself to allow read and write access to a username - i selected admin.
2. The windows credential required the router username "admin" and the password for admin. I tried my windows username and password, and i was able to connect to map the drive, but not open the contents of it. With admin and the password, i was able to get it to work!
>Found a solution:
>go into user account in control panel
>if you're in windows 10 select manage your credentials this will open 2 options
>web credentials and windows credentials
>head to windows credentials and add a new windows credential
>enter the location of the drive \\readyshare on the first line
>your windows user name in the second line
>your windows password in the third line
>and you're done, you should see the drive under network and be able to access it as before
>good luck
- MattMJFSep 30, 2016Aspirant
Hooch80,
I did this and it worked for me! Thank You for researching this and publishing the solution.
I just had the motherboard replaced on my Lenovo desktop computer and afterwards a plethora of Windows updates installed. I suspect my old credentials where lost or whatever.
I can now map the drive and access \\R7000\USBStorage
Great Job!
- LinotypeOct 02, 2016Tutor
Thank you Hoosh80. You solved a problem that has been a pain in my neck for over a week.
- MardnSNov 07, 2016Aspirant
Any fixture for Windows 8.1? None of the above worked for me.
- knightEknightNov 25, 2016Initiate
I found a different (but probably related) solution based on previous comments.
I logged in to my Windows 10 laptop as an administrator.
Opened a command prompt and issued the following command:
net use U: \\readyshare\USB_Storage /user:%username% /SAVECRED
After running this command one time I had no problem re-mounting the drive after a reboot with just this:
net use U: \\readyshare\USB_Storage
Then I right-clicked on Computer / Map Network Drive, selected U: and \\readyshare\USB_Storage, checked "reconnect at sign-in" and checked "Connect using different credentials". I specified my current username and password (just as I did in my original net use command above), and after this I could reboot the PC and the drive would be there. However, I'm pretty sure I would have to repeat these steps for every user I wanted to have access to it.
kEk