We'd love to hear about it! Click here to go to the product suggestion community
I have here SG330 device. Users are synced from AD backend.
Now since user accounts in active directory are able to log on to only specific workstations (AD user account attrribute "logonworkstation" has been set), these users are not able to authenticate if they try to log in to UTM through User portal. Only message "Invalid username/password etc" shows up.
This behavior is caused exactly by setting the "logonworkstation" attribute (we are not facing here any other problem). If I remove the attribute, users are able to log in just fine.
So the question is:
What computer name for the UTM device shloud be set as value for "logonworkstation" attribute in AD(we already tried the name of the UTM computer object in AD but no luck)? Or is it even possible to make the setup as we desire?
Hi Memo and welcome to the UTM Community!
This is the first time this question has been asked here. What do you see in the authentication log in the AD server? What is in the User Authentication log at the same time?
You also should open a case with Sophos Support. If we solve this here, they can always just close the case.
Cheers - Bob
In reply to BAlfson:
In the aua.log I can see this record:
2018:07:18-10:53:08 utm-2 aua: id="3005" severity="warn" sys="System" sub="auth" name="Authentication failed" srcip="x.x.x.x" host="" user="test-user" caller="portal" reason="DENIED"
Where x.x.x.x is public IP address of client trying to access User portal.
In the same time, see this event on AD server below:
An account failed to log on.
Security ID: SYSTEM
Account Name: ADserver01$
Account Domain: XXX.int
Logon ID: 0x3E7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: test-user
Failure Reason: Unknown user name or bad password.
Sub Status: 0xC000006A
Caller Process ID: 0x1e4
Caller Process Name: C:\Windows\System32\lsass.exe
Workstation Name: ADserver01
Source Network Address: 10.1.1.254
Source Port: 64096
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
In reply to Milos Tomanicek:
It looks like your initial analysis was spot on, Memo. Maybe Sophos Support will have a suggestion better than adding the UTM as a logon workstation to every user's account. Please let us know.