Windows 10: Can't see other computers in Workgroup on Windows 10 computer
In our home network with a mix of Win 7 and Win 10 PCs plus a NAS my new Win10 laptop only sees 2 other PCs - in spite of having tried most of what is described above. Correction: Sometimes it sees all but mostly not.
But all PCs can be accessed with \\Computername so my quick&dirty fix is to do so and 'Pin to Quick access'
Not very elegant but it works until MS gets it right...
Yeah, that's the problem I have. My older PCs on the home network (one running Windows Home Server and one Win 7) get this;
Imgur: The most awesome images on the Internet
Whereas my Laptop with Win 10 Pro can only see these on the same network;
Imgur: The most awesome images on the Internet
Very, very annoying!
I have a little "different" problem right now compared to many others. It's on the same topic so I thought I'd still use this thread instead of starting a new one:
My home network consists of a server running Windows Server 2012 Essentials.
My desktop running windows 10.
My laptop running windows 10.
I skipped domain join for my clients and instead just use the same WORKGROUP.
Now, my desktop works lika a charm. Adding a folder from the server as network drive works and all computers (server, desktop, laptop and also my TV-receiver which is connected through samba) are seen in the explorer for network and all can be browsed.
My laptop can also see all the clients, HOWEVER, the server client can't be browsed, it will just think for half a minute and then give message saying it can't be reached and control the spelling etc etc.
Adding the network drive from one of the server folders also fails. I can however enter the actual ip-address of the server in the explorer and then it works and I can browse all folders. Also giving the network drive the ip-address enables it as well.
I tried rebooting the router and all computers on the network. I tried netcfg -d and ipconfig /flushdns on my laptop, nothing works.
What could be causing me seeing the server in "Network" on explorer but failing to access it?
EDIT: Okay I think I know the problem now... if i go into cmd and ping the server name, I can see that it tries using the wrong ip (192.168.1.2 instead of 192.168.13.2). How do I update this for the laptop? The desktop resolves the right ip. Like I said I already tried flushing the dns on the laptop but it doesn't change. Can I somehow manually editing the record?
Last edited by olo; 17 Aug 2016 at 14:12.
I come bearing gifts.
None of my desktop PCs are new, so I have a few old ones instead. They all run Pro Versions of Windows (XP, W7, W10).
Networking is usually 'hit and miss', and every file manager I have tried stumbles, stutters, and many times gives up, on showing shared folders. I also have an ADSL2 router that has a USB3 socket, which was extremely 'hit and miss' when trying to access that from my PCs.
AND THEN I FOUND THIS -
EF Commander Free Download
It is better than ALL the other file managers, in finding shared folders (including the shared router USB thumb drive), and is very fast.
And it is free.
Running Windows 10 build 1607 (Anniversary build) (This build is buggy as heck, beware. Hopefully, issues straightened out soon):
I resolved my Issue this way: I am connected to both a domain and run a small office workgroup at the same time. The workgroup computers would return an error of network path not found when clicking on the computer icon in Network. I finally got in by typing in the network address bar \\computername (e.g. \\freddellcomputer).
The username and password login box comes up and you have to log in as the windows account of the computer you are trying to connect to. If you use a Microsoft account, type that in (the account you use to log in to windows), not the user name you see from the start menu, because that won't work if different from the windows account name (Thanks Microsoft for added layer of confusion--no need to have two user names). This worked for me. I haven't tried setting up a homegroup, but on my other small home network, that works too, because it lowers all the security and allows all home computers to access each other. They really need to have a network panel where you could set up your whole network and user accounts and security in one place instead of fumbling around in different section of windows. I hope this helps and saves people some time. Aggravating!
Have you downloaded and installed the Windows Server Essentials Connector launchpad? When you connect using the connector and click on shared folders, the connector opens up a separate Windows explorer window and then all the network computers show up including the server. Outside of that only the workgroup computers show up.
I tried most every fix....disabling IPv6 in adapter properties worked!
First time poster. I joined only to share my fix and to show appreciation for all of the other shared remedies. The fix that worked for me is one almost anyone can try (very easy to do). No elevated CMD prompt or deep networking knowledge needed. Right click the network / Internet icon at the bottom right of your screen. Open "Network and Sharing Center". On the left hand side, open "change adapter settings". Under properties, uncheck IPv6. My NAS INSTANTLY showed up on the two Windows 10 machines on my WORKGROUP after disabling IPv6.
Thanks StayLeft - I did exactly what you proposed above and it worked for me as well. I was able to immediately see a Linux box which I could not see before. The odd thing is that on a Windows 7 box, I can see this same Linux box and I've verified that the IPv6 setting is checked for the network adapter.
The only outstanding question is what do we lose by unchecking IPv6 in terms of functionality? Google tells me... (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. But in practical terms I don't know what the implication is. Nevertheless, I'm sticking with the config change for now. Thanks for tracking this down!
Found this site while looking for a solution to "losing" other networked PCs in a Workgroup. I could still connect to the other PCs but their names were missing in File Explorer. After trying some of the solutions with no success and being shy of editing the registry I turned off the router and NAS then rebooted the router and NAS and all the linked PCs have reappeared in File Explorer.
I'm embarrassed to say, my issue was a simple one. I had two PCs with the same machine name. Renamed one and all was fine.
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...