• 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 Nero C
      Windows Terminal to gain Settings UI in the next version
      by Nero Cui

      Microsoft released Windows Terminal in 2019 replacing the default Windows Console that PowerShell and CMD use by default. The new terminal program contains many features that command-line users have been asking for years like tabs, profiles, and modern text rendering. Although the JSON based settings allow users to customize the app, many users have asked for a GUI page (Graphic User Interface) for the settings menu because editing JSON, while flexible, is very hard.

      Today, a program manager (Kayla Cinnamon) from Microsoft teased on Twitter that Settings GUI is coming in the next preview version of Windows Terminal. From the GIF, we can see that the Settings page opens in one of the tabs just like how a new terminal tab would. The design seems to be following the Windows 10 Settings app, featuring a sidebar on the left and a detailed page on the right.



      Users who wish to manually edit the Settings JSON file still have the option to do so according to the GIF, but GUI is a nice feature for most users who just want to quickly launch and change some settings. The sidebar suggests that users will be able to customize areas of the app and each of the profiles.

      This new feature will soon come to a Windows Terminal Preview release. More information is available through Windows Terminal's GitHub page.

      Source: Kayla Cinnamon (Twitter)

    • By Nero C
      Microsoft doubles down on Win32
      by Nero Cui

      Microsoft has been trying to modernize Windows and its development platform for a decade now. With Windows 8's Metro UI, Windows RT, Windows 10's UWP, Project Reunion and Windows 10X, Microsoft are trying their best to convince users and developers to move to a modern platform, but it apparently doesn't mean the end of Win32 as the company had just released a major capability to make it easier to consume Win32 APIs in programming languages other than C or C++.



      According to the blog post, Win32 APIs used to be only available to C and C++ developers, and programs developed in other languages needed to go through an error-prone wrapping or binding process. This process used to be done by the developers and it would only benefit the single language that the developers target. Moreover, the huge number of Win32 APIs available also doesn't make this process easier.

      To make consuming Win32 APIs easier in languages other than C or C++, Microsoft released new tooling called win32metadata. As stated by Microsoft:

      According to Microsoft, developers can use win32metadata to generate wrappers to Win32 APIs making the process much easier and less error-prone than manually writing every single one of them. Following this effort, the C# wrapper library C#/Win32 by Andrew Arnott and Rust wrapper library windows-rs by Microsoft are utilizing win32metadata to make Win32 APIs available in these two languages.

      Microsoft is hoping, with this tool, more languages will be able to make use of Win32 APIs. More information can be found on the project's GitHub page.

      Source: Windows Blog

    • By Abhay V
      A near-final build of Windows 10X has leaked to the web
      by Abhay Venkatesh



      A near-final build of Windows 10X has leaked on to the web, giving those interested in going through the tricky process of installing it a glimpse at Microsoft’s latest OS – a competitor to Google’s lightweight Chrome OS. The initial release is expected to be aimed only at single screened PCs and is reportedly set to launch this spring.

      Windows 10X was first showed off back in October 2019 and was aimed at dual-screened devices like the Surface Neo. However, with the Neo delayed indefinitely, the Redmond giant repurposed the OS for single-screened devices. Additionally, while the OS was expected to debut with support for Win32 apps through a virtualization technology called VAIL, those plans reportedly changed, making Windows 10X an offering slated to debut on low-end devices due to its lightweight nature.

      Microsoft is supposedly planning to add Win32 app support in the future and the OS is not expected to arrive on new form factors – such as dual-screened devices – till at least 2022. A report from The Verge suggests that the leaked build contains support for Win32 apps in a developer-only mode which cannot be accessed by general users. For now, the offering runs UWP apps from the Microsoft Store and Progressive Web Apps through the Chromium-based Edge browser.

      With the development of the company’s lightweight OS now nearing completion, it will be interesting to see when the firm plans to unveil the offering officially. Rumors are making the rounds that the launch will be one without much fanfare. OEM partners are also expected to unveil low-power PCs running Windows 10X aimed at the education market and the like in the coming months.

      Considering the risks and complexities associated with installing leaked builds, we will not be posting links to any resources for the build. Additionally, we always urge users to exercise caution and not install these builds on their main machines.

    • By Abhay V
      New report details the possible changes coming with Windows 10's Sun Valley update
      by Abhay Venkatesh



      Microsoft is said to be working on a major overhaul for Windows 10 due for release in the second half of this year. A recent job listing was also spotted that hinted at a “sweeping visual rejuvenation of Windows”, providing credence to reports about the revamp. While glimpses of what the upcoming designs might look like were provided by the updated Alarms & Clock app and the latest News and interests section in the Insider builds, that’s all there is to work with, currently.

      Now, a new report from Windows Central’s Zac Bowden sheds light on the possible changes coming to Windows 10. The information comes from sources close to the Redmond firm’s plans, based on which the publication has also created a few mockups. Changes and refreshes are expected to be made to the Start Menu, taskbar, Action Center, in-box apps, and more, along with new OS features.

      Windows 10X Action Center mockup | Image credit: Windows Central As reported earlier, the focus is expected to bring about a consistent user interface for the various parts of the OS, including consistent design elements such as rounded corners – something that some apps like Calculator have already begun receiving. The firm is also reportedly aiming to simplify the taskbar design by moving icons into a redesigned Action Center – a component that might be shared with Windows 10X. The Action Center is said to sport individual sections for media, notifications, and quick settings.

      Windows 10 Sun Valley Start Menu mockup | Image credit: Windows Central Unsurprisingly, the Start Menu too will feature rounded corners and an updated design. Bowden speculates that the firm might offer users the option to switch between live tiles and a simplistic menu – like the one expected to debut with Windows 10X. The Start Menu, Action Center, and context menus on the taskbar – such as the Jump Lists might hover over the taskbar and could be “visually separated”. The OS is also said to bring some new animations for a more fluid experience.

      As for OS features, the company is reportedly planning to bring improvements to Settings in the way of a new battery usage chart – akin to what is present in mobile OSes – that provides granular power consumption information. Multitasking abilities are also said to be getting a few new features, with Snap Assist gaining the ability to let users snap two Edge tabs side-by-side and improvements to scaling when moving across different displays. There also could be a new “dashboard” feature in the Task View area that displays users’ account summary and calendar information.

      Windows 10 Sun Valley Snap Assist mockup | Image credit: Windows Central Other enhancements reportedly in the works include improvements to voice and pen input capabilities, a new “gesture layer” aimed at making touch-based navigation easier by introducing trackpad-like gestures to navigate through the OS, and the ability to allow users to uninstall many in-box apps – a feature aimed at “power users”.

      Microsoft is expected to start testing Sun Valley bits with Windows Insiders in the next few weeks. The firm is reportedly planning to sign off the final build sometime in June, with a public release expected to happen in October. It will be interesting to see how this update shapes up. As with all rumors and internal reports, plans could change at any time and the company could decide to delay any of the reported features if they are not ready in time.

      Source: Windows Central

    • By Abhay V
      Microsoft releases Edge Dev 89.0.760.0 with Password Monitor for Mac users
      by Abhay Venkatesh



      Microsoft has released the second Edge Dev build for this year, bringing version 89.0.760.0 to users in the Dev channel. Today’s build adds a few new features, chief of which is the Password Monitor feature for macOS users. While the feature has been available to Insiders on Windows for a while now, it is being enabled for Mac users with this build. As a reminder, the firm added support for Apple Silicon Macs with last week’s build.

      In addition to the password monitor, there are a few other minor additions relating to management and update policies. Here is the complete list of features added with today’s release:

      As usual, the update also brings with it a bunch of reliability improvements. Here is the complete list of fixes:

      And here are all the fixes for changed behavior:

      Lastly, there are a bunch of known issues with the update, some of which are being tracked for a past few releases. Here are all the known issues:

      The browser should automatically be updated in the background for Dev users. However, you can also force-check for an update via Settings > About Microsoft Edge and pull the update manually.