Link to home
Start Free TrialLog in
Avatar of rsnellman
rsnellmanFlag for United States of America

asked on

HELP!!! Have a wierd issue occurring on my network with usernames.

Hi, I am having a strange issue happening to my users, particularly, students.  Some have to capitalize the first character of their username before it will allow them to log into the domain computers.

It won't let me them login with all lowercase or all uppercase, but just the first character.  

Not all student's usernames are effected by this.  It seems to be random and just started happening.

I verified in the AD that the student's UPN (Full Name) of their user account object is the first character is uppercase and then some are all lowercase, so not sure if that plays a factor.

I was always under the impression that Windows environment the username is not case sensitive, only the password.  I know in a Unix / Linux environment that username is case sensentive.

Has something changed with Server 2008 R2 (ADDS) or Windows 7 Enterprise/Pro?

Does anyone have an idea what is causing this?

Thanks in advance.
Avatar of x-men
x-men
Flag of Portugal image

I think it has something to do with the kerberos authentication
Avatar of rsnellman

ASKER

Would kerberos authentication have issues if the DC on the branch site, (where the students are having the issue) running Server 2003 x64, while our main site DC running Server 2008 R2?

Just not sure why this started happening.

x-men,
How can I go about verifying if it is a kerberos authentication?  And how to fix the kerberos authentication issue, if it is that?

Thanks.
OK, now this is strange.  The accounts in question are now working with all lowercase for username.

Hmmmm...
with out any inte3rvention?
ASKER CERTIFIED SOLUTION
Avatar of rsnellman
rsnellman
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
magic...
Problem went away on its own.  Could not replicate the issue.  Not sure what happened, but not certain the issue is completely fixed yet.