<div>
Here is the article to configure iscsi verify if all the steps are covered : <a href="https://www.experts-exchange.com/articles/11404/HOWTO-iSCSI-with-Multi-Path-in-a-Windows-Server-Environment.html" rel="ugc">https://www.experts-exchange.com/articles/11404/HOWTO-iSCSI-with-Multi-Path-in-a-Windows-Server-Environment.html</a>
</div>


Here is the article to configure iscsi verify if all the steps are covered : https://www.experts-exchange.com/articles/11404/HOWTO-iSCSI-with-Multi-Path-in-a-Windows-Server-Environment.html [https://www.experts-exchange.com/articles/11404/HOWTO-iSCSI-with-Multi-Path-in-a-Windows-Server-Environment.html]

<div>
Hi Ginesh,<br />
<br />
Give me something to go through...
</div>


Hi Ginesh,

Give me something to go through...

<div>
Thanks expert - Ganesh on providing article on how the iSCSI work in depth. I really appreciated and the iSCSI establishment always broke issue eventually solved.
</div>


Thanks expert - Ganesh on providing article on how the iSCSI work in depth. I really appreciated and the iSCSI establishment always broke issue eventually solved.

<div>
<div class="content wysiwyg-content">
This is using MS Windows 2008 r2 server. The iSCSI Initiator has been configured to map to a iSCSI target from Synology NAS. There are altogether 3 iSCSI targets available from the NAS, and each of these target connected to one server. For example, serverA connect to iSCSI A, and so on. However, the rest of the 2 servers do not have any iSCSI dropping issue, but this server. The situation is, this iSCSI establishment always found &quot;missing&quot; once per week. But, after manually configured with CHAP secret, the iSCSI will connect in no time, why?<br />
<br />
I am thinking to create a daily routine job to disconnect and re-connect this iSCSC target, will it be a good idea?<br />
<br />
Thanks in advance.
</div>
</div>


This is using MS Windows 2008 r2 server. The iSCSI Initiator has been configured to map to a iSCSI target from Synology NAS. There are altogether 3 iSCSI targets available from the NAS, and each of these target connected to one server. For example, serverA connect to iSCSI A, and so on. However, the rest of the 2 servers do not have any iSCSI dropping issue, but this server. The situation is, this iSCSI establishment always found "missing" once per week. But, after manually configured with CHAP secret, the iSCSI will connect in no time, why?

I am thinking to create a daily routine job to disconnect and re-connect this iSCSC target, will it be a good idea?

Thanks in advance.

iSCSi establishment always dropped, why?

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.