Results 1 to 9 of 9
Hi,
To be sure that the remote desktop was working, I tried from home, where I have both the laptop I want to connect to and the laptop from which ...
- 05-05-2011 #1Just Joined!
- Join Date
- Mar 2011
- Posts
- 19
Remote desktop just works when connecting from close distance
Hi,
To be sure that the remote desktop was working, I tried from home, where I have both the laptop I want to connect to and the laptop from which I make the connection. It worked without any problem, but now I'm trying to connect from my work place and it's not working anymore. Both are connected to the same VPN, so I don know where the problem comes from.
Any ideas??
Thanks in advance
- 05-05-2011 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Just because both the host and client systems are connected to the same virtual network doesn't mean that either a firewall rule is engaged, or that the host you are trying to connect with is listening on the correct network segment and port.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-05-2011 #3Just Joined!
- Join Date
- Mar 2011
- Posts
- 19
That doesn't look good...is there any way of checking where the problem is coming from?
Thank you!
- 05-05-2011 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Check IP table rules, SELinux settings, remote desktop server configuration, etc.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-05-2011 #5Just Joined!
- Join Date
- Mar 2011
- Posts
- 19
I don't know what are you talking about, but I'll do my best to look for it
Thanks!!
- 05-05-2011 #6Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
You can see what your iptables rules are with the command "/sbin/iptables-save" for IPv4, or "/sbin/iptables6-save" for IPv6 networks. You can see if SELinux is enabled with the command "/usr/sbin/selinuxenabled" doing this:
It will output 0 if not enabled, and some other value (probably 1) if SELinux services are enabled.Code:/usr/sbin/selinuxenabled echo $?
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-05-2011 #7Just Joined!
- Join Date
- Mar 2011
- Posts
- 19
Thank you!
The SELinux is enabled (1). The other command (/sbin/iptables-save) doesn't give anything as response (not even an error).
Thanks again!!
- 05-05-2011 #8Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Ok. So you are running Security Enhanced Linux (SELinux). This is likely the cause of your problems. You need to configure it to allow the remote desktop access over the VPN. Since such rules are very specific to your system configuration, there is no simple "do this, and that" sort of anwswer.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-06-2011 #9Just Joined!
- Join Date
- Mar 2011
- Posts
- 19
That's weird, as I've just checked the file /etc/sysconfig/selinux and it says that it's disabled...
I had tried before this command to disable it temporarily, just to see what happened: echo 0 >/selinux/enforce, but when I write
/usr/sbin/selinuxenabled
echo $?
I still have the same reply: 1
Maybe the computer needs to be restarted to change that, but I can't restart it now, so it'll need to wait a couple of days.
Thanks anyway!
Cheers


Reply With Quote