Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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: 796 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