Answer the question
In order to leave comments, you need to log in
Server without video system, how to make RDP work?
Good day dear community.
Given:
- self-assembly computer based on Gigabyte Z390 UD motherboard (without video) and i3 9400F processor (also without video core)
- Windows Server 2012 r2 x64
Problem:
- RDP is not connected. That is, when you try to connect to the server via RDP, you get a standard error: it is impossible to connect to a remote computer, contact the owner of the remote computer ... Moreover, the computer boots normally, is accessible via the local network, automated routine tasks are performed without problems. It's just not possible to connect via RDP.
Reasoning:
- I suspect that when connecting via RAdmin - there will be no problems, but I'm not sure.
- the problem is precisely in the absence of a video system in the computer's configuration, because it is worth connecting a video camera - everything works right away.
- I understand that the easiest way is to connect any video and score on the problem, but I would like to look for another solution.
Please help the community.
Thank you all in advance :-)
Answer the question
In order to leave comments, you need to log in
I would like to find another solutionBring this system to a virtual machine. You will connect to the virtual machine via RDP without problems. You can also manage a virtual machine without an RDP connection to the host. Moreover, the hypervisor may not be a screw one at all.
Does the server have the application server role selected? Are there any licenses?
mstsc should give an error code along with the text, if not on the screen, then in the invet log of the broken machine, the code will tell more information
It is very strange. It seems that RDP has almost nothing to do with the video system. The most definitely has a server without a video core, RDP works great.
Good day to all.
Problem found: in Windows Server 2012 r2, when installed on platforms with modern desktop processors, an error occurs with the Large Send Offload (LSO) function of modern Ethernet adapters, which is enabled by default.
On the off-site of the small-software, several options for editing the registry are proposed to solve this problem.
However, the solution does not always work.
For me it didn't work.
I had to reinstall the server. Luckily there wasn't much info on it.
Windows Server 2016 does not have this issue.
In Windows Server 2012 r2 installed on server platforms, there is no such problem either.
The video system is not affected at all.
Thank you all for your help
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question