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

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

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

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      228
    3. 3
      PsYcHoKiLLa
      161
    4. 4
      Steven P.
      76
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!