ReadyCloud signin

---

bhague01 wrote:

 

C:\WINDOWS\system32>net use * /delete /y net use t: \\192.168.1.100\bhague01 **********

---

I gave you two different commands (on different lines!).  You can't enter them as one command.

The typing really matters here, CMD is not forgiving on mistakes.

Thanks, StephenB

I tried what you suggested, using the syntax: net use t: \\192.168.1.100\B2music user:Bill ******** for the second command, first without the preceding command, second with previous  net use * /delete /y command, and there was no t: drive to be seen, either before or after a reboot.

I have checked in the folder for the program but could not see an obvious credentials subfolder.

I have just rechecked the Win10 Credentials manager: oddly, the IP address credential for the NAS had a combination username, which does not appear in the User list on the Admin page of the ReadyNAS, but is an amalgam of the bhague01 username and the second part of the email address.  I was about to delete that user name on the Admin page, but thought I would get your advice first.  I have just disabled it for the moment.

The MYNAS credential is currently applied to my (correct) gmail address.

Your thoughts and further suggestions appreciated.  I am very confused!

---

bhague01 wrote:

The MYNAS credential is currently applied to my (correct) gmail address.

 

---

Which is wrong. It should be using one of your NAS user account names.  The email address in the NAS account setup is not the username.  The entry in Name field is the username (BH or bhague01).  That is what should be in the Windows credential, and also is the username you should be using in the net use command.

---

bhague01 wrote:

 

I have just rechecked the Win10 Credentials manager: oddly, the IP address credential for the NAS had a combination username, which does not appear in the User list on the Admin page of the ReadyNAS, but is an amalgam of the bhague01 username and the second part of the email address. 

 

---

Might be something you accidentally did before.  You can either edit the credential or delete it and make a new one.  No need to change the account on the NAS.

Also (something I should have said earlier) - you need to be creating windows credentials, not web or generic credentials in the Credentials manager.

---

bhague01 wrote:

 

I have checked in the folder for the program but could not see an obvious credentials subfolder.

 

---

I don't know what you mean by this.  What program???  

---

bhague01 wrote:

 

I tried what you suggested, using the syntax: net use t: \\192.168.1.100\B2music user:Bill ******** for the second command, first without the preceding command, second with previous  net use * /delete /y command, and there was no t: drive to be seen, either before or after a reboot.

 

---

T would disappear after a reboot.

Since you weren't using the right username, it's not surprising it didn't work - likely there was an error reported after you entered it.

Hi StephenB

Thanks for your patience!

I have now edited the Windows (never the Web!) credentials for both MYNAS and for 192.168.1.100, giving the first the BH username and the second the Bill username, for clarity of understanding.

I then ran the net use * /delete /y command, which produced the response:

    You have these remote connections:

    Z: \\BRENNANB2\music
    Continuing will cancel the connections.

    The command completed successfully.

(The BRENNANB2\music is the source folder I have been trying to mirror.)

I then ran the net use t: \\192.168.1.100\B2music user:Bill ******** command, which produced the syntax message, as previously.

I checked the Network page in Explorer and there was no T: drive.

I reran the net use * /delete /y command, which produced the response

     There are no entries in the list

And then ran the net use t: \\MYNAS\B2music user:BH ******** command command, which again produced the syntax response, and again there was no T: drive.

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.

Thanks for clarifying about the transient nature of the (as yet non-existent) T drive.

So now I have the correct usernames and the correct sharenames, I believe!  And I have used the correct commands (though the fact that I got back a syntax message on both occasions makes me worried that there is still something I am not doing correctly!).

What can I try next?

Cheers

---

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?

---

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.

 

Any backup (or other) program that stores user network credentials in plain text anywhere is unsecure and should never be used.  I doubt your program does that, so you need to look somewhere within the options of the running program itself for where to add the credentials.

BTW, the Windows Credential Manager does encrypt the credentials, it just automatically encrypts/unencrypts them for you when you are logged in.

Thank you, Sandshark, for clarifying that.

StephenB and I had been in conversation about entering credentials, and for interest, not being a programmer!, I had thought I would just sniff around check in the folder of the program I had been having difficulty with, while realising that the issue was likely to be with how I was using the Win10 credential manager.

Cheers

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!

---

bhague01 wrote:

However, there is still no T: drive shown in the network explorer page!!

 

---

When you are looking at "This PC", you don't see the T drive under "Devices and Drives"???

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.

I'm glad everything is working for you now. :smileyhappy:

👍 Thanks again.