Check that network discovery is on for the Windows machine as well and that the profile is appropriate, (the public profile cripples Windows network connectivity)...

https://www.isunshare.com/windows-10...indows-10.html

Ok it's already on.


Also- to ferrari-

I checked the Function Discovery Resource Publication and Function Discovery Provider Host, and they were both off so I truned them on.

Still won't connect.

Ok, and appropriate profile (not public) configured? Other than that I have no further suggestions I'm afraid.

Wait what's "appropriate profile (not public)"?

Refer to the page I linked to in post #17, or search 'windows 10 network profile' for information on how to configure it.

Oh right, right, yea It's already on.

Well, hell now I just ran Malwarebytes and it quarantined a bunch of stuff but when I rebooted it still didn't work.

Well but hey thanks for sticking with the question for so long. I'll fight it again in the morning,

rw

I don't know what you mean by this reply. Make sure the network connection is not using a public profile.

Oh I see- yes, I've tried with both detection on and off, doesn't work either way.

No, I'm referring to the network profile (home, work, public) for a given connection.

So then we're not talking about this, the url you gave?:

https://www.isunshare.com/windows-10...indows-10.html

Yes, that was for network discovery etc, but you can also change the network location (profile) for a given network connection. I'll leave you to check that out further

Oh I see, ok thanks I'll circle back,

rw

Ok I looked around to find out where to set it to public or private, and I couldn't find it- but- I did find under the file and print sharing it's options said "Private (current profile)" So looks like I'm set to private, right.

Similarly in Network and Sharing Center / Advanced Settings, it also says "Private (current profile)" too.

That's what I want, right?

Ensured. It is still relevant and timely.

Shouldn't it be still supported for backwards compatibility?