several questions about protocol, vaults and windows iscsi

Hi,

Which protocol Cleversafe used to transfer data from accessor to slicestors ?

A second question :

I installed two vaults with one accessor and each vault use the same 4 slicestors. I setted up the target iscsi and the initiator, so I have one folder for each vault. When I add data in a folder (in a vault), there is the same data in the second vault. Why?

The third question :

I want to installed a iscsi initiator on a windows host so I use Microsoft iscsi initiator, I see the vaults but I attempt to log on I have this error message : "Connection failed"

thanks a lot

Your questions are bolded for reference.

Which protocol Cleversafe used to transfer data from accessor to slicestors ?

The protocol was written specifically for the dsNet software, and it runs over standard TCP/IP.

Can you provide more information about your specific deployment?  Assuming you are using Linux OpenISCSI, can you provide the output of this command (as root):

iscsiadm -m session -P 3

Are there any firewalls or NAT involved? 

If you've already checked connectivity between initiator and accesser, are you currently logged onto those targets using the Linux initiator when you try to connect with the Windows initiator?  Multiple simultaneous initiator connections to the same vault are currently unsupported.

Thanks for answers.

My second question is resolved.

For my connection between windows initiator and linux target I still have the problem. I have a firewall cisco pix but i allowed port 3260 and I added a new entry for NAT. I see the targets from my windows os but I can't log on. No initiator are currently logged onto those targets when I try to connect with the Windows initiator.

It can be a problem with user, my linux target doesn't now the user who wants to connect from the windows os?

For my connection between windows initiator and linux target I
still have the problem. I have a firewall cisco pix but i allowed port
3260 and I added a new entry for NAT. I see the targets from my windows
os but I can't log on. No initiator are currently logged onto those
targets when I try to connect with the Windows initiator.

Your second questions shouldn't pose an issue.  We regularly connect Windows initiators to Linux targets without any sort of authentication required.

Do you have any firewall rules setup in iptables on your Linux host?

If iptables isn't the issue, could you attempt a connection with the Windows initiator and send me the accesser.log file?  It should be under the output directory (possibly buried within a subdirectory).  My e-mail is zmark@cleversafe.com.  If you could send a Wireshark packet capture of the attempted logon as well, that might be helpful (but the accesser.log is more important).