VCB can't even connect to VC

[H_a_r_m_o_n_t]

I have two ESX 3.5 servers which are managed by VC 2.5. Recently I installed VCB into one of virtual machines and now trying to configure it in iSCSI SAN mode. Microsoft iSCSI initiator works well and I can see LUNs. But when I try to execute

vcbMounter -L 6 -h vcIP:443 -u User -p Password -a Name:vmIP -r E:\mnt\ -t fullvm -M 1 -F 1

I get

08-10-15 15:32:57.239 'vcbMounter' 5064 trivia] Initializing SSL context

08-10-15 15:32:57.239 'BaseLibs' 5064 info] Using system libcrypto, version 90703F

08-10-15 15:32:57.771 'App' 5064 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

08-10-15 15:32:57.771 'vcbMounter' 5064 info] Connecting to host vcIP on port 443

08-10-15 15:34:57.790 'vcbMounter' 5064 error] Error: Other error encountered: Connection terminated by server

In network sniffer I see that VCB establishes connection with VC (SYN - SYN,ACK - SYN) but no other packets appear.

Also I should say that without :443 VCB tries to establish connection via port 902 inspite of the fact that I downloaded the last VCB version.

Please help.

[H_a_r_m_o_n_t]

Also I have ability to connect from VCB host to VC via VI Client without any problems (it uses the same 443 port). vcbVmName shows same output as vcbMounter. It stucks while initializing SSL.

I tried to compare connection initialization of VI Client with VCB utilities and have found that after (SYN - SYN,ACK - SYN) next packet (SSL Hello) should be posted from VCB host. So I think that problem is in VCB virtual machine or VCB framework itself. But actually I don't know where.

Could anybody help? I can provide network sniffer logs if it is neccessary.

[ranga1978]

.

[H_a_r_m_o_n_t]

I have resolved this issue. The problem was in old VCB version.