Trouble connecting to Synology DS218J NAS


  1. Posts : 8
    Windows 10
       #1

    Trouble connecting to Synology DS218J NAS


    Hi,

    I have a Synology DS218J on SMB. I have been able to access it via Windows Explorer with \\hostname just fine, but I just tried today and it no longer works. I get the following error message when I try to access a folder within the NAS
    Trouble connecting to Synology DS218J NAS-nas_error.png

    I get the following error message when I try to access the NAS hostname/IP address directly
    Trouble connecting to Synology DS218J NAS-nas_error2.png

    When I try to map a new network drive, it doesn't detect anything on my network.
    Trouble connecting to Synology DS218J NAS-nas_error3.png

    The Synology web portal works fine. I'm able to access it on my web browser. I'm also able to ping it just fine. I'm also able to access it on my Android device using the DS file app. However, I can't access it via Windows Explorer either via \\hostname or \\ipaddress.

    What's wrong?

    - - - Updated - - -

    I tried net use * /delete and then manually add the NAS root or the shared folders. Here are the results:

    "net use X: \\hostname or IP address" - The network path was not found.

    "net use X: \\hostname or IP address\SharedFolder" - System error 1790 has occurred. The network logon failed.

    If I try the above net use command again, I'll get "System error 59 has occurred. An unexpected network error occurred."

    I also tried the following:

    "pushd \\hostname or IP address\SharedFolder" - I get either "The operation being requested was not performed because the user has not been authenticated." or "A device attached to the system is not functioning."

    I've tried rebooting both my PC and the NAS, disabling(then re-enabling) SMBv1, disabling IPv6, turning on network discovery and file and printer sharing (though this should only affect my sharing of my PC right?)
      My Computer

  2. swarfega's Avatar
    Posts : 6,510
    Windows 10 Pro 64-bit
       #2

    Hi and welcome to the forums.

    SMBv1 was discontinued by Microsoft due to security concerns. Is there anywhere in the NAS control panel that lets you specify which SMB version to use like it does on mine?
      My Computers


  3. Posts : 8
    Windows 10
    Thread Starter
       #3

    swarfega said:
    Hi and welcome to the forums.

    SMBv1 was discontinued by Microsoft due to security concerns. Is there anywhere in the NAS control panel that lets you specify which SMB version to use like it does on mine?
    Yes, the NAS is setup to support both SMBv1 and v2. I didn't change anything so I'm not sure why it suddenly stopped working. Seems like my PC is able to reach the NAS over the network, but isn't able to access it as a NAS.
      My Computer

  4. swarfega's Avatar
    Posts : 6,510
    Windows 10 Pro 64-bit
       #4

    Yea try not to use SMB1. Windows no longer supports it.
      My Computers


  5. Posts : 8
    Windows 10
    Thread Starter
       #5

    Yes I know, but that doesn't help. Just to confirm, I've tried using only SMBv2 on the NAS, same problem.
      My Computer

  6. NavyLCDR's Avatar
    Posts : 13,356
    Windows 10 Pro
       #6

    From this article (I would suggest you read the whole article):
    How to kill off SMB1, NetBIOS, WINS and *still* have Windows' Network Neighbourhood better than ever | iXsystems Community

    Try:
    Next, ensure the services that WSD relly [SIC] on, are run automatically. Their full names are "Function Discovery Provider Host" and "Function Discovery Resource Publication. The registry edits/commands are either of these, as you prefer:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fdPHost]
    "Start"=dword:00000002
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FDResPub]
    "Start"=dword:00000002

    or

    sc config fdPHost start=auto
    sc config FDResPub start=auto
      My Computer



  7. Posts : 1,672
    Windows 10
       #7

    I use a Synology DS212j. Several months ago I had a problem signing in to it. Doing these things seem to resolve it, no idea why. I have very minimal knowledge of Network things.

    1) Do a reset on your NAS box, a pin hole on the back panel (a Power Off does not help on mine).

    2) Download and install the Synology Assistant.

    Run that, then fully exit it from the Taskbar icon. Run it again.
    You can use Connect and Map drives from this once it shows up in the Assistant.

    NAS box settings - currently SMB1 to SMB2 and Large MTU (could be up to SMB 3)
    Windows 10 features - SMB 1.0/CIFS Client and Server are ticked. Automatic Removal not ticked.

    Attachment 273193
      My Computer


  8. Posts : 8
    Windows 10
    Thread Starter
       #8

    Thanks for the tip on Synology Assistant. I tried it and realised that nothing was found, so I disabled my Windows Firewall for all 3 profiles (public/private/domain) and then got Synology Assistant to detect my NAS. I then enabled the Firewall 1 by 1 and realised that once I enabled the firewall for private (which is my current profile), Assistant can't find my NAS anymore.

    Not sure why this is the case as I'm pretty sure it should pass through SMB packets? If not, how can I configure it as such?

    Also, even after disabling the firewall, I'm STILL unable to access the NAS in Windows Explorer. If I try to use Synology Assistant to map the drive, I get the following error.
    Trouble connecting to Synology DS218J NAS-nas_error4.png
      My Computer


  9. Posts : 8
    Windows 10
    Thread Starter
       #9

    So I tried a few other things
    1. Ran Wireshark on the problematic desktop. My desktop would return a RST,ACK instead of an ACK, right after the NAS's SMB2 Negotiate Protocol Response packet
    2. Tried connecting to the NAS on a Linux VM on the desktop with "smbclient -L <host>". Got a "protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE" error.
    3. Tried forcing SMB2 on with smbclient on the Linux VM with "smbclient -m SMB2 -L <host>". This works!

    I tried looking at Wireshark captures for #2 and #3. The error for #2 is different from #1. It's not a RST,ACK, but a ACK followed by a FIN,ACK, which is a more graceful connection teardown.
    I then looked at the differences between #1 and #2/#3. I can see that in #1, Windows is sending a SMB2 Negotiate Protocol Request packet to the NAS, while for #2/#3 (and also for the working laptop), Windows is sending a SMB Negotiate Protocol instead. I don't know if and why that makes a difference.

    Any ideas?
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:09.
Find Us




Windows 10 Forums