10

This vulnerability is described in the Microsoft article A case study in industry collaboration: Poisoned RDP vulnerability disclosure and response. This study was done in collboration with Check Point researcher Eyal Itkin. In this article is described an attack by an infected server against a client connecting via RDP. The attack consists of the server ...


5

These type of scammers look for non-tech-savy people. Software like Teamviewer detects "likely" scammer activities and warns people about scams if you get connected, for example, to an IP geofenced from say India and you are not in it: ... We have taken the necessary steps to make sure that the remote IDs can no longer be used for illegal purposes ...


2

If both are using Ubuntu, you're in luck—you don't have to install any additional software—all of the remote capabilities are built in, you just need to change some settings. Set Static IP Addresses (Recommended) Before you do anything, go into your router settings and setting a dedicated IP address for each device, that way you don't have to do an IP lookup ...


2

You can use mod_rewrite to redirect to where you want - integrate this in the SSL vhost: RewriteEngine on RewriteCond %{REQUEST_URI} ^/$ RewriteRule .* /RDWeb/ [R,L] Don't forget to enable mod_rewrite (use a2enmod if at all possible).


2

Remote desktop works, also on a auto-login system, so that would work. But it is probably the wrong solution to your problem. The Windows Task Scheduler has the option to define a task that runs X minutes after startup of the computer. First try to setup the exe-file to be run through that. Don't start it immediately after startup as chances are the computer ...


1

Jim Browning had a series of videos that explained how he does his "WhiteHat" hacking. His videos are out there still. They were very technical & extremely detailed, but not so simplified that anyone could follow along. Without a fair knowledge of coding & tech slang they were confusing. Best to leave that kind of thing to those that ...


1

Relaxing the requirements for Network Level Authentication as described in https://windowsreport.com/local-security-authority-cannot-be-contacted/ worked! I'm not sure why my two RDP clients behaved differently, but suspect it might be because the laptop is a work laptop, and might have been configured for access on that network.


1

It's possible Windows is caching some credentials at some level you're not aware of (TERMSRV for example), and the cache has become corrupted. You can see which credentials are cached using Credential Manager (Control Panel\User Accounts\Credential Manager). Here you can examine each of the cached credentials in detail, and edit or delete them as required. ...


1

You can connect to an existing login over Remote Desktop, but it locks the session out for any local user. It doesn't terminate any running tasks to do this, it's merely an interaction lockout as far as anyone sitting at that machine would see; a 'curtain' in effect. If you lose the connection for any reason, the remote session should just start up again ...


1

The behavior you are seeing is by design as Windows snaps scale factors to specific boundaries. This change was made at the end of 2018 to address underlying architectural issues. Scale factors in the latest Windows releases will snap to: 125% 150% 175% 200% 225% 250% 300% 350% 400% 450% 500%


1

I tried all of the above suggestions but none of them worked for me. I just wanted to restart the remote machine to see whether it will fix the issue. It indeed worked. I did the following to restart the remote machine via command line (with admin privilege) as I could not find a way to restart the remote machine via RDP. Step 1: Login to the remote machine ...


Only top voted, non community-wiki answers of a minimum length are eligible