Vista's having trouble with domain login

[JBruyet]

Hey all,

I'm running Vista Business on a fairly new ThinkPad. About a month ago Vista occasionally would give me a "The user name or password is incorrect" when I logged in. At first I thought it was me but sometimes I would type using two fingers to make sure I wasn't spelling anything wrong and sometimes I'd still get the error. This morning I removed my laptop from the domain and had some trouble getting it to reconnect. NOW, neither of my domain logins is working--Domain Admin or my Domain name login. I know that I'm not spelling anything wrong, and I know both accounts are working because I can log into other machines with both accounts. I've tried logging in using:

DomainUser
DomainPassword

Domain\User
DomainPassword

User@Domain.com
DomainPassword

BiteMeMS
FrustrationMounting

None of these worked, but then I didn't really expect the last one to work. I've already had to go in and reactivate the accounts. I'm not sure about any other ways to change the login syntax. Has anyone else had this problem and figured it out? I'm Running a Win2k3 domain. Any and ALL answers will be appreciated!

Thanks,

Joe B

 

[linney]

Can you connect if you load "Safe Mode with Networking"?

What is showing up in the Event Viewer, especially the Security logs?

A couple of XP related threads might give you a few ideas to try?

Windows XP pro error, what is up with this one?
thread779-1213095

Can't join Win XP Pro to Win Server 2003 domain
thread779-1091084

Have you also tried posting in the 2003 Server Forum?

http://www.tek-tips.com/threadminder.cfm?pid=931

 

[JBruyet]

Hi Linney,

I tried logging in with "Safe Mode with networking" and got the same error.

Event Viewer on the laptop doesn't show anything going on when I try to log in. I checked the DCs and I only saw one entry for the administrator account, but it was for a separate server that stores user files. I'm letting that slide for now.

I haven't posted in the 2k3 forum yet because everything else is working. I also didn't want to dupe post.

I wanted to get back to you on the quick ones. I'll check the links a little later and let you know what I find out.

Thanks,

Joe B

 

[PRPhx]

Try this (works in XP):
1) REMOVE your laptop from the domain (as you said you've done)

2) ADD your laptop to a WORKGROUP (ANY workgroup. I've used A before)

3) Log into the workgroup, use any credentials.

4) If asked to reboot, go ahead and do so, just remember the creds you created (again, user A and password a should work or something easy along those lines)

5) Now take your laptop out of the workgroup and add it into your domain. Use your real credentials here. Reboot. You SHOULD now be in your domain with your domain credentials.

 

[JBruyet]

Hi linney & PRPhx,

I discovered an issue with my Windows 2003 domain controllers. I'm in the process of correcting that problem and I'll see if fixing that fixes my Vista login problem.

Thanks for the help,

Joe B

 

[JBruyet]

Yep, I just tried to login with my laptop (that has Vista on it) and I got in on the first try.

Thanks all for all the help,

Joe B

 

[linney]

Can you leave a idea of that which you corrected, it might be handy for the next person? Forget about it if it means writing a book.

Thank you

 

[JBruyet]

Hi linney,

I posted this problem in the Server 2003 forum and received some suggestions regarding possible domain controller troubles. I had ASSUMED that the problem was with my laptop because everything else was working right.

I ran REPLMON and found out that one of my DCs wasn't communicating. DCDIAG showed several errors. I tried to reinstall DNS and got an "Invalid Data" error, and when I tried to check the logs in Event Viewer I got a "Data Corrupted" error message. Superficially this server was behaving normally, but when I started to dig I found out it was having serious issues.

I seized all FSMO roles to my second 2k3 DC and removed the first DC from the network. I wiped the first DC and at this moment server 2003 is being installed. In the future I'm going to focus more on preventative maintenance. Running some basic diagnostic tools on a regular basis probably could have told me what was up before I started having problems.

Thanks again for the help, and your suggestion about listing the corrective measures was a good one that I never even thought about.

Joe B

 

[linney]

Thank you for the feedback.

 

[JBruyet]

It's Baaaaaack!

Ok, once again I'm unable to log onto the network using my laptop. I've tried removing the laptop from the domain and going into a workgroup, then rejoining the domain but no joy. I've tried logging in with some other good accounts and no joy. I checked my servers and they're all working fine this time.

I'll go through and retry the suggestions up above, but since they didn't help last time I'm not sure they'll work this time. As before, I'm open to all suggestions.

Thanks,

Joe B

 

[linney]

Is this a Wired or Wireless connection by your Laptop? I only ask as I have seen problems reported with Thinkpad Wireless Connection Manager in the past. Also what brand of Network Card does it have?

 

[PRPhx]

Hmmm. Is this a work laptop or home?

If it's a home laptop, try going into the command prompt (Start->run->type cmd and press return)

at the prompt type: ipconfig /release and press enter. Then type ipconfig /renew. This MAY do the trickk for you. IF not, reboot the laptop.

IF this doesn't work or it's on a work domain, AND if you have an IT department, I would call them. Have them remove your laptop from the domain and re-enter it (you may have to rejoin a work group, exit the workgroup and join the domain, then reboot).

 

[JBruyet]

Hi linney, I've tried logging in with both my wireless and wired connections and neither one works.

PRPhx, it's my work laptop. I've already tried your recommendation on joining a workgroup and rejoining the domain. No joy.

This laptop uses the fingerprint scanner, and when I try doing the scan I get a Success message but then I get the error about an incorrect login or password. The error logs don't show anything, and my DC logs don't show anything either. I know that Vista is still quirky, so I'm hoping that an update or something will fix it.

Thanks,

Joe B

 

[JBruyet]

Ok, here's an entry from the Event Viewer that has the same time stamp as one of my failed domain logon attempts:

An account failed to log on.

Subject:
Security ID: SYSTEM
Account Name: VISTA1$
Account Domain: LINK
Logon ID: 0x3e7

Logon Type: 2

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: jobee
Account Domain: LINK

Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0

Process Information:
Caller Process ID: 0x300
Caller Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Workstation Name: VISTA1
Source Network Address: 127.0.0.1
Source Port: 0

Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

I tried looking this up on eventid.net but they didn't have it in their database yet. Googling it didn't help much either. Does anyone have any other suggestions on how to get this laptop to not "mangle" the login name or password? The login information works fine on all other workstations.

Thanks,

Joe B

 

[linney]

I can't remember where I dug these up from, but I'll pass them on to you.

Logon Failure Error Codes Legend:
Error Code Hexadecimal Cause
3221225572 C0000064 User logon with misspelled or bad user account
3221225578 C000006A User logon with misspelled or bad password
3221225581 C000006D User logon has incorrect user name
3221225583 C000006F User logon outside authorized hours
3221225584 C0000070 User logon from unauthorized workstation
3221225585 C0000071 User logon with expired password
3221225586 C0000072 User logon to account disabled by administrator
3221225875 C0000193 User logon with expired account
3221226020 C0000224 User logon with "Change Password at Next Logon" flagged
3221226036 C0000234 User logon with account locked

 

[JBruyet]

Hmmm... 6d means an incorrect user name. BUT, that's always been my user name. I know that one variation for a login name is user@domain.com. I've tried that one and it didn't work. Do you know if there are any other variations for a login? And why would my login process with the fingerprint scanner work for a while and then quit working? All I can say is we're not upgrading to Vista in the foreseeable future!

Thanks,

Joe B

 

[PRPhx]

try: domainname\username as an alternative.

 

[JBruyet]

PRPhx, yeah, I've tried that one too. No joy. FWIW, I've tried using some different, legitimate network accounts and they all give the same result. I've looked to make sure CAPS LOCK is off too. I'm baffled.

Thanks,

Joe B

 

[smah]

I have to say it, even though it's unlikely: make sure the number lock is not on. This actually happened with a laptop at my office today - the user account never changes, and since the password characters are obscured, no one realized that some of the letters being typed were actually numbers.

 

[JBruyet]

smah, I'll check that out and see. One never knows...

Thanks,

Joe B