• 0

Suddenly can't access network share in Windows 7


Question

nvewuaji

I have a Synology NAS on my LAN. It is running fine and has been accessible to all of the other computers on the LAN for many years now. However, on one of the LAN computers I recently ran some Windows 7 update stuff (I don't remember what the updates were, it had been a while since I last updated) and now I when I try to access the Synology share from this particular computer it gives me a "network path not found" error (error code 0x80070035). I can see the share fine in the network view in explorer, and it's enumerated when I run nbtstat -c and net view. It's just when I actually try to access it (double-click on the icon share, or use the UNC or LAN IP in file explorer) that I get the error. Other Windows 7 computers on the LAN can access the NAS the same as before, so I'm quite confident that the problem lies with this particular computer rather than anything on the Synology side.

 

I've tried a lot of the common fixes like disabling Windows firewall, ensuring NetBIOS is enabled for my network adapter (it already was), removing redundant 6to4 adapters in device manager (I had none to remove), and ensuring that various network services were running (they already were). Nothing has worked. Any ideas of what else to try?

 

By the way, I know I could just reinstall Windows but doing so would be a real pain for this computer, so I'd rather not unless I absolutely have to. Also, I can access the NAS by navigating to the LAN IP in my web browser and logging in through the web interface, it's just that I can't access the share in explorer/dopus to do file operations.

Link to post
Share on other sites

17 answers to this question

Recommended Posts

  • 0
+BudMan

Why is the computer problem and not the nas?  Do you have other machines accessing these shares?

Link to post
Share on other sites
  • 0
nvewuaji

Yeah, I have a couple of iPads, another Win7 machine and a Linux machine and they can all access the NAS fine. It's just this one Win7 computer that is having the problem.

Link to post
Share on other sites
  • 0
+BudMan

What error do you get when you do net view \\computername or \\ipaddress? from cmd line?

Link to post
Share on other sites
  • 0
nvewuaji
1 hour ago, BudMan said:

What error do you get when you do net view \\computername or \\ipaddress? from cmd line?

For both I get:
 

System error 53 has occurred.

The network path was not found.

Link to post
Share on other sites
  • 0
+BudMan

If I had to GUESS... Your windows update removed smb1 - which should of been turned off years ago... And you don't have your nas set to use smb2 or 3..

 

Your other clients prob still using smbv1.. What does your nas show for your smb setting?

 

Here is off my synology

 

nassmbsettings.thumb.png.1eb4428437ee4b1fa64cf420123cea2c.png

Link to post
Share on other sites
  • 0
nvewuaji

I have an older Synology (110j) so it only has the maximum SMB protocol option; it was set to 1 so I set it to 3 but it made no difference.

 

Also, to test whether the Synology is the issue I created another share on a different Win7 computer. Unfortunately I get the same problem: I can see the share in network view but I get the "network path not found" error when I try to access it. I used to have more shares on that computer and could access them from this one without problems, so I'm pretty sure it's something to do with the Windows 7 settings on this particular computer. Anyway, thanks for your help!

Link to post
Share on other sites
  • 0
+BudMan

What version of DSM are you running?

 

A sniff of the traffic when you try and access the share should be able to point to where the problem is..  But getting error 53 when you trying access just the view via \\ipaddress "could" be version protocol problem... A sniff could for sure help figure out the root problem.

 

Grab wireshark... Run it and then try and access your shares.. Post up the sniff.

 

When doing this make sure all your other applications are turned off, etc.  Have had people post up a sniff to troubleshoot something they were streaming a movie at the same time ;)  Don't be doing anything on the machine other than trying to access your shares.  Only apps that should be running is wireshark and your file access..

 

Do you have ipv6 enabled or disabled?  If your dsm is older prob doesn't even support ipv6 anyway.  And wouldn't come into play if you doing \\IPv4address

 

You didn't disable file and print sharing all together did you?

Link to post
Share on other sites
  • 0
nvewuaji

DSM version is 5.2. IPv6 is set to Auto in DSM. File and printer sharing in Win7 is enabled.

 

Here is what happens when I click on the Synology share. 10.0.0.2 is the Win7 computer that has problems accessing shares, and 10.0.0.4 is the NAS:

 

wireshark.thumb.png.7aace55cebd93f6c3c0d62575372a4b2.png

Link to post
Share on other sites
  • 0
+BudMan

Well be much easier if could actually open that in my wireshark to read what is in the response of the smb negotiation you see the request and response.

 

the RST is being sent by the client.. Not a very friendly way to end the conversation.. Normally you do a fin, ack  But then it tries again to neg..  My guess is they can not agree on what version of smb to use.. You never even ask for shares, or any sort of auth.. Its just the protocol neg part.

 

edit:

 

Here is like a normal conversation start you see the syn and syn,ack then the neg

 

normalconversation.thumb.png.09997316466668530ae6ae291ffad538.png

 

Client is .100 and server is .9 in this conversation.

 

Client sends out what versions it can talk.. and then the server responds back with lets talk this..  So you see the 0x0311 from the client side, since this is a windows 10 client it can talk that version... But the server its talking to is running 2012r2 best could be the 302 version

 

2.0.2 Windows Vista, Server 2008

2.1.0 Windows 7, Server 2008 R2

3.0.0 Windows 8, Server 2012

3.0.2 Windows 8.1, Server 2012 R2

3.1.0 Windows 10, Server 2016

 

So what exactly did you client send and what did it get back in that neg part?  Since right after that is sends a RST... Which is saying this conversation is DONE!!!

 

Could be signing required or something.. Be helpful to actually be able to open that in my wireshark and look at the request and response, etc.

Link to post
Share on other sites
  • 0
+BudMan

Well your client is saying it can talk some really OLD ######!!!

 

clientrequest.thumb.png.bec7ef2634e4e494aeaaeda6660edb0d.png

 

Your server answers back with 0x02ff which should match, and sends back 0x0210 which you would think would match 2.??/ as well - but not sure match but then your client says F off with the RST..

 

not sure why your client is sending back RST.. Is your workstation service running?

 

 

Link to post
Share on other sites
  • 0
+BudMan

I will check with my wifes laptop when I get a chance.. Its still running windows 7..  But you shouldn't be sending all of those dialects.. lanman???   You got something major wrong with that thing... Thought one of the more recent updates was to kill off smbv1.. I don't see how your running all of those old before smbv1 dialects..   This was back in 2017 they announced that.

 

You sure and the hell should have it disabled after wannacry, etc.  So yeah something is not right with that box sending all those OLD dialects..

Link to post
Share on other sites
  • 0
nvewuaji

At this point I think I'm just going to reinstall, since the problem seems to be very obscure. I really appreciate all your help with this though, thanks again!

Link to post
Share on other sites
  • 0
Tay Ruong

This is an old post, but I see people are still having the problem and the solution is undoubtedly obscure.  Google search may still bring people to this old post.

Go to your Synology control panel and select File Services/Advanced

Then unselect "WS-Discovery", apply the change, then select "WS-Discovery" again and apply the change again.

Link to post
Share on other sites
  • 0
Mindovermaster
12 minutes ago, Tay Ruong said:

This is an old post, but I see people are still having the problem and the solution is undoubtedly obscure.  Google search may still bring people to this old post.

Go to your Synology control panel and select File Services/Advanced

Then unselect "WS-Discovery", apply the change, then select "WS-Discovery" again and apply the change again.

Won't matter after January... :rolleyes:

  • Facepalm 1
Link to post
Share on other sites
  • 0
+BudMan

MS has backed off yet again on killing off W7.. As long as you pay you can still get support ;) And the price will go up every year...

 

BTW ws-discovery has nothing to do with the dialect of smb offered or asked for.

 

Link to post
Share on other sites
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By indospot
      Patch Tuesday: Here's what's new for Windows 7 and 8.1 this month
      by João Carrasqueira



      Today is the second Tuesday of February, and that means it's also the second patch Tuesday of 2021. As tradition mandates, Microsoft is rolling out a series of cumulative and security updates for all supported versions of Windows, including many versions of Windows 10, as well as Windows 8.1 and, for ESU customers, Windows 7.

      As usual, there are two sets of updates for the operating systems, one monthly rollup and one security-only update. The former rolls out to most users automatically, and it can contain non-essential fixes and changes; while the latter has to be downloaded manually and only includes security patches.

      Or, at least, that's usually the case. This month, all the updates contian the same changes for both Windows 8.1 and Windows 7. For Windows 8.1, this month's rollup update is KB4601384 and it can be downloaded manually here. Here's what's new:

      THere's a single known issue, and it's the same one we've been seeing for months now:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      As for the security-only update, it's KB4601349, and you can download it manually here. It includes the same exact changes and known issue as the update above.

      Turning over to Windows 7, as a reminder, you'll need to be paying for extended security updates for your organization to get these updates. If you are, the monthly rollup update is KB4601347 and you can download it manually here. It includes the same changes as the updates above, as well as the same known issue.

      Finally, the security-only update for Windows 7 is KB4601363, and you can download it manually here. It includes all the same changes and has the same issue as all the other updates.

      As mentioned above, the monthly rollup updates are usually installed automatically, but you may prefer downloading and installing them manually. With the security-only updates, you have no choice but to do it manually. Since this month's updates are the same, you should be fine getting the automatic updates from Windows Update.

    • By indospot
      Here's what's new for Windows 8.1 and 7 this Patch Tuesday
      by João Carrasqueira



      We're now two weeks deep into 2021, and since it's the second Tuesday of January, that means it's also time for the first Patch Tuesday of the year. Microsoft is rolling out cumulative updates for all supported versions of Windows, and that includes Windows 8.1 and Windows 7, assuming you're paying for extended security updates for the latter.

      As usual, there are two sets of updates for the operating systems, one monthly rollup and one security-only update. The former rolls out to most users automatically, while the latter has to be downloaded manually. For Windows 8.1, this month's rollup is KB4598285 and it can be downloaded manually here. Here's what's new in this release:

      The update includes a single known issue that we're familiar with by now:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      As for the security-only update, it's KB4598275, and you can download it manually here. It only includes the following changes:

      It has the same known issue as the monthly rollup.

      Turning over to Windows 7, again, you'll need to be paying for extended security updates for your organization to get these updates. It's also possible that the cost of these updates is doubling soon, since it's been one year since support was ended for the OS. Either way, if you're paying for them, the monthly rollup update is KB4598279 and you can download it manually here. It includes the following changes:

      The only known issue is the same as for the Windows 8.1 updates above. Finally, the security-only update is KB4598289, and you can download it manually here. You'll only be getting the security updates mentioned in the last bullet point above, and the known issue is also the same as for the rest of the updates.

      As mentioned above, the monthly rollup updates are usually installed automatically, but you may prefer downloading and installing them manually. With the security-only updates, you have no choice but to do it manually.

    • By Usama Jawad96
      A canceled Windows Core OS build has reportedly leaked online
      by Usama Jawad

      Back in 2018, it was reported that Microsoft is building a new, modern version of Windows 10 for PCs, codenamed Polaris. This would be under the Windows Core OS umbrella which also included Andromeda as the operating system for foldable mobile devices. It was rumored that this flavor of the operating system will strip much of the legacy code and compatibility issues that the OS is currently encumbered with. While Microsoft canceled both Polaris and Andromeda in 2018, and tapped Windows 10X as their replacement, a build of the former has now leaked online.



      Windows Central reports that an old build of Polaris - the modular flavor for traditional PCs - has leaked online, but unfortunately, there's not much to be excited about. The leak is a very early build from 2018 and contains no shell or apps. This essentially means that it has no GUI either and is just the bare OS package.

      While there's not much that can be messed around with in the build, some interesting tidbits are that it is an RS3 RTM build and is compatible with ARM32 architecture. This means that it can be booted up on the age-old Surface RT.

      Polaris was supposed to be a modular version of Windows, offering better flexibility, power management, and performance. However, it is important to emphasize that the OS is no longer in development, and has been superseded by Windows 10X, which is slated to arrive in spring later this year. As this is a leaked build of the software and could contain undisclosed issues, we would advise against trying to tinker around with it on your primary machine.

      Source: Windows Central

    • By zikalify
      Firefox 84 launches with support for Apple Silicon CPUs
      by Paul Hill



      Mozilla has released Firefox 84 with native support for Apple Silicon CPUs. Firefox 83, by contrast, was released just after Apple’s CPU announcement and had to run using Apple’s Rosetta 2 emulation software on newer Macs.

      Aside from support for Apple Silicon CPUs, it’s worth mentioning again that Firefox 84 is set to be the last version of Firefox that will include support for Adobe Flash. The plug-in, which has largely been supplanted by HTML5 and Unity, was first released in 1996 and sometimes acted as a security weak point.

      Firefox 84 is a big update in terms of Mozilla’s rollout of WebRender, its Servo rendering architecture. The rollout has been extended to devices running macOS Big Sur, Windows devices with Intel Gen 6 GPUs, and Intel laptops running Windows 7 and 8. Linux users with the GNOME desktop with X11 will also get WebRender switched on in this update but it’s unclear when users of other desktop environments and of Wayland will get the feature switched on.

      The final point worth mentioning also pertains to Linux; Mozilla says it is now using “more modern techniques” for allocating shared memory on Linux which improves overall performance and increases compatibility with Docker.

      Head over to the Firefox website now to grab a fresh copy of the browser or wait for your existing installation to upgrade itself. You can also force the upgrade by going to the Menu button > Help > About Firefox where you should see the update download and eventually offer to restart the browser.

    • By Abhay V
      Patch Tuesday: Here's what's new for Windows 8.1 and 7
      by Abhay Venkatesh



      It is the second Tuesday of the month, which means that it is time for Patch Tuesday, the day that all supported versions of Windows receive cumulative updates, which include Windows 10 version, Windows 8.1, and Windows 7 devices enrolled for Extended Security Updates (ESUs).

      First up are the updates for Windows 8.1 and Windows Server 2012 R2. As usual, there are two sets of updates, the monthly rollup and the security-only update, with the latter only available for download manually. The monthly rollup is identified as KB4592484 and can be downloaded manually from the Update Catalog here. Here are the fixes in this update:

      And there is one known issue in the update:

      Symptom

      Workaround

      Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

      Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.


      The security-only update is KB4592495 and can be manually downloaded from here. The fixes in this update are identical to the second and third points from the monthly rollup. It also shares the single known issue with the monthly rollup.

      Next up are updates for Windows 7 SP1 and Windows Server 2008 R2 SP1. It must be noted that these updates will be served only to users that have opted to pay for extended updates. The monthly rollup is KB4592471 and can be downloaded manually from here. Here is the list of fixes made in this update, which is almost identical to the one for Windows 8.1:

      As for the known issues, the patch contains the rename operation bug for Cluster Shared Volume (CSV) files listed above, along with another issue specific to this version:

      Symptom

      Workaround

      After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History.

      This is expected in the following circumstances:

      If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article.

      The security-only update for these Windows versions is labeled KB4592503 and can be downloaded from the Update Catalog here. The list of fixes and known issues for this package is identical to that of the monthly rollup.

      A quick note for Windows 10 users this week is that this month’s updates will be the last to roll out for Windows 10 May 2019 Update (version 1903) as it is reaching its end-of-support today. Support ends for all SKUs, including for Enterprise and Education users. While the Redmond firm has already begun moving users on this version to Windows 10 version 1909, if you are still running version 1903, it’s best to check for updates and move to a newer version.