Open lasersPew opened 3 months ago
I get a (likely) similar issue when I try to connect via rdp to a podman created instance.
I'm on Bazzite (Fedora Silverblue).
https://github.com/dockur/windows/issues/616#issuecomment-2258929693
Try a different RDP client
Like Remmina (install with sudo apt install remmina
)
Try a different RDP client Like Remmina (install with
sudo apt install remmina
)
That in fact, did not help.
https://github.com/user-attachments/assets/0d3df9ab-0f96-4cee-9011-949e89918cf8
Try a different RDP client Like Remmina (install with
sudo apt install remmina
)
I'm on a silverblue based system (bazzite) so I don't have apt. But I did the ostree method for overlaying remmina and tried that as well as the flatpak of remmina, neither method worked on linux, though my Macbook and Android phone can connect to the windows container via rdp.
Ran into this issue as well using podman
, will see if docker does not have this issue, I've tried Remmina
, xfreerdp
(version 2 and 3), and also tried to run netexec rdp
.
I saw this :
RDP 127.0.0.1 3389 127.0.0.1 [*] Probably old, doesn't not support HYBRID or HYBRID_EX ({nla})
[!NOTE] Seems that Docker and RDP does work, something with podman network setup might be at the heart of this issue.
RDP 127.0.0.1 3389 WIN-RANDOMHOSTNAME [*] Windows 10 or Windows Server 2016 Build 22621 (name:REDACTED) (domain:REDACTED) (nla:True)
EDIT:
I could only find that inside the code of the tool, something about self.nla
is not properly set, hence why the failure : https://github.com/Pennyw0rth/NetExec/blob/e927f33f2b37fa626a0439886c1de3d6eaf6cdb7/nxc/protocols/rdp.py#L112
Docker does pass into the else
statement instead.
But I'm not sure if that's related to the root cause of the failure, the domain
is apparently missing, but I don't think that would hinder an RDP connection.
I'm also affected by this. Fedora 41 (podman version 5.2.2)
Try connecting to the vnc or rdp from a different machine on your meteor by using the machine ip an the router
some clue to run freerdp with podman
https://universal-blue.discourse.group/t/podman-and-freerdp-problem/2000/2
That seems to work @Moon1moon but only in the shell spawned from
podman unshare --rootless-netns
Then inside that shell, you can connect using xfreerdp
and it does work with podman.
I had to specify (under NixOS with a shell managed by Home-Manager, else it was failing to enter the new shell)
SHELL=/bin/sh podman unshare --rootless-netns
with the following error :
Error: fork/exec /run/current-system/sw/bin/zsh: no such file or directory
Operating system
Fedora Linux 40 (Workstation Edition)
Description
When connecting to docker container (through localhost:3389, localhost:8006) with RDP protocol using Remmina, Gnome Connections, and freerdp, it says
[12:11:26:983] [6325:000018ba] [ERROR][com.freerdp.core.transport] - [transport_read_layer]: BIO_read returned a system error 104: Connection reset by peer
Docker compose
Docker log
❯ Starting Windows for Docker v3.12... ❯ For support visit https://github.com/dockur/windows ❯ CPU: 11th Gen Intel Core TM i5 1135G7 | RAM: 13/16 GB | DISK: 74 GB (btrfs) | HOST: 6.9.11-200.fc40.x86_64...
❯ Detected that the version was changed, but ignoring this because Windows is already installed. ❯ Please start with an empty /storage folder, if you want to install a different version of Windows. ❯ Booting Windows using QEMU v8.2.4... 3h3h3hBdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,96D84048-43BD-4EDA-9D81-08A156209F4C,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,96D84048-43BD-4EDA-9D81-08A156209F4C,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi ❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
Screenshots (optional)
No response