New
#121
Now for the fix for the Linux NAS boxes!
Let me just chime in and say that I am having exactly the same issues mentioned in this thread. Specifically these issues:
- Workgroup computers not showing up in the Networking window
- even after applying the "troubleshooting" fix that supposedly fixes the missing networking sockets issue, I still can't see every single Workgroup computer (only Win 10 boxes are showing up, Windows XP desktop isn't showing up)
- Homegroup isn't working: even after creating a new Homegroup, other computers seem to join it but don't show up
- BIGGEST PROBLEM OF ALL: The Windows XP box has my Printer attached to it, so all the computers in the home network access this "server" to print remotely. Because this latest update broke networking, Win 10 boxes can't detect the XP box and thus can't print remotely to this printer! HUGE HEADACHE!
[update]: I was able to fix the remote printing issue by manually typing in the network location of the printer using the "Metro" settings app-->devices-->add a printer or scanner-->the printer that I wan't isn't listed-->select a shared printer by name-->[entered in network location of printer on network]-->next-->SUCCESS!
Is Microsoft aware of this issue after the latest Cum Update? Why did this happen?
PS: I also tried clean installing Windows 10, but this doesn't solve these network issues! Basically, it looks TH2 (and later) created these problems, as the July RTM build didn't have these problems for me at all!
Last edited by rogerwilco91; 15 Dec 2015 at 23:15.
Do you mean that with SMB2/3 enabled you see all Win7/10 comp's and can reach the NAS shares added to QA without problems?
Cause I cannot. I have serious problems reaching my NAS and my Mac with this setup.
I'm laughing with you, and it pisses me off that MS force us to be involved in the beta program without consent.
Have you tried what's in post #5 here Win10 suddenly stopped seeing other computers on network
Have you tried diagnostic measures on the problem machine--SFC /SCANNOW and https://www.tenforums.com/tutorials/7...age.html?ltr=D?
Yes, I ran sfc /scannnow and of course it found a bunch of problems that it could not fix - that's a surprise! In the past, I have never had much luck trying to fix a screwed up Windows system so I've resigned myself to take the time and do a fresh/clean install of W10 v1511. Hopefully, that will end this saga.