Windows 10: Windows 8.1 and W7 see W10 computer but cant access files Solved

Page 2 of 2 FirstFirst 12
  1.    22 May 2015 #11

    Hi there

    Latest build 10122 seems to have fixed the problem (this time !!!!).

    Cheers
    jimbo
      My ComputerSystem Spec

  2.    03 Jun 2015 #12

    Sorry to resurrect this thread but I have found why my 8.1 netbook got the 80070035 error when trying to access my win 10 shares.

    Both my win 10 and 8.1 comps were logged into my one MS account. When I changed the 8.1 to a local login it could then access the win 10 shares fine.

    Is this a bug? If so, is it 8.1 or 10 at fault? Mmmmm.
      My ComputerSystem Spec

  3.    03 Jun 2015 #13

    I'm guessing one of them you first created a local account then converted it to a Microsoft account, and the other was created initially as a Microsoft account.

    The difference would be that each creates a different local profile account name, and Microsoft networking probably uses the local networking account for passthrough authentication. You might want to use HomeGroups instead.
      My ComputerSystem Spec

  4.    03 Jun 2015 #14

    That's interesting, Mystere. The 8.1 did originally have a local account so your theory is looking good!

    Also tried with win 10 local and 8.1 MS and this produced the error. The error, then, is in the 8.1 machine when it is using an MS a/c.

    Never used Homegroups. WD MyBookLive NAS would likely be a problem.

    At least I have discovered something that fixes that error!

    I'll revert the 8.1 to a local account as it doesn't need to be on an MS one.

    Thanks for input.
      My ComputerSystem Spec

  5.    04 Jun 2015 #15

    Hi there

    Build 10130 seems OK except FROM ( note FROM) Samba to the "C" drive -- even when "C" is shared it keeps asking for passwords etc. to access the "C" drive or any folders on it. All other shared drives are OK including a Storage Space consisting of an aggregate of 4 HDD's.

    Win ==>Win no problem -- so I suspect something in Windows has altered the protection of the "C" drive. I'm using a standard SSD for the C drive - standard NTFS -- no GPT or anything. It's a liveable with problem since I rarely need to access the "C" drive as shared anyway.

    (The wonders of Windows networking !!!!!!).

    Cheers
    jimbo
      My ComputerSystem Spec

  6.    04 Jun 2015 #16

    Indeed, Jimbo!

    Another thing that is annoying, especially with 8.1, after a a time the network display stops showing the shared devices. Restarting brings them all back again. Whether that is the network scan failing, or whether the routers are not providing the info, I don't know.

    Anyway, I am happy that my network is doing all I want and even if 8.1 is a bit 'funny', who cares, as it won't be here long!
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
How to Add or Remove Recent files from Quick access in Windows 10 Windows 10 replaced Favorites from previous Windows with Quick access. The Quick access page is the shortest route to files you've been working on and folders you often use. These...
Windows 10 Files Search in General Support
Hi everyone! On Windows 7/8/8.1, I have always used the built-in indexer to index folders which contains portable utilities and using the search function to easily launch these executable. However on Windows 10 Build 10240, it seems that I am...
I am locked out of other computer through the network. Originally it asked for my credentials (username/password), which did not work. I found out I have to give it the machinename\domain. So, when I entered that, I still put the wrong name (or...
http://i.imgur.com/6tiV6Mo.jpg http://i.imgur.com/hDcLSPe.jpg http://i.imgur.com/5s8rLWI.jpg http://i.imgur.com/Q7UIuP6.jpg
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 02:02.
Find Us