Question Unable to access Synology NAS

[taxpert1]

Hi,

I can't acess my Synology NAS on Windows 10.

I always get this error message:



I have already tried a workaround stopping and restarting the Workstation service (since the NAS has several users), but the error continues.

What should I do next?

Thank you,

 

[taxpert1]

Run the network troubleshooter and says that "DNS server might be unavailable". I don't undrestand, I have Internet, what is wrong?

 

[Ralston18]

Several users....

Who is the Synology NAS Administrator?

That person should be your first POC (Point of Contact).

 

[taxpert1]

Several users....

Who is the Synology NAS Administrator?

That person should be your first POC (Point of Contact).

Myself.

 

[taxpert1]

Changed the DNS servers, went to Cloudflare in WARP mode.

Still unable to access.

I found out that I can access Synology DSM, through web browser and can also ping it. What is wrong?

 

[Ralston18]

Is \\DS220plus the correct NAS name?

The target should be something like \\DS220plus\Share

And on the NAS itself you grant the Windows 10 system/user the necessary permissions to the share.

With access to the Synology DSM you should be able to assign yourself the necessary permissions.

The following Synology link should help you work out the necessary configuration settings:

https://kb.synology.com/en-global/DSM/tutorial/How_to_map_shared_folder_Windows_PC

Take a few minutes to plan it out first.

Then configure.

 

[taxpert1]

Thanks, I'll look into it and report if the problem is solved or not.

 

[taxpert1]

I was able to map one folder in my Windows 10 yesterday. I guess the problem was I tried to map all the folders (\\DS220plus) instead of a specific folder.

I guess the problem was solved. But it isn't.

Today, the mapped folder is no longer mapped. When I tried to remap it, Windows told me that folder is already mapped, but does not show up in Windows Explorer. Why?

 

[punkncat]

This type of thing is exactly why I don't care too much for my Synology NAS.

Says it is hot swappable, but it's not. This leads further to the issue that a couple of years back there was some attack specific to Synology, so they went on to recommend doing away with the admin account....well!

So, now I can surf to it with the correct address, use it for shares all day long. I have no access to the UI and cannot see status or anything. Knowing the moment I go to reset it and restore the admin function those drives data will all be lost, again. Happened to me three times on the first setup.

I know for fact I won't be purchasing one again after this experience.

 

[USAFRet]

This type of thing is exactly why I don't care too much for my Synology NAS.

Says it is hot swappable, but it's not. This leads further to the issue that a couple of years back there was some attack specific to Synology, so they went on to recommend doing away with the admin account....well!

So, now I can surf to it with the correct address, use it for shares all day long. I have no access to the UI and cannot see status or anything. Knowing the moment I go to reset it and restore the admin function those drives data will all be lost, again. Happened to me three times on the first setup.

I know for fact I won't be purchasing one again after this experience.

QNAP had a thing like that.

But the recommendation was to disable or remove the default admin account, and create a new one.
Which I had done since Day 1.

 

[punkncat]

QNAP had a thing like that.

But the recommendation was to disable or remove the default admin account, and create a new one.
Which I had done since Day 1.

Yeah, I took it a bit too literally on that aspect, however, my experience with rebuilding the data in spite of the supposed hot swap has kept this off priority status for a bit.....well, that and sheer laziness.

 

[kanewolf]

Hi,

I can't acess my Synology NAS on Windows 10.

I always get this error message:



I have already tried a workaround stopping and restarting the Workstation service (since the NAS has several users), but the error continues.

What should I do next?

Thank you,

The question is what shows up in the Network section of file explorer?
If the DS220plus doesn't show up, try the IP address.

 

[taxpert1]

Everytime I boot my PC, the mapped drive disappears.

The NAS appears everytime in the Network section of File Explorer, but everytime I get the error above (DS220plus is not accessible...).

 

[taxpert1]

Synology was not of any help, I guess their Customer Support right now is AI... I'm *****.

[Note: Moderator edit to remove profanity. Remember that this is a family friendly forum.,]

 

[bill001g]

Did you try to use the IP address rather than the name

 

[taxpert1]

Yes. Same result. And I don't want to use IP, since it changes once in a while. I'll try a few tweaks I found in the meantime and report

 

[Ralston18]

Be careful about those "tweaks" - especially any that involve third party software and/or editing the Registry.

= = = =

Regarding "And I don't want to use IP, since it changes once in a while."

Update your post to provide more explanation and detail.

I would expect that the NAS would have a static IP address assigned.

Make and model router (or modem/router) if combined?

Run "ipconfig/.all" (without quotes) via the Command Prompt.

Copy and paste the full results here.

 

[taxpert1]

Synology NAS works in DHCP, it changes the IP address once in a while.
The tweaks I made was to clear and disable (by default) all the credentials in Windous when rebooting, since the NAS can be accessed by 4 different users, so my goal is to whenever I click in the mapped drive, Windows pop up a logon screen to insert User and Password.
But although I don't have any credentials saved, Windows is not doing this.
And I still have not been able to solve the major problem: I create a mapped drive, but after rebooting, I have to do it again. This is simple stupid. My cocnlusion is that windows cannot keep mapped drives (and I even created it in command prompt with persistent option YES). So, I believe there is no way to solve, I am just about to give up.

 

[kanewolf]

Synology NAS works in DHCP, it changes the IP address once in a while.
The tweaks I made was to clear and disable (by default) all the credentials in Windous when rebooting, since the NAS can be accessed by 4 different users, so my goal is to whenever I click in the mapped drive, Windows pop up a logon screen to insert User and Password.
But although I don't have any credentials saved, Windows is not doing this.
And I still have not been able to solve the major problem: I create a mapped drive, but after rebooting, I have to do it again. This is simple stupid. My cocnlusion is that windows cannot keep mapped drives (and I even created it in command prompt with persistent option YES). So, I believe there is no way to solve, I am just about to give up.

First I would recommend that you put a fixed IP address on your Synology. It is a server. The IP shouldn't change, IMO. You could do that in two ways. On the host or via a DHCP reservation in your router.

 

[Ralston18]

Agree with @kanewolf

I just set up a Synology DS223j NAS with a fixed IP address of 192.168.1.101 as applicable to the host network.

No problems with drive mapping and/or user access rights.

Do you have admin rights to the network router?

 

[USAFRet]

Agree with the above. The NAS should be a static IP address.
My QNAP has been the same since 2017.

 

[taxpert1]

Agree with @kanewolf

I just set up a Synology DS223j NAS with a fixed IP address of 192.168.1.101 as applicable to the host network.

No problems with drive mapping and/or user access rights.

Do you have admin rights to the network router?

Yes, I have.

My reason to leave it without a static IP is due to security reasons (if a breach exists in my network it's easier to find a device with a static IP). What do you think if I apply an hybrid methodology: continue to use DHCP, but with a reserved IP adress (based on the MAC adress of the NAS). That would be the best of the 2 worlds? Security and stability? Do you agree?

 

[kanewolf]

Yes, I have.

My reason to leave it without a static IP is due to security reasons (if a breach exists in my network it's easier to find a device with a static IP). What do you think if I apply an hybrid methodology: continue to use DHCP, but with a reserved IP adress (based on the MAC adress of the NAS). That would be the best of the 2 worlds? Security and stability? Do you agree?

There is no difference between a device static and a DHCP reservation. End result is a consistent IP address. If there is a breach, then the software would probably scan for ALL IP addresses in the subnet.
The desire for security and network shares that are always available is contradictory. Your NAS would most likely be impacted because a share was available to a compromised device. Your PC is probably the most likely device to be compromised.