StarWind Software

Just downloaded and installed the free version for testing. I have a seperate VLAN for iSCSI traffic and I am trying to change or add to the SErver Settings/Network section. I see the local loopback IP address is enabled. I click Add and select the IP for my iSCSI connection. I have the correct ports and the Enable Network Interface is selected. I hit ok and the screen returns to the Network window without my newly added network. I check the log fils and keep seeing this when I try adding:


9/19 18:06:51.816 1970 error: assertion failed: c:\_starwind\_v5\starwind\service\common\fn_common.cpp:28 (isEmpty())
9/19 18:06:51.816 1970 Srv: bind() to 192.168.10.12:3260 failed: An attempt was made to access a socket in a way forbidden by its access permissions. (code: 10013).
9/19 18:06:51.816 1970 error: assertion failed: c:\_starwind\_v5\starwind\service\common\fn_common.cpp:28 (isEmpty())
9/19 18:06:51.816 1970 Srv: Waiting for iSCSI connections at 127.0.0.1:3260 ...
9/19 18:07:11.160 16cc conf: Variable 'listen' is set to '*,'.


I have this installed on
Windows Server 2008 R2 Datacenter with SP1.
36 GB Ram
64 Bit OS
Single Intel Xeon CPU E5506 @ 2.13 GHz

I fixed it by uninstalling rebooting and reinstalling again.

Looks like a firewall issue to me.

I think it was also related to the fact that I had the Microsoft iSCSI Target software installed. So a uninstall of both programs and a reboot fixed it.

Port conflict. By default both apps try to bind to port 3260. There's a way to make StarWind use other TCP port so both targets should in theory co-exist on the same machine but getting rid of MS target is a better idea

krisjturn wrote:I think it was also related to the fact that I had the Microsoft iSCSI Target software installed. So a uninstall of both programs and a reboot fixed it.

Hi,

sorry for replying this old Thread, but where can I find how to change the default port of Starwind? I have MS iSCSI-Target running and want to test the performance with a parallel Installation of Starwind. Thanks a lot for your help!

We don`t recommend to run tests when both targets are installed. We recommend to disable MS iSCSI target service and best option is to uninstall it.
The reason for it is that you can face with performance issues during testing.