After a recent Windows Update I could no longer access the folders on my Windows XP file server. A window popped up asking for a username and password even though they are both the same on the two computers. The error message each time was “Logon failure: unknown username or bad password.”
I typed in my username and password five times. It reached the point where I thought I had gone crazy and was typing in the wrong one: it kept on coming back to me with the dreaded “Logon failure: unknown username or bad password.”.
I quickly returned to my senses and guessed something was up with the authentication between XP and Windows 7. A few Google searches later I found out that a Local Security Policy needs changing.
- Open the Start menu
- Type “Local Security Policy” in the search box
- Open Local Security Policy
- Navigate to “Local Policies” -> “Security Options” and then locate the entry named “Network security: LAN Manager authentication level”. Double click on it.
- In the dropdown list choose “Send LM & NTLM – use NTLMv2 session security if negotiated
- Click OK
It seems that a recent Windows Update has changed that policy’s settings to be undefined, which —from what I can tell— forces NTLMv2 session security always. My XP installation mustn’t have NTLMv2 capability and that is why I kept seeing “Logon failure: unknown username or bad password.” errors.
After changing the local policy I was immediately able to connect to my network shares again.
Links
- Microsoft forum: “I can’t map a network drive from Windows 7″
That was it!!! after tons of searching this did the trick!
Thanks,
Ted
THANK YOU!!! after 5 hours this was the one that fixed it!
I just got a new Windows 7 laptop and am trying to connect my printer to it through my wireless network on another PC running Windows Vista Business. Windows 7 finds the other computer in the network sharing but when I try to search for a printer, nothing comes up. When I try to browse for the printer it pops up a box to enter in a password. After entering it, I get the same message that you posted above. I did what you suggested on the Vista desktop but am still getting that message on the laptop. ANY IDEAS????
That worked for me too, after spending several hours looking. Thanks.
Try following the steps on the Windows 7 laptop: it’s Windows 7 that is refusing to authenticate against Windows Vista. If that doesn’t work I have no idea, sorry.
My thanks goes out to you johnny, after re-installing windows 7 twice, running updates, many google searches, etc etc. This finally fixed my problem.
The crazy thing is that this policy was ‘undefined’ by default. Bill has done a good job on 7 this time round, but issues like this should not be present on fresh installs.
regards, steve
Thank you so much … after lots of search finally it worked .
thank you ,thank you , thank you …
works ! nice info – thank you
WoW… Finally after doing a vast amount of searching the immense world of the WWW … found it … Thanks ever so much for the information provided … it worked. Thank The Sun for people smart enough to work out these bloody M$ problems…
Thanks so much again!
Thanks very much. I wasted 1 hour looking for this. Does anyone know why Microsoft did this?
Hey thanks a ton.. It helped :)
Fantastic advice – this also did it for me . Thanks a million!!!
I spent three weeks of spare minutes/hours trying to get to the bottom of this same issue. You are a star!
Does anyone have the address where I can invoice Microsoft for my time? :-)
Just change your time and time zone. It solves your problem.
Nice … Nice … Real Nice!
Pingback: ویندوز سون به اکس پی کانکت نمی شه
Holy mother of god! It worked! I don’t know where you found it on google, but I found your solution googling. My Win7 was a fresh installation and I had the same problem.
Thanks. Saved me a headache
Thank you. After lots of searching the information you had did the trick. Thank you!
thank you.this solved my problem.
Why does Microsoft trip their users up like this and then make them feel like idiots?
thank you. This also worked well between w7 and server 2003.
Thank You Very Much. that was the solution that i was looking for… I had tried a lot of “solutions” like changing the time and to have the same user and password in the computers… Once again… Thanks :)
Thank you for being born. While I had a different problem–I couldn’t perform remote debugging using Visual Studio 2008 because I kept getting the same logon failure when I was trying to connect from a computer on a domain to a workgroup computer–the solution was what you described. Thanks again!
thank you very much for hint!
Thank you very much, I was looking for solution of problem for long time but they are not work. Luckily, I find your solution, so nice, thanks again!
If you’re using the “Home Premium” version of Windows 7/Vista, you probably don’t have the “Local Security Policy” snap-in. In this case you need to make the change manually in the registry. See this TechNet article for details:
http://technet.microsoft.com/en-us/library/cc960646.aspx
If you’re not familiar with editing the Windows registry by hand, do a Google search. :-)
Thanks a lot !!!!
After tons of searches this has helped me….
Thank you very much……..
This had me stumped all morning! Thanks so much! Now I can finally go to lunch!
I tried to make this change on the XP machine, the machine that is hosting the printer, and I still getting the error message on the Window 7 machine. I don’t know how to make this change on the Window 7 machine, because I can’t find Local Security Policy on Window 7. Can anyone provide a step by step on making the change on the Window 7 Machine for this? Thanks.
Thanks by Ajay
Blah. This solution works for everyone but not me. I really don’t know what to do now.
Found the solution for me:
Start the Microsoft Management Console (MMC) Local Security Policy snap-in (Start, Control Panel, Administrative Tools, Local Security Policy).
Expand the Local Policies branch.
Select Security Options.
Double-click “Network access: Sharing and security model for local accounts.”
Select “Classic-Local users authenticate as themselves”, and click OK.
Pingback: NetzwergBlog - Dennis Körner » Blog Archiv » Zugriff auf Freigabe auf XP-Rechner von Windows 7 nicht möglich – Was tun?
unbelievable. this is invaluable. it took me a day to figure out to go to the GLOBAL POLICY editor to open the local for THIS option. I was going directly to just the local but I may have been taking it too literally. Either way after going into gpedit then to local I was able to get this option to come up, and sure enough this did the trick. Its amazing though because this was not an issue a couple months ago. Thanks!
thanks budd surberb
Pingback: Windows Xp de paylaşılan klasöre, Windows 7 üzerinden erişememek « Tamamen Kişisel
thanks ..it worked for me….best solution….
if this won’t work like it did to me. try running the program as administrator..
Thank God you Knew the solution for this issue. Very helpfull. Gracias!
Thank you very much….
Thats Great!!!
Its working good..
Thanks..
Hey Thanks a lot posting this solution. I was facing this error on Win-7 PC since 2 days and now I got it fixed after going through this process.
Thanks a ton.
–
Prem Soni
The same trick for Windows Vista Home Edi…
1 . Open registry editor ( Start search – regedit)
2 . Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Create a new DWORD value with the following properties:
NAME: LmCompatibilityLevel
VALUE: 1
4. Restart your PC and try the connection again…
You hit the nail on the head for me (though my issue is between 2 identical copies of Windows 7 Home Premium.) Unfortunately, Home Premium does not have Local Security Policy, so I was forced to create a DWORD value in the registry.
However, there’s no change.
By any chance – do you know which update caused this? I’m sure rolling back the update will not revert the settings back to normal, but I’d be able to avoid that one for now.
Incidentally, I KNOW it was an update that caused the issue. I performed a clean install and it was perfect until the last batch of updates performed. I have no choice but to do it again, but this time I would know which to delay.
thx man… it’s ton of thank you…