Windows Ten having a problem accessing the Workgroup

Today I'm reviewing the paths to the network as well. This may be very easy for 10Forums to answer.

On the MSI-HD

The path to the network folder is:

Sytem - Network MSI-HD UsersShare (pipe symbol) - Public (folder)

On the MSI-WIN10 there is no complete path to the network folder as:

System - Network - MSI-WIN10 (and that 'location is greyed out.)

I simply do not know the code to create and share folders. It looks like the folder called Public has to be shared or created on MSI-WIN10.

On Windows 10 I see no comparable stock or default folders to use. If there are any please indicate.
I'll see if I can get a screen shot of that so the path or lack of one is clear.


ok image attached of greyed out network window.


No folder can be added from the selection at top of that network window.

Some progress. In Windows 10 I found the path MSI-WIN10 > Users > Public (and the folders in it.)

Found by typing Public in the Search Bar.

I think there was some info on this above in a command statement. But I request assistance in
getting the Share statement made to, for example, share the Public Documents folder and start
putting things in that. The syntax to do this is always frustrating for me.

Again progress.

On opening the Public Documents folder and right click select for Sharing, I found that the share files on the Network button was turned off. I don't know if that's the default position. Also don't know for sure if a lookup from other PCs is possible yet. For any other new users I'll make a screen shot of that.

Maybe this has been discussed elsewhere but I have had a lot redos in the Win10 install and set ups to include backups
when I change something. Not all the clone jobs were successful and I had no adequate size flash drive to make
the prescribed repair 'disk.' as they call it.

A windows 7 Repair CD was useable for getting back my Windows 7 in someinstances. But I'm getting a thumb drive
of adequate size soon.

My screen shot is not needed since TwnForums has a nice presentation of the screens and path
to get to turning Sharing on or off.

Turn On or Off File and Printer Sharing in Windows 10 | Windows 10 Tutorials

Everything seems to going ok, so I'm ready to mark this solved and thank all who answered.

Clintlgm said:

Workgroup is pretty much the same as far as setting it up, windows 10 does give us a few headaches to get up and running. As Shares and Security have to be set up correctly

Your older computers may still need SMB 1.0 Windows 10 latest versions turn it off. Programs and Features/ add remove windows features. Also, check that these two services are running set them to auto start
Function Discovery Provider Host
Function Discovery Resource Publication

I have revisited this thread with some problems. Made the quote to check servcies again.

I have repeatedly reset Turn on File and Print sharing which doesn't seem to stick--

checking the Services Function....

Ok, I set those to Auto from Manual. One Service shows 'running' but In network there are still
no PC's visible on the workgroup called Homenet. I got through this before by simply
turning on network and file shareing. Please help to troubleshoot this with any first step
I missed. Maybe need a new thread since this was marked solved.

I don't see my reply query posted today but re running the netsh series of commands got my
network PCs recognized. I can't keep track of all this so failed to backtrack far enough. Also I did a 'tween
operation which may have interfered with the network: Classic shell and whatnot.

For clarity the commands were

Start > Cmd elevated > at system 32:

netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh in ipv6 reset.log

adding my screen shot of the results

Thanks Eagle51 for answering. This is all a bit much just to get the PC in one room to communicate with the
one in the other room.

Once set up I should have fewer problems.

However in the screen shot can you explain the errors presented?

I copied this rote from a previous post on the netsh commands.