jameran
Contributor
Contributor

VDM cannot connect to guest with multiple virtual NIC's

Jump to solution

Hello,

I'm deploying VDI / VDM in a testing environment; some of the XP guests have multiple NIC's that are connected to VLAN-tagged port groups.

Problem is... of the 4 NIC's in the guest, only 1 can actually get out of its subnet and over to the VDM server. After adding these new NIC's, they obtain windows' 169.x.x.x random addresses, since these interfaces don't have dhcp server access and will be changed very often for labs.

What I surmise is happening is that the VDM agent is providing these addresses to VDM, and VDM is attempting to get an RDP connection off of them. This will always fail.

The exact error is:

Problem starting channel 0 for Port3: Failed to allocate onbound connection to 169.254.142.159:3389 - java.net.Sock

Does anyone know how to force the VDM agent (or whatever is causing this to happen) to use the first virtual NIC in Windows??

Thanks!!

0 Kudos
1 Solution

Accepted Solutions
pcomo
Enthusiast
Enthusiast

Hi,

you can add a REG_SZ "subnet" registry key to HKLM/Software/Vmawre.inc/VMware VDM/Node Manager/

edit the key and add subnet info:

n.n.n.n/m with n.n.n.n TCP/IP subnet and m the number of bit in the subnet.

ex:

Virtual desktop IP VDM: 192.168.1.4 subnet 255.255.255.0

n.n.n.n: 192.168.1.0

m: 24

subnet= 192.168.1.0/24

I hope that i can help you.

View solution in original post

0 Kudos
2 Replies
pcomo
Enthusiast
Enthusiast

Hi,

you can add a REG_SZ "subnet" registry key to HKLM/Software/Vmawre.inc/VMware VDM/Node Manager/

edit the key and add subnet info:

n.n.n.n/m with n.n.n.n TCP/IP subnet and m the number of bit in the subnet.

ex:

Virtual desktop IP VDM: 192.168.1.4 subnet 255.255.255.0

n.n.n.n: 192.168.1.0

m: 24

subnet= 192.168.1.0/24

I hope that i can help you.

0 Kudos
jameran
Contributor
Contributor

Thank you VERY much! That works perfectly.

0 Kudos