Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Windows 10 SMB/Sharing/LAN issues

Oct 8, 2015 8:33AM PDT

I am having issues with sharing folders over my network after a recent upgrade to Windows 10. Here are the details:

I have 2 computers on my home network. One, an HTPC, running Windows 8.1 and a second, Desktop, which I recently upgraded from Windows 7 to Windows 10.

The HTPC is used almost exclusively to run Kodi/XBMC. It also has the majority of my media stored on its HDDs, except for one drive of media which is in the Desktop.

Prior to upgrading, the HTPC had access to said drive over the network through Kodi/XBMC via SMB. After I upgraded the Desktop to Windows 10, the HTPC no longer had access to these files. Kodi/XBMC can see the computer on the network, but cannot access it/any shared folders.

Here is what I have tried to far:

-Disabled password protected sharing on both machines
-Disabled firewall on both machines
-Disabled anti-virus/Windows Defender on both machines
-Shared both the root drive as well as specific folders on the drive, giving full read/write access to 'Everyone' in the homegroup

-Attempted to directly map the network drive to the HTPC. When I try to do this via the Desktop's name, I get error code 0x80070035. When I do it with the Desktop's IP, I can map the network drive, but when I try to access it, I am told I do not have the proper permissions.

I'm not sure what else, if anything, I am missing to make this work. Any tips would be greatly appreciated. Let me know if there is more info I need to supply to help troubleshoot this issue. Thanks.

Discussion is locked

- Collapse -
Clarification Request
Tell how you deal with accounts, network shares, etc.
Oct 8, 2015 10:48AM PDT

First, if you happen to use the email login system I won't write there is a fix. I go back to local logins. (always.)

Next if a network share is getting permission issues, I always see if I have an account on the PC that is serving up the content. Yes, that's well discussed and not a Homegroup issue.

I can't tell what sharing system you want to use, login details and more. For some, they don't want the security so they enable the Guest account.

--> Be careful here. Some folk take multiple tries to understand that when a share is to All Users that means users with an account. The Guest account opens it from all users to any user. The difference eluded many.

- Collapse -
Local login default from upgrade? Guest acct on which pc?
Oct 8, 2015 1:38PM PDT

I login with the same self-selected user "name" and password that I set when I originally installed Windows 7, not an email. I did read that the Microsoft email login causes problems, but assumed that since I am still using the same login/pw from before the upgrade that I was "local." Is that the correct assumption, or is there something I need to disable that I might not realize set up the email login without me knowing?

As for the other account question, my Desktop has only one user account with PW, and is an admin. The HTPC has one user account, but no PW. Do you mean I should set up a Guest account on the Desktop? And how would I point the HTPC to try and access the shares from that specific account? Just log onto the (Desktop) Guest account and re-set the shares and permissions to all?

- Collapse -
User account is Local
Oct 8, 2015 1:46PM PDT

Nevermind the first question. I opened up User Accounts in control panel and see that my account is listed as 'local'.

- Collapse -
About the guest account.
Oct 8, 2015 2:45PM PDT

Since that means we don't have to check usernames and more, that's a quick fix for many.

As to the single account, the issue of corrupt profiles means that only those new to Windows would not have a backup admin account.

To me this sounds like the same discussion as before. It worked before so no reason to talk about the router's firewall.