Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Neufuse

Win10 access to Synology box randomly doesn't work specific way

Recommended Posts

Posted · Original PosterOP

This is an odd one. I have a Synology DS1517+ on my network with the IP 192.168.1.40 and the host name DS1517.

 

When I'm on any of the windows systems in my network I can go to \\ds1517 and browse the shares like you should be able to.

 

What happens though is if I map a drive on any of these systems then restart and come back that mapped drive will not resolve correctly. It will ask me for the user / pass, I will enter it then it will give me an error message saying it cant map the drive.

 

If I browse to at this point \\ds1517 it will not work, I can ping the host name fine, but windows will not open that UNC path. If I go to the IP \\192.168.1.40\ it works fine.... Remap the drive to a drive letter and reboot..

 

Now it's the same issue but with the IP, the mapped IP drive will not work but the host name path will...

 

I have no clue what is going on with this. I can not consistently map a network path to a drive without it causing this behavior on any of my systems... I've been seeing this at least since 1703 and still am in 2004. 

 

Not sure if it's somehow my network setup, DNS is handled by a Microtik Routerboard router, I changed to a Pi hole server handling local DNS and it seemed to get a little better (not failing every time i remapped on the next reboot but maybe every few) but then it started again.

 

Edit: the Windows error I'm getting is

 

Quote

An error occurred while reconnecting Z: to \\192.168.1.40\MyData Microsoft Windows Network: THe local device name is already in use. This connection has not been restored.

 

Link to post
Share on other sites

Make sure that:

  • If you use any VPN solution, that they are turned off, and not running.
  • Under Windows, you have SMB Direct enabled.
  • Make sure that your network, under Windows, is setup as Private (Settings > Network & Internet > Status, look at the status graph, middle item, make sure it says private)
  • Make sure that Network share is enabled in the Advanced Sharing Panel under Windows.
  • Make sure your Synology drive OS is fully updated.
  • Under your Synology Control Panel, go under "File Services", and make sure "Enable SMB service" is enabled, and workgroup name is set to "WORKGROUP" (all caps), then go under Advanced tab, and make sure "Bonjour" is enabled , SSDP, and WS-Discovery.

Once don restart your PC and Synology drive. Wait for your Synology drive to be fully loaded. Same for Windows (wait a min or so after you are loaded in your account idle, giving a chance for delayed services to start . Now, open File Explorer, and type in: "\\<your Synology drive network name>" in the address bar (without quotes), and hit Enter. See if you can reach it. So for example, if your Synology network name is "pineapple", in the address bar type: \\pineapple

 

It should ask you for your user name and password, enter the admin account user name and password for your Synology drive, and check the box to remember it.

You should have access to your files now.

Link to post
Share on other sites
Posted · Original PosterOP
6 hours ago, GoodBytes said:

Make sure that:

  • If you use any VPN solution, that they are turned off, and not running.
  • Under Windows, you have SMB Direct enabled.
  • Make sure that your network, under Windows, is setup as Private (Settings > Network & Internet > Status, look at the status graph, middle item, make sure it says private)
  • Make sure that Network share is enabled in the Advanced Sharing Panel under Windows.
  • Make sure your Synology drive OS is fully updated.
  • Under your Synology Control Panel, go under "File Services", and make sure "Enable SMB service" is enabled, and workgroup name is set to "WORKGROUP" (all caps), then go under Advanced tab, and make sure "Bonjour" is enabled , SSDP, and WS-Discovery.

Once don restart your PC and Synology drive. Wait for your Synology drive to be fully loaded. Same for Windows (wait a min or so after you are loaded in your account idle, giving a chance for delayed services to start . Now, open File Explorer, and type in: "\\<your Synology drive network name>" in the address bar (without quotes), and hit Enter. See if you can reach it. So for example, if your Synology network name is "pineapple", in the address bar type: \\pineapple

 

It should ask you for your user name and password, enter the admin account user name and password for your Synology drive, and check the box to remember it.

You should have access to your files now.

* I dont use a VPN

* Synology box is set to SMB2 not SMB3 so SMB Direct should have no consequences of being off... however it is enabled on all my windows 10 systems 

* Yes my systems are on the private network settings

* Network share being enabled doesn't make a difference my client are not the shares the synology box is, however network discovery is turned on and sharing is turned off on the clients

* Synology auto updates to the latest releases automatically, and there are currently no updates available that are not installed

* Workgroup name is already workgroup on every device in my network including the synology box, WS-Discorvery was already enabled as was bonjour already also

* SMB min version is SMB2 max version is SMB3

 

but like I said above it works one time, on the next reboot it will not reconnect unless I use the opposite path if I use UNC first on reboot UNC wont work only IP will and vice versa..

 

when this happens though I can get to the box's web interface just fine on the method that doesn't work with the mapping.

 

This same thing happens on anonymous authentication shares also so it's also not a password / user issue

 

 

Link to post
Share on other sites
Posted · Original PosterOP

I'm going to add this ONLY happens when a path on the share is mapped in windows... If I disconnect the mapped drive so the drive no longer shows as a mapped path everything starts working again. Even the the UNC path that didn't work before right after it was failing it will work after disconnecting the mapped drive.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×