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

Hi there.

Old perennial has come up again.

W8.1 on a PHYSICAL machine SEES W10 machine on network but can't access any files. W10 can access W8.1 computer -- no problem at all. Same with W7 computer -- can SEE but not access W10 computer. W10 computer can access W8.1 and W7 machines (real not VM's). All machines X-64.

Build 10074 after latest set of updates - -- Powered off Computers (all 3 ), all mobile phones / tablets and powered off and reset router to ensure NOTHING hidden was on the network.

Same problem after restart. --W8.1 and W7 machines cannot access anything on W10 system although computer visible in Network.
W7 and W8.1 machines have no problem sharing files with each other (both ways).

Files all shared.

Why is Windows Networking always a matter of pure luck -- if it doesn't work on a particular machine NOTHING - but NOTHING seems to fix it.

W10 computers -- no problem or even SAMBA (from Linux). Seems W8.1 and W7 computers just don't like W10.

Update -- restored W10 build 10061 and then - surprise you've got it !!!! - everything is working. Of course the wretched thing will then want to Update and it all will get lost again - but an interesting test.

C'mon Ms - surely in your labs you must have a few machines around where you test this stuff !!! I know it's a TEST build but Networking is fundamental these days even to quite small HOME users. I can't think of a single household near me that doesn't have at least 4 computers / tablets / phones etc.

I like the builds so far but PLEASE get networking to function without problems. If Linux can do it (all the years I've been using Linux - Networking has always worked even if setting up samba can be a bit fiddly) then it should be an absolute DODDLE for Windows seeing all the resources Ms has.

The reason why I need the W8.1 and W7 computers to access W10 rather than the other way around is that I have my storage spaces on W10 containing a large set of multi-media files which I want to access from those computers. I can't update those computers to W10 yet for all sorts of reasons.

Cheers
jimbo

:)

 

Windows 10 computers can't find Windows 7 computer in homegroup

I went ahead and upgraded the W7 machine to W10, issue remains.

I re-established homegroups , issue remains.

I turned off both my norton firewall and the windows firewall, issue remains.

The laptop that was W7 still can access both W10 laptops.

The W10 laptops can not access files on the former W7 laptop

The W7 machine now does show up as in the homegroups of both W10 laptops, but if you try to open anything from either W10 machine, the W10 laptops search and eventually bring up the Windows diagnostic screen, which when run, returns the same "Your computer
appears to be correctly configured but the device or resource is not responding" message.

 

Network drives on a home network

I was able to share files between both computers until a recent windows 10 update. My laptop, which is windows 7, and my desktop, which is windows 10 are both in the same workgroup. My W10 desktop can still read files from the W7 laptop, but after the
W10 update, my W7 laptop can no longer access the files or the printer on the W10 desktop. Both computers are in the same homegroup. All of the folders that I want shared on the W10 desktop are still shared. Any help that can be provided would be appreciated.

 

Glad I am not the only one thinking he was going mad! I'm getting the same sort of problems. The error is 80070035.

My win 10 can see the shares on the 8.1 but the 8.1 gets the dreaded 80070035 when looking at win 10.

A win 7 here can see the win 10 shares fine.

That error has been around for several years if you google it. No one seems to have a reliable fix, either.

But, yes, my networking has gone backwards since 10061.

 

For build 10074, try this:
Solved Lost home network in build 10074 - Windows 10 Forums

 

Have already set Netbios on on both comps but makes no difference. In any event, that would just be a workaround as networking should work with the defaults. Oh, well, maybe it will get fixed again in the next release!

 

@jimbo - had any luck with the networking? No joy here. Can't figure whether it is win 10's fault or win 8.1.

Hoping the rumoured 10122 will fix things!

 

Windows 10 has a new Network stack, and as such, it's in constant flux... so yeah, expect problems...

You might want to do things like disable SMB3, or IPv6. Check your event logs for clues.

 

Thanks for input, Mystere. Tried disabling IPv6 to no avail.

Coming to think my 8.1 notebook is the issue as everything is the same with 100122. Win 10 is fine with all shares available, as is a win 7 laptop.

But this darned 8.1 is really problematic. After a while it only shows itself on the network even though it accesses my NAS fine using WMC or Kodi.

This notebook is attached to the TV and is going to be upgraded to win 10 after RTM. Think I will keep to that plan as it doesn't need to attach to anything other than the NAS.

I'm moving on!

 

Did you enable LANMAN support in your 8.1 laptop to connect to the NAS? If so, that might be interfering with connecting to 10, which I believe no longer supports LANMAN as it's insecure.

Unfortunately, many old NAS's run on old versions of Linux with old versions of Samba that have old versions of CIFS/SMB that don't fully support modern file sharing, and have very insecure protocols. Windows 10 most likely defaults its configuration (and may not even support) those old versions for security reasons.

 

On one of my systems I noticed it was showing as a Public Network even though the IP address and Workgroup were correct.

I noticed there was a setting in the Networking APP concerning sharing which seems to override the normal Advanced Settings dialog. So look at Settings and then Network settings and see if the WiFi or Ethernet has an Advanced setting to allow sharing which may be set to off. On my network, the system was not visible, so your situation may be different.

Sorry I can't give more exact directions but I am not on Windows 10 right now.

 

No, haven't touched LANMAN. NAS access is fine.

 

Hi there

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

Cheers
jimbo

 

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.

 

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.