raspberrypi

3574 readers

1 users here now

Community about the single-board computers, micro-controllers and related projects.

https://www.raspberrypi.com/

Other RaspberryPi communities on Lemmy

founded 4 years ago

MODERATORS

testman@lemmy.ml

RDP stopped working (lemmy.giftedmc.com)

submitted 1 month ago by haui_lemmy@lemmy.giftedmc.com to c/raspberrypi@lemmy.ml

1 comments fedilink hide all child comments

Hi folks, I'm running a pi4 with rpiOS and had been using rdp to log into my pi that has no peripherals connected. I can still ssh in and I do have physical access but this kinda bothers me.

I know rpi connect is a thing but I'm not too comfortable using another "cloud service" to connect to something on my homenetwork from my homenetwork.

The rdp service does not seem to run anymore and I am unsure how to search for the culprit. I did search for a service resembling rdp on the journal but it doesnt turn up. what could be the correct service name?

Thanks for reading. have a good one.

you are viewing a single comment's thread
view the rest of the comments

[–] bravemonkey@lemmy.ca 4 points 1 month ago* (last edited 1 month ago)

From the Windows side (assuming you're using Windows to connect, considering it's RDP and not VNC), you can open PowerShell and test to see if the Raspberry Pi is even listening for RDP connections with:

Test-NetConnection x.x.x.x -port 3389

Replace x.x.x.x with the IP address of the Raspberry Pi. If it shows successful, then the Raspberry Pi is listening for RDP connections.

Do you know what RDP package you installed, and what operating system you're running (Bookworm, Bullseye, etc)? I don't have a raspberry pi with a desktop to test on, but if you're using xrdp you could try:

sudo systemctl status xrdp

Does this give any input? If not, then you'll need to know what package you installed to get RDP, assuming one is still installed even. If it does give you a message it might be a hint as to why it's not working.

If you get output from the above command you can also try:

sudo journalctl -b | grep -C 2 xrdp

There are much better ways of searching journalctl but I'm a noob too. The -b returns only errors from the last boot time, the -C returns that many lines before and after a match is found.