Capitalising of Usernames

[Guest]

I am a tech agent for Netzero, and our agents have been reciving calls
concerning an invalid username and password error.

the have been occurances (many) where it is caused by a capitalised first
letter of the username.

the user names are case sensitive so this causes an invalid username and
password error due to the capitalization.

It only happens on XP computers, and it isnt on every computer.

Is there a setting that might be able to be selecdted off in order to
rectify this issue?

Anyhelp would be appretiated.

 

[Guest]

Case sensitive passwords are programmed by the server and not by WindowsXP.
NetZero must be using a case-sensitive server, and informs their subscribers
to create alphanumeric passwords.
Check with your systems analyst for settings on the NetZero server to
eliminate
this problem. Passwords should be programmed at lower and upper case
keyboard strokes to avoid confusion by novices using/accessing the Internet.

 

[Guest]

Its not that The servers are wrong. They are case sensitive.

What i am saying is that, When they go to hit connect the User name
magically capitalizes the first lettr of the user name, and since the user is
case sensitive it wont log on.

 

[Malke]

Its not that The servers are wrong. They are case sensitive.

What i am saying is that, When they go to hit connect the User name
magically capitalizes the first lettr of the user name, and since the
user is case sensitive it wont log on.

I'm sorry, but this simply isn't true, at least regarding usernames and
passwords in Windows. All my Windows boxen use lower case usernames
because it's easier in my mixed os network. These are computers running
Win9x, Win2k Pro, Win2003 server, and WinXP Pro SP2. The problem
probably lies with the NetZero connection software.

Malke

 

[Guest]

You said it, that is the servers settings. Screen names and email addresses
should NOT be case sensitive but passwords should be. NetZero's software
is likely the cause. As a former user of Juno back in the 90's we had a
similar problem but they solved it back then.