Debian Configuration :: Configure Vino Remote Desktop To Start At Boot?
Jan 29, 2011
Kernel: Linux 2.6.26-2-686 (i686)
Compiled: #1 SMP Thu Nov 25 01:53:57 UTC 2010
C Library: GNU C Library version 2.7 (stable)
Distribution: Debian GNU/Linux 5.0.8
Desktop Environment: GNOME 2.20
Gnome comes with Vino Remote Desktop as part of it's package. I want Vino to run at boot so that I can login remotely.I am using VNC-4.1.3 for remote viewing. However, I can only view remotely once I have logged-in locally
Kernel: Linux 2.6.26-2-686 (i686) Compiled: #1 SMP Thu Nov 25 01:53:57 UTC 2010 C Library: GNU C Library version 2.7 (stable) Distribution: Debian GNU/Linux 5.0.8 Desktop Environment: GNOME 2.20
Gnome comes with Vino Remote Desktop as part of it's package. I want Vino to run at boot so that I can login remotely. I am using VNC-4.1.3 for remote viewing. However, I can only view remotely once I have logged-in locally.
so as my title implies I like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot
I like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot.
I'm trying to use Gnome's built in remote desktop viewer, Vino, to remote to my PC. When I use the vnc client on another computer to get to my OpenSuse 11.1 box, it lets me type in a password and pauses. If I look at the screen on my OpenSuse box it is waiting for the gnome keyring password and it wanting it for vino-preferences. It specifically says: The application gnome remote desktop (/usr/bin/vino-preferences) wants access to the default keyring but it is locked.
Does anybody know how to bypass needing the password for this? I'm not sure how to begin to figure this out. I've been a longtime Fedora user and vino worked fine there so I don't think this is the way it is supposed to work.
I'm trying to use Gnome's built in remote desktop viewer, Vino, to remote to my PC. When I use the vnc client on another computer to get to my OpenSuse 11.1 box, it lets me type in a password and pauses. If I look at the screen on my OpenSuse box it is waiting for the gnome keyring password and it wanting it for vino-preferences. It specifically says: The application gnome remote desktop (/usr/bin/vino-preferences) wants access to the default keyring but it is locked. Does anybody know how to bypass needing the password for this? I'm not sure how to begin to figure this out. I've been a longtime Fedora user and vino worked fine there so I don't think this is the way it is supposed to work.
my OS is SuSE 11.2 with gnome.Remote administration is active.The VNC-session then connects to the login-screen and after login opens a new desktop.How can vino be configured to attach to the desktop that is already running. (Ubuntu does that per default so it should be possible with SuSE too)
my OS is SuSE 11.2 with gnome. Remote administration is active. The VNC-session then connects to the login-screen and after login opens a new desktop. How can vino be configured to attach to the desktop that is already running. (Ubuntu does that per default so it should be possible with SuSE too)
I have a fileserver running debian 6 and I would like to be able to remote control it over VNC. I have enabled Remote Desktop in Gnome and it works, however I have to be logged into Gnome for it to work. Gnome doesn't enable vino before a user is logged in for some reason. This presents a problem as there is no keyboard or mouse connected letalone a screen.
I looked up the issue on google and found this: [URL] Long story short, I have to edit /etc/gdm/Init/Default and insert "/usr/lib/vino/vino-server &" just before 'exit 0' at the end of the file, and change "KillInitClients" to "false" in /etc/gdm/gdm.conf. I edited the first one as it says, but I can't find gdm.conf anywhere. I did however find a 'daemon.conf' in the /etc/gdm directory, and added the line there.
When I try to connect after doing the above, my vnc viewer (client) just disappears - no errors, message, sound - nothing. It doesn't even ask for a password. I checked the comments in the link, and the second to last comment suggests it's because of some negotiating-issue which should be an easy fix:
Turned out I had to enable connections to vino not related to my user account. To do this run sudo vino-preferences and duplicate the settings instructed here
I cannot remote desktop to the Debian machine from anywhere,hether within the same network, or on a different network elsewhere. Also, the personal wiki I set up on it to be viewed via a normal web browser cannot be accessed, either. Both time out when attempting to connect to them. I can still ping the Debian machine when on the same network, though.
This started some time ago when we had a failure occur on our main server.had to powercycle everything in order to restore things back to normal, the Debian machine included. Since that time, this problem started to occur. This is a major thorn in my side in attempting to prepare for our website to move,I've been unable to figure out how to fix it.Originally, I thought it would be something in between the Debian machine and anything else, which would mean something like our firewall box or our hardware switch was the problem. But the tech support people who maintain those for us confirm that there is nothing wrong with them, so now I'm not certain anymore.
I have a bit of an odd network setup, shown in the pic here:I am trying to remote desktop from the XP boxes on the side to the one on the bottom, behind a Debian box/firestarter firewall. Is this possible to do without changing my network (IE wiring/topology) setup? If I had my druthers, I would put the router behind the Linux box, before the XP box, but my work laptop does not allow me to connect in that fashion as I can't change the internet settings.
I am certain the setup is correct on both the Windows clients and host, so it has to be something with my firestarter firewall, or something else I'm completely missing. I have the RDP port opened on firestarter, but whenever I try to connect to the XP box, whether it's by computer name or LAN IP address, it is unable to connect. I had thought about setting up a VPN server on my Debian box, and then VPN'ing to it, and then in turn RDC'ing to my Windows machine. Is this possible? If all else fails, I may just plug the Windows box directly into the router and deal with the lower security or get a second wireless router just for my work pc.
I'm trying to get an laptop running more or less like a headless server, my reasons are not all that serious. Mostly I want to leave the laptop running as a seed box when my main PC is turned off, also want to setup it up as a media top, common place for media files and playback on Tv. So essentially I want to be able to access the remote machine, preferably sharing the same session and persisting while I log out from remote.
What I've done: setup keys for ssh to connect automatically between machines, so I can login via terminal, access the file system without issues, which is already a great step. enabled remote access on remote machine lightdm manager setup deluge for daemon torrenting, which enables almost seamlessly client to connect remotely (though deluge is not the best with speed)
What I've tried so far: Connect directly with a new X session Code: Select allX -query your_server_ip :1
Works alright, creates a new display (:1) which is oddly in F2 tty instead F8 as is expected. Works alright, not much lag, audio is not routed.
But an issue! whenever I decide to log out X will simply shutdown, screen goes black and I can't resume on my regular session on my local machine.Connect X with nested Xephyr session
This works too and might be the best solution yet, a windows is created and the remote session is nested in your current X session. Visual and performance is ok. Only real issue is that session is not shared, eg, application will not remain running...Connect via VNC
So it seems only solution for shared sessions is VNC.
With the remote desktop apps from KDE (which is the DE for both), I can connect buzz around and etc, but its kinda cumbersome and laggy, password always resets and I usually need to accept on the remote machine.
I've tried setting up lightdm to allow a vncserver at logon, but this is erratic at best, took a long time to get the Xvnc command correct enough for me to login remotely, and even then got a garbled screen and the X session wasn't even the same...
So that's it... Isn't there a way of regular X session sharing in the remote computer? Or a better solution for lightdm vnc invoke?
If i got gnome i may go to the top-panel: choose system, choose preferences and go to "remote desktop" and make my settings (allow, ask for allow, password, and other stuff). I don't want to be bound to gnome (though i like it, thats not the problem).Which config-files are the ones i am looking for?
I did search the web, but i can't find useful how-to's, explanations, etc.Cause what i find is related to the path i described above (gnome: top-panel, preferences...)Which is the app/tool which pops up and says:"someone wants to access, you want to allow it, yes or no?". The performance of VNC is lousy comopared to NX. Lousy is the friendly version. What might i be doing wrong?i usually do it from a Debian-host to a VirtualBox-guest.I am mainly asking for how-to's/docus and stuff like that. Links. Explanations are welcome too. Of course.
I have a Debian VPS running Lenny and I'm trying to setup a way to run remote desktop sessions from it. I went with FreeNX, NX client for windows from nomachine, XDM and xfce4. All seems to have installed well, but I can't start an NX session on my box. I can connect to the server and authenticate, but the client hangs on "Downloading the session information," eventually timing out. The log output is below - I'm not even seeing an error message. Any ideas?
The only thing I noticed during install, which was about 400 packages since this was a barebones VPS, was that I should consider recompiling the kernel with CONFIG_SOFTWARE_SUSPEND=y. I don't know if this has any impact on session information, however, since this is a new session, not one I'm trying to resume.
I'm using debian 5 x64 with xfce.Is there a way to configure (start/stop/restart) services (especially Apache2, mySQL and PHP) using a graphical or cli tool? I tried to use sysv-rc, sysv-rc-conf, rcconf and rc-conf in the terminal but Bash didn't find them (Although Synaptic show that sysv-rc is installed).
I have Ubuntu 10.04 installed on an older desktop and when I first installed Ubuntu I set up Remote Desktop Vino services and was able to connect just fine with my Windows XP, Windows 7, Leopard, Snow Leopard PCs and my iPhone using VNC all just fine. So I apply updates to my Linux box and now it's broken. I can not remote into my Ubuntu machine at all now. So something with the updates is broken. I don't really use my Ubuntu machine at all, all it is used for is for a dedicated Folding@Home server. I attached a screenshot as what my Remote Desktop settings look like.
I have a debian 8.1.1 server running owncloud and a proxy server at home. I have everything working fine, with one exception. The proxy server won't start on boot. If I ssh into the server, then run "sockd -D" as root, it starts up and runs just fine. Any guides I find refer to the init.d script method that worked in Wheezy, but that isn't working. I think it has to do with Jessie switching to systemd? I had used someone elses script in init.d, and ran update-rc.d, but it still doesn't start.
With Jessie, how can I make "sockd -D" execute on system startup?
I'm running Debian Etch AMD64, and currently trying to clean up my system in preparation for an upgrade to Lenny. One problem I have is that resolvconf (which is installed) does not start at boot time, but if I start it manually then bring the NIC down and back up, it works OK, with no error/warning messages.
I am very pleased with a new Squeeze desktop that I built. I am use to using BSD style init scripts (Slackware, OpenBSD, Arch) and am trying to tweak my system not to start vsftpd at boot. I use vsftpd occasionally to move large files between computers on my LAN. My inittab shows run level 2 as default.
I am running Debian-Squeeze with apache2. However, apache2 doesn't start at boot time, even though there is of course the required script in init.d. I can start it later on using "/etc/init.d/apache2 start". I have checked the configuration with "apachectl configtest" - giving the answer "Syntax ok". How do I get it to start automatically at boot time?
I have just recently installed firestarter to get an idea of iptables editing with a GUI. Firestarter works great and I love it, however when I turn my system on, and my system is booting up the terminal displays a "Failed" message when attempting to start up firestarter. Now I have been doing my homework (reserch) and have read that a user will get this error because firestarter trys to load prior to the network manager starting up. I have also read some other variables that can cause this is if you use network manager and have a password on your user account (which I do have) can cause this issue.
However in most cases from what I have read is even though it gives the user a "Failed" startup message, once the user logs in, and is connected to the internet firestarter will actually load the iptables. I did some tests and from what I understand I can see that this is true because I have allowed access to certain torrent trackers, and denied access to others, and I can see some come online. Does firestarter load iptables once the user logs in? Or once it fails to load, does it not load at all unless you manually open/load the application. If firestarter just modifies iptables, then once I save my listings in firestarter then I really don't need it to start up correct?
I have access to my linux home server , through ssh
I wanna start using now remote desktop , so i can connect to my home server through vnc.
I've tried this old post here , but I could not connect
What I did was to ssh with putty (and Xming) and X11 forwarding on , to start vino-preferences , which seemed to work BUT even though I connect with vnc to my remote server , all I see is grey stripes....
PS I have forwarded port 5500,5800 and 5900 to my home server pc of course
remote desktop requires authentication on server side when trying to login remotely via VNC. I have the option set to not require confirmation of each access to the machine, I set a password that the user must enter from the client side.just testing this locally over my LAN, VNC connects and asks for a password(the user field is blank; might be nice to have to enter a valid username and password so I don't have to share a general password). after entering the password on the client, a window pops up on the server 'An application wants access to the keyring Default but it is locked' and requires me to enter a password, which once I do then the VNC gets control and all is good... but obviously if I am trying to remote further than down the hall this won't work.
Ideally I would like to remote into ubuntu desktop with account credentials from the server and require no physical person at the server to allow access. I currently have an XP pro box setup this way with remote desktop and works flawlessly. I want to keep it true to the same functionality where when I log in remotely it joins a session with applications already running, such as a web browser and mail client, with those applications left running when I logout of the remote session. its not all that important if it locks the server side locally as there will eventually be no physical access to the machine once its been setup.
as you may have noticed I am fairly new to linux, but very willing to learn. my primary reason to move to the linux platform is that I am hoping it will provide better performance than windows XP/windows 7 when I upgrade the box to an atom based mainboard. any other thoughts or recommendations on my planned setup would be greatly appreciated as well.just to be clear, the 'server' is ubuntu desktop and client side is generally windows XP, windows 7, windows server (I work almost exclusively on windows boxes)
I have recently added a second screen and uses separate X screens as my x screen settings. No xinerama. After adding the display Vino refuses to start. IIRC using dual X screens with xinerama works as expected.
Starting it manually results in code...
Is it even possible to use vino with two server-side x screens? I would be perfectly happy with only one X screen exposed via VNC if it is impossible in the VNC client to choose which X screen to connect to.