Windows 10: Can't see other computers in Workgroup on Windows 10 computer
I did read that thread. I still don't know what SMB is or why it matters, even after reading it.
In my reply #201, I said that the link Railtech had recommended led me to a discovery that solved the problem I was originally having, that not all computers in the Work Group were available in File Explorer under Network.
Now, the issue is that, when the older desktop (Optiplex755) is the MB, external drives mapped to reconnect on the laptop all come online with no issues at boot. Only one of these drives is attached physically to the Optiplex 755. When the newer desktop (Optiplex9020) is the MB, the only external drives that connect reliably when I boot the laptop is the one mapped from the Optiplex755 machine. The resources mapped from from the Optiplex9020 say that they are disconnected, even though they have connected, or so it seems because clicking the link brings up the files on that mapped drive.
What you're seeming to say now is that a fix is on its way and SMB has something to do with this issue?
SMB, which stands for Server Message Block, is a protocol for sharing files, printers, serial ports, and communications abstractions such as named pipes and mail slots between computers.
So basically a mechanism or standard for the transmission of data between computers.
SMB device discovery is done by NetBIOS. NetBIOS (Network Basic Input/Output System) is a program that allows applications on different computers to communicate within a local area network (LAN). It was created by IBM for its early PC Network, was adopted by Microsoft, and has since become a de facto industry standard.
Windows 10 because of the bug being discussed here does not discover devices at all times that use NetBIOS for discovery. Ironic isn't it!
Yes a supposed fix from Microsoft for the bug is slated for the next Win 10 upgrade in March.
I'll have to wait for the next update, I guess. I'm unwilling to run beta software on my production machines.
Thanks for that Railtech.
There is also the part Lanman plays. Lanman client asks a device for its shares and the Lanman server replies with the answer. They use the SMB protocol to communicate. But, to muddy the waters, there are different versions - SMB1,2,&3. Last year I had one comp that would give the dreaded 80070035 error when interrogated. The problem turned out to be that Lanman server on the offending comp had SMB2 forced in registry and the other client comps were using SMB1 causing the lack of communication.
Probably more than anyone wants to know!!
MS is VERY quiet on this issue but fingers crossed for a March fix. At least the Insider versions work by getting NetBIOS to do the work.
Sorry, don't know what you've tried, but I encountered similar problems and browsing here, I found that the information listed below fixed my problem:
Disabling samba3: https://support.microsoft.com/en-us/kb/2696547
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto
Been there many times, Mark. This doesn't fix the problem. WSD discovery just doesn't cut it. The Insider releases use NetBIOS as a backup for the flawed WSD discovery method.
Apart from shares not showing, another proof is just to run 'net view'. If you are not the master browser you get a 1231 error. Basically, this needs NetBIOS and it works in the Insider releases.
Interestingly, one of my 1511 comps started seeing my newly installed Linux based NAS but it can't discover my Insider Preview. And after a reboot it went back to only being able to see itself.
Waiting till March but not holding my breath!
Applied update KB3140743, and rebooted. Linux server shows up in network now.
This worked 100% on all my PC's. Now can see them all and access them all.
It sounds like good news is on its way. I read over the Update notes for KB3140743 at this link:
Windows 10 receives cumulative update KB3140743, now at build 10586.122 WinBeta
Do any of you folks know if that is a beta user release? I honestly couldn't tell from what was written.
Rolled out to all of my machines today via window update, so not beta.
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...