Windows 10: Can't see other computers in Workgroup on Windows 10 computer
From the link that Railtech posted the other day, I found this new link:
One of the desktops did not have the service "function discovery resource publication" running nor started. I changed that setting and now I can see all computers in the Workgroup. I don't have a NAS drive but someone on that link seems to be indicating they were able to upgrade SMB, and, from what I've gleaned, SMB is related to NAS.
I have a small Workgroup setup here so that link may not be useful to those of you with larger networks. Heck! It might not be useful at all but, if it is an answer for any of you, I'd sure like to know.
I have a mixed peer-to-peer network with Win 7 Pro, Win 8.1 Pro and Win 10 Pro. Wholesale changes are a bit cumbersome to implement so I generally make changes computer-by-computer as needed.
I have a Windows 10 system that isn't showing all the computers. It's only showing WSD discovered systems. NetBIOS is turned on on its NIC and it's been rebooted since. In fact, that made no difference.
This appears to be a case of Win 10 not showing any NetBIOS-discovered devices. So, I'm wondering if there's a way to enable that?
You said a mouthful there and I agree with you that NetBIOS discovered devices are not showing up when in the mix of network attached devices. Example, my fairly new Asus AC3200 Tri-Band router is discovered by my attached Win 10 systems by WSD. I have a WD MyBook HDD attached to that router which uses NetBIOS discovery. Well, as you might guess sometimes that device shows up and sometimes it does not. I've wondered too if there was a way to force NetBIOS to run but so far in my research I haven't found it. If you do please post it here because I think that would be the magic bullet if you get my meaning!
We have usually turned off ipV6. So, on the one Windows 10 system, I took a hint from this thread and turned on ipv6.
Now, this computer has been sitting on the network unused for weeks.
It was only showing around 8 computers using the discovery method WSD.
Now it's showing all the NetBIOS-discovered computers it appears. There are a lot more of them!
I've observed some new behavior and I'm wondering if any of you might be able to explain the "why" of it.
As I've mentioned previously, there are three computers on my small network. Two are desktops running Windows 10 Professional, which was the upgrade path from Windows 7 Professional. The laptop is running Windows 10 Home, which was its upgrade path.
When the Optiplex755 Windows 10 Pro computer is the master browser for the network, all external drives mapped on the laptop connect when I boot the laptop. When the Optiplex9020 Windows 10 Pro computer is the master browser, I have a scenario where the drives are reported as not connected but clicking on them proves that they are.
My best guess on why the two desktops take turns at being the master browser is that this role is granted to the first computer that completes its boot sequence. Or, if I reboot the master browser computer during the day, the role is switched to the active computer on the network.
The Optiplex755 is an older, refurbished computer. The Optiplex9020 was purchased new in June 2015. My most important external drives are connected to the Optiplex9020 because it has more horsepower.
I've just tried disconnecting and remapping those drives, shutting down the laptop completely, and rebooting it. The drives appeared to have not connected (i.e., red X) but clicking on those drives proved they were.
Can someone suggest a reason for this? Do you need more information? I'd call Dell again but, well, they weren't able to help me with this problem last time I called and I don't want to waste hours trying to get support from Microsoft again.
A Solution found
I admit I haven't had time to read through all the thread, but in case anyone wants to know, a solution is found.
Enable both SMB1 and SMB2 using PowerShell ISE. In y copy of Windows 10 I had Powershell and Powershell ISE installed by default (10 Pro).
Powershell ISE has the cmdapplet required.
Follow the steps to enable both SMB1 and SMB2 and all works again. Looks like Win10 totally disables SMB1 by default with the latest builds, stopping a lot of Linux based machines showing in particular, but also stopping some windows machines showing up.
No restart I needed to test it, just refresh the "network" page after running the applet commands
I have so much trouble networking with win10. You'd think these things would get easier over time. I've been using windows for years, XP was difficult enough to get networking to work but now I've just about given up with win10. I'm going back to using a usb stick to transfer files because nothing makes sense anymore. I can see all the machines from one pc including the old XP but the same XP machine can no longer see the new win10 machine but it can still see my other win10 machine. Homegroups, workgroups, networks, user groups, admin, pins, Microsoft account log in, wifi, whatever! I'm starting to hate it all. They have over complicated our lives with this crap.
I give up, maybe in another 10 years things will improve with Microsoft networking but for now it's still a huge time wasting confusing exercise. I have better things to do with my time, these things should just work. Enter a password, done!
I got fed up with this stupid 'Homegroup' problem, and decided to try by removing it and just using the Workgroup, but at the same time I renamed the Workgroup on all computers to ensure a consistant name.
After this I shared what I needed from each concerned computer, and wonder of wonders.. everything is visible everywhere... including the Printer I have been having trouble with 'seeing' on one of the computers. All appears to now work, so seems best way is to totally forget the Homegroup and revert to old standard Workgroup practices.
[QUOTE=austwhite;575573]I admit I haven't had time to read through all the thread, but in case anyone wants to know, a solution is found. ....
Forgot to mention Powershell ISE needs to be run with admin privilege.
Note: I do not use homegroups, I find them insecure and a waste of time and effort so I can not say if this will work with homegroup. When using Workgroups it is definitely critical that ALL Devices belong to the same Workgroup, but this has always been the case since Workgroups was conceived.
Is everything working good for you without any issues?
i upgraded 2 computers to windows 10 and java doesnt work on both
Finally installed Win10 on a computer with raw HD. It installed realtively easy.
But I can not figure out how to setup a network to see two Win7 computers on a small business type workgroup.
I disabled Homegroup since I am most comfortable...