Windows Ten having a problem accessing the Workgroup

My first post on Tenforums.

A recent addition to my home network simply called HOMENET consisting of an XP-style Workgroup brought forward to Windows 7 on two PCs. Now I've added a third running Windows 10 to experiment with. The Win10 is producing an error and not recognized on the workgroup called HOMENET. I can make a screen shot of the error the text of which is vague and says it could be this or it could be that involving passwords or permissions which are not usually a problem.

My question is : Are there common errors with Windows 10 combined with an old style Workgroup?
I felt the need to upgrade but even early on, I've sought out the Classic Shell programs that get the old Windows 7 desktop back and not so much glitz and eye candy.

I'll make a second post when I get a screen shot.

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

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

No, Windows 10 see's Vista and above without any problem with SMBv1 disabled. It uses WSD vs. netbios for the discovery method.

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 am making a quote since I was not logged in properly.

Full disclosure starts here of things I did wrong and forgot.

1.) Did not start with zeroed disk (low level format, then use the Admin tools etc.

2.) Win10 wrote over (upgraded it said) my Win7. I did not want that.

3.) Since it wrote the profile, I did not see the option for the Password so it
showed up as blank which is part of the screen shot error. Previously, since this
is my private user stuff, I just click through the Password on Win7 install and
it goes through.

I'll come back when I have cleaned the disk, done the format and run the installer
again. It should be simple: just join HOMENET (sorry for all caps, that's the way
my workgroup looks.)

Also on the Services: I was fooling with those from info at Sevenforums just lately.
A clean slate is needed. But I will look up those Services from the Black Viper list which I was
using to tweak for speed. Perhaps a bad idea.

I'll get the screen shot posted. Thanks for your replies.

See attached

Continuing,

I did the scratch install requesting Custom rather than the dialog to save everything.

The install goes smoothe. I gave it a password. I asked for HOMENET in the workgroup dialog which is unchanged from what I know from Win7. It gives the welcome greeting.

The same error appears.

But I noticed that File and Printer Sharing are not turned on.
In the scant desktop info can you give a path to that screen? In the meantime I'll try to
work through it.

The 'details' dropped down on the error box says network path not found.

I'll review the machine name and such but it looked like it had a connect at the Joined "Welocome" dialog.

Progress.

With File sharing turned on I was able to get to the dialog of username and password again. This seemed to be part of Win10 setup to have a domain name and then be logging on all the time. ( The only other option was to connect to a business network if I remember correctly. )

The MSI-HD opened it's network files from MSI-WIN10.

Can I make my username as an administrator or some such to eliminate all the logins to my own rig?
BTW I never understood all of the HD sharing (make them 'J' and 'K' and so on) from back in the XP days.

The second major question is: the network node of Win10 does not show the default "Shared" folders called Public, music, some others.

Perhaps the Public Folder in use for HOMENET can be transferred/shared to the Win10 PC?

As a workaround to all these domain actions could I revert to doing the install with the all the data saved options and just remember to turn on File and Print Sharing?

Can I make my username as an administrator or some such to eliminate all the logins to my own rig?

Did you tell it to remember my credentials ?

BTW I never understood all of the HD sharing (make them 'J' and 'K' and so on) from back in the XP days.

If you're referring to map a network drive, this tutorial should help - Map Network Drive in Windows 10 | Windows 10 Tutorials

The second major question is: the network node of Win10 does not show the default "Shared" folders called Public, music, some others.

Did you turn on Network Discovery and File & Print Sharing for Guest/Public ?
Did you setup the Share/NTFS Permission for the Public folders you want to share ?

Perhaps the Public Folder in use for HOMENET can be transferred/shared to the Win10 PC?

You should not have to do this once Public folder sharing is setup.

As a workaround to all these domain actions could I revert to doing the install with the all the data saved options and just remember to turn on File and Print Sharing?

I wouldn't, seeing how you just did a reinstall.