Fix : Windows 10 accessing network drives : Password incorrect


Recommended Posts

The workgroup comment was a joke to how bad the info in this thread is..  You don't have to use computername\user to access shares..  Not sure what the original poster was doing or thinking or what everyone else that chimed in saying that fixed it was doing..

 

But windows does not use that info as I clearly showed by putting in whatever for a domain and authing just fine, etc..

 

I would love to be shown wrong -- if there is a local account billy, with password as the password and you send just billy and password or something\billy and password does not matter.  Now if machine your authing to is part of a domain, and it has local accounts billy and domain accounts billy your going to need to specify which one.

  • Like 1
On 30.06.2015 21:40:13, warwagon said:

I ran into an issue that was driving me nuts after installing Windows 10 on 2 computers. I could not access any of my network drives from either of those machines. It kept telling me my password was incorrect, but it wasn't. But I would go to a Windows 8 or Windows 7 machine, enter the username and password and it would connect first try.

Normally when you connect to a network drive it prompts you for your username and your password.

On windows 10 in the username box instead of entering just the username enter the computer name plus the username.

Example.

computername\owner  (Do not put \\computername ... that will not work so leave the \\ off)

Now enter the password and you should be able to access the network share just fine.

Hope this helps anyone else that was pulling their hair put.

Thank you very much friend. I solved our network problem at office thanks to your answer. I signed in forum just to thank you. Thanks!

On 12/15/2015, 2:12:55, cell-chouk said:

Thank you very much friend. I solved our network problem at office thanks to your answer. I signed in forum just to thank you. Thanks!

Warwags did you sign up another account and thank yourself? common fess up :p 

5 minutes ago, offroadaaron said:

Warwags did you sign up another account and thank yourself? common fess up :p 

Actually that would have to be "Accounts" ... more than 1 account, because there have been a lot of 1 post wonders thanking me! But no I didn't! People just found that helpful :D

 

I count about 8 people joined just for this thread :)

  • Like 1
2 minutes ago, warwagon said:

Actually that would have to be "Accounts" ... more than 1 account, because there have been a lot of 1 post wonders thanking me! But no I didn't! People just found that helpful :D

but you're making people type to much lil pal, all they need is .\username you've now got all these kids typing out long computer names unnecessarily lol. And what happens if you can't find the computer name haha.

6 minutes ago, offroadaaron said:

but you're making people type to much lil pal, all they need is .\username you've now got all these kids typing out long computer names unnecessarily lol. And what happens if you can't find the computer name haha.

Fair point lol . is localhost

20 minutes ago, Mando said:

Fair point lol . is localhost

Warwags is just trying to get people to use their keyboards more so he can sell them a new one because they'll wear out quicker with more use ;)

 

It's a great tactic! Very cleaver :p 

 

"I count about 8 people joined just for this thread"

 

People joining for FUD... Who would of thunk it...  Lets start creating threads about FREE this and Free that, and will get lots of google traffic and people joining ;)

 

While your intentions seem to be genuine, but the information is not correct... Windows that is not a member of a domain does not give 2 ###### to what anything other than the username and password is.. Now maybe there is something going on when trying to use MS accounts...  But if that is the case that should be spelled out, since saying you need to use domain\username to access shares to machines that are not members of a domain is just not correct..  Plain and simple so as this thread is currently going its just a bunch of FUD... That yeah quite often draws users ;)

 

24 minutes ago, BudMan said:

"I count about 8 people joined just for this thread"

 

People joining for FUD... Who would of thunk it...  Lets start creating threads about FREE this and Free that, and will get lots of google traffic and people joining ;)

 

While your intentions seem to be genuine, but the information is not correct... Windows that is not a member of a domain does not give 2 ###### to what anything other than the username and password is.. Now maybe there is something going on when trying to use MS accounts...  But if that is the case that should be spelled out, since saying you need to use domain\username to access shares to machines that are not members of a domain is just not correct..  Plain and simple so as this thread is currently going its just a bunch of FUD... That yeah quite often draws users ;)

 

You sound really bitter. When people make up their minds with stuff like this, you will not change it. 

 

duty_calls.png

 

  • 2 weeks later...

Reading this thread has solved my problem. I found it hard to follow but managed to fudge my was through.

 

My problem -I could no longer access my linkstation shares after upgrading to win10.

 

The help given here was kind-of giving me hope but I would not get a user password authentication prompt when following instructions just a not=authorised error.

 

A comment within this thread somewhere (struggling to find it now) about the authentication not being able to distinguish between local and windows live accounts was a breakthrough. I went onto my linkstation admin page. Changed the user name of the linkstation local account to something different from my windows live account id. When I tried to access share from the explorer again I was this time asked for a username and password and gained access.

 

(I used the NAS name as a domain but understand from this thread is doesn't matter. I mistakenly put \\ in front of the domain name in the authentication box at first - that didn't work)

 

Thanks for getting me there. I have been without share access for months!

 

Michael

 

  • Like 2
  • 3 weeks later...
  • EmuZombie locked this topic
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      492
    2. 2
      +Edouard
      224
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!