List, good afternoon,
Hopefully, I've overlooked something, but cannot think what.
Installed F14 on a Samsung NB30 netbook, from the RC2 XFCE CD. 'yum update' last night (it updated nearly 450 programs/libraries). Installed Vino (vino-2.31.91-1.fc14) but cannot log into into the netbook's desktop from another machine.
(Had first tried vino-2.32.0-1.fc14 from 'test updates' repository, but when I failed to log into that, reverted to this slightly earlier version which is from the main F14 repository.)
Netbook is connected to local network, replies to pings, and can access internet. Firewall set to 'trust' eth0 and wlan0; and tried with firewall both enabled, and disabled. Same result, VNC client reports failure to connect. (VNC client has unrestricted access to the network, and can access all 4 other desktops on the network, without problems.) A different VNC client (Krdc on Debian/KDE) reports 'no server running at that address/port (5900)'.
Noticed that, on F13 (on another machine), had to run 'vino-preferences' before a VNC client could log in. Have run 'vino-preferences' on the netbook, allowed 'control of machine', assigned a password, and tried with 'configure network to automatically accept connections' either set, or unset; same results.
vino-preferences 'checks connectivity' and sometimes reports (i) 'local network only, using name localhost' (which surprised me because on the other machine using F13 it reports the machine name and its IP address), or (ii) it sometimes says the machine can be accessed using our external, routable, IP address (which it cannot, because that's blocked at a gateway and the internal network is NATted and there are no port-forwards set).
Vino doesn't appear in the XFCE 'system services' graphical list. Maybe it isn't running, just as KDE surmised.
Could I ask - how should I check if it is running, and is there a specific command to start vino running? (Under F13, it seemed to run after vino-preferences was run.)
Thanks for reading this far, grateful for any suggestions.
regards, Ron
Add:
/usr/lib/vino/vino-server
to your 'autostarted apps' in Xfce.
Then make sure you use -via with your vnc client to tunnel the connection over ssh. ie:
vncviewer -via username@vinomachine localhost:1
That should work.
kevin
Kevin Fenzi wrote:
Add:
/usr/lib/vino/vino-server
to your 'autostarted apps' in Xfce.
Well.
That might be the problem, then, because there isn't /usr/lib/vino on my FC14 system. (There isn't on my FC13 installation on another machine, either.) /usr/lib has .../udev and .../vte, when listed alphabetically.
Kevin, I regret I'm unfamiliar with the facilities in XFCE or the CLI - could you suggest how could I search for 'vino-server' since it must be there somewhere because it's installed, and 'vino-preferences' runs?
Many thanks, Ron
On Tue, 26 Oct 2010 17:58:44 +0100 Ron Leach ronleach@tesco.net wrote:
Kevin Fenzi wrote:
Add:
/usr/lib/vino/vino-server
to your 'autostarted apps' in Xfce.
Well.
That might be the problem, then, because there isn't /usr/lib/vino on my FC14 system. (There isn't on my FC13 installation on another machine, either.) /usr/lib has .../udev and .../vte, when listed alphabetically.
Kevin, I regret I'm unfamiliar with the facilities in XFCE or the CLI
- could you suggest how could I search for 'vino-server' since it
must be there somewhere because it's installed, and 'vino-preferences' runs?
Sorry, it should be /usr/libexec/vino-server I should have checked. I think it used to be in /usr/lib/ in the past.
kevin
Kevin Fenzi wrote:
Sorry, it should be /usr/libexec/vino-server
Kevin, well done, that's brought up vino, after I restart.
Hmm... But I can't log in over wireless, not can I ping the machine now. Even if I disable the firewall.
But if I abandon WiFi, and use eth0, then I can log in fine. Perfect.
Worried about the wireless, though. And I'm using the 'wild' rtl8192e driver. I wonder if that doesn't like 'inbound' signals? Doesn't really make sense, though, does it, they're just a series of packets on a link that's already up. When I tried to login, the vnc viewer (tight-vnc, vista) tried to connect, and took a 'long' time to decide it couldn't get through, maybe 15 secs. Normally fails in around 5 secs if something is blocked. Odd.
It's not a vino issue, obviously. It's likely a network/driver issue, I think. I'll start a thread on the laptop list since it's a chipset common to a lot of laptops.
Thanks, again, Kevin. Oh. Should the vino package have installed itself in autostart? (It didn't under FC13, either, by the way.)
regards, Ron
Ron Leach wrote:
Hmm... But I can't log in over wireless, not can I ping the machine now. Even if I disable the firewall.
Kevin, please ignore. Something wrong here on the WiFi AP, possibly. Now working intermittently. I won't follow up any more. If I think there's a driver issue in the end, I'll post on the laptop list.
As far as the XFCE package goes, F14 vino is fine (once autostarted). Thanks, again.
Ron.
-
Kevin Fenzi -
Ron Leach