Do you have all the correct permissions applied on the shared folder? I.e, the permissions for the account you are using to access this folder?
I've got no issues connecting to my Thinkpad running Windows 10. There was a time, as I mentioned above that I had to give permissions to all and sign in as a guest, but since a few updates it seems I don't have to do that anymore. I can just use my normal account now.
Having used Windows File Share for over 20 years, I can say that is usually works fine, but sometimes, you just end up with something not working, and there's no real way to fix it. You can usually work around the problem using IP addresses directly, but it's always been a little broken.
Oh, I didn't mean to imply I wasn't directly connecting via IP address. That's just the way I've always done it. I was more meaning the account credentials and ability to actually connect are working.
Once you can get the computers to see each other, you're 90% of the way there. It's just this whole "new" Microsoft account thing that has made another mess. Not everything that can connect through windows file share likes accounts made using a Microsoft account. I have to assume it's the fact that your log in account is an email address in that case, and older software gets very confused when there's an @ in your username.
No, I just never set my Windows account up as a MS account. I worked around that. The sole user account on the machine is a local admin account.
This is most likely the answer. If you did not opt for a local account when setting up Windows 10 (and they make it very un-obvious in the recent versions) than I would suggest either removing your M$ account from Windows, or creating a new user, and setup your shares from user’s credentials instead.
Leopard should work out of the box, but I believe you’d be correct for Tiger. I usually use AFP for everything, my Windows use is pretty much limited to games.
