NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyCloud signin
Ready Cloud has been working well in the past, but I have been out of action in recent weeks. When I came back to use the laptop with the ReadyCloud client installed, I have first had some issues wi...
Hi StephenB
Thank you. I think we are sorted! Everything is now accessible - hurrah!
I am now using the IP addresses to identify both the source and the endpoint of the FreeFileSync program, and all appears to be working fine again.
I have learnt some things about the various technical terms, which are not always well explained, as well as the importance of careful use of syntax.
I still don't understand why things went wrong in the first place, but all is well that ends well.
We should probably entitle this conversation "The case of the missing T: drive"!
I am very grateful to you for your time and input. I would like to have given you a lot more kudos, which I only noticed at the end.
I am sure you will be a great help to many more folk, who come looking for it!
Cheers and very best wishes
bhague01 wrote:
I then ran the net use t: \\192.168.1.100\B2music user:Bill ******** command, which produced the syntax message, as previously.
The syntax is
net use t: \\192.168.1.100\B2music /user:username password
Looks like you are missing a slash in front of user (the opposite slash from the ones in the path to the share).
bhague01 wrote:
In relation to your query as to "What program?", I was meaning the mirroring program that I have been trying to use: I thought I would look in its program folder for any suggestion of a specific credentialling option, as you had earlier suggested that some programs have.
Got it. What mirroring program are you using?
Thanks, StephenB! That would explain why the syntax message came back! I have to say that I find the instructions rather confusing, so I just followed your initial guidance (though not exactly, as you have already pointed out! :) ).
I will now make the necessary change, including the /, and report back.
Hmm! After making the change, I ran the new command and got back:
System error 86 has occurred.
The specified network password is not correct.
I rechecked the password in Credential Manager: still only ******** in length, so I reentered and retried the command. Still the same.
So I went back to the admin page for the NAS, where the same ******** was shown. So I reentered the password, and this time got the response:
The command completed successfully.
Hurrah!
However, there is still no T: drive shown in the network explorer page!!
Now what?
Thanks again for your patience!
- No.The NAS is there, but not as a T drive.Odd!
Interestingly, I just retried the net use * /delete /y command, which produced the response:
You have these remote connections:
T: \\192.168.1.100\B2music
Continuing will cancel the connections.The command completed successfully.
So obviously, the T: drive is being recognised by the system, but not by Win10!
Is my logic correct?
PS The mirroring program is FreeFileSync from https://freefilesync.org/
I guess the main question now is whether the NAS files are accessible from windows explorer. If it is, then the missing T drive just an oddity.
bhague01 wrote:
Interestingly, I just retried the net use * /delete /y command, which produced the response:
You have these remote connections:
T: \\192.168.1.100\B2music
Continuing will cancel the connections.The command completed successfully.
If you want to pursue this, then enter those two commands again, then follow up by entering this
dir T:
You should see the files/folders in the root of the B2music share listed in the cmd window.
Hi StephenB
Thank you. I think we are sorted! Everything is now accessible - hurrah!
I am now using the IP addresses to identify both the source and the endpoint of the FreeFileSync program, and all appears to be working fine again.
I have learnt some things about the various technical terms, which are not always well explained, as well as the importance of careful use of syntax.
I still don't understand why things went wrong in the first place, but all is well that ends well.
We should probably entitle this conversation "The case of the missing T: drive"!
I am very grateful to you for your time and input. I would like to have given you a lot more kudos, which I only noticed at the end.
I am sure you will be a great help to many more folk, who come looking for it!
Cheers and very best wishes
I'm glad everything is working for you now. :smileyhappy:
👍 Thanks again.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
