Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1 Source: iScsiPrt

Initiator failed to connect to the target. Target IP address, port number and error status are given in dump data.


0000: 00 00 0c 00 01 00 66 00 ....f.
0008: 00 00 00 00 01 00 00 c0 .... <.status code c0000001
0010: 01 00 00 00 00 00 00 00 .... (STATUS_UNSUCCESSFUL)
0018: 00 00 00 00 00 00 00 00 ....
0020: 00 00 00 00 00 00 00 00 ....
0028: 9d 3b 7a 91 bc 0c 00 00 ;z.. <<< 9d 3b 7a 91 is IP Address
0030: b5 00 00 c0 .. <<< Port number is 00cbc (3260)
<<< b5 00 00 c0 is the status returned by TCP for connect request. Here it is
See EV100486 (iSCSI Disconnects with BXOIS Errors with Event ID 1 and Event ID 10) on how to troubleshoot this problem.
ME976072 provides a list of several reasons for which this event may be recorded (along with suggested fixes).
As per Intel: "This message can be generated when the Microsoft iSCSI Software Initiator is on a different network than the iSCSI adapter and the Send Target command was setup to use Microsoft's default mechanism, which is to try every portal until a successful Send Target occurs and then stop when results are received. This is the setting that PROSet for IP Storage uses and is an option on the Microsoft iSCSI Initiator. The message is a warning rather than an error, especially if the targets are displayed. If they are not, delete the old Send Target and create a new one with corrected settings".

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.