This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unusual Web Logging

Hello,

Can anyone translate this persistent weblog, it is not stopping, im afraid it will consume the ASG 425 hardware resources.

Thanks

sub="http" request="0xeb0700c0" function="auth_adir_auth_crap_callback" file="auth_adir.c" line="887" message="Authorization denied (NT_STATUS_NO_SUCH_USER)"
2011:03:12-11:35:40 astaro httpproxy[12066]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xeb0700c0" function="auth_adir_auth_crap_callback" file="auth_adir.c" line="887" message="Authorization denied (NT_STATUS_NO_SUCH_USER)"
2011:03:12-11:35:40 astaro httpproxy[12066]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xeb0700c0" function="auth_adir_auth_crap_callback" file="auth_adir.c" line="887" message="Authorization denied (NT_STATUS_NO_SUCH_USER)"

This thread was automatically locked due to age.

Parents

0 BAlfson over 14 years ago

These do sound like configuration issues.

AD-SSO only works for internal users logged into your Windows domain. SSO in not related to any AD server you might have defined on the 'Server' tab of 'Users - Authentication', so SSO also is not related to pre-fetch.

An authentication window pops up because the user has the browser configured to use the Astaro HTTP/S Proxy, and the user is in a network for which the proxy is in 'Basic user authentication' mode. The other way the user sees an authorization pop-up is if his browser is not configured to use the proxy, and is in a network in the 'Transparent with authentication' mode.

If using the FQDN doesn't work, it could be because you don't have an internal definition for that, and the user is getting name resolution from public DNS.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 14 years ago

These do sound like configuration issues.

AD-SSO only works for internal users logged into your Windows domain. SSO in not related to any AD server you might have defined on the 'Server' tab of 'Users - Authentication', so SSO also is not related to pre-fetch.

An authentication window pops up because the user has the browser configured to use the Astaro HTTP/S Proxy, and the user is in a network for which the proxy is in 'Basic user authentication' mode. The other way the user sees an authorization pop-up is if his browser is not configured to use the proxy, and is in a network in the 'Transparent with authentication' mode.

If using the FQDN doesn't work, it could be because you don't have an internal definition for that, and the user is getting name resolution from public DNS.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data