Re: VNC server stops responding after a few days
On 16/11/2011 22:56, Christopher Woods (CustomMade) wrote: Surely if a machine has a fixed static IP, it doesn't even enter into discussion with the network's DHCP server to request a lease? Just the usual broadcast traffic... I'm not a networking or Windows expert, but this presumably depends on whether the client (XP?) actually has the VNC server's IP address in its hosts file (something like C:\WINDOWS\system32\drivers\etc\hosts). If it doesn't, then it will send a request to get the address from the DHCP server. If the client ends up using the IP address supplied by the server, then it will eventually expire. I've had exactly this problem on another X server (not VNC). James: what's in your hosts file? And how does the client actually connect to the server? What's the VNC command line? ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: VNC server stops responding after a few days
On 14/11/2011 16:41, James Wheaton wrote: Hi everyone, We've got a problem with RealVNC server which stops working after a few days. A computer reboot is required to get it to work again. The error message upon connecting is: unable to connect to host. 2 computers do this on the regular and they have Windows XP installed. Is this a known problem? Any idea what could be causing it? DNS lease timeout? ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
Re: VNC to N3 network?
On 25/11/2010 14:40, Philip Herlihy wrote: Your best bet is using a listening client and initiating a session from the controlled machine. This is my fallback plan, but it's so inconvenient that it probably wouldn't be worth it. I don't think this could be blocked - could it? The surgery computer can always see outside N3 on a browser, so presumably tunnelling on 80/443 should be fireproof. The issue for incoming connections, as you point out, is authorisation. It's possible to get authorisation, but it's next to impossible to find out *how* to get authorisation. This is what I've been googling for. There are half-a-dozen commercial solutions that do exactly this, but I can't find anyone at N3, or any technical docs, to tell me what's involved or who to apply to. You can apply to use an existing third-party commercial solution, but that's it. The third-party solutions have various problems, apart from price - some only encrypt between the surgery computer and the N3 gateway, some use offshore/US servers, and so on. End-to-end vnc/ssh is my preferred solution. So, what I was hoping was that someone here has already been through the pain, and found out how to apply to get through the gateway, or how to get through without finding someone to apply to... -Paul ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
VNC to N3 network?
Has anyone managed to set up VNC to allow access into the secure N3 (NHS) network? I've spent hours on Google, and haven't managed to find anything on getting through the gateway, or even on finding IP addresses for the surgeries I want to get to. Thanks - Paul ___ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
