Network binding after license change

[CamiloHPS]

Hello!

I have installed Starwind VSAN Free on two Windows Servers 2022. The 2nd server only binds to the lookback adapter 127.0.0.1. I only noticed this when no synchronization was possible after using "CreateHASmbWitness.ps1". Everything else worked.

The reason for this could be that I had previously tried the configuration in a test environment. Everything worked here without any problems. I then installed the physical servers with the same license. I thought that deleting the test environment would release the licenses again.

When I read that my problem could be the license, I requested and received a new license for Starwind VSAN Free. I installed the new license on the 2nd server. Unfortunately, the problem that the 2nd server only binds to the 127.0.0.1 lookback adapter has not changed.

What can I do to ensure that the 2nd server finds all network cards under “Network”?

Best regards
Camilo

[yaroslav (staff)]

You need to reinstall the OS to change from TRIAL to FREE.
Please see if you have iSCSI Target Server installed in your Windows server. Uninstall it if you have the role installed.

[CamiloHPS]

I may not have expressed it correctly, I did not use a TRIAL version. I suspect that I activated a 4th FREE license by mistake. I don't know whether this means that I only get a binding to the loopback adapter. Can anyone confirm or deny this?

I have now received a new FREE license (i.e. exchanged a FREE license by a new FREE license). This new license is also displayed correctly in the console. Unfortunately, this does not change the problem with the binding to the network interfaces.

I would like to avoid reinstalling the OS.

[yaroslav (staff)]

Seeing the screenshot of how the issue manifests itself could help.
Is the system running Windows Server?
If so, please make sure to have networking configured using Static IPs and iSCSI target server role is not installed.

[CamiloHPS]

I am very grateful. Removing the iSCSI target server role has helped. I had also uninstalled StarWind and reinstalled it without iSCSI target server role. Now all interfaces appear under Network.

I would never have thought that the iSCSI target server role caused the problem. On the 1st server the role is installed without causing any problems.

About the setup: Two servers with Windows Server 2022 and static IPs.

[yaroslav (staff)]

Thanks for your update.
iSCSI target server is operating over the same ports as StarWind VSAN, causing some sort of clashing from the OS perspective. The solution can be using custom ports.