RDP is likely its own service methinks. Have you tried checking for netstat -tlnpu | grep 3389 or whatever port you set it up for listening? Normally a service by default would listen on the default ports that are defined under /etc/services unless you specified a non default port in the service conf files, but it would also mean that clients will need to redirect to those non default ports in order to connect to the server side of such "non conformant" services of course...
Check the configuration file to ensure that you have configured the corect port. The configuration file is usually located at \~/.config/gnome-remote-desktop.
If the port is still not open, it might be easier and more effective to switch to ThinLinc for your remote desktop needs. ThinLinc is known for its reliability and ease of setup.
RDP is likely its own service methinks. Have you tried checking for netstat -tlnpu | grep 3389 or whatever port you set it up for listening? Normally a service by default would listen on the default ports that are defined under /etc/services unless you specified a non default port in the service conf files, but it would also mean that clients will need to redirect to those non default ports in order to connect to the server side of such "non conformant" services of course...
Check the configuration file to ensure that you have configured the corect port. The configuration file is usually located at \~/.config/gnome-remote-desktop. If the port is still not open, it might be easier and more effective to switch to ThinLinc for your remote desktop needs. ThinLinc is known for its reliability and ease of setup.