Recommended Posts

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

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.

Maybe your NAS doesn't support using a Microsoft account to authenticate - using [email protected] 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.

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/

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 [email protected] 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

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

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.

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.

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

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 :(

 

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

 

 

 

I kid I kid :P

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

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.

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:

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?

  • 2 months later...

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.

  • 2 years later...

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

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....

  • Jason S. locked this topic
This topic is now closed to further replies.
  • Posts

    • To give context to everybody, I bought about 2 sets of RAM, ddr4, 3200, 64 gb, 2 years ago. It costed me 150 usd for each set. If you buy RAM now you only incentivate companies to sell you expensive stuff, as Nvidia did.
    • KillerPDF 1.4.2 by Razvan Serea KillerPDF is a lightweight, portable PDF editor for Windows built for users who want full control without subscriptions, installers, or telemetry. It runs as a single executable, making it ideal for USB use and field work. You can view PDFs with smooth PDFium rendering, navigate quickly with thumbnails, zoom, and shortcuts, and reorganize pages using drag-and-drop. It supports merging multiple PDFs, splitting documents, and extracting selected pages. KillerPDF also allows inline text editing with font matching to preserve the original layout, plus annotations like text boxes, freehand drawing, highlights, and reusable signatures. You can search full text, copy content easily, and print documents with flattened annotations. Designed as a free and open alternative to bloated PDF tools, it works fully offline on Windows 10/11 x64. No runtimes install. Everything needed is inside the EXE (targets .NET Framework 4.8, which ships with every supported Windows release). KillerPDF key features: High-quality PDF rendering via PDFium Edit PDF text inline (double-click to modify text) Page thumbnails and fast navigation with zoom and shortcuts Merge multiple PDFs into one Split PDFs and extract selected pages Drag-and-drop page reordering Font matching to preserve original document appearance Text boxes for notes Freehand drawing tools Highlight overlays with adjustable color, size, opacity Undo actions and clear per-page annotations Create, draw, and save reusable signatures Click-to-place signatures anywhere Full-text search with highlighted results Drag-select or Ctrl+A to copy text Print with annotations flattened Portable single-file app (~10 MB) No installer, no admin rights required No account, no telemetry KillerPDF 1.4.2 changelog: What's new PDF form filling. Interactive PDF forms now render their fields (text inputs, checkboxes, radio buttons) as live controls. Fill them in directly and save — field values are written back into the PDF. PDF outline (bookmark) navigation. A new OUTLINES tab in the sidebar displays the document's bookmark tree. Click any entry to jump to that page. The sidebar auto-fits its width to the longest entry on open and can be dragged wider; switching back to PAGES snaps to the pages-mode width. Fixed Page rotation no longer reverts after saving. Rotations applied via the sidebar context menu now persist correctly through the save pipeline. Copied text words were out of order on PDFs where glyphs are stored in non-reading order (Issue #66). Text extraction now sorts words by position and uses a dynamic line-grouping threshold so both drag-select and Select All produce correctly ordered output. PDFs with malformed or non-standard XRef tables now open in read-only mode instead of showing "Invalid entry in XRef table" and failing entirely. Download: KillerPDF 1.4.2 | 6.1 MB (Open Source) Link: KillerPDF Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "...a low price of just $340..." I don't think it means what you think it means.
    • This Corsair Vengeance DDR5-6000 32GB RAM with RGB is a great deal for limited time by Sayan Sen Memory prices have been through the roof for a while, though it seems like things might finally be getting better. If you are in the market for one, then grab this Corsair Vengeance DDR5 32GB (2x16GB) DDR5 6000 CL36 kit with RGB for a low price of just $340 (purchase link under the specs table down below). The kit is compatible with both AMD and Intel systems as it supports both EXPO and XMP overclocking profiles, respectively. 6000 MT/s is often the sweet spot for many systems as it provides ample data transfer speed while still being on Gear 1 mode. This Vengeance variant has RGB so if you love bright setups with such lighting, this is a win-win for you. The technical specifications of the Corsair Vengeance memory kit are given in the table below: Specification Value Memory Type DDR5 Memory Size (Total) 32GB Kit Configuration 2 × 16GB Form Factor UDIMM (Desktop) Pin Count 288-pin Speed (Data Rate) 6000 MT/s Speed Rating PC5-48000 Tested CAS Latency 38-44-44-96 Voltage (Tested) 1.35V Performance Profile AMD EXPO & Intel XMP Heat Spreader Aluminum heatspreader Cooling Type Passive (Heatsink) Lighting Ten Zone RGB Software Support Corsair iCUE Get it at the link below: CORSAIR Vengeance RGB DDR5 32GB (2 x 16GB) 6000 CL38 – Gray (CMH32GX5M1E6000Z38): $339.99 (Sold and Shipped by Woot US, Fulfilled by Amazon US) This Woot deal is US-specific and not available in other regions unless specified. This is a first-party seller link (at the time of article publishing); ensure that you also purchase from a first-party seller link only. If you don't like it or want to look at more options, check out the previous deals that we have covered, OR you can also visit Amazon US deals page. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
    • The very fact that a TPM (v2.0 specifically which is part of the issue I suspect) is now a baseline for any supported Windows installation will naturally mean other vendors will start to leverage it as they know it'll be there. It's called progress, and it's always been the way. A TPM isn't a windows thing, it's just a module designed to securely store keys. Secure boot isn't a Windows thing (although MS are the TCA as I recall hence the upheaval this year as the 2011 certs expire), it's just a way to verify a bootloader is signed. Windows simply leverages them.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      66
    5. 5
      Skyfrog
      65
  • Tell a friend

    Love Neowin? Tell a friend!