Unable to use RDP client on a modified 2019 LTSC

It appears to actually be a setting (or something missing) on the target rather than the client. I performed the following snuff tests:

NTLite mod client - > NTLite mod target = FAIL (An internal error has occurred.)
Standard client - > NTLite mod target = FAIL (An internal error has occurred.)
NTLite mod client - > Standard target = PASS (Prompted by MSTSC to enter user/pass.)

What I believe to be the target's settings have been attached. I'm already starting to feel like this is a PEBKAC error... :p
 

Attachments

  • Auto-saved session {77546CE8-4C74-4C11-91A1-45C98464CE8F}.xml
    49 KB
Sorry for the delay, had a busy weekend.


Code: 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
"DisabledComponents"=dword:ffffffff
 
Too many articles keep repeating the wrong size of the bitmask.

Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
Name: DisabledComponents
Type: REG_DWORD
Min Value: 0x00
Max Value: 0xFF (IPv6 disabled)

For your unmodified install, do you apply the same registry changes? Windows rarely issues a TCP RST outside of firewall behavior, that's almost always done by network devices. OS'es tend to time out failed connections.
 
Usually, yes. I have some legacy equipment that doesn't quite understand IPv6 so I have to disable it network wide. I can try the same regedit in the unmodified VM to see if that produces an unusual result.
 
shotgunhero said:
I just tried setting it in the test VM to the wrong value for a smoke test, and I was still able to connect.
Click to expand...

You didn't mention VM before. Which one are you hosting? Also you're disabling dead gateway detection, that's only done in a multi-homed environment. Is there more than one interface?
 
Last edited:
The target is an actual physical host; I just spun up a VM that was untouched just to see if it was something in configuration. The physical host DOES have more than one interface, but only one is in use.
 
shotgunhero, thanks for the extra info, missed the continuation of the topic myself.
Tried your latest preset (live-applied) and RDP keeps on working, latest patched LTSC and NTLite.
Do you have a preset tested with the latest NTLite that produces the RDP Server-side issue, while it passes on the full Windows ISO from the same client?

Thanks.
 
Yeah, I have another, but I'm not sure if they're the same one. I never tried it in live, that never occurred to me, so that leads me to believe I have either removed something or pushed in a configuration that totally breaks it. This one might be missing its RDP server though, I'll have to search through my presets for another.
 

Attachments

  • Auto-saved session {77546CE8-4C74-4C11-91A1-45C98464CE8F}.xml
    68.5 KB
You must log in or register to reply here.
Back
Top