Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Server 2008 R2 iscsi initiator fails to connect to the target after the target reboots

Answered Server 2008 R2 iscsi initiator fails to connect to the target after the target reboots

  • Friday, January 25, 2013 8:58 PM
     
     
    Sign In to Vote
    0

    I have several Windows server 2008 R2 systems connected to an iscsi target running ubuntu 10.04. Also have an SBS 2011 connected to the same target. If I reboot the target (the ubuntu system), the Server 2008 R2 iscsi initiators immediately display a status of "inactive" and never reconnects itself, I must do it manually. At the same time, the SBS 2011 system's iscsi initiator shows a status of "reconnecting" and then reconnects by itself when the ubuntu iscsi target comes back up.

    Can anyone help me with this? Why does SBS 2011 work as expected and 2008 R2 fails to reconnect? It almost seems like the timeout on server 2008 R2 is way too short. But I checked the registry and it is fine.

    It is the exact same problem as this unanswered thread:

    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/3c338d51-6812-439e-9d3b-6279007edd50

    I've tried the basic disk vs dynamic disk thing and that didn't make a difference.

    Any assistance would be greatly appreciated.

     

All Replies

  • Saturday, January 26, 2013 10:55 AM
     
     
    Sign In to Vote
    0
    Does is stuck on "connecting..."? Does it throw any errors? Anything inside system event log related to failed automatic reconnect?

    StarWind iSCSI SAN & NAS

     
  • Monday, January 28, 2013 10:22 PM
     
     
    Sign In to Vote
    0

    The status goes to "inactive" right away. The system log in event viewer shows two errors:

    First error:
    Connection to the target was lost. The initiator will attempt to retry the connection.

    Second error:
    Login request failed. The login response packet is given in the dump data.

    Both of these error happen at exactly the same time stamp in the log.

    My iscsi connection does not require a login user name or password. And will connect without a problem when I do it manually.

     
  • Wednesday, January 30, 2013 8:00 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    Have a try to reinstall the NIC driver. If there is any newer driver, update it to see the result.

    If issue still exists, have a try to recreate the iSCSI connection:

    - On the server disconnect the iSCSI-Connection and delete all Items in the “Favorite Targests” – Tab and the “Volumes and Devices” Tab and the “Discovery” Tab
    - On the iSCSI-Storage delete the old Target-Object, create a new Target-Object from scratch, add the Initiator to the new target Object and configure chap
    - Discover the Target again and Login to the target with chap again This procedure deletes all caching information on the Initiator and the iSCSI-Target(Storage)

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.