Open vinsenzzo opened 7 months ago
There should be no interaction between dotnet and RDP, especially if you're not actually running an aspnetcore server (it sounds like you've downloaded it, but not built anything yet). Is it possible something else was picked up during reboot - a Windows update or a new Group Policy?
Is there an existing issue for this?
Describe the bug
I've encountered an issue with accessing to my on-prem servers via RDP protocol after downloading the ASP.net core 6.0.9, hosting bundle from Microsoft and restart of the server.
Server details: Windows server 2022 Use RDP protocol to access this server from a jumphost Downloaded .net core 6.0.9 hosting bundle and restarted server Didn't have an existing .net core installed previously in the server, the server that is connecting consist of the .net core v6.0.5.
Do let me know if you need any more details to find out the root cause
Expected Behavior
Able to RDP into customer's environment and continue operations
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
.NET Core 6.0.9
Anything else?
No response