11-13-2014 10:29 AM
We are doing a Domain migration to another domain with which we have a full trust with. I have added an Automated User Assignment for users/computers in the new domain to connect to the DLO server. The DLO client installs success fully when running from the DLOAgent share. When I launch the client the spash screen appears and goes away without error, client console never starts. I looked in the logs and event viewer on the client machine and nothing is there.
On the server I notice the user and computer never registered, nothing in the Alerts. In looking at the Event Log I see the error:
Log Name: Application
Source: MSSQL$DLO
Date: 11/13/2014 12:47:42 PM
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: ***\***
Computer: ****
Description:
Login failed for user '***\***'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <named pipe>]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSSQL$DLO" />
<EventID Qualifiers="49152">18456</EventID>
<Level>0</Level>
<Task>4</Task>
<Keywords>0x90000000000000</Keywords>
<TimeCreated SystemTime="2014-11-13T17:47:42.000000000Z" />
<EventRecordID>80039</EventRecordID>
<Channel>Application</Channel>
<Computer>****</Computer>
<Security UserID="S-1-5-21-2834317594-801733261-2494563199-21142" />
</System>
<EventData>
<Data>***\***</Data>
<Data> Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.</Data>
<Data> [CLIENT: <named pipe>]</Data>
<Binary>184800000E0000000C0000005000450049002D004400430033005C0044004C004F000000070000006D00610073007400650072000000</Binary>
</EventData>
</Event>
Anyone have any ideas on whet the problem may be and how to resolve?
11-15-2014 12:56 AM
Can the client access the NUDF share from their system ? If yes, can they create/delete a new file ?
You'll have to enable debugging so that logging can be captured on the client's end. Use this KB for doing so - http://www.symantec.com/business/support/index?page=content&id=TECH51435