• 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

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
+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
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 anmol112
      Windows 11 may get support for third-party widgets after all
      by Anmol Mehrotra



      Earlier this week, a Windows 11 build leaked online giving us the first look at the upcoming OS update. While, the new update comes with a visual overhaul, it also brings back a long lost feature. Tucked between the File Explorer and Task View sits the widgets option. If you have used Windows 7 in the past then you must be familiar with the widgets option. Unfortunately, the widgets option in the leaked Windows 11 build is just News and Interests which was launched for Windows 10 earlier this year.

      However, reliable Microsoft insider, Walking Cat claims that Microsoft is planning to add support for third-party widgets that will allow users to customize the widgets menu as per their liking. However, initially, Windows 11 will support only first-party widgets, with third-party support rolling out later.

      This is further confirmed by Rafael Rivera who did not find APIs related to third-party widgets in the leaked build indicating that the initial Windows 11 update will not ship with support for the third-party widgets.

      Microsoft is expected to announce Windows 11 at an event next week. However, thanks to the recent leak, we were able to take a look at Windows 11 this week. You can check out our first impressions as well as hands-on articles for more information on Windows 11. In essence, the new update merges Windows 10 and Windows 10x while also bringing performance improvements as well as features such as the new window snapping assist.

    • By Abhay V
      Microsoft's second event for June 24 is aimed at Windows developers
      by Abhay Venkatesh



      Microsoft is slated to hold a “What’s next for Windows” event at 11 AM ET on June 24 to unveil Windows 11, a name that has recently been confirmed thanks to the leaked build that made it to the web. However, it turns out that the Windows 11 event might not be the only one to be taking place next Thursday, as the Redmond firm is holding an event for 3 PM ET, which it announced via Twitter today.

      As is the case with these event invites, not much in the way of information is being provided. However, the company is rumored to be working on a brand new Microsoft Store with new policies that expand the types of apps that can be distributed through the store. It is possible that that announcement, along with more information on the specifics for developers, will be provided during the event.

      During the firm’s Build conference last month, CEO Satya Nadella said that the company will “create more opportunities for every Windows developer” and that it will “welcome every creator who is looking for the most innovative, new, open platform to build[,] distribute[,] and monetize applications”. It is possible that the developer-focused event dives into new app development and monetization capabilities brought by the revamped Microsoft Store policies. It is anybody’s guess if there are any surprise announcements.

      The developer event is scheduled for 3 PM ET on June 24, four hours after the live stream for the Windows 11 event begins. The firm will stream the developer event on YouTube here.

    • By Copernic
      Groupy 1.49.1
      by Razvan Serea



      Groupy is a powerful organizational tool for Windows that will keep information tabbed and organized. You can drag and drop multiple applications and documents together to group them into a tabbed interface for easy access and reference.

      Key Features:

      Drag and drop applications together to group them under a common tabbed interface Organize multiple applications and documents together for convenient access Group related tabs together for optimal workflow Save groups of applications together for future usage Manage tabs in quick and natural ways with the browser-like interface Add new tabs to existing groups quickly and easily Mouseover tabs to preview the window contents Copy files between Explorer tabs. Drag files to the target tab, pause to switch, and then into the target window. Automatically group instances of the same application together Groupy 1.49.1 changelog:

      Fixed a Groupy titlebar grab \ drag \ lag issue introduced in 1.49 Fixes an issue with auto-grouping ignoring the locked status Fixes bars showing on other virtual desktops when you switch to them briefly Potentially resolves an issue with auto grouping and virtual desktops grouping multiple windows from different groups Groupy is only $4.99. For more information about Groupy, please visit https://www.stardock.com.

      Disclaimer: Neowin's relationship to Stardock.

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Usama Jawad96
      How to install new fonts in Windows 10 for apps like Office
      by Usama Jawad

      Fancy! While Microsoft already ships a decent set of fonts with Windows 10 which Office apps also utilize, there may come a time in your life when they may not be enough and you may feel the need to install a custom font downloaded from the internet. Such a moment came recently in my professional life when a client wanted my team to develop a dashboard in Microsoft Power BI using a custom font. Although we thought there would be a straightforward solution for this requirement, we learned that we would need to specify the font in a JSON theme file, but it would only work if said font is installed on your Windows machine.

      Much to our disappointment, we learned that the font the customer wants us to utilize is not available in Windows 10, which means that we have to install it first. Thankfully, the process to install new fonts on Windows 10 is easier than I anticipated, and today, I will walk you through what you need to do in order to enable the same, should you ever be faced by a similar requirement - or if you just want to try new fonts. This approach will also work for apps installed on Windows 10, like Microsoft Office.

      Step 1: Download a custom font
      First up, you obviously need to have the custom font downloaded on your machine. There are multiple ways to do this. Starting with the built-in options on Windows 10, you need to head over to Settings > Personalization > Fonts and click on "Get more fonts in Microsoft Store", as can be seen in the screenshot above.

      This will open a dedicated section in the Microsoft Store listing some custom fonts. Choose any font that tickles your fancy, and click on the "Get" button from the store listing. For the sake of this guide, I clicked on the "Ink Journal" font, as can be seen above.

      Once the font is installed, it will be visible to you in Office apps from the fonts drop down. As you can see in the screenshot above, I selected the "Ink Journal" font which I just installed, and I can use it without any issue.

      But wait, what if a font you want is not available in the Microsoft Store? That is a completely valid scenario considering the Microsoft Store just contains a couple dozen custom fonts, and it's very likely that if you're looking for a specific obscure font, it won't be there. Or maybe you just like the fonts available there.

      In this case, we would want to download something from the web. Good news is that this is fairly simple too. Supported font file format types in Windows 10 are .ttf and .otf, which stand for TrueType and OpenType respectively. If you're interested in knowing the difference between them, there are multiple guides available on the web which tell you exactly that, however, this is out of the scope of this article.

      In our case, we are only interested in downloading .ttf or .otf font files and install them on Windows 10. Luckily, there are lots of dedicated websites which offer exactly that, such as Font Squirrel and DaFont, among others. Most downloads will contain a .zip file which you would need to extract using WinRar, 7Zip, or some other compression tool. In our case, I downloaded "Cassandra", just because it looks fancy, sue me. As you can see in the screenshot above, there is font file named "CassandraPersonalUseRegular-3BjG.ttf", which is what I'll be installing in the next step. This concludes our first step in terms of your options for downloading fonts not available on the Microsoft Store. For the sake of simplicity and brevity, I'll refer to whatever font you downloaded as the ".ttf file" in the next parts of this guide.

      Step 2: Install a custom font
      Now that you have downloaded a .ttf file from the web, your next step would be to install it on your machine. There are multiple ways to do this but you may require administrative privileges on your operating system because fonts on Windows 10 are installed in the C:\Windows\Fonts directory by default.

      One way to install the custom font would be to once again open the Settings > Personalization > Fonts configuration in Windows 10, and at the top, you'll notice an option called "Drag and drop to install". Do exactly that with the .ttf file you downloaded, and that's it. After you do this, it will also be visible in the fonts list on the same page. A screenshot of this option is attached above.

      Another way to install a font is via the context menu. Simply right click on your .ttf file which will open the context menu containing two options called "Install" and "Install for all users". The first will install it just for the current user, the second will install it for all users and is something to consider if you are using a shared machine. Click on either of these options depending on your preference as shown in the screenshot shown above, and you're done.

      Yet another option to accomplish the same as the two alternatives described above in this step is to simply double-click on the .ttf file which will automatically open it in a dedicated editor. Click on the "Install" option at the top, and that's pretty much it.

      Once you're done with either of the options explained in the step above, the font will be visible in the list on the Settings > Personalization > Fonts page as well as the C:\Windows\Fonts directory. A screenshot of the former is above. You could copy-paste the font file to the C:\Windows\Fonts directory directly and while that may be the fastest option, it's not the most user-friendly if you're not familiar with the Windows directory structure.

      Step 3 (optional): Uninstall a custom font
      If you viewed this article just to find out how to install a custom font, you don't need to read further. That said, there may come a day where you would like to uninstall a custom font just to clear the bloat on your machine as well as the options available to you in Office apps on Windows 10.

      In this case, simply head over to the same Settings > Personalization > Fonts page, locate the font you want to uninstall and click on it. This will open a dedicated page for the font, where you'll see a button called "Uninstall" as shown in the screenshot above. Click on it, and the font will be uninstalled. This concludes our guide as well!

      Did you find this guide useful? Have you ever come across this use-case before? What other tutorials would you like to see on Neowin next? Sound off in the comments section below!

    • By Abhay V
      Nvidia to drop Game Ready Driver updates for Windows 7, 8, and 8.1 starting this October
      by Abhay Venkatesh



      Nvidia today detailed its plans for Game Ready Drivers upgrade support for Windows 7, Windows 8, and Windows 8.1. The company posted a support article that states that it will cease to provide Game Ready Driver updates for its graphic cards for the mentioned versions starting October 2021. However, it does note that it will continue to serve “critical security updates” for systems running those operating systems until September 2024.

      Microsoft ended support for Windows 7 in January 2020, while Windows 8 lost its support in January 2016 – a short life span for the OS thanks to Windows 8.1 and the debacle that Windows 8 was. However, while Windows 8.1 reached the end of mainstream support back in 2018, the OS is still being serviced with security updates and will be till January 2023.

      Nvidia, says that a “vast majority” of its GeForce customers have migrated to Windows 10 and that it aims to provide the “best possible security, support, and functionality” for those users, which is why it is focusing on Windows 10 alone. In the FAQ section, it adds that it will ship the last Game Ready Driver that supports the three operating system on August 31, with the first drivers to drop support for the versions completely expected to ship in October.

      The change might not be a major one considering that most users are running the latest offering from the Redmond giant. However, for those that are still on older versions, they can rest assured that their GPUs will be served with updates to address any critical vulnerabilities. However, they will lose out on upgrades with performance enhancements, new features, and bug fixes, Nvidia says.