Hot answers tagged vnc
10
One simple way is to turn on vnc screen sharing by going to System Preferences -> Sharing -> Screen Sharing on the machine you want to share. For client compatibility reasons you may need to select both "Anyone may request permission to control this screen" and the "VNC viewers may control this screen with a password" checkboxes.
Once you've set up the ...
7
Aside from bandwidth and latency issues (which can vary a bit), the big differences are the functionality it provides.
VNC exports a whole session, desktop and all, while ssh will run a single program and show its windows on your workstation.
The VNC server exports a session that survives even when you disconnect your screen, and you can reconnect to it ...
6
Port 5901, generally by convention Port 5900 + XDisplaynumber, is the TCP Port on which the VNC service listens. That's their relation. Actually you may use arbitrary TCP Ports with arbitrary Xdisplaynumbers.
The VNC service is meant to transports input (mouse, keyboard) from the client to the server and output (an image) from the server to the client. This ...
5
As noted by yasouser, middle-click is the standard way to paste the selection buffer in linux. This buffer gets written every time anything is selected with no need to initiate a copy command. In gtk based or influenced apps, there is usually a keybinding for this as well. Shift+Insert
In most Desktop Environments there is also a copy buffer that is ...
5
Definitely review security with a good Linux Security Checklist as the first order of business. SANS publishes a nice one.
Second step is to get rid of packages that you won't use.
Third step is df -h and record how much disk space the install uses.
And then fourth step is to tar up the entire disk using the --exclude option to exclude the output tarball. ...
5
On Linux,
ss sport = :5900
Would tell you the currently established TCP connections on port 5900.
For anything else, we'd need to know what VNC server you're using as there exist dozens.
If you know the name of the VNC server command,
lsof -ai tcp -c that-command
(as the user running the VNC server or as root) would also tell you the currently ...
4
Finder doesn't use X APIs, so can't be forwarded over over ssh like that. Same with most mac applications; apple have their own windowing system called Aqua. Sharing the desktop via VNC or apple remote desktop works fine though -- look in the "Sharing" preference pane for the "Screen Sharing" option to set it up on the mac, then use a vnc client on the other ...
4
Your solution would work, but I think it's a little bit rougher than it needs to be. In particular, the vnc over ssh on android is going to be troublesome. It's possible, but it's not as usable or stable as it could be.
I would suggest using RDP instead. There are great RDP clients on Android, the bandwidth consumption is a lot lower so it's more usable and ...
4
Have you tried creating
~/.vncstartup
or
~/.vnc/xstartup
In my version of vncserver, that's where you put your startup commands, e.g.
xterm -geometry 80x25+0+0 &
xterm ...
...
See also Taking your desktop virtual with VNC.
4
The problem is that the vnc server is listening (per default) on localhost and not on your external IP address. It is important to understand that a service can listen on a specific IP address and is only reachable via this address. In your case the VNC service is only listening on 127.0.0.1 and can only be reached via localhost. As VNC is not encrypted it ...
4
systemd has something called 'targets' which can be thought of as the runlevels of init.
prefdm.service will be run with the "default.target" which is set by default to "graphical.target".
So, by setting the default target to "multi-user.target" (aka. SystemV runlevel 3) you will start all but the X11-server.
Your vncserver@:[0-9].service will be unaffected ...
3
iTALC lets you monitor and control several computers in a classroom environment. It might do what you need. I'm not sure about showing a student's screen on all others, though.
There is also LanSchool, Nettop, and NetSupport Assist, all of which are commercial solutions.
If none of those are what you're looking for, you might want to take a look at ...
3
The problem is solved now. I had made the silly assumption that the key bindings were global when in fact, they are per-user. I had changed the key bindings logged in as root, but was logging into a VNC session created by another user. The 'hide all normal windows…' shortcut was set to Mod4+D for this user. The standard solution—changing it to ...
3
This probably does belong on SuperUser, but, here's a solution.
I use the vnc viewer from TightVNC (so, this might not work on all vnc viewers). On the tool bar at the top of the vnc viewer window there is an ALT modifier button. Click that (it should remain pressed). Then, just press tab. Once you've got the window you want, click the alt button again to ...
3
Inherently, none.
When you run the xvncserver it needs to do two things.
Open a listening port (which for VNC is 5901
Create a display target
The display target can be any number. Commonly, logging in on the console via X will use display :0. It doesn't have to, you could log in on the console first and then use startx :36 instead. VNC uses 1.0 by ...
3
Create a custom LiveCD/LiveDVD with the software you require, for e.g. Fedora the instructions are here. You can also put it on an USB stick.
I'm sure users knowledgeable in other distributions will chime in and add links to instructions tailored to their favorite.
3
If you'd like the graphical login screen then install a Desktop Manager such as GDM, KDM, LXDM, SLIM, Qingy, LightDM, WDM (I'm sure there are many others, but these are all that I could rattle off the top of my head).
Once installed, enable it start at boot. The procedure for enabling this to start at boot will depend on your distribution's init system ...
3
If I understand you right: you want to share gnome or other environment remotely as it is, then the easiest way to achieve this is to use x11vnc. It shares real X11 server as it is after user logged in:
x11vnc -display :0
Or if you want vnc server run after login, you can automate with this script:
#!/bin/bash
/usr/bin/x11vnc -nap -wait 50 -noxdamage ...
2
ssh -X redirects X11 commands to your local X server. So it is as if you were running the program locally, when it's really running on the computer at the other end. It's very slow because it uses a great deal of bandwidth. (This is what people are talking about when they say X11 is "network transparent.")
VNC and other remote desktop apps instead let the ...
2
Ok I kinda have a fix for this. There is a nice explanation from this site https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/336660 :
The explanation of the problem is the
following:
When you su to root from a terminal
where you are logged in as another
user the new "su-ed" user gonna
inherit the environment variables from
the parent ...
2
You might want to look in ~/.vnc/xstartup on the remote end. It's possible that you're running something like twm, which is somewhat feature-free when it comes to a desktop envrironment.
Also, did you know that the VNC traffic is not encrypted? Your password and keypresses are being sent in the clear over the network. Most people tunnel their VNC session ...
2
Double and triple check your firewall configuration. There are plenty of resources online for researching that.
Next, move SSH to a non standard port. If your box is secure, this won't matter as much but you'll have less log spam from script kiddies. If there are security issue (able to log in a root, week passwords, etc) moving to a non standard port will ...
2
I did manage to find how I was still able to connect: In Yast, theres a Remote Administration section that allows you to enable to disable remote remote administration. This, seemingly, creates a port listening on 5900. As far as the problems displaying the desktop, turns out KDE4 went under a major overhaul with their new desktop environment called ...
2
So, as I said in a comment, the most secure way is vnc over an ssh tunnel. It might not be the fastest because of the ssh encryption. I've just set this up on my machines, so I'll show how to set up the tunnel after you've gotten the server running.
Set up the tunnel from the client (windows) machine:
ssh -N -f -L 5901:remotehost:5901 -l remoteuser ...
2
x11vnc -auth $XAUTHORITY starts a VNC server where you authenticate with an X cookie. A cookie is a byte sequence that is randomly generated when the X server starts and which (under most setups nowadays) any application that wants to connect to the X server must provide. The cookie is typically stored in a file called ~/.Xauthority or indicated by the ...
2
tightvnc is designed to present an independent session. What you want is something like the vnc server extension for xorg which exports the running console X11 session via RFB. It is packaged for a number of Linux distributions (try the vnc4server package on Debian or Ubuntu).
The X11VNC package can also do it and is considerably more flexible, although ...
2
You should be able to modify the keyboard shortcut assigned to switching windows on the VNC server side desktop. You didn't specify what desktop environment you are using but on my computer (Ubuntu 10.10 with Gnome) this is the Keyboard Shortcuts control panel from the System menu (System > Preferences > Keyboard Shortcuts).
The Alt-Tab function is near ...
2
I'm not the expert in X11 and even Linux, but I heard that OS X implementation of Xorg Server doesn't support some required extensions for visually rich UI. Or may be transparency (and other effects) in Linux can only be achieved with composition manager (such as xcompmgr, Compiz, etc.) on client side, so they can not transfer them over network based X11 ...
2
I know it has already been suggested in the comments, still I also think screen is the best way to go to handle all your cli activity. It just takes a bit of time to get used to its windowing commands. Here is a small tutorial you might find handy.
For the X11 part (the product you're using on the cluster), you might want to give a look at XPra which ...
2
You should start the shells in screen or tmux so they can be easily reattached in a new terminal.
With screen this is done with the following steps:
Start the shell somewhere (e.g. in VNC):
screen -S myshell
Reattach the shell somewhere else (e.g. a new terminal with SSH):
screen -x myshell
While the methods above are highly recommended, they are not ...
Only top voted, non community-wiki answers of a minimum length are eligible
