• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 895
  • Last Modified:

Server Variables LOGON_USER returns no value from ASP

HI!  When I run the code below, I see "You are" and not the logon name.  Does anyone know why?
<HTML>
<BODY>
      You are <%=Request.ServerVariables("LOGON_USER")%>
</BODY>
</HTML>
I have read posts on this subject for the last hour and can't figure out what I'm doing wrong.   In IIS, Enable Anonymous Access is checked and the logon name is IUSR_OURMACHINENAME.  Integrated Windows authentication is checked.  We are running Windows 2003 server, ASP Classic and SQL Server 2005.  I am trying to get the AD group of the user so I can display a menu on the intranet (not external site) based on their group without the users having to ask users to log in via a login form.  Any ideas?  I have seen so many posts from people doing the same thing but they were able to see the results of the Server Variables.  When I looked at WIndows Firewall as one of the posts I reviewed suggested, I got a message saying the WIndows Firewall Service wasn't even started.
Thanks,
Alexis
0
alexisbr
Asked:
alexisbr
  • 3
1 Solution
 
hongjunCommented:
You will need to uncheck Anonymous Access and tick authentication method like Integrated Windows Authentication
0
 
alexisbrAuthor Commented:
Thanks, Hongiun.  How will unchecking Anonymous Access affect existing users?  We have hundreds of users on this intranet and I don't want to mess up their access.  Integrated Windows Authentication is already checked.

Alexis
0
 
alexisbrAuthor Commented:
We unchecked Anonymous Access.  However, it caused login problems for some users so we had to check it again.  Do you have any suggestions?  Is there another way to tie Active Directory users to SQL Server logins so I can restrict datasets based on the logins?  I already set up the users in SQL Server based on their AD group but now I need to tie that to that to the ASP pages.
Thanks,
Alexis
0
 
alexisbrAuthor Commented:
We decided to go another route because just unchecking anonymous access caused other problems.  I didn't hear back on any other solutions so we are going to have to set up our own login logic and force the users to log in instead of using Active Directory setup.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now