debian wheezy desktop sharing

[crp]

So I clicked on the big icon to allow the desktop to be shared and entered in a password , cleared the firewall and went off to another pc. How can I connect to remotely take control?

TightVNC - put in the ip address and after a few seconds it prompted for password. Then nothing

RDP - nada, says nothing there.

 

So evidently the port in play is 5900 , but no screen shows up. I tried IP:2 and IP::2 but that results in error connecting.

[securitybreach]

Vinagre is a great remote desktop app that support VNC, SSH, RDP and SPICE. It is a gnome app but you can use it on any environment. https://projects.gnome.org/vinagre/screenshots.html

[crp]

since sharing the user's screen, it is :0 .

Wonder how to set it up so that :1 would work .

[securitybreach]

Not really for sure what you are asking..

[Guest LilBambi]

Which Desktop Environment/GUI are you using, crp?

[crp]

Which Desktop Environment/GUI are you using, crp?

The default on installation, seems like some sort of GNOME. I really, really, dislike it but since this is intended as a server and not something used with any frequency I'll stick with it.

[burninbush]

So I clicked on the big icon to allow the desktop to be shared and entered in a password , cleared the firewall and went off to another pc. How can I connect to remotely take control?

TightVNC - put in the ip address and after a few seconds it prompted for password. Then nothing

RDP - nada, says nothing there.

 

So evidently the port in play is 5900 , but no screen shows up. I tried IP:2 and IP::2 but that results in error connecting.

 

 

Not clear if what you are doing should /should not work, but when I use TightVNC I have always started the server daemon on the remote machine (first). Works well here linux-2-linux or linux-2-windows.

[jimg]

I use x2go for remote access. It works through the ssh port (22) and has clients for both linux and windows.

See http://wiki.x2go.org/doku.php/wiki:repositories:debian

[Guest LilBambi]

jimg, can you change the port? If not, I would never use it. The ssh port 22 is way too much attacked and your logs will fill up the hard drive!

[crp]

jimg, can you change the port? If not, I would never use it. The ssh port 22 is way too much attacked and your logs will fill up the hard drive!

really? we get lots of attempts on telnet , much less on ssh. (btw: telnet is turned off on our servers)

[Guest LilBambi]

Yep, telnet is another port that is hit hard. We got a lot of ssh hits as well. We switched the ssh port years ago when this was happening and have never gone back.