Recent content by shotgunhero

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...

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.

I just tried setting it in the test VM to the wrong value for a smoke test, and I was still able to connect.

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.

Sorry for the delay, had a busy weekend. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters] "DisabledComponents"=dword:ffffffff

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.)...

Sure thing. I'll give it a try and see what I come up with.

A clean host is now doing it too. So, I think it's safe to say it's a configuration issue on the OS rather than the removal. So, I shall sort through it.

I kept RemoteFX in my installation. I kept both Remote Desktop Server and Remote Desktop ActiveX Client, as a matter of fact, I just checked.

Sorry if this is the wrong forum! o_O Yeah. Fortunately the computer I'm working with is a CF-19 so I can change out the hard drive quickly. I had an idea about seeing if I could find a few DLLs that I know RDP needs to work.

nuhi Sorry to ding you, but are there any components that can be removed that may affect the functionality of Remote Desktop? Other than the ActiveX Client of course. It appears from a WireShark dump the client is connecting, but then the connection just evaporates, which leads me to believe...

I don't think it did either, but whenever I use a standard installation it works without issue. Hmm.

Yep. Technically it's the same VLAN, as they're both on an old Cisco 3750G. Both results fail. Interestingly, other RDP clients like RoyalTS or Terminals also do not work.

Roger that, it's entirely possible I missed something. Standby. Here's both dumps on both the client and the target. I'm starting to suck at this in my old age.

On the target or the client?