The customer is trying to do a new installation on a new server. When SIM (Symantec Installation Manager) is doing the initial configuration, it fails:
A critical error occurred: The request failed with HTTP status 401: Unauthorized. Configuration failed while attempting: Pre-configuring...
Entry 2: ConfigureNS - task_Completed(): Configuration Task Pre-Configuring ... Failed: The request failed with HTTP status 401: Unauthorized. The request failed with HTTP status 401: Unauthorized. [System.Net.WebException @ System.Web.Services] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult) at Symantec.Installation.NSConfiguration.Tasks.AsyncTask.EndAsync(IAsyncResult result)
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. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">; <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2020-03-25T18:21:15.497565900Z" /> <EventRecordID>48305</EventRecordID> <Correlation ActivityID="{501E5A8B-018E-0019-8C5A-1E508E01D601}" /> <Execution ProcessID="868" ThreadID="9632" /> <Channel>Security</Channel> <Computer>SMPServer.domain.com</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-0-0</Data> <Data Name="SubjectUserName">-</Data> <Data Name="SubjectDomainName">-</Data> <Data Name="SubjectLogonId">0x0</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">APP_ALTIRIS85_PROD</Data> <Data Name="TargetDomainName">one</Data> <Data Name="Status">0xc000006d</Data> <Data Name="FailureReason">%%2304</Data> <Data Name="SubStatus">0x0</Data> <Data Name="LogonType">3</Data> <Data Name="LogonProcessName"> </Data> <Data Name="AuthenticationPackageName">NTLM</Data> <Data Name="WorkstationName">SMPServer</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x0</Data> <Data Name="ProcessName">-</Data> <Data Name="IpAddress">169.89.114.110</Data> <Data Name="IpPort">54563</Data> </EventData> </Event>
Environment Configuration. In this particular case, the issue was caused by having two NIC cards with their one IP Address and specific Hostname assigned to them. It was causing an issue with DNS resolution and validating the proper server name.
Resolution
After looking online for references on that Security event log entry and IIS logs 401.1 entry, we found something that helped.
In regards to this: Failure Information: Failure Reason: An Error occured during Logon. Status: 0xC000006D
and getting 401.1 on an asmx page, these 2 websites refers to the same possible solution: