Description of problem:
Open-iscsi Initiator is unable to discover target .

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
1.  Run command : 
iscsiadm -m discovery -t sendtargets -p 192.168.100.41 -d 8

2. Using a Hardware iSCSI Target from Pillar. 
   The ip address 192.168.100.41 is location of iscsi portal.



Actual results: Initiator Error , discovery fails.


iscsiadm -m discovery -t sendtargets -p 192.168.100.41 -d 8
iscsiadm: Max file limits 1024 1024

iscsiadm: updating defaults from '/etc/iscsi/iscsid.conf'
iscsiadm: updated 'discovery.sendtargets.iscsi.MaxRecvDataSegmentLength', '32768' => '32768'
iscsiadm: updated 'node.session.timeo.replacement_timeout', '120' => '120'
iscsiadm: updated 'node.conn[0].timeo.login_timeout', '30' => '15'
iscsiadm: updated 'node.conn[0].timeo.logout_timeout', '15' => '15'
iscsiadm: updated 'node.conn[0].timeo.noop_out_interval', '5' => '5'
iscsiadm: updated 'node.conn[0].timeo.noop_out_timeout', '5' => '5'
iscsiadm: updated 'node.session.err_timeo.abort_timeout', '15' => '15'
iscsiadm: updated 'node.session.err_timeo.lu_reset_timeout', '30' => '20'
iscsiadm: updated 'node.session.initial_login_retry_max', '4' => '64'
iscsiadm: updated 'node.session.cmds_max', '128' => '128'
iscsiadm: updated 'node.session.queue_depth', '32' => '32'
iscsiadm: updated 'node.session.iscsi.InitialR2T', 'No' => 'Yes'
iscsiadm: updated 'node.session.iscsi.ImmediateData', 'Yes' => 'No'
iscsiadm: updated 'node.session.iscsi.FirstBurstLength', '262144' => '262144'
iscsiadm: updated 'node.session.iscsi.MaxBurstLength', '16776192' => '16776192'
iscsiadm: updated 'node.conn[0].iscsi.MaxRecvDataSegmentLength', '262144' => '262144'
iscsiadm: updated 'node.session.iscsi.FastAbort', 'Yes' => 'No'
iscsiadm: starting sendtargets discovery, address 192.168.100.41:3260,
iscsiadm: sendtargets discovery to 192.168.100.41:3260 using isid 0x00023d000000
iscsiadm: discovery timeouts: login 15, reopen_cnt 5, auth 45.
iscsiadm: connecting to 192.168.100.41:3260
iscsiadm: connected local port 60645 to 192.168.100.41:3260
iscsiadm: connected to discovery address 192.168.100.41
iscsiadm: discovery session to 192.168.100.41:3260 starting iSCSI login on fd 3
iscsiadm: sending login PDU with current stage 1, next stage 3, transit 0x80, isid 0x00023d000000 exp_statsn 0
iscsiadm: >    InitiatorName=iqn.1994-05.com.redhat:30e0876d54a3
iscsiadm: >    InitiatorAlias=ca-ftsuperm-14
iscsiadm: >    SessionType=Discovery
iscsiadm: >    HeaderDigest=None
iscsiadm: >    DataDigest=None
iscsiadm: >    DefaultTime2Wait=0
iscsiadm: >    DefaultTime2Retain=0
iscsiadm: >    IFMarker=No
iscsiadm: >    OFMarker=No
iscsiadm: >    ErrorRecoveryLevel=0
iscsiadm: >    MaxRecvDataSegmentLength=32768
iscsiadm: wrote 48 bytes of PDU header
iscsiadm: wrote 252 bytes of PDU data
iscsiadm: read 48 bytes of PDU header
iscsiadm: read 48 PDU header bytes, opcode 0x23, dlength 0, data 0x1c8a0670, max 32768
iscsiadm: login response status 0202
iscsiadm: discovery login to 192.168.100.41 rejected: initiator error (02/02), non-retryable, giving up
iscsiadm: disconnecting conn 0x1c89c040, fd 3
[root@ca-ftsuperm-14 redhat]# uname -a
Linux ca-ftsuperm-14 2.6.18-164.el5xen #1 SMP Tue Aug 18 15:59:52 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux


Expected results:
Discovery succeeds.

Additional info:

The open-iscsi initiator works on an AMD and Intel x86_64 
server but fails on an super micro server.

THE iscsi target is connected to a windows host and is usable.

Is there a configuration change that may be needed ?