Hi,
Missing network device - EXTERNALDRIVE
Since the last Windows 10 update which I installed on Dec. 9 I am missing one devices in Explorer > Network on one of three network computers.
They are all present on the other two computers. One of these is Windows 10., the other is Vista Premium.
The complete device list under network is Frankspc, Charlottespc, and Sue_ASUS and ExternalDrive.
The missing device on the Explorer list on Frankspc is EXTERNALDRIVE. I can ping it at 192.168.1.3
Any Ideas on how to get it back in the Explorer list?
Thanks
Frank C
HP Envy
Windows 10
I got my Explorer Network access straightened out by following the instructions of KRL here:
Solved *** How I Fixed My Missing Network Homegroup Computers *** - Windows 10 blog
I don't have 100% success yet because one laptop (Sue_asus) does not show the EXTERNALDRIVE. The other two do show it.
The Explorer display now looks like this:
network2.png
My fix didn't last through a restart. I am still in need of a fix.
Frank C
Frank, you may want to try setting up a HomeGroup. I didn't want to - don't like HomeGroups - and didn't think I should "have to" use a HomeGroup when I had a perfectly good Workgroup already setup (but broken after last update), but I finally broke down and just did the HomeGroup. Now everything is working and communicating as it should.
If its an external drive ( a network attached storage drive) , then the problem most likely is that with Windows 10, it is unable to 'see' samba devices in the local network. Windows 10 seems to use SMB3.11 protocol by default, so you can change this by the following command prompts:My fix didn't last through a restart. I am still in need of a fix.
Frank C
Go to Start, then Command Prompt (admin)
at the command prompt enter the following commands. Its easiest to copy and paste from below, and press enter after each paste:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Then reboot your Windows 10 machine; with a bit of luck you will now see your external drive on the 'network' list.
Thanks Kiwi1,
That did the trick. I ran the cmds on both Windows 10 computers and I now see the EXTERNALDRIVE in Explorer on both.
This is very important to me because that is where I keep backups.
It would have save me a lot of time if Microsoft had told me that this was a necessary step.
CountryBumpkin,
I will also try to get the Homegroup set up correctly.
I do see homegroup but it insists on a password to join. I don't know the password and I can't find it.
Perhaps I can create a new homegroup and delete the old one.
I'll work on this.
Frank C
Yes its hard to find info about that issue and I spent a lot of time googling to find out more; its buried in Windows support here but doesn't actually mention Windows 10 and I found that it worked by trial and error.
By the way, even though you couldn't 'see' the Network Drive, you would still have been able to map the drives by using File Explorer, Map Network drive, \servernamefoldername
Microsoft ought to be a bit more proactive, but I also think the NAS drive folks such as WD should re-issue firmware for there drives that supports SMB3 and fixes the problem
Kiwi1,
Thanks for your detective work. I had spent hours on the problem with no success.
Country Bumkin,
I did try to set up a Home group. One computer running windows 10 could not join.
There is a access error of: 0x80070035 which i think is interfering. I posted this on Network and Sharing under Error code 0x80070035
Frank C
I got the homegroup set up. I needed credentials for both windows 10 computer to access each other.
However, this did not solve the local network access problem between the two Windows 10 computers.
If I try to open any folder, using homegroup, on SUE_ASUS from Frank C nothing happens.
Likewise, the reverse is true. SUE_ASUS cannot open any folder on Frank C.
Frank C
