Hello
I am using the Win10-internal remote desktop function very often.
Unfortunately I do not get a connection as soon as eBlocker is turned on. After switching eBlocker locally (on remote desktop) off the connection can be established after a reboot of the remote desktop.
Is there a way to allow this connection within the LAN even if eBlocker is running?
Best regards
Stefan
Hi @StefanF1,
it seems like, you are not able to connect to your rdp, because the name resolution of the target device is not working.
Can you please check this in a dos promt, when eblocker is turned on for the device?
Dosbox
nslookup targetname
and then turn of eblocker and check again.
Please post the output of both tests.
Kind regards
Sven
Hello Stefan
So just to be sure I understand this correctly: You're trying to start a RDP connection from one Windows 10 computer to another Windows 10 computer where both computers are within your local LAN and this is not working?
And if you switch off eBlocker for the remote Windows 10 computer, it's working again?
Which version of eBlocker to you use? Do you have the HTTPS integration turned on?
Best regards,
Martin
Hello
I am using on raspberry Pi 3B+. https in switched on and integrated in Mozilla Firefox which is working fine.
I have not found a possibility to install any certificate for the remote-desktop app. And the question is how to exclude this connection via port 3389 (?) from the check-functions / routing through eBlocker.
@Sven:
With eBlocker switched on AND eBlocker on destination-PC (server) switched off - absolutely the same result in both cases:
C:\Users\stefa>nslookup 192.168.1.200
Server: fritz.box
Address: fd00::2e91:xyz
Name: Stefan-PC.fritz.box
Address: 192.168.1.200
Best regards
Stefan
certificate in the trusted root certification authority
@calimero is right: You need to add the cert to your browser and install it on the operation system (windows I guess) as well. You will easily fail if the cert is installed by just double-clicking it. Please use the wizard for this - and follow exactly.
Anyway you should mark Microsoft as trusted app (Settings>HTTPS>Trusted Apps -> here select Microsoft services) - which I guess might be enough already in this case.