Home/ Questions/Q 143311
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T08:04:31+00:00

I’m porting a legacy (read ancient) .asp application to a new server for backup

  • 0

I’m porting a legacy (read ancient) .asp application to a new server for backup purposes. It uses this code to determine the user:

sLogonUser = LCase(Request.ServerVariables(‘LOGON_USER’))

I believe in order for this field to be populated, I’ve got to turn on ‘Windows Integratged Authentication’ using IIS Manager. I’ve done this, but now I get an error message stating ‘The website cannot be displayed’. I think this must have to do with authentication, because even a simple ‘hello.asp’ has the same problem.

This leads me to believe that valid windows users have to be registered on the new server. Is this ‘Active Directory’? What’s the best way to go about adding users?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I believe for this to work the Web server must be on the same domain as the client accessing the web server and the users be created in the domains active directory schema.

    The client must use IE for the LOGON_USER to be automatically sent to the server

    If you are using IE it may be worth turning off friendly http error messages to see if the server is sending any more detailed information that IE is masking.

    This can be done by going to;

    • Tools -> Internet Options
    • Select the Advanced Tab
    • Uncheck the option that says ‘Show friendly http error messages’

    Now reload the page. If there is anymore detailed info there will be an HTTP status code (more than likely 403.x) if you google ‘http status code ‘ replacing with the code displayed you should find more information on the problem.

    HTH

    • 0