Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 20, 2017 10:23 AM
Hello Experts,
We have a requirement where in one of my users requested to have a UPN suffix for a local user account on any server.
LocalUserName is a local user created on the server ServerName which is part of the domain Domain.Com
The Requirement is to logon to the server like below and none of the below two methods work:
or
LocalUserName@ServerName
Audit Failure Message from Security event logs below:
##Attempt to logon like :: [email protected]
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: [email protected]
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: MyLaptop
Source Network Address: -
Source Port: -
Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0
##Attempt to logon like :: LocalUserName@ServerName
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: LocalUserName@ServerName
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: MyLaptop
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
================================================================
Please help..
System Administrator
All replies (5)
Thursday, April 20, 2017 11:13 AM
Hi,
I don't think local user accounts has UPN suffixes (UPN suffix is domain part of logon format and local users are not domain users).
It's just another format of defining domain user in multidomain environment.
Radek
Thursday, April 20, 2017 3:31 PM
Try it with a terminating dot:
username@servername.
disregard. tried it myself and that doesn't work
Friday, April 21, 2017 8:10 AM
Thanks and I know what upn suffix is, the requirement is there is an application which needs the user name in this format only:
and they can't use a domain account in this case.
System Administrator
Friday, April 21, 2017 11:21 AM
Thanks and I know what upn suffix is, the requirement is there is an application which needs the user name in this format only:
and they can't use a domain account in this case.
System Administrator
I would say that application is designed to work with domain accounts only. :/
Monday, April 24, 2017 11:58 AM
Thanks and I know what upn suffix is, the requirement is there is an application which needs the user name in this format only:
and they can't use a domain account in this case.
System Administrator
I would say that application is designed to work with domain accounts only. :/
Yeah I think so..
<object data-extension-version="0.5.0.161" data-install-updates-user-configuration="true" data-supports-flavor-configuration="true" id="__symantecPKIClientMessenger" style="display:none;"></object>
System Administrator