Posted: Tue Jun 14, 2016 15:14 Post subject: Windows 10 doesn´t see NAS
Greetings.
I have a problem seeing my NAS (WD) in Windows 10. It used to work, did upgrade some time ago the Router (WRT-160NL) and now I cant see it in the Network anymore, nor can I search for it.
It does show in the Router under USB without a problem, status here;
--- /dev/sda1
Block device, size 931.5 GiB (1000167440384 bytes)
Windows BOOTMGR boot loader
NTFS file system
UUID E026928526925BFA
Volume size 931.5 GiB (1000167439872 bytes, 1953452031 sectors)
/dev/sda1 mounted to /tmp/mnt/sda1
My Samba settings are set as Workgroup: Workgroup (same as Windows), I selected the correct drive and set Public Share.
Posted: Wed Jun 15, 2016 3:17 Post subject: Re: Windows 10 doesn´t see NAS
Painstouch wrote:
Greetings.
I have a problem seeing my NAS (WD) in Windows 10. It used to work, did upgrade some time ago the Router (WRT-160NL) and now I cant see it in the Network anymore, nor can I search for it.
It does show in the Router under USB without a problem, status here;
--- /dev/sda1
Block device, size 931.5 GiB (1000167440384 bytes)
Windows BOOTMGR boot loader
NTFS file system
UUID E026928526925BFA
Volume size 931.5 GiB (1000167439872 bytes, 1953452031 sectors)
/dev/sda1 mounted to /tmp/mnt/sda1
My Samba settings are set as Workgroup: Workgroup (same as Windows), I selected the correct drive and set Public Share.
Windows 10 doesn't see anything.
Help?
Turn on your network discovery on Windows 10. When you do that, Windows will detect NETBIOS name of Samba server on WRT-160NL, which by default is called DD-WRT. You can of course change it via DD-WRT setup page on "Router Name" or by adding this string on Samba general section of configuration file, "netbios name = WRT-160NL"
On your Windows 10, if you press "Windows Key" and R and type in the UNC location \\DD-WRT or \\192.168.1.1, as per Detection, you should be able to see your Samba/NAS share.
If you don't see DD-WRT (The default NETBIOS) or any other computer (NETBIOS) names on the network under your windows "Network" icon, it means "private network discovery" is off. If you can't open the UNC \\DD-WRT\share-name, it means your Samba/NAS on WRT-160NL is not configured properly. _________________ Linksys 54G v2
Linksys 54G v6
Linksys 54GS v6
Linksys 120N
Linksys Valet-M10 Tomato v132
Linksys Valet-M20 Tomato V132
Netgear WNR3400 Advanced Tomato
Netgear WNR3400 Advanced Tomato
TRENDNet TEW-632BRP DD-WRT r22118
TRENDNet TEW-632BRP DD-WRT r22118
Buffalo G300NH DD-WRT r22118
TPLINK WNDR1043ND DD-WRT r22118
TPLINK WNDR1042ND Stock
TPLINK WNDR841ND r22118
DLINK DIR-835 A1 r22118
DLINK DIR-835 A1 r22118
DLINK DIR-835 A1 r22118
DLINK DIR-501 Stock firmware
DLINK WBR-2310 Stock firmware
Linksys E3000 Shibby Tomato
Linksys E2500 Advanced Tomato
Netis WF-2404 Stock
Netis WF-2404 Stcck
Belkin N600 Extender (Bricked on its own)
I have similar problem with WIndows 10. I can't access DD-WRT NAS. It says
\\DD-WRT is not accessible. You may not a=have premission to use this network resource. Contact the server administrator to find out if your= have the permission"
I had no problem in Windows 7 to access the drive. I added user nae ans password in DD-WRT but it does not work.
Joined: 16 Nov 2015 Posts: 6440 Location: UK, London, just across the river..
Posted: Sun Jan 22, 2017 8:59 Post subject:
in that case there must be some settings in W 10 firewall that are blocking NAS, so either unblock it or create a new rule that permits it, make sure you use home networks not private or just the firmware is buggy, for certain tings some builds are better than the others... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
