Security on the Lansweeper web view

[Jezza]

Is it possible to restrict who can access the Lansweeper web page. If so how please?

[Jezza]

Thanks you for resolving this, much appreciated.

For anyone reviewing this, the issue was that the iis express was an old version which did not support NT authentication.

[Hemoco]

Please contact us by e-mail for this problem.
I suggest first resetting your web.config file to the default values.

[Jezza]

Lansweeper wrote:
Please contact us by e-mail for this problem.
I suggest first resetting your web.config file to the default values.

e-mail sent

[Hemoco]

can you set the allow roles to *, then surf to page "usertest.aspx"

[Jezza]

Lansweeper wrote:
can you set the allow roles to *, then surf to page "usertest.aspx"

<authentication mode="Windows"/>
<identity impersonate="true" />
<authorization>
<allow roles="*" />
<deny users="*" />
</authorization>
<compilation debug="true" strict="false" explicit="true"/>

if I type in my browser usertest.aspx I get a proxy message saying the wesite can not be found.

If I try to go to Lansweeper I get the following:

Server Error in '/' 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]

did you change the IIS security settings also?

[Jezza]

Lansweeper wrote:
did you change the IIS security settings also?

from the iisexpress file


<authentication>

<anonymousAuthentication enabled="false" userName="" />
<basicAuthentication enabled="false" />

<clientCertificateMappingAuthentication enabled="false" />

<digestAuthentication enabled="false" />

<iisClientCertificateMappingAuthentication enabled="false">
</iisClientCertificateMappingAuthentication>

<windowsAuthentication enabled="true">
<providers>
<add value="Negotiate" />
<add value="NTLM" />
</providers>
</windowsAuthentication>

</authentication>

<authorization>
<add accessType="Allow" users="*" />
</authorization>

<ipSecurity allowUnlisted="true" />

[Jezza]

Lansweeper wrote:
did you change the IIS security settings also?

Is there a number I can call to discuss this please?

[Jezza]

Lansweeper wrote:
did you change the IIS security settings also?

yes.