Windows 10: Network drive not showing up (Samba)

Windows 10 x64 14393.479
External USB drive ethernet connected to my router, Samba enabled.
Recently I freshly installed Windows 10.
Before that whilst the pre-anniversery version, the external drive showed up under 'Network' in the Explorer tree and I could create folders and files.
In the router nothing has changed.
The drive now shows up, say, below 'This PC' in read mode only. Folders files, they can displayed, video can be played. That's it. I am unable to create folders or add files.
The drive does not show up under 'Network' as before.

Any suggestions?

Thanks
=

:)

 

Windows 10 Nov Update and the Network Issues that Ensued.

Networking has been broken in the 1511 upgrade.

Disabling SAMBA V3 causes a loss of network connectivity to the Win 10 machines on the network. You can't see NAS (Samba) drives in File Explorer as well as PC Shared Folders with the 1511 upgrade.

I've set my NAS drive as a shared folder until MS fix this as there's a danger of seriously screwing things up with some of the fixes suggested f you aren't experienced in network protocols etc. It seems the safest option.

For MS to expect people to try to fix broken basic functionality with low-level network commands on a consumer product may be pushing the fix-it-yourself philosophy a bit too far....

 

Windows 10 November Update - cannot see other network devices

The most persistent news I have on these issues is that my Linux Samba server still does not show in the Network Neighborhood on the Windows 10 machines.

My home network (Workgroup) consists of 2 desktops, 1 laptop and 1 Surface Pro 3 all on the latest Windows 10 1511 build. And 1 Linux machine that I upgraded this week to Fedora 23 and Samba 4.3.1.

The Linux machine also serves as the WINS server and a VPN server. Thus offering remote access to the Windows based shares.

After the upgrading of the Windows machines several weird and peculiar connectivity problems turned up. Machines not showing, not able to connect to shares, printers (wired to the Linux machine) not reachable. Long waits on restoring persistent shares mapping
to drives.

I'd subsequently checked, reset and/or reconfigured all networking related settings like hostnames, workgroup name, protocol settings, etc.

End of the story is that everything is working as it should without any serious issues.

From the Linux machine I can access all the Windows based hosts and shares again. And all Windows 10 machines are shown to be part of the Windows Network.

Windows 10 machines now do show in each others Network Neighborhood. Persistent share to drive mappings work as a charm again. No gibberish output for nbtstat -r anymore. Also the Linux host, share and printers can be reached by name from all my machines
again.

I did not disable any SMB version setting anywhere. I do even expect everything is communicating based on the latest SMB v3.11 level which is supported by the now installed Samba 4.3.1.

Perhaps here a huge benefit having a home made Linux based 'NAS' which gives maximum flexibility in upgrading and configuring. Could be much different from NAS devices with much older Samba releases embedded.

As said. The only persisting minor issue is the Linux Samba server not being visible in the Windows 10 Network Neighborhood.

 

Sounds like account permissions. The previous account on the previous install is probably admin. You probably need to reset permissions on the external USB or try to take control with Windows 10.

 

Regretfully, I am afraid I have no idea how to do that... :-(

 

Right Click on Folder or drive. Click Security Tab. Click advanced button on the Bottom. See Owner, see if you can change the drive to your account.

 

I understand what you are saying, but in this case 'properties' look different.

=



=

 

Plug in the USB to your PC and try this. Being a Network drive is why you can't access the data.

 

If I want full access on my router attached USB drive I have to log into it using my routers admin account.

Sounds like you're no longer logged into the shares using an admin account for the router.

Try entering the IP address of the drive \\192.168.1.xxx\ into Windows Explorer to see if you can force a login prompt to show.

 

Below is the situation from the past, a few weeks ago, and now, after fresh install of 1607.
Before it was located under 'Network' and had a different icon. Could access it like a normal drive.
Now it is under this PC and it looks as it is a media player thing
=










=

 

That's normal , if you're not logged in correctly , windows will still see the DLNA media server as available and stream from it.

You still need to force a login to get full access to the drive.

 

I give up. Forget it. Spent way too much time on this. Unable to restore the old situation for one reason or the other.
Anyway, thanks for the feedback.
=

 

Did you Try entering the IP address of the drive \\192.168.1.1\sda1\ into Windows Explorer to see if you can force a login prompt to show?.

 

Old thread but this happened to me this week and I think must be to an windows update resetting something but the following helped:

 

Thanks. Being unfamiliar with this matter and not being able to solve it, I gave up and actually already got rid of the drive.
To be honest: I did not give it a try with another external drive.
This was something falling within the category 'nice if it works', but if it doesn't, well, then the drive physically has to move between living room and my pc. Maybe I give it a try with another drive, one of these days.
BTW and FWIW... as for the settings, with me, they read SMB 1.0/CIFS (not CIFC)
Don't know whether it makes any difference though.

-




-