User Acccess Control to Lansweeper web site

[Pollak]

Though I can enable "Digest authentication for Windows domain servers" thus prompting for cridential, it appears to allow regular Domain User to log in and gain access to the Lansweeper web site. I tried removing the local Users group but that break the web interface to Lansweeper, but doees prevent regular domain user and not Domain Admins from gaining access.

The following users and group are part of the local user's group.

ASPNET
NT AUTHORITY\Authenticaed Users
NT AUTHORITY\INTERACTIVE
SQLDebugger

[Pollak]

There does not appear to a way to attach the file. ?

[Hemoco]

Could you upload your web.config please.

[Pollak]

Did not work. Running lansweeper 3.5 Beta. Fresh install. I get the following error.


Server Error in '/lansweeper' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

[Hemoco]

See this page:
http://www.lansweeper.com/kb/restrict.aspx