Remote desktop connects, black screen, disconnects after a few seconds

Question

I have several servers running Windows Server 2012 R2. These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server.
Yesterday I noticed one of the servers was having an issue with its remote desktop connection. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. No error message is given. I tried
this from a couple different Windows 7 machines, and got the same result. I tried from my wife's iMac, which runs Jump Desktop, and too was met with the same result.
I can, however, remote into this machine via RDP from my work-issued laptop, which is running Windows 8. However, I cannot remote into the problem machine via Remote Desktop Connection from one of the 2012 R2 servers--I am met with the same result as the
other machines: connect, black screen for 2-3 seconds, disconnect without error.
I can remote into all of the other 2012 R2 servers without issue from any machine, including the iMac. I am experiencing this problem on one server only.
Since it is a test server, I reinstalled Windows from scratch this morning. This meant formatting the SSD and wiping everything out. I reinstalled the drivers, joined the server back to the domain and installed all of the updates available from Windows Update.
And rebooted. And yet, the problem persists!
I tried troubleshooting the "usual suspects," like turning off Windows Firewall, disabling antivirus software (currently none installed), disabling IPv6, setting a static IP instead of using DHCP, etc. I did notice the network adapter said it was
on a Network, not a Domain Network. I corrected DNS settings, and the network reidentified itself as being on the ParietalBone.net network. And yet, the problem persists. Remote Desktop to this server still yields a black screen for 2-3 seconds, followed by
a disconnect--EXCEPT from the aforementioned Windows 8 machine.
I looked in the TerminalServices-LocalSessionManager log on the offending server, and there are no errors. I only see repeated entries that say "Session X has been disconnected, reason code 12," where X is 1 or 2. On a couple occasions, the reason
code is 11. But I don't see any errors indicating a breakdown in security negotiation.
Without any robust logs or debug details, I'm at a loss of where to look for a solution.

Answer 1

I am cautiously optimistic that this may have been resolved.
The network card in the computer was only a 10/100 built-in card, so I replaced it with a 1Gbps card. Interestingly, this did NOT resolve the issue. I ran netsh to check on the state of the chimney offload, but it was already disabled.
In the network card properties, I changed the link speed and duplex from automatic to 1Gbps full, re-ran "netsh int tcp set global chimney=disabled" and rebooted. The problem persisted.
And so I went to the network card properties and set IPv4 Checksum Offload, Large Send Offload (three of these -- IPv4, v2 IPv4 and v2IPv6) and TCP Checksum Offload (IPv4 and IPv6) to Disabled. Jumbo Frames were also disabled. I rebooted again.
After the subsequent reboot, I was able to connect to this Server from machines that previously gave me difficulty. The only machine I haven't been able to test today (I'm in the office) is my wife's iMac, which is at home. However, I was able to bring this
server up via Jump Desktop on my iPad, so I'm suspecting that perhaps one of the offload options was to blame. I'm not sure why this would allow me to connect from some machines but not others. And as noted above, I have many other machines running Server
2012 R2 and they are NOT experiencing this problem. And I've not done any tinkering with network settings on any of them, so their chimney and offload settings are all in the default configuration.
Regarding the other items -- NIC team, virtual machine, etc. -- there was no NIC team, no SRIOV and no RDMA involved.
I had to turn IPv6 off on this machine, and only on this machine, because having it enabled was causing a lot more problems. DNS registration would keep failing, it couldn't pull Group Policy, it couldn't get time sync with the DC, etc. The servers are all
set up with static IPv4 addresses. The router supports IPv6 but I'm not actually using it, so disabling IPv6 wasn't a concern to me.