Results 1 to 16 of 16

Thread: Very weird problem accessing Synology NAS using Windows File Explorer

  1. #1
    Evil Monkey! MrJim's Avatar
    Join Date
    Aug 2012
    Location
    London
    Posts
    2,325
    Thanks
    310
    Thanked
    476 times in 366 posts
    • MrJim's system
      • Motherboard:
      • MSI Tomahawk X570
      • CPU:
      • AMD Ryzen 5900X
      • Memory:
      • 32gb Kingston 3600 DDR4
      • Storage:
      • Aorus 1Tb NVME SSD, Samsung 1Tb 970 Evo SSD, Crucial 2tb MX500 SSD, Seagate Ironwolf 4Tb SSD
      • Graphics card(s):
      • EVGA 3080Ti
      • PSU:
      • Seasonic Prime Ultra Platinum 1300W
      • Case:
      • Fractal Meshify 2
      • Operating System:
      • Windows 11 Pro
      • Monitor(s):
      • Viewsonic 27" XG2703-GS
      • Internet:
      • BT 900 mb/s FTTP

    Very weird problem accessing Synology NAS using Windows File Explorer

    I changed ISP a while ago, and ever since then, I've not been able to access the files on the NAS using Windows File Explorer. Before changing ISP, file access was working fine.

    I'd actually pretty much forgotten about the problem, as these days I don't need file access all that often. Just out of curiosity, I tried accessing the files from File Explorer just now, & it worked! Then I realised that I had my VPN (Private Internet Access) switched on. So I switched the VPN off, and now I can't access the files once again! The network error box pops up saying that Windows can't access \\diskstation, with the error code '0x80070035'.

    Checking the network settings in DSM 6.2, the network is obviously connected (I can access the NAS through the web interface without problems). I have the internal IP address manually set to 192.168.0.2, and the router (default gateway) is set to 192.168.0.1 using IPv4. I don't have the NAS set up for external access as I don't need it.

    Can anyone shed any light on what's going on? I'm a bit bemused!
    Last edited by MrJim; 03-10-2023 at 12:24 PM.

  2. #2
    Senior Member
    Join Date
    Jul 2003
    Posts
    12,123
    Thanks
    906
    Thanked
    584 times in 409 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Havent used DSM, but do you have SMB enabled on your machine?

  3. #3
    Almost Ex-HEXUS Staff Jonatron's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    707
    Thanks
    48
    Thanked
    275 times in 169 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Does \\192.168.0.2 work instead of \\diskstation ?

  4. #4
    Evil Monkey! MrJim's Avatar
    Join Date
    Aug 2012
    Location
    London
    Posts
    2,325
    Thanks
    310
    Thanked
    476 times in 366 posts
    • MrJim's system
      • Motherboard:
      • MSI Tomahawk X570
      • CPU:
      • AMD Ryzen 5900X
      • Memory:
      • 32gb Kingston 3600 DDR4
      • Storage:
      • Aorus 1Tb NVME SSD, Samsung 1Tb 970 Evo SSD, Crucial 2tb MX500 SSD, Seagate Ironwolf 4Tb SSD
      • Graphics card(s):
      • EVGA 3080Ti
      • PSU:
      • Seasonic Prime Ultra Platinum 1300W
      • Case:
      • Fractal Meshify 2
      • Operating System:
      • Windows 11 Pro
      • Monitor(s):
      • Viewsonic 27" XG2703-GS
      • Internet:
      • BT 900 mb/s FTTP

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by [GSV]Trig View Post
    Havent used DSM, but do you have SMB enabled on your machine?
    Yes, SMB is enabled in 'File Services'.

    Quote Originally Posted by Jonatron View Post
    Does \\192.168.0.2 work instead of \\diskstation ?
    Using \\distsation in Windows File Explorer doesn't work, unless the VPN is active. Otherwise, I get the error I described previously, & in Chrome I get a 'Your file couldn't be accessed' message. Using just the IP address in both File Explorer & Chrome brings up the web interface to the NAS.

  5. #5
    Senior Member
    Join Date
    Jul 2003
    Posts
    12,123
    Thanks
    906
    Thanked
    584 times in 409 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by MrJim View Post
    Yes, SMB is enabled in 'File Services'.
    I didn't mean in services on the NAS, I meant on your machine, a few years back I think it was SMB was disabled by default, you have to add it as a feature now within Windows.

  6. #6
    Chaos Monkey Apex's Avatar
    Join Date
    Jul 2003
    Location
    Huddersfield
    Posts
    4,707
    Thanks
    1,142
    Thanked
    285 times in 204 posts
    • Apex's system
      • Motherboard:
      • Asus Z87M-PLUS
      • CPU:
      • Intel i5-4670K
      • Memory:
      • 32 GiB
      • Storage:
      • 20 TiB
      • Graphics card(s):
      • PowerColor Radeon RX 6700 Fighter 10GB OC
      • PSU:
      • 750
      • Case:
      • Core View 21
      • Operating System:
      • Windows 10 pro
      • Monitor(s):
      • Dell S2721DGFA
      • Internet:
      • 200Mb nTL Cable

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    change of isp = change of router ?

  7. Received thanks from:

    MrJim (03-10-2023)

  8. #7
    Evil Monkey! MrJim's Avatar
    Join Date
    Aug 2012
    Location
    London
    Posts
    2,325
    Thanks
    310
    Thanked
    476 times in 366 posts
    • MrJim's system
      • Motherboard:
      • MSI Tomahawk X570
      • CPU:
      • AMD Ryzen 5900X
      • Memory:
      • 32gb Kingston 3600 DDR4
      • Storage:
      • Aorus 1Tb NVME SSD, Samsung 1Tb 970 Evo SSD, Crucial 2tb MX500 SSD, Seagate Ironwolf 4Tb SSD
      • Graphics card(s):
      • EVGA 3080Ti
      • PSU:
      • Seasonic Prime Ultra Platinum 1300W
      • Case:
      • Fractal Meshify 2
      • Operating System:
      • Windows 11 Pro
      • Monitor(s):
      • Viewsonic 27" XG2703-GS
      • Internet:
      • BT 900 mb/s FTTP

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by [GSV]Trig View Post
    I didn't mean in services on the NAS, I meant on your machine, a few years back I think it was SMB was disabled by default, you have to add it as a feature now within Windows.
    Ah, sorry I misunderstood. Yes it is enabled - as I said, when the VPN is active I can access the files on the NAS using Windows File Explorer without issues.

    Quote Originally Posted by Apex View Post
    change of isp = change of router ?
    Yes it was a change of router. Although when I said 'change of ISP', it was really just a change of service; I stayed with BT, and change the router for what seems to be an identical one. I thought I'd kept all the settings to same as before.

    Just out of curiosity, what exactly doe activating a VPN do? I thought all it did was to change the external IP address to whichever country you select, & encrypt the data you exchange thereafter? I just wonder what else could be changing to might affect file access to my NAS?

  9. #8
    Super Moderator Jonj1611's Avatar
    Join Date
    Jun 2008
    Posts
    5,741
    Thanks
    1,786
    Thanked
    1,015 times in 777 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Doesn't it also change the DNS?
    Jon

  10. Received thanks from:

    MrJim (03-10-2023)

  11. #9
    Almost Ex-HEXUS Staff Jonatron's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    707
    Thanks
    48
    Thanked
    275 times in 169 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by MrJim View Post
    Yes, SMB is enabled in 'File Services'.



    Using \\distsation in Windows File Explorer doesn't work, unless the VPN is active. Otherwise, I get the error I described previously, & in Chrome I get a 'Your file couldn't be accessed' message. Using just the IP address in both File Explorer & Chrome brings up the web interface to the NAS.
    There's a difference between putting \\192.168.0.2 and 192.168.0.2 in file explorer. What does the former do?

  12. Received thanks from:

    MrJim (03-10-2023)

  13. #10
    Senior Member
    Join Date
    Jul 2003
    Posts
    12,123
    Thanks
    906
    Thanked
    584 times in 409 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by MrJim View Post
    Yes it was a change of router.
    Erm, does your machine think that you have connected to a different network and has firewall setup for a public network so its turned off and/or blocked access to stuff...

  14. Received thanks from:

    MrJim (03-10-2023)

  15. #11
    Evil Monkey! MrJim's Avatar
    Join Date
    Aug 2012
    Location
    London
    Posts
    2,325
    Thanks
    310
    Thanked
    476 times in 366 posts
    • MrJim's system
      • Motherboard:
      • MSI Tomahawk X570
      • CPU:
      • AMD Ryzen 5900X
      • Memory:
      • 32gb Kingston 3600 DDR4
      • Storage:
      • Aorus 1Tb NVME SSD, Samsung 1Tb 970 Evo SSD, Crucial 2tb MX500 SSD, Seagate Ironwolf 4Tb SSD
      • Graphics card(s):
      • EVGA 3080Ti
      • PSU:
      • Seasonic Prime Ultra Platinum 1300W
      • Case:
      • Fractal Meshify 2
      • Operating System:
      • Windows 11 Pro
      • Monitor(s):
      • Viewsonic 27" XG2703-GS
      • Internet:
      • BT 900 mb/s FTTP

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by Jonatron View Post
    There's a difference between putting \\192.168.0.2 and 192.168.0.2 in file explorer. What does the former do?
    Oh well that's interesting - putting \\192.168.0.2 worked! Thank you so much! Just out of curiosity, what difference does the \\ make?

  16. #12
    Almost Ex-HEXUS Staff Jonatron's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    707
    Thanks
    48
    Thanked
    275 times in 169 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    I needed to google path formats, but according to https://learn.microsoft.com/en-us/do...mats#unc-paths :

    UNC paths

    Universal naming convention (UNC) paths, which are used to access network resources, have the following format:

    A server or host name, which is prefaced by \\. The server name can be a NetBIOS machine name or an IP/FQDN address (IPv4 as well as v6 are supported).
    A share name, which is separated from the host name by \. Together, the server and share name make up the volume.
    A directory name. The directory separator character separates subdirectories within the nested directory hierarchy.
    An optional filename. The directory separator character separates the file path and the filename.

    The following are some examples of UNC paths:
    Path Description
    \\system07\C$\ The root directory of the C: drive on system07.
    \\Server2\Share\Test\Foo.txt The Foo.txt file in the Test directory of the \\Server2\Share volume.

    UNC paths must always be fully qualified. They can include relative directory segments (. and ..), but these must be part of a fully qualified path. You can use relative paths only by mapping a UNC path to a drive letter.

  17. #13
    Evil Monkey! MrJim's Avatar
    Join Date
    Aug 2012
    Location
    London
    Posts
    2,325
    Thanks
    310
    Thanked
    476 times in 366 posts
    • MrJim's system
      • Motherboard:
      • MSI Tomahawk X570
      • CPU:
      • AMD Ryzen 5900X
      • Memory:
      • 32gb Kingston 3600 DDR4
      • Storage:
      • Aorus 1Tb NVME SSD, Samsung 1Tb 970 Evo SSD, Crucial 2tb MX500 SSD, Seagate Ironwolf 4Tb SSD
      • Graphics card(s):
      • EVGA 3080Ti
      • PSU:
      • Seasonic Prime Ultra Platinum 1300W
      • Case:
      • Fractal Meshify 2
      • Operating System:
      • Windows 11 Pro
      • Monitor(s):
      • Viewsonic 27" XG2703-GS
      • Internet:
      • BT 900 mb/s FTTP

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by Jonatron View Post
    I needed to google path formats, but according to https://learn.microsoft.com/en-us/do...mats#unc-paths :

    UNC paths

    Universal naming convention (UNC) paths, which are used to access network resources, have the following format:

    A server or host name, which is prefaced by \\. The server name can be a NetBIOS machine name or an IP/FQDN address (IPv4 as well as v6 are supported).
    A share name, which is separated from the host name by \. Together, the server and share name make up the volume.
    A directory name. The directory separator character separates subdirectories within the nested directory hierarchy.
    An optional filename. The directory separator character separates the file path and the filename.

    The following are some examples of UNC paths:
    Path Description
    \\system07\C$\ The root directory of the C: drive on system07.
    \\Server2\Share\Test\Foo.txt The Foo.txt file in the Test directory of the \\Server2\Share volume.

    UNC paths must always be fully qualified. They can include relative directory segments (. and ..), but these must be part of a fully qualified path. You can use relative paths only by mapping a UNC path to a drive letter.
    Thanks very much for going to the trouble of looking up the convention for UNC paths. The odd thing is, typing \\diskstation wasn't working initially (without the VPN working), but once I tried \\192.168.0.2 as you suggested, it does now work. I don't quite understand why that should be the case, but I'm happy it's working all the same!

  18. #14
    Almost Ex-HEXUS Staff Jonatron's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    707
    Thanks
    48
    Thanked
    275 times in 169 posts

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Guessing based on "The server name can be a NetBIOS machine name or an IP/FQDN address (IPv4 as well as v6 are supported)." that NetBIOS is disabled.
    There's a few windows settings that need to be right, and matching on different machines for windows to be able to find the IP address of \\diskstation
    There's a whole bunch of different things in different places in windows to check: https://superuser.com/questions/1240...can-by-localho

  19. #15
    Chaos Monkey Apex's Avatar
    Join Date
    Jul 2003
    Location
    Huddersfield
    Posts
    4,707
    Thanks
    1,142
    Thanked
    285 times in 204 posts
    • Apex's system
      • Motherboard:
      • Asus Z87M-PLUS
      • CPU:
      • Intel i5-4670K
      • Memory:
      • 32 GiB
      • Storage:
      • 20 TiB
      • Graphics card(s):
      • PowerColor Radeon RX 6700 Fighter 10GB OC
      • PSU:
      • 750
      • Case:
      • Core View 21
      • Operating System:
      • Windows 10 pro
      • Monitor(s):
      • Dell S2721DGFA
      • Internet:
      • 200Mb nTL Cable

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    NetBIOS turned off on the new router, the master browser election not working till you went to it via the ip and then it decided to sort itself out; frankly the fact any of it works at any time is a blessing.

  20. #16
    Senior Member
    Join Date
    Mar 2005
    Posts
    4,940
    Thanks
    171
    Thanked
    386 times in 313 posts
    • badass's system
      • Motherboard:
      • ASUS P8Z77-m pro
      • CPU:
      • Core i5 3570K
      • Memory:
      • 32GB
      • Storage:
      • 1TB Samsung 850 EVO, 2TB WD Green
      • Graphics card(s):
      • Radeon RX 580
      • PSU:
      • Corsair HX520W
      • Case:
      • Silverstone SG02-F
      • Operating System:
      • Windows 10 X64
      • Monitor(s):
      • Del U2311, LG226WTQ
      • Internet:
      • 80/20 FTTC

    Re: Very weird problem accessing Synology NAS using Windows File Explorer

    Quote Originally Posted by Apex View Post
    NetBIOS turned off on the new router, the master browser election not working till you went to it via the ip and then it decided to sort itself out; frankly the fact any of it works at any time is a blessing.
    I'd be highly surprised if a home router has anything to do with NetBIOS. Realistically the only setting a home router might influence is via DHCP - however I doubt those DHCP options will be present as configurable. If the option is missing, Windows defaults to on (certainly my Windows 10 does. Win11 might not)
    "In a perfect world... spammers would get caught, go to jail, and share a cell with many men who have enlarged their penises, taken Viagra and are looking for a new relationship."

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •