RDP session from Windows to Ubuntu Studio connects then closes

Support and Help
,
1

I have windows 11 Pro, and installed KRD onto Ubuntu Studio 26.04. Ubuntu Studio uses KDE.

I was using RDP to connect to Ubuntu Studio, and it worked fine. Now when using windows RDP to linux, The screen comes up, and just closes on the linux side.

I have a program installed in windows called bitvise, and I use that to connect via SSH, and then click on RDP. That works for some reason. I have no idea what changes I made if any. Bitvise is a variation of Putty, that I like allot better.

Anyone have any ideas?

2

So… You RDP to a Windows box to then SSH to a Linux system? Why the middle system? Can you not just SSH directly to the target Linux system directly?

3

I have 2 computers. 1 is windows 11 Pro. Second one is Linux with Ubuntu Studio.

I installed KRDP onto the linux machine. I then use computer one, my Windows 11 Pro to RDP into My second machine, that has Ubuntu studio installed. The Default RDP software that comes with windows for some reason no longer works to maintain a connection to Linux. The session connects then closes.

I then tried bitvise. I connect via SSH from windows, to linux. Once the SSH session is connected, I then click on RDP inside of bitvise, and it works.

4

How does that work? IIUC, bitvise is just a “better” PuTTY, which is a terminal emulator, so how can you “click on RDP inside of bitvise”, when it shouldn’t even know what RDP is, let alone there being no clickable icons inside a terminal?

5

I connect via SSH first, then connect with RDP in bitvise. Bitvise has an icon on the side that says “New Remote Desktop”. Clicking on that icon, allows for RDP. The New Remote Desktop icon only appears after connecting via SSH.

6

Ahh, now it makes sense; thanks for clearing that up. As for why that works, I can only guess that it’s tunneling RDP through your SSH channel, which makes it appear like it’s coming from localhost on the Ubuntu box, so maybe you need to look into configuration settings; some services are setup to only listen on localhost by default, to prevent people from having open ports they might not even know are there, just because some package recommended XRDP or whatever.

sudo ss -lbtup

should show all listening ports and the associated program. If that shows that the rdp server is listening on localhost only, you need to change the configuration to listen on a public address.

Firewall rules might also play a part in this.

7 
Netid      State       Recv-Q      Send-Q           Local Address	Port                    Peer Address	Port     Process                                                     	
tcp        LISTEN      0           50                           *	ms-wbt-server                      *	*         users	(("krdpserver",pid=3471,fd=38))

I could not see it listed for UDP, though I do know I opened that port. I had to look up a how to, to allow access in.

I dual boot my linux box with my Windows 10. I booted into windows 10, and tried to RDP from my Windows 11 PC. Would that have messed up my RDP stuff in windows 11?

Microsoft is doing away with RDP sometime this year. And moving to the Windows App. I just read an article on it. So at least I have bitvise.

8 
When I do the command: krdpserver -u aaron -p test
I get the following output: org.kde.krdp: Unable to listen for connections on QHostAddress(QHostAddress::Any) 3389
9

That’s because the port is already bound to the krdpserver process, which the above ss -lbtup shows. Don’t mind that there’s no UDP port open; that’s just my catch-all command to see what network ports are listening.

I dual boot my linux box with my Windows 10. I booted into windows 10, and tried to RDP from my Windows 11 PC.

So these machines are on the local network, I take it? No NAT router that might need some ports forwared? What are the IP adresses of your Windows and Linux boxes? On Linux you can just run:

ip address
ip route

On Windows it should be something like ipconfig, IIRC. If it can’t be found in the IP config, there must be some authentication issue, I reckon; could be that newer Windows versions require some RDP “extension” which free implementations don’t implement.

Would that have messed up my RDP stuff in windows 11?

I doubt it.

Microsoft is doing away with RDP sometime this year. And moving to the Windows App. I just read an article on it. So at least I have bitvise.

You could checkout X2Go, which I have fond memories of.

10

What are you doing on the remote system? There may be a better solution or are you just using the SSH tunnel to super secure the RDP session?

11

The Linux computer is a ways away from, my main PC. So I do not want to walk over to it every time I need to do something. I am lazy. Bitvise automatically tunnels RDP through SSH. It happens automatically.

12

x2go does not support wayland. Yes, they are on a local network.

the windows machine has an ip address of 19.168.56.1 and the linux machine is 192.168.50.64 which i find odd. Everything gets the IP address automatically from the router.

13

So what? :winking_face_with_tongue: That’s actually the one use case X11 shines in, compared to Wayland. Can even use the rather cool NX protocol, which one-ups on X.

There must be some typo involved here. You should also just post the output of the commands I’ve suggested above to remove all ambiguity. The IP address says (almost) nothing without the accompanying netmask and default route. Usually 192.168.0.0/16 addresses are used in /24 nets, which either means there is some additional local router involved or there might a problem with the IP config, because 192.168.56.0/24 is a different net than 192.168.50.0/24.

14

I set up KRDP on the Linux system. I then RDP into my second computer, which has Ubuntu Studio installed, using my Windows 11 Pro. For some reason, the Windows default RDP program is no longer able to keep a connection to Linux. After connecting, the session ends.

I tried bitvise after that. I connect to Linux using SSH from Windows. I click RDP in Bitvise after the SSH session is established, and it functions.

1 Like
15

@kim533, welcome to the discussion and thanks for sharing your experience, which gave me the impetus to widen my search perimeter, and I’ve found this troubleshooting guide on the KDE Discourse; seems to fit the bill. I think the HW acceleration workarounds are secondary and possibly specific to certain GPU’s, but the credential handling could do the trick.

@robertsaron, IIRC, you had connected to the dual booting Ubuntu / Windows 10 box from the Win 11 machine, when the former was running Win 10. Maybe that saved the credentials for Win 10 and tries those when connecting to Ubuntu/KRDP, which I reckon has a different user/password combo, and somehow the rejection isn’t handled gracefully by the Win 11 RDP client. DHCP servers tend to reuse IP addresses for returning MAC addresses, so your dual boot system probably has the same IP address in both Windows and Ubuntu which in turn might confuse the Windows client. Long story short, maybe you need to reset or delete that connection; and maybe I was wrong in my initial dismissal of that possibility. :innocent:

16

OK… What are you doing on the remote system that needs the full desktop session?

17

I install software and play with it via remote session. The goal is to have this linux box be a media server, and productivity box. Contain all my video editing software and graphic art, todo lists etc….I can do all of that on windows, but I want to keep it all on linux.

I have the output of everything. I removed the computer name and mac addresses.

$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether  brd 
    altname enx
    inet 192.168.50.64/24 brd 192.168.50.255 scope global dynamic noprefixroute enp0s31f6
       valid_lft 85839sec preferred_lft 85839sec
    inet6  scope link noprefixroute 
       valid_lft forever preferred_lft forever

$ ip route
default via 192.168.50.1 dev enp0s31f6 proto dhcp src 192.168.50.64 metric 100 
192.168.50.0/24 dev enp0s31f6 proto kernel scope link src 192.168.50.64 metric 100 
$ 

$ sudo ss -lbtup
[sudo: authenticate] Password:           
Netid    State     Recv-Q    Send-Q        Local Address:Port                  Peer Address:Port    Process                                                                                      
udp      UNCONN    0         0                127.0.0.54:domain                     0.0.0.0:*        users:(("systemd-resolve",pid=790,fd=18))                                                          
udp      UNCONN    0         0             127.0.0.53%lo:domain                     0.0.0.0:*        users:(("systemd-resolve",pid=790,fd=16))                                                          
udp      UNCONN    0         0                 127.0.0.1:323                        0.0.0.0:*        users:(("chronyd",pid=2398,fd=4))                                                                  
udp      UNCONN    0         0                   0.0.0.0:37451                      0.0.0.0:*        users:(("kdeconnectd",pid=3643,fd=41))                                                             
udp      UNCONN    0         0                   0.0.0.0:mdns                       0.0.0.0:*        users:(("avahi-daemon",pid=2150,fd=12))                                                            
udp      UNCONN    0         0                     [::1]:323                           [::]:*        users:(("chronyd",pid=2398,fd=5))                                                                  
udp      UNCONN    0         0                         *:1716                             *:*        users:(("kdeconnectd",pid=3643,fd=36))                                                             
udp      UNCONN    0         0                         *:37748                            *:*        users:(("kdeconnectd",pid=3643,fd=42))                                                             
udp      UNCONN    0         0                      [::]:mdns                          [::]:*        users:(("avahi-daemon",pid=2150,fd=13))                                                            
udp      UNCONN    0         0                         *:mdns                             *:*        users:(("kdeconnectd",pid=3643,fd=40))                                                             
tcp      LISTEN    0         4096          127.0.0.53%lo:domain                     0.0.0.0:*        users:(("systemd-resolve",pid=790,fd=17))                                                          
tcp      LISTEN    0         4096                0.0.0.0:ssh                        0.0.0.0:*        users:(("sshd",pid=4311,fd=3),("systemd",pid=1,fd=89))                                             
tcp      LISTEN    0         4096              127.0.0.1:9050                       0.0.0.0:*        users:(("tor",pid=3699,fd=6))                                                                      
tcp      LISTEN    0         4096             127.0.0.54:domain                     0.0.0.0:*        users:(("systemd-resolve",pid=790,fd=19))                                                          
tcp      LISTEN    0         4096              127.0.0.1:ipp                        0.0.0.0:*        users:(("cupsd",pid=2602,fd=7))                                                                    
tcp      LISTEN    0         50                        *:1716                             *:*        users:(("kdeconnectd",pid=3643,fd=39))                                                             
tcp      LISTEN    0         4096                   [::]:ssh                           [::]:*        users:(("sshd",pid=4311,fd=4),("systemd",pid=1,fd=90))                                             
tcp      LISTEN    0         50                        *:ms-wbt-server                    *:*        users:(("krdpserver",pid=3393,fd=38))                                                              
tcp      LISTEN    0         4096                  [::1]:ipp                           [::]:*        users:(("cupsd",pid=2602,fd=6))
18

The troubleshooting steps from this link: https://discuss.kde.org/t/troubleshooting-krdp-a-guide-to-connecting-from-windows-native-rdp-clients/43874/4 fixed it. I never would have found this. Thank you every one for the help.

1 Like
19

This topic was automatically closed 18 hours after the last reply. New replies are no longer allowed.