Since the OP is using Windows then Fing is the best choice of network scanning tool.ChrisBriggsy wrote: Yes, you can connect to the Pi running win10 without a monitor as long as you know its IP address. A network scanning app such as nmap on PC or iNet on IOS would be able to discover the Pi's IP address.
Win10 IoT Core is not designed to be a standalone Operating System like Win 10 Desktop, it is primarily a 'slave' devicelucdig wrote:Thank you,
the solution seems to be using PowerShell. I have Windows 7 Enterprise and I found this page in the MS Download Center:
http://www.microsoft.com/en-us/download ... x?id=34595
Once connected, is there a way to download and activate a VNC Server on Windows IoT?. In Raspbian I use tightvncserver.
As stated above, Windows 10 IoT Core does not have the capability to be a ServerMiaW wrote:Is it OK to post a questions to your answers? I have the same question basically, could anyone please give advice on how to set up a VNC server when running win10? I need to see the screen connected ti the Pi from my PC, not just remote control with commands using power shell. I have searched the whole day and found nothing but some references to libVNC but no examples for the raspberry Pi with win10.
Please report back when you have created you VNC Server Project in Windows 10 IoT Core, thank youMiaW wrote:Well I know that Microsoft has not included a VNC sever functionality for win10 core. Thats why I need to implement the functionality in another way. What is the point of IoT devices if you cannot remotely see whats going on? So please do not tell me it is impossible. I have found other VNC servers that should be possible to port to win10 core, and I am almost sure someone have done it already.
It is not possible to create a VNC server for the Pi as there is no way to get/attach to the screen buffer. Without that capability all is lost. You might like to consider altering the GPU code to try and achieve it but that is WAY outside my (and probably most peoples) capability and even then you would have to figure out how to connect to that modified GPU.MiaW wrote:Well I know that Microsoft has not included a VNC sever functionality for win10 core. Thats why I need to implement the functionality in another way. What is the point of IoT devices if you cannot remotely see whats going on? So please do not tell me it is impossible. I have found other VNC servers that should be possible to port to win10 core, and I am almost sure someone have done it already.
Windows 10 IoT Core is based of Microsoft NT Kernel and has zero relationship to Raspbian (Debian) which has a Linux KernelMiaW wrote:Are you sure? It works for Linux:
https://www.raspberrypi.org/documentati ... ccess/vnc/
ricl gave you the answer, instead of argueing with helpful volunteers who are unpaid go to Microsoft as it is their proprietary closed-source software and argue with themMiaW wrote:OK so let me rewrite my comment. Since it is possible to run a VNC server on a RPi running Linux, I want to know how I can find a similar solution for my RPi with win10. And I still find it quite unlikely that the concept of IoT does not allow remote access with VNC for support purposes.
Or do you mean that win10 core has excluded the possibility to access the graphic memory?
There appears to be no way to get at the physical address of the video memory. It is up in the system space and not reachable from the user/admin space.MiaW wrote:Or do you mean that win10 core has excluded the possibility to access the graphic memory?