Shared Folders Intermittent Disconnect

Page 1 of 2 12 LastLast

  1. gfd
    Posts : 74
    Windows 10 Pro 2004 (19041.264)
       #1

    Shared Folders Intermittent Disconnect


    Greetings,

    I am new to this forum. My question is in regards to shared folders. I run a desktop and laptop connected by ethernet, through a router. Both machines run Windows 10 Pro. Both machines have static IP addresses setup in the router. I do not use a software firewall and both computers are allowed onto the network.

    I share folders on both machines in order to run client software on the laptop which connects to the flight simulator on the desktop. All of the shared folders have full control setup for everyone in both security settings and the shared folders tab.

    There are HomeGroups set up on both machines with the correct information.

    The problem (finally you say) :) is that occasionally, one computer cannot open the shared folders on the other over the network. This doesn't happen all the time, nor is the solution consistent. Ssometimes closing and reopening the netwok folder fixes it. Sometimes just waiting does it. Other times, I have to reboot the computer(s). This creates issues with my client software tryong to connect to the desktop. The error is: 0x80070035 Windows cannot find.....(to paraphrase).

    I should point out that the other machine shows up in the network folder. I just can't access it when this happens.

    This happens mainly on the laptop attempting to connect to the desktop, although once in awhile the desktop cannot find the laptop.

    I have checked and rechecked settings, deleted and rebult the HomeGroup, ensured password protected sharing is off, network discovery is on; amongst other things.

    I read about changing the shared computer name to its IP address. I also read somewhere about changing a number of registry entries that would force a change in Windows network behaviour. Now I'm fishing :)

    If anyone who has experienced this could give me some trouble shooting steps and/or solution, I would be most grateful.

    Many thanks,
    Graham
      My Computer


  2. Posts : 1,936
    win 10 Insider
       #2

    Win 10 network discovery is munted. Try the registry mods to restrict to SMB1. Run the commands in the admin command prompt.

    Restrict to SMB1
    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
    sc.exe config mrxsmb10 start= auto


    ------------------
    Reset back to default
    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
    sc.exe config mrxsmb20 start= auto
      My Computers


  3. gfd
    Posts : 74
    Windows 10 Pro 2004 (19041.264)
    Thread Starter
       #3

    linw,

    I am not familiar with the commands. Do you want me to run Restrict to SMB1 and Reset or just the Restrict?

    Thanks for your help.

    Graham
    Last edited by gfd; 13 Jan 2016 at 02:06.
      My Computer


  4. Posts : 1,936
    win 10 Insider
       #4

    Just the restrict. The reset commands are to put it back as it was.
      My Computers


  5. gfd
    Posts : 74
    Windows 10 Pro 2004 (19041.264)
    Thread Starter
       #5

    Thanks again.
      My Computer


  6. Posts : 9
    windows 10 64 Beet
       #6

    gfd said:
    Greetings,

    I am new to this forum. My question is in regards to shared folders. I run a desktop and laptop connected by ethernet, through a router. Both machines run Windows 10 Pro. Both machines have static IP addresses setup in the router. I do not use a software firewall and both computers are allowed onto the network.

    I share folders on both machines in order to run client software on the laptop which connects to the flight simulator on the desktop. All of the shared folders have full control setup for everyone in both security settings and the shared folders tab.

    There are HomeGroups set up on both machines with the correct information.

    The problem (finally you say) :) is that occasionally, one computer cannot open the shared folders on the other over the network. This doesn't happen all the time, nor is the solution consistent. Ssometimes closing and reopening the netwok folder fixes it. Sometimes just waiting does it. Other times, I have to reboot the computer(s). This creates issues with my client software tryong to connect to the desktop. The error is: 0x80070035 Windows cannot find.....(to paraphrase).

    I should point out that the other machine shows up in the network folder. I just can't access it when this happens.

    This happens mainly on the laptop attempting to connect to the desktop, although once in awhile the desktop cannot find the laptop.

    I have checked and rechecked settings, deleted and rebult the HomeGroup, ensured password protected sharing is off, network discovery is on; amongst other things.

    I read about changing the shared computer name to its IP address. I also read somewhere about changing a number of registry entries that would force a change in Windows network behaviour. Now I'm fishing :)

    If anyone who has experienced this could give me some trouble shooting steps and/or solution, I would be most grateful.

    Many thanks,
    Graham
    on the network device, right click then select properties, then Power management, un-check everything there...
    *probable cause is that the network device is put to sleep mode when idle for some time...
      My Computer


  7. gfd
    Posts : 74
    Windows 10 Pro 2004 (19041.264)
    Thread Starter
       #7

    Thanks gl3. I'll check that out as well.
      My Computer


  8. Posts : 2,292
    Windows 10 Pro (64 bit)
       #8

    I think as one of the replies said networking is 'munted'. I don't have the problem with viewing/accessing other machines (one windows 10, two windows 7) but I see similar behaviour with accessing NAS drives (which I also have mapped as drive letters). Most of the time they are viewable and connect but every I cannot access them from my Win 10 machine. Mainly see this if I reboot the Windows 10 machine or turn it on within a short time of last being turned off. Usually it's only a short delay after switch on and suddenly they become accessible again but it's not instantaneous. It's pretty sporadic though and never happens on the Win 7 laptops. Kind of similar to your issue.
      My Computer


  9. gfd
    Posts : 74
    Windows 10 Pro 2004 (19041.264)
    Thread Starter
       #9

    Good to know it's not just me. I wonder why it's intermittant. One would think that it either works or doesn't. Of course, my statement is out of ignorance.
      My Computer


  10. Posts : 408
    Windows 10 Pro
       #10

    gfd said:
    Good to know it's not just me. I wonder why it's intermittant. One would think that it either works or doesn't. Of course, my statement is out of ignorance.
    Everybody has this issue, regardless of whether they use HomeGroups or not. At this time there's no solution.

    The issue appears intermittent for several reasons.

    Firstly, after you receive the 0x80070035 error, if you wait for about 30 seconds, the network begins to work normally (YMMV, wireless connections seem to take longer). It continues to work fine as long as you keep accessing the shares. But once you stop accessing shares the network kinda "falls asleep" again and generates 0x80070035 error on the next access. It will "wake up" after ~30 seconds again... And so on and so forth...

    Secondly, this issue seems to be somehow tied to network name resolution. Most of the time, when access to '\\SERVER\Share' fails, access to, say,
    '\\192.168.1.5\Share' works perfectly fine (where '192.168.1.5' is the IP address of 'SERVER'). This means that in regular "workgroup" type of Windows network the behavior might depend on what computer implements/dominates name resolution duties, which in turn depends on the order in which computers joined the network. Because of this one day everything might works fine, and other day fail with 0x80070035.

    Basically, the only workarounds we have at this time is: 1) use explicit IP addresses to access network shares (not foolproof, but works better), 2) take advantage of the aforementioned "wake up" behavior: try to access the remote share, get
    0x80070035, wait a bit and try again - you should succeed eventually.
      My Computer


 

  Related Discussions
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 00:54.
Find Us




Windows 10 Forums