Score:0

Windows Server 2019 - create rdp-listener on second NIC

tm flag

Windows Server 2019 in workgroup mode.

Unable to create rdp-listener on second NIC.

Tried creating a new connection via tsconfig.msc from Windows Server 2012/2008R2. I also tried creating a new connection through the registry by creating a new key similar to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp"

Further, through tsconfig.msc, as well as through PowerShell scripts, I tried to change the binding to network cards.

(Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TSNetworkAdapterSetting -Filter "TerminalName='RDP-Tcp'").SetNetworkAdapterLanaID(2)
(Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TSNetworkAdapterSetting -Filter "TerminalName='RDP-Tcp-2'").SetNetworkAdapterLanaID(1)

Or

(Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TSNetworkAdapterSetting -Filter "TerminalName='RDP-Tcp'").SelectNetworkAdapterIP("192.168.1.10")
(Get-WmiObject -Namespace root\cimv2\TerminalServices -Class Win32_TSNetworkAdapterSetting -Filter "TerminalName='RDP-Tcp-2'").SelectNetworkAdapterIP("192.168.2.10")

But all this does not help. Still, the Terminal Services process is only listening for incoming connections on one NIC at address 0.0.0.0.

Please tell me how to solve the problem?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.