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.
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 3389Replace 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 xrdpDoes 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 xrdpThere 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.