﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>UltimateWindowsSecurity.com Forum / Ultimate Windows Security Forum / Security Log / 552 - Logon attempt using explicit credentials  / Target Server not always Local Host / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>UltimateWindowsSecurity.com Forum</description><link>http://forum.ultimatewindowssecurity.com/</link><webMaster>noreply@ultimatewindowssecurity.com</webMaster><lastBuildDate>Tue, 07 Feb 2012 12:21:01 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Target Server not always Local Host</title><link>http://forum.ultimatewindowssecurity.com/Topic358-35-1.aspx</link><description>Do you have a situation where you are getting a 552 on the client computer and a corresponding 528/540/4624 on the server?  If so, can you post examples?</description><pubDate>Fri, 16 Apr 2010 09:36:48 GMT</pubDate><dc:creator>RandyFranklinSmith</dc:creator></item><item><title>Target Server not always Local Host</title><link>http://forum.ultimatewindowssecurity.com/Topic358-35-1.aspx</link><description>I have seen this event where the target server is not LocalHost, but another server in another domain.  &lt;/P&gt;&lt;P&gt;In analyzing, It appears if EventID 552 appears on one computer and the target was another computer, that I see a logon (528 or maybe 540 or 4624) on the Target Server's event log, with the target user name as the username of the 552 event, but the 528/540/4624 event does not seem to identify where the logon came from (i.e. the Name or IP address of the source computer, where the 552 eventid is logged), thus it's hard to correlate.&lt;/P&gt;&lt;P&gt;Has anyone else been looking these?  it may show when explicit credentials are used but correlating appears difficult.  &lt;/P&gt;&lt;P&gt;...But if target server is localhost, it looks like this event is redundant to 528.</description><pubDate>Thu, 15 Apr 2010 19:41:57 GMT</pubDate><dc:creator>Braino</dc:creator></item></channel></rss>
