Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > User Device Tracker (UDT) > UDT - Knowledgebase Articles > UDT fails to display logins when IPv6 to IPv4 translation happens

UDT fails to display logins when IPv6 to IPv4 translation happens

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 791 Votes: 0 Revisions: 7

Issue:

User Device Tracker (UDT) fails to display user logins when IPv6 to IPv4 translation happens. The event log shows event message 4768 stating a successful attempt. 

Explanation and Resolution:

Event message 4768 does state a successful attempt yet the client address is listed as ::ffff:a.b.c.d vs a.b.c.d. The additional field (:ffff) happens when the Stateless IP/ICMP Translation Algorithm is applied. This algorithm is necessary for IPv6 to communicate with IPv4. For more information on this algorithm, see "RFC2765." 

To resolve, enable Audit Kerbos Service Ticket Operatons on your Domain Controller.

Expected Results:

UDT displays user logins when IPv6 to IPv4 translation happens.

Last modified

Tags

Classifications

Public