Windows 10: Why does 24h2/2025 host give only RDP over TCP?

After upgrading to 24h2, the ability to connect to RDP via UDP disappeared everywhere. However, on previous versions everything is fine, configuring policies and substituting mstsc.exe etc. does not solve the problem. This problem itself was still in insider versions and how could it go in production? This creates some performance issues and network overhead. Of course I really appreciate that 24h2 was rewritten to sse4.2 and it gives a noticeable speed increase everywhere, but however rdp only via tcp messes everything up... The problem still exists to this day and on the latest version 2610

:)

 

"dial tcp: lookup <website name>: getaddrinfow: No such host is known" problem

When trying to open any website in the browser(edge, chrome as well as Firefox), I am getting the error "dial tcp: lookup <website name>: getaddrinfow: No such host is known" . I am using windows 10
and windows firewall is also enabled. Please suggest on the steps to resolve it

 

RDP

I guess I am showing my age.

In times past I was able to use RDP to remotely connect from my pc to a remote host pc - provided that remote pc was RDP enabled and the fire-wall was opened for the RDP port.

These days it seems much more complex.

Is there a step-by-step instruction sheet to follow? Or, better, is there an app/utility which configures the host more-or-less automatically?

 

Dial tcp error

When trying to open any website in the browser(edge, chrome as well as Firefox), I am getting the error "dial tcp: lookup <website name>: getaddrinfow: No such host is known. I am using windows 10 and windows firewall is also enabled. Please suggest on
the steps to resolve it