formatting my netgear rn104

this

x-raid confirmed

I cannout mount t:nas entire

with the right code

now is working with

+user/realpassword

1. after a restar I had to remount everything.

but the system now accepts the password and the new user

2. second restar I lost also credentials again

---

carlocki wrote:

now is working with

+user/realpassword

---

As I originally said, you need to use the real admin password instead of the placeholder (nas-admin-password) I used.

Also, you cannot use \\192.168.1.4\net-car, because net-car is not a share (and also not the volume name).

So the fact that everything worked tells me that there is nothing wrong with the NAS setup, and therefore no need to do a factory default.

I believe the issue is simply that you aren't using the correct credentials when accessing the NAS from the PC.

---

carlocki wrote:

 

but the system now accepts the password and the new user

 

---

You can only map the full data volume with the NAS admin credentials.  So if you want to do the test with Windows CMD again with the new username, you need to use \\192.168.1.4\sharename  Again, sharename is a placeholder - you need to use a real sharename on your NAS.

If that works, then try the same test again, using \\net-car\sharename This will confirm that you can access the NAS using both its hostname and its ip address.

---

StephenB wrote:

---

carlocki wrote:

now is working with

+user/realpassword

---

As I originally said, you need to use the real admin password instead of the placeholder (nas-admin-password) I used.

---

I DID IT.

---

StephenB wrote:

---

er/realpassword

---

.

Also, you cannot use \\192.168.1.4\net-car, because net-car is not a share (and also not the volume name).

 

 

So the fact that everything worked tells me that there is nothing wrong with the NAS setup, and therefore no need to do a factory default.

 

I believe the issue is simply that you aren't using the correct credentials when accessing the NAS from the PC.

---

.I lost everything every restart

https://app.screencast.com/EcWduZcPP8cWT

---

carlocki wrote:

---

.I lost everything every restart

 

https://app.screencast.com/EcWduZcPP8cWT

---

Not sure what you mean by "lost everything", and how that relates to your screenshot.

Did you create credentials for the NAS in the Windows Credential Manager?

Normally there would be two credentials - one for the NAS hostname, and one for the NAS IP address.  You'd include the username you want to use for the NAS.  You can also specify the password - if you leave that out, Windows will prompt you for it when you try to access a NAS share.

If you are wanting to map shares to drive letters, then it is not unusual for Windows to drop them when you reboot.  The simplest work-around is to create a batch script that remaps them, and run that as needed.

---

carlocki wrote:

i don't know how to write that script.

---

remount.bat could look something like this:

net use * /d /y
net use z: \\192.168.1.4\sharename /u:username password
pause

sharename, username, and password are all placeholders.

You can add additional lines above the pause to mount other shares to drive letters.

You can create this file with notepad.

---

 

Did you create credentials for the NAS in the Windows Credential Manager?

DONE

restart all mapped units do not work

 

Normally there would be two credentials - one for the NAS hostname, and one for the NAS IP address.  You'd include the username you want to use for the NAS.  You can also specify the password - if you leave that out, Windows will prompt you for it when you try to access a NAS share.

 

NAS SIDE (web access) all work

windows side all restart means lost mounted units

 

If you are wanting to map shares to drive letters, then it is not unusual for Windows to drop them when you reboot.  The simplest work-around is to create a batch script that remaps them, and run that as needed.

 

i thin i need this script

 

---

a full nas reinstall will no helP?

windows has few days and it is pefeclty working with all registries new

---

carlocki wrote:

a full nas reinstall will no helP?

 

---

I don't think there is anything wrong on the NAS.

If you like, you can send me a private message (PM) with a link to the full log zip file.  Download the full log zip from the logs page, then upload it to cloud storage (Dropbox, google drive, etc). Make sure the link in the PM is set so anyone with the link can download it. 

Send the PM using the envelope icon in the upper right of the forum page.

on this code

net use * /d /y
net use t: \\192.168.1.4\NET-CAR /user:admin mypass

i cannot map t: or any other 

---

carlocki wrote:

on this code

net use * /d /y
net use t: \\192.168.1.4\NET-CAR /user:admin mypass

 

i cannot map t: or any other 

---

I told you why above.  NET-CAR is not a share. It is the hostname of the NAS. So it cannot be mapped.

If you are trying to map the data volume, you need to use either

• \\192.168.1.4\data  or
• \\NET-CAR\data

i used this code and I made a bat file

net use * /d /y
net use t: \\192.168.1.4\nasarc /user:xxxxxxx yyyyyyyy
pause
net use x: \\192.168.1.4\musica /user:xxxxxxx yyyyyyyy
pause
net use y: \\192.168.1.4\risorse /user:xxxxxxx yyyyyyyy
pause
net use w: \\192.168.1.4\archivio /user:xxxxxxx yyyyyyyy
pause

---

carlocki wrote:

i used this code and I made a bat file

 

 

net use * /d /y
net use t: \\192.168.1.4\nasarc /user:xxxxxxx yyyyyyyy
pause
net use x: \\192.168.1.4\musica /user:xxxxxxx yyyyyyyy
pause
net use y: \\192.168.1.4\risorse /user:xxxxxxx yyyyyyyy
pause
net use w: \\192.168.1.4\archivio /user:xxxxxxx yyyyyyyy
pause

 

---

That should work.

it works except i would like to access inside a folder for "fumetti" but it is ok

can you explain why I need this code on a perfectly working windwos? any limitation of my net card?

---

carlocki wrote:

 

can you explain why I need this code on a perfectly working windwos? any limitation of my net card?

---

Normally mapped drives are not persistent, so you need to map them again when you reboot (or log out/log in).

There is a switch (/persistent:Yes) that you could add to your script.  For instance

net use t: \\192.168.1.4\nasarc /persistent:yes /user:xxxxxxx yyyyyyyy

Even with this switch, a mapped drive sometimes won't mount.  But it would mount most of the time.

But there are alternatives to mapping shares to drive letters that you might want to google.

• You can create desktop shortcuts for each share from file explorer, that would navigate to the share when you click on them. 
• You can pin network shares to  "quick access"
• Windows 11 lets you pin network shares to start  - not sure if Windows 10 has that feature or not.

---

carlocki wrote:

it works except i would like to access inside a folder for "fumetti"

---

These other methods would let you access subfolders within shares directly, so they would let you do this.

Mapped drives are the easiest way for a more novice user to access the NAS.  They also help when a program isn't set up to access a network share directly.

As StephenB said, this isn't necessary to access the shares, there are other ways.  But since you never did state how you were attempting to access them, we could not help you figure out what you were doing wrong or simply not doing.

If you were expecting the shares to simply show up, as if they were on a USB drive attached to the computer, then you really didn't do your homework before purchasing a NAS to understand what you were buying.  A little Googling of network access from Windows might be in order.

---

Sandshark wrote:

 

If you were expecting the shares to simply show up, as if they were on a USB drive attached to the computer, then you really didn't do your homework before purchasing a NAS to understand what you were buying. 

---

FWIW, carlocki has had the RN104 since 2013.  So I think the goal was just getting everything working as it did before he spun up Win10 on this PC.

---

Sandshark wrote:

Mapped drives are the easiest way for a more novice user to access the NAS.  They also help when a program isn't set up to access a network share directly.

 

As StephenB said, this isn't necessary to access the shares, there are other ways.  But since you never did state how you were attempting to access them, we could not help you figure out what you were doing wrong or simply not doing.

 

If you were expecting the shares to simply show up, as if they were on a USB drive attached to the computer, then you really didn't do your homework before purchasing a NAS to understand what you were buying.  A little Googling of network access from Windows might be in order.

---

I must say thanks to Stephen. I Learnt a lot and everything is working great now.