Windows 10: Can't see other computers in Workgroup on Windows 10 computer
It is probable that having tsclient and seeing the NAS are related events.
It might be helpful looking at this link security - Mysterious Network Client - Server Fault
Well yes, I suppose that was what I was trying to say. But in what way related? What have I done in the computer which displays the NAS that I haven't done in the other computers? (Thinking aloud, really!)
I've been aware of tsclient for some years, even when running WIN XP, and it's something which has appeared on all of my computers in the past. But with WIN 10 it has disappeared (for no accountable reason that I can think of) except for this one computer.
Thanks for the link. It'll take me some time to digest that but it looks interesting.
YES!! That answers the question!
The computer on which the NAS is displayed is one that does not have its own keyboard and screen and therefore I always access it via Remote Desktop.
I have just logged in to the computer on which I usually work via Remote Desktop and the NAS is now displayed on that computer.
Many thanks for your help in tracking this down. The next question is whether there is a service enabled when RDP is in use which makes the display of the NAS possible. If so, can that service be turned on permanently? And if it can, would this be a wise thing to do?
The problem with windows 10 not seeing windows 7 or nas systems under Network like WdMyCloud devices has been a problem for some time. I have installed over 85 windows 10 systems from upgrades to Clean Install for clients and non of them ever permanently saw the other systems but the do sometimes see the win 7 computers and even the NAS but not for long.
They do see other windows 10 systems but even that goes crazy at times and they don't even see themselves.
I had a Microsoft Support Person connecting remotely to my win 7 support PC and they could not find the problem, spent about 3 hours at it. Then said they would escalate the issue. Nothing has happened so far. I have had 28 out of the last 32 computers that users have upgraded to Win10 gone back to Win7. I like many of the features of Windows 10 but even I took all my office PC's back to Win 7 as well due mainly to this problem, as we all share data and transfer files to each other. I am in the IT consulting business and I am lost for answers. Microsoft do NOT have an Answer to this problem, that is probably why they ignore all these posts on their own sites.
YES I can get it to work for a day or two at most, then its gone again. the problem was always there but got worse after the last big Update . The unfortunate thing about this problem is many users are going back to Win7 due to it, I had to revert all my machines due to it. Great Pity.
Network Sharing issues
I have a workgroup private network that includes 3 windows 10 PC's and 1 Windows 7 PC and 2 XP Pro PC's. 2 of the Windows 10 PC's can see all 6 pc"c but one Windows 10 only sees the Windows 10 boxes. Oddly the XP and Windows 7 PC's can see and access the problem unit. I have done all of the simple things listed here and they were all correct. I went into windows firewall advanced settings and enabled several rules for the outbound traffic and I was able to see the other 6 boxes for a couple of days and now I am back to access only to the 2 Win 10 boxes. Since 2 of the three work properly, and the XP boxes and Win 7 box can see the problem PC, I know the problem lies within the PC and not the network.
I did do a work around by opening the "This PC" window and tapping on "Add a Network location" at the top. Put in the name of the pc and then the c drive or where ever you want to go. I put the C drive so I can get to every thing on that drive.
This adds access to the PC via the drop down tree in file explorer, under the This PC tab.
Still does not show in networks, but at least I can get to the XP boxes
But that won't work with an NAS running Linux. You can only do that using a sub-directory.
Since I upgraded both W-10 PC's to the new Build 14257.1000 and still have the same-o problem, this must be way down on Microsoft's list of fixes.
I still can't access from the Wifi laptop to the Desktop, get "Cannot access, check the spelling...." yet from the Desktop to the Laptop, I'm good.
Have tried everything, NetBIOS, etc.
Can anyone get a message to Gabe Aul ????
You just need to wait few hours or sometimes a few days, and the win10 machines may even not show themselves let alone the win7 machines. I have multiple machines at several sites with networks of over 35 machines and the problem is at all the sites, we may get two or three win 10 machines seeing everything including the NAS for a few days then all of a sudden they gone, then a different few see the network for a short period, and so it goes on. The windows 7 machines never fail. for fun I added two old XP machines on the network, all win 7 machines saw the XP machines but still the Win 10 machines saw nothing some of them no even themselves. It is totally random and never the same machines doing the same thing. I have a fishy idea it may have something to do with what machine takes over the master browser, I am going to play on that possibility and try some tricks. Will update. Microsoft is aware of the problem, but its deeper than we think. Had some interesting chats to some people and they seem to thing MS is trying to play the matter down for some reason, If you use a Microsoft search engine and search for win10 and not seeing other network devices few if any sites come up, but use google and plenty come up. I did not find this site when browsing with Bing only found it searching from google. Is this a coincidence or what. Cant get any response from MS on the problem or try to divert the issue or suggesting that businesses use HOMEGROUP. Seems less problems when using a network domain. but many companies are not taking a chance yet.
Lexlen, you surely describe the problem well. I only have a little home network that no longer works properly but you have a much more serious issue. I really feel for you and other business people. You can't help but feel seriously let down, even betrayed, by MS.
Your comments on Bing and Google results are interesting!
The master browser is part of the problem as win 10 has no problem on the comp that is the MB. It is just that other win 10 comps can't access the MB data. These comps give a 1231 error with net view.
NetBIOS figures here as well as the latest Insider releases show shares on Linux devices being discovered by NetBIOS and the win 10 comps by WSD.
It just seems as if MS was trying to 'modernise' network discovery protocols and this ploy seriously back fired to the severe detriment of the win 10 adopters. But it is hugely worrying that this serious deficiency was released into the wild, and even more worrying that we are being kept in the dark.
In one forum an MS employee has acknowledged the problem and says a fix may come in March! We have to hope it is 1 March.
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...