Solved

MS WinXP and Server 2003 machines with same administrator/password combination: "bad username or password" ???

Posted on 2009-04-15
7
331 Views
Last Modified: 2012-06-27
Hi,

I have a Windows XP PRO SP3 machine which is only member of a workgroup.
Furthermore I have a MS Windows 2003 SP2 machine with its own Active Directory.

On both machines the administrator username and password are the same.

OK, now I log in as an administrator on my WinXP machine:
Now, if I do a "net use * \\server\C$" from the commandline on the WinXP machine, I get an error that my username or password is invalid:

C:\Documents and Settings\Administrator>net use * \\SERVER\C$
The password or user name is invalid for \\SERVER\C$.

Enter the user name for 'SERVER':

Strange enough, when I now type in: administrator and my password, the share will be connected.

It's strange that the server is asking for my credentials, because the passwords of the administrator account are for both PC's identical!

I also have a third Win XP machine, also WinXP PRO SP3, with the same config as the machine stated above (not part of a domain, just its own workgroup).
This machine has also the same password for the Administrator account, when I execute the command to connect the share I don't have to fill out my credentials:

C:\Documents and Settings\Administrator>net use * \\SERVER\C$
Drive Y: is now connected to \\SERVER\C$.

The command completed successfully.

Now for  the verry weird part, I've setup a virtual machine, installing Server 2003 SP2 on it, and edited the administrator user to again, have the same password as all of the aforementioned machines.
If I execute the command to connect the C$-share to my previous "problematic" win XP machine, it works without it asking my credentials!

So why is it, that this one server will NOT accept the password from the administrator user from this particular Windows XP machine???

The reason I am asking this is because I wanted to use Remote Debugging for ASP.NET pages with this client machine and server.
I have Visual Studio 2008 installed on the XP machine, and remote debugger 2008 on the server.
But the problem was that the Administrator user could not log on to the debugger service, while from another PC or another user it WAS possilbe!
So I started narrowing this problem down, and now it seems that only the administrator account from this Win XP machine is rejected.
I get the following failure audit on the server when I try to connect as "Administrator":

Event Type:      Failure Audit
Event Source:      Security
Event Category:      Account Logon
Event ID:      680
Date:            15-4-2009
Time:            13:34:34
User:            NT AUTHORITY\SYSTEM
Computer:      SERVER
Description:
Logon attempt by:      MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
 Logon account:      Administrator
 Source Workstation:      WINXPMACHINE
 Error Code:      0xC000006A

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As you will see, the error code: 0xC000006A means that the password is invalid.

I've been researching this problem for quite a while now, and cannot seem to fix it.
One other thing: if I create another user on this problematic winxp machine and the same user on the server with again the same password, then it will work, the server accepts the credentials right away. Only NOT from the administrator??









0
Comment
Question by:dplus
  • 4
  • 2
7 Comments
 
LVL 3

Expert Comment

by:ealcaniz
ID: 24147210
Error code: 0xC000006A (Error code 0xC000006A) - According to Microsoft Windows XP attempts a limited logon for each account that is displayed on the Welcome screen to determine whether to prompt the user for a password. An attempted logon is logged for each account displayed. To resolve this problem, obtain the latest service pack for Windows XP. To prevent these events from being logged, disable the Welcome screen and use the classic logon screen or turn off auditing of logon events.
0
 
LVL 3

Expert Comment

by:ealcaniz
ID: 24147253
Another check this key in registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\NoLMHash there 3 values. Put 1 or 0.
More details in

How to prevent Windows from storing a LAN manager hash of your password in Active
Directory and local SAM databases
<http://support.microsoft.com/kb/299656/en-us
0
 

Author Comment

by:dplus
ID: 24147320
All systems are fully patched and up-to-date with the latest service packs.
The policy: "Network security: Do not store LAN Manager hash value on next password change" is disabled and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\NoLMHash has the value 0 (zero).
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 

Author Comment

by:dplus
ID: 24147466
By the way: the password for the administrator account is on all pc's more than 15 characters long and meets the complexity requirements. Wanted to say that because of the NTLM comments posted above by ealcaniz.
0
 
LVL 6

Expert Comment

by:danf0x
ID: 24147753
Hello I thought I would chime in on this.
  Remember that on a workgroup it tries to authenticate machinename/username not domain/username.  If the machine is not on the domain but the server does have a domain user the user and pass are the same but the group it tries to authenticate to is different.
0
 

Author Comment

by:dplus
ID: 24148036
Please understand it's only the ADMINISTRATOR account of 1 XP-machine which is giving problems.

If I create other users on this machine, or if I use another Administrator account on a different XP machine that is also NOT part of a domain, all goes well....

0
 

Accepted Solution

by:
dplus earned 0 total points
ID: 24599267
I did a reinstall of my Windows 2003 server, and all is functioning OK now.
Still don't know how this could happen...
0

Featured Post

Will my email signature work in Office 365?

You've built an email signature using raw HTML code in Office 365, but you can't review how it looks with Transport Rules. So you have to test it over and over again before it can be used. Isn't this a bit of a waste of your time? Wouldn't a WYSIWYG editor make it a lot easier?

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
profile migration 14 39
Can't get access/ownership to folder 3 89
Windows 10 IE Certificate Issue 10 42
iPhone v Android phone 7 34
This is an article about Leadership and accepting and adapting to new challenges. It focuses mostly on upgrading to Windows 10.
Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now