I am not using ASPNETDB or membership. I am in a corporate/intranet environment using Active Directory.
I can quickly reproduce this issue as follows. Create a new web application with a single page:
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:LoginName ID="LoginName1" runat="server" />
</div>
</form>
</body>
</html>The LoginName control simply displays User.Identity.Name. If I deploy this application to two different servers, and access them both at the same time, my LoginName shows up as Company\DoeJ on one and Company\doej on the other.
My question is why is the case of the LoginName (or User.Identity.Name) different on different servers? What determines the case of the LoginName? This seems like it should be a simple question, but I haven't been able to track down a satisfactory answer. Thanks for any help on this.