VNC remote desktop
Hello,
Does the RevPI Core3 have VNC capability ( the remote desktop'ish software that is typically available on a raspberrypi )? I see that under the raspi-config screen there is still an option to enable it, but even when it is enabled, the connection is refused. Is there an extra step in order to enable this feature on a RevPI? Thanks,
Does the RevPI Core3 have VNC capability ( the remote desktop'ish software that is typically available on a raspberrypi )? I see that under the raspi-config screen there is still an option to enable it, but even when it is enabled, the connection is refused. Is there an extra step in order to enable this feature on a RevPI? Thanks,
If you issue the command "sudo netstat -A inet -a -n", do you see a line for port 5900? If yes the vnc server is listening for connections.
Please also describe in detail what you are doing (which system on both sides, which distribution on both sides, what network infrastructure, etc.). According to our quick inspection the system should start the service and be able to connect.
Unser RevPi Motto: Don't just claim it - make it!
My development PC runs windows 7 sp1 and the VNC viewer on it is version 6.17.731. I'm connected directly to the RevPi Core 3 via ethernet and the Core 3 is NOT connected to the internet. I have configured the Core 3 to boot to desktop and I have enabled VNC in raspi-config. When I run "sudo netstat -A inet -a -n" i'm not seeing any connections listening on port 5900. The only one whos state is listen is 0.0.0.0:22.
Does your PC deliver a DHCP service? RevPi Core needs a DHCP server if you have not configured a static IP manually.
Unser RevPi Motto: Don't just claim it - make it!
Yep, I'm running open DHCP standalone and my Core 3 is being assigned ip addr 192.168.1.11. I'm able to SSH into the Core 3 and use the cli, but am unable to connect via VNC viewer.
please follow the request of Lukas and look for the port being up listening.
If it is up and listening the next step could be to check the network traffic by wireshark and find out if the RevPi really sees any requests from the client PC.
If it is up and listening the next step could be to check the network traffic by wireshark and find out if the RevPi really sees any requests from the client PC.
Unser RevPi Motto: Don't just claim it - make it!
Ok, so now I've had time trying VNC. It perfectly works for me. I followed this intructions, using a Win7 PC and a RevPi Core3:
https://www.raspberrypi.org/documentati ... ccess/vnc/
After all I can't see any technical reasons why it should not work if you follow the instructions.
https://www.raspberrypi.org/documentati ... ccess/vnc/
- I enabled VNC via sudo raspi-config
I started startx on my RevPi Core (actually I did a sudo startx but thats for another reason)
I started the prfered VNC Viewer (see link above) on my Windows PC.
I entered the IP of my RevPi Core3 in the LAN.
I clicked OK on the security warning popping up
I entered User pi and PW of my RevPi
Voliá: My Windows PC was showing the RevPi desktop!
After all I can't see any technical reasons why it should not work if you follow the instructions.
Unser RevPi Motto: Don't just claim it - make it!
b.t.w. : I also tried the virtual VNC desktop by starting vncserver on my SSH console . I works perfektly: I could connect by VNC viewer using my IP plus port #1 and got an empty fresh desktop of my RevPi!
Same positive result with the remote cloud connection: It perfectly works. I connected to my RevPi Desktop using an Androis smart phone (shame on me all you securtiy experts... yes, I would never recommedn such an open system for a real life machine control...Imagine my smart phone gets lost and some lucky kid gets control over my nuclear plant... ).
Same positive result with the remote cloud connection: It perfectly works. I connected to my RevPi Desktop using an Androis smart phone (shame on me all you securtiy experts... yes, I would never recommedn such an open system for a real life machine control...Imagine my smart phone gets lost and some lucky kid gets control over my nuclear plant... ).
Unser RevPi Motto: Don't just claim it - make it!
Well, I think my problem was that my date and time were set incorrectly. After I set the time zone date and time I was able to connect to problem.