Windows 10: Another can't see other shares in Workgroup thread.

Ever since the Win10 1709 update, my network has gone off the rails. I'm hoping you folks can help me get it back.

I have three computers connected through a router. An office computer, shop computer and a laptop. The office and shop are hard wired and the laptop is wireless.

Immediately following the update I had absolutely nothing in the way of connectivity. I found the update had changed the workgroup names back to the default name "Workgroup". After changing this, I now have partial connectivity. The office can connect to the laptop and the shop can connect to the laptop and the laptop has full connectivity with everything. The office and shop don't even list themselves in network computers.

Here's a shot of the network information on the office computer.




The shop computer is the same except says Network2 rather than Network and Local Area Connection rather than Ethernet.
The laptop says ATT383 (router name), and Wi-Fi (ATT383).

All of my network connections are dhcp. I read in one place that this is correct and another that said to make them static. Personally, I don't think this has anything to do with the issue but felt I should throw it out there.

Thanks in advance for any and all suggestions,
Walt

:)

 

Sharing problem on Win 10

I have 3 computers installed win 10 education version.

Now I have 2 questions:

1. 3 computers are in the same public lan. when I changed one's workgroup name, other computers can still see this computer in the network. How to use workgroup correctly?

2. 3 computers are in the same public lan. I shared a folder in one computer, how can I make only one specific another computer's account visit this folder, while other accounts can't see or visit it.

thanks.

 

Want windows 10 machine to rejoin a workgroup and see files on XP machines

This was working but with the last Windows update my Windows 10 machine no longer sees the Workgroup it belongs to. I can find no instructions anywhere on how to get it to see the other Workgroup machines again and to be seen by them. What happened? How
do I fix it?

The Workgroup name is intact and has not changed on the Windows 10 machine but it can't find the network or the workgroup. Network Discovery is turned on. This had been working just fine for over a year such that I could share files and printers.

 

I assume you are talking about the computers not seeing one another in the Network section of File Explorer. Microsoft really messed things up with this and they are aware of it. Why they are not doing something to fix it is unknown. There are a couple of workarounds for this.

1. If you have a router that has the capability of working as the "master browser", this would be the best option.
2. Otherwise as a temporary fix, if you enter the UNC name (as "\\<computer name>") of each missing computer in the File Explorer Network address bar, the computers should pop up. Unfortunately you would probably have to do this each time you restart a computer.

Good luck,
JohnD

 

This is really not what I wanted to hear.
I tried your suggestion of entering the UNC name and that does work.
Thing is, most of my files are consolidated on the office computer and I can't use this method to open them in the shop.
I would need to transfer the file to the shop, work with it, then transfer it back.
Thanks for the info John.

 

Well, the work around works much better than I thought it would. After my last post, I realized the syntax you used in the address bar is the same as that used to set up a shortcut. I went out to the shop and, sure enough, even though the network is not showing, the shortcuts work just fine. I can get inside any program, navigate to the directory I want through the shortcut, and it will open and save normally.

I'm marking this as solved until Microsoft gets off their duff.

Thanks again John.

 

As another workaround, you could set up a homegroup on one of the hardwired computers, and join the other two to the homegroup and see if that allows you access what you want to - avoid setting up the first homegroup client on the wireless laptop as a small number of wireless networks have issues with being the "Base Station"

 

I tried the homegroup thing. Maybe I was doing something wrong but it didn't give me much access at all.