Network admins at my company did something...took away privileges and add others and now my report interface no longer is able to read the user accessing the reports. This is important because there is code that is dependent upon the user that logs in. I need help trying to figure out what went wrong so I can fix it because they don't think they did anything wrong. Where do I start?

User.Identity.Name used to return the username logging into the application. Now it returns nothing, so certain users are unable to access their special reports.

Help?!?!

The first thing I would do is find out if the admins turned on "Anonymous Access" in IIS. If they did that for the virtual folder in which your application resides (or any virtual folder above it), then client machines will no longer send certificate information to the web server, and User.Identity.Name will have nothing (same problem as the Request.ServerVariables collection).

Brandon

Anonymous Access is turned on, but that is the only way the application will work. When I turn it off I get an error screen...

Is it the infinitely usefull "Page Cannot Be Displayed" error? It's possible that there's an error in the ASP somewhere that only surfaces when User.Identity.Name actually has a value. Whatever the cause, if Anonymous Access is enabled in IIS, there is no way to automatically detect the user from the Web server. In the right environment, you might be able to use Client-side Javascript to detect the user and pass the username through a hidden form. Check out the "WScript.Network" ActiveX Object for details.

Brandon