• 0

Cannot access SMB network shares on Windows 8.1


Go to solution Solved by BudMan,

Question

gregor

Hi,

 

recently, I've found out, I "lost access" to my NAS SMB configured device from Windows 8.1. When trying to access it from Windows Explorer, I get "Windows cannot access \\XXX.XXX.XXX.XXX" (where x's is real network ip). The thing is, I CAN access those shares from:

- other linux computer,

- windows 7 pro

- android phone using ES File Explorer. 

 

Error that shows is "0x80004005" and I even attached epl file if you can scan through it. 

 

I've googled a bit and found several ideas to try:

 

- changing policies in Local Computer Policy

- disabling Antivirus & firewall

- adding registry key IRPStackSize to value 14, 20 etc

- running powershell command as admin:IRPStackSize

 

Set-SmbServerConfiguration -EncryptData $true
Set-SmbServerConfiguration -EncryptData -RejectUnencryptedAccess $false

 

I have no idea what to do.

 

Ping works, transmission can be accessed and ftp too. There's only this win 8.1 computer that doesn't want to communicate.

 

Can someone please tell me what else I can try?

 

 

Thank you and best regards

 

Gregor  :angry:

2A38EBA3-3DAD-420D-8E51-EA5E82A7A431.Diagnose.0.etl.zip

Link to post
Share on other sites

20 answers to this question

Recommended Posts

  • 0
+BudMan

All fixed! ;) Port issue.. smb.conf was listening on 443 not 445.. He has some weird issue with his nic that needs to be worked out. But he can access his shares now. TV made it so much easier to see what was going on.

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

Do you have file and print sharing enabled on the win 8.1 box? Check properties box of your network interface.

Can you access other shares from this 8.1 box? Are you wired or wireless? Is the nas wired or wireless?

These are normally easier to troubleshoot/fix if just do a Team Viewer session.

Link to post
Share on other sites
  • 0
jamieakers

0x80004005 indicates a generic "Access Denied".  Are you logging into the Windows 8 box with a blank password?

Link to post
Share on other sites
  • 0
T4G3RXIII

Maybe your NAS doesn't support using a Microsoft account to authenticate - using name@outlook.com to log into 8.1 vs using a local account.  I had this problem with my old QNAP NAS.  Try creating a local account on your PC and use the same credentials on the NAS.

Link to post
Share on other sites
  • 0
+Ryster

I had this same problem with some our SAN volumes at my work. But only some of them, others are fine. It depends if the SAN (or NAS in your case) supports the new secure SMB mechanism that the new OS' use.

 

I now have a .reg file that I import on Windows 8 machines that fixes it straight away. If I remember rightly, this disables secure SMB or SMB2 or something like that.

 

I'm at home now so don't have access to it, but I'll grab it for you tomorrow. Assuming nobody else beats me to it before then.


Update, this might be it as it sounds familiar:

 

http://www.adamfowlerit.com/2013/05/26/unable-to-map-drives-from-windows-8/

Link to post
Share on other sites
  • 0
gregor

0x80004005 indicates a generic "Access Denied".  Are you logging into the Windows 8 box with a blank password?

Hi. Windows 8.1 has only 1 LOCAL account, no password.

 

Do you have file and print sharing enabled on the win 8.1 box? Check properties box of your network interface.

Can you access other shares from this 8.1 box? Are you wired or wireless? Is the nas wired or wireless?

These are normally easier to troubleshoot/fix if just do a Team Viewer session.

File and print sharing is enabled on network interface.

 

My pc is on network over cable, same goes for NAS device. I agree about TV.

 

 

Maybe your NAS doesn't support using a Microsoft account to authenticate - using name@outlook.com to log into 8.1 vs using a local account.  I had this problem with my old QNAP NAS.  Try creating a local account on your PC and use the same credentials on the NAS.

Of course it doesn't. Its set up as everyone on network can access PUBLIC directory with anonymous access. :) I will make another local account and try to access again.

 

 

I had this same problem with some our SAN volumes at my work. But only some of them, others are fine. It depends if the SAN (or NAS in your case) supports the new secure SMB mechanism that the new OS' use.

 

I now have a .reg file that I import on Windows 8 machines that fixes it straight away. If I remember rightly, this disables secure SMB or SMB2 or something like that.

 

I'm at home now so don't have access to it, but I'll grab it for you tomorrow. Assuming nobody else beats me to it before then.

Update, this might be it as it sounds familiar:

 

http://www.adamfowlerit.com/2013/05/26/unable-to-map-drives-from-windows-8/

Did most of what your url states except those registry inputs. Going to try those too.

 

Also called on Microsoft support and, yep.. here's the answer they gave "we don't support 3rd party apps but you can call UK support if they can help you out with that" o_O

Link to post
Share on other sites
  • 0
daorbed9

Go in credential manager, remove any credentials for the network share and reboot.  Then try to connect again.

Link to post
Share on other sites
  • 0
gregor

Go in credential manager, remove any credentials for the network share and reboot.  Then try to connect again.

 

No credentials there at all.

 

Also, tried to create another LOCAL account with password. Same results.

post-292-0-39149300-1413480603.png

Link to post
Share on other sites
  • 0
gregor

Do you have file and print sharing enabled on the win 8.1 box? Check properties box of your network interface.

Can you access other shares from this 8.1 box? Are you wired or wireless? Is the nas wired or wireless?

These are normally easier to troubleshoot/fix if just do a Team Viewer session.

 

Adding: Yes.. i can access raspberry pi SMB without a problem.

Link to post
Share on other sites
  • 0
+BudMan

If you want to do a TV session more than happy to take a look see. Just PM your info and we can take a quick look see, I would install wireshark before hand so we can do a sniff and see what the NAS is sending back exactly..

Wireshark is free - you can grab it here.. https://www.wireshark.org/download.html

or we can install when I TV in.

  • Like 1
Link to post
Share on other sites
  • 0
Draconian Guppy

All fixed! ;) Port issue.. smb.conf was listening on 443 not 445.. He has some weird issue with his nic that needs to be worked out. But he can access his shares now. TV made it so much easier to see what was going on.

Show off!

 

You didn't help me when I was all alone here, you're not the hero I thought  you were :(

 

http://www.neowin.net/forum/topic/1225735-mapping-linux-drive-to-windows-81-pc/

 

 

 

I kid I kid :P

Link to post
Share on other sites
  • 0
+BudMan

I would of been more than happy to help in that thread ;) Just didn't see it.. While I do visit that section now and then, its more when nothing else is going on in the other section ;)

If you want me to look into a thread, PM me next time ;)

  • Like 1
Link to post
Share on other sites
  • 0
Draconian Guppy

I would of been more than happy to help in that thread ;) Just didn't see it.. While I do visit that section now and then, its more when nothing else is going on in the other section ;)

If you want me to look into a thread, PM me next time ;)

The funny thing I was going to PM you, but I managed :P  Just starting some friendly conversation. Now.. quit the thread hacking.

Link to post
Share on other sites
  • 0
gregor

Good morning. I'm stil shocked and amazed to see the issue is finally gone, thanks to @BudMan. 

 

- Wireshark, for start, did show that my NAS is rejecting my Win8.1 machine. 

- Checking Network adapter settings, we've found out, we cannot access ipv4 properties to check IP settings. It said there's no adapter installed/enabled.  :|

- Checking NAS device, there was samba service running, but checking listening ports, 445 wasn't among them.

- Checking smb.conf, listening ports for samba were stated as 443 139. Yes, 443 instead of 445. After switching this to 445 and restarting service, I could access shares from my win8.1.

- I still have to fix no adapter found (google search resulted in removing network adapter from device manager and reinstalling it).

 

But, I'd like to thank BudMan again for his help. Finally, I've found a sysadmin somewhere just waiting for my problem to pop-up on a forum :) Thank you!

 

 

Regards all!  :woot:

Link to post
Share on other sites
  • 0
+BudMan

I think you have some clean up to do in that network, lots of protocols enabled that prob of no use LLMNR, LLTD.  While these protocols can be of use - security 101 says if not actually using them -- turn them off.  You would of thunk MS would of learned this lesson years ago with IIS, and messenger being on out of the box and all the trouble that caused. 

 

Sorry but you don't need 3 different transition methods to get to ipv6 from ipv4 on out of the box!!  isatap, teredo and 6to4 -- let the user turn on the one they need if any.

 

Here to help if you have any questions..  Your systems did seem to be very responsive - got some decent hardware I do believe, and internet connection was solid.  Let us know how that nic error turns out, did you uninstall it and reinstall yet?

Link to post
Share on other sites
  • 0
GaryO

I am having a similar issue.  I have 3 different NAS.  Buffalo, Drobo & Iomega.  They all appeared under network, the Drobo and Buffalo are still mapped.  I cannot reach the IOmega,  I can ping to it.  I can not resolve to it.  I see it frin frm Windows 7. It worked until this week.

Link to post
Share on other sites
  • 0
BILLASH

hello BUDMAN

 

Please could you help me ?

 

I have a oppo multimedia and music / video nice system client which can connect to my shares and usb drives to my windows seven computer, my iomega nas, mysmart  tv, my printer, but bad really bad thing it can't connect to the dual core recent acer computer connected by ethernet with SMB protocols actived 1.0 if i remember

 

but i have to give you an information the oppo  can connect to the C:  internal drive only of the computer WIN 8.1. I hope you may have an idea of this bad situation because i bought this computer ((8.1) for purposal susic and video shares with my oppo client system which answers by error name/pass altough i tried all credentials possible.

 

note: ALL other system may acceed to the 8.1 only oppo is a problem but as i said the oppo is aceeding in all other usd drives sharing or nas

So the oppo is not a problem

 

Thanks ver y much for your help i must conncet to thhis 8.2 PC with pnp servers which does not fits me totally far from this

 

Best regards

 

Thanks !

 

 

Bill

Link to post
Share on other sites
  • 0
Mindovermaster
2 hours ago, BILLASH said:

hello BUDMAN

 

Please could you help me ?

 

I have a oppo multimedia and music / video nice system client which can connect to my shares and usb drives to my windows seven computer, my iomega nas, mysmart  tv, my printer, but bad really bad thing it can't connect to the dual core recent acer computer connected by ethernet with SMB protocols actived 1.0 if i remember

 

but i have to give you an information the oppo  can connect to the C:  internal drive only of the computer WIN 8.1. I hope you may have an idea of this bad situation because i bought this computer ((8.1) for purposal susic and video shares with my oppo client system which answers by error name/pass altough i tried all credentials possible.

 

note: ALL other system may acceed to the 8.1 only oppo is a problem but as i said the oppo is aceeding in all other usd drives sharing or nas

So the oppo is not a problem

 

Thanks ver y much for your help i must conncet to thhis 8.2 PC with pnp servers which does not fits me totally far from this

 

Best regards

 

Thanks !

 

 

Bill

Make your own thread. Please do not necro this old thread....

Link to post
Share on other sites
  • 0
Jason S.

Please start a new thread. This one is from 2015. Thank you.

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 Abhay V
      Windows Holographic version 21H1 rolls out with a bunch of new features
      by Abhay Venkatesh

      Microsoft today announced the availability of the next major version of Windows Holographic for HoloLens 2 devices. Version 21H1 is beginning to roll out with a bunch of new features. Interestingly, while 21H1 for desktop is going to be just an enablement package that will light up minor new features for the OS, the version seems to be a major one, bringing features such as the new Chromium-based Microsoft Edge, Settings app improvements, a revamped Power menu, and much more.

      First up is the addition of the new Microsoft Edge browser based on Chromium, which will be the default offering for HoloLens users. However, the company says that Legacy Edge will continue to exist in the OS. Users will also be able to sync history and favorites as it is based on a shared codebase. It also supports WebXR and the 360 Viewer extension for immersive web experiences, the firm says.



      Next up is the new Settings app that contains granular controls and is tailored for the HoloLens 2. It includes updated settings for Sound, Power & sleep, Network & Internet, Apps, Accounts, Ease of Access, and more. The firm adds that since the new Settings app is “distinct from the legacy Settings app”, it will remove any previously placed windows in the environment. A few examples of the improved settings experience include the ability to set or reset default apps, adjusting independent app volumes, account management, and various improvements to audio preferences.

      There is also a new Display color calibration tool in Settings to let users choose alternate color profiles to adapt to various display brightness and ambient light settings. There are six pre-set color profiles to choose from.

      Another nifty feature is a new Swipe to type feature that mimics the experience found on mobile devices. Users can pass the tip of their fingers through the letters and can continue typing just like on mobile and the system automatically inserts spaces after each word. However, the company calls the feature “tricky” as the holographic keyboard does not offer any haptic feedback or resistance to users’ fingers, unlike on mobile devices.

      Rounding off the major changes is a new Power menu that can be accessed from the ellipsis icon next to the users’ profile picture. It offers users options for signing out, shutting down, or restarting the device, and displays a yellow indication icon when updates are available, similar to the Windows 10 power menu. The sign-in screen is also adding support for displaying multiple user accounts, making it easy to switch between accounts.

      There also are updates aimed at IT admins such as the auto-enabled Visitor Auto-logon for Kiosk mode feature, improved error handling, and more. You can head to the release notes page here for complete documentation on everything that is new, along with useful links. The Redmond firm also notes that it will no longer serve updates for version 1903, with the only supported version now being 2004, 20H2, and 21H1.

      Windows Holographic version 21H1 is heading out to HoloLens 2 users starting today bringing build 20346.1002. Users can head to the Settings app and check for updates from the Windows Udpate section under Update & Security. The company has also made available manual update packages for IT admins.

    • By Abhay V
      Windows 7 and 8.1 Patch Tuesday updates are out, here's what's new
      by Abhay Venkatesh



      As is the case every second Tuesday of the month, Microsoft is releasing cumulative updates for all supported Windows versions. That includes all supported Windows 10 versions, along with Windows 8.1, and Windows 7 customers that have opted to receive extended security updates. As for Windows 10 users, it must be noted that versions 1909, 1809, and 1803 will be reaching the end of support, with 1803 being completely unsupported – including for enterprises – starting today.

      As for Windows 7 and Windows 8.1 (and the corresponding Windows Server versions), there are two kinds of updates. The monthly rollup packages are downloaded automatically from the Windows Update, while security-only packages are made available for manual download.

      Starting with Windows 8.1, the monthly rollup for this month is KB5003209 and can be manually downloaded from the Update Catalog here. The changelog for the patch is as follows:

      As for known issues, there is just one known issue that is being tracked for a while, and it still seems to not have been addressed:

      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.

      Heading to the security-only update, it is listed in the knowledge base article KB5003220 and is available for manual download from here. It includes the following fixes and comes with the same known issue as that of the monthly rollup:

      Moving on to Windows 7, the monthly rollup is KB5003233 and can be downloaded from the link here. The list of fixes being made to users of the OS with this month’s update includes the following:

      And here are the known issues that users should be aware of:

      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.

      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.

      For those looking for the security-only update, it is KB5003228 for this month and can be manually pulled from the Update Catalog here. The list of changes and fixes are as follows:

      The known issues for this update are shared with the monthly rollup, which means that the rename operation problem – which has been around for a while now, is still not fixed.

      As usual, you can head to Windows Update and check for updates to pull the monthly rollup patches. You can also head to the individual download links for the security-only updates which can only be manually installed.

    • By Abhay V
      Windows 10X reportedly delayed indefinitely, focus to shift to Windows 10
      by Abhay Venkatesh



      In what may be disappointing news for Windows fans, Microsoft is reportedly delaying the release of Windows 10X – its next-generation operating system – indefinitely. The report comes from Petri, citing information from those in the know of the matter.

      Microsoft originally showed off Windows 10X in 2019 alongside the Surface Neo and Surface Duo. While the Surface Duo that was powered by Android made it to the market, the Neo was delayed and Windows 10X was repurposed for single-screened devices. A supposed near-final build of the modern OS even leaked and Microsoft was said to be readying the platform for release sometime this spring. That timeline moved once again to later in the fall this year, according to reports.

      However, Petri reports that those plans have now changed, with Windows 10X now on the backburner. The company is reportedly moving resources back to Windows 10, which is expected to receive a major update codenamed Sun Valley later this year. As for 10X, there is no concrete information on if and when the OS will see the light of the day, and it is possible that the offering as we know it will never make it to users.

      A few reasons for the decision, according to insiders, include the fact that the OS just was not ready. The firm reportedly believes that the “timing and market conditions” are not right and that the feedback from users, too, has not been as positive as it may have hoped to. While enthusiasts hoped to see 10X make it to new devices, marketing a brand-new OS on new devices, especially during the times of the pandemic that has seen the adoption of traditional Windows 10 PCs increase, might have been difficult. Add to the fact that at launch, the OS was said to lack support for traditional Win32 apps, which again might have worked against the offering.

      Additionally, the report states that the company execs feel that Windows 10X doesn’t offer solutions that its customers want. Therefore, it makes sense for the Redmond giant to introduce certain features such as seamless updates and app containers to Windows 10 while working on a possible lightweight platform for release.

      As it stands now, it is safe to assume that Windows 10X as we know it is dead and so are plans to introduce a lightweight Chromebook competitor OS. It is not clear if the company will publicly announce the plans that it has for Windows 10, including the visual overhaul and new Microsoft Store policies at its Build conference later this month. The report from Petri does state that the company will make “formal announcements” about the fate of the OS, so it will be interesting to see what those are.

    • By Laurentiu A.
      Hello Neowinians.
       
      I have one question for all of you...
       
      What is this ugly, beta, squared, badly pixelated THING on my taskbar?
      It says News and interests and yes, I know its a new feature from Microsoft.
       
      But..
       
      How can a billion dollar company, with thousands of employees and rich history in software, design this?
      The sun icon looks very bad, the text that displays the weather is blurry and the app itself is sluggish. 
      How can they release something like this worldwide, without shame?
       
      I am serious...
       
       

    • By Adel Samir
      I am using Windows 8.1 Pro 64-bit (6.3, Build 9600) on laptop dell inspiron 3542 core i7 and for some reason all my removable USB flash drives are shown with generic icons whatever their manufacturer of format are:
       

       
      This doesn't affect the performance and every thing works fine.
       
      I switched to a different user on the same PC and the same operating system and the icons are shown correctly:
       

       
      Now I know it is a problem with the user but don't know how to fix it.