I've missed a few episodes of this drama, so hope I'm not going over old
ground. I don't think you're doing enough to distinguish problems with VNC
server from general network problems. When the machine(s) are not
responding are you able to ping them? (You may need to allow echo on the
server firewall's ICMP tab, and you may be able to ping directly from the
router's diagnostic interface, if you can access that externally.) However,
you can test just as well with a VNC viewer on a machine on the same local
network. Is the network interface set to wake the machine if a connection
is made? Turning off standby might be a good option.
If you run ipconfig /all in a command window you'll see useful DHCP stats,
including the date/time any DHCP lease was obtained. For anything acting as
a server you're better off with a static IP (or a reserved DHCP address).
Reduce the DHCP range or scope to leave room at either end for a few
static IPs, and use one of those for this type of machine. Netscan.exe from
softperfect.com is a good free network scanner which might help you spot
issues.
You're not using wireless, are you? To be avoided if possible.
Check in Task Manager - if Peak Commit Charge becomes greater than Physical
Memory, the machine will have been paging out idle processes, and this might
include VNC server or maybe (?) networking components.
Philip Herlihy
-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of James Wheaton
Sent: 21 November 2011 14:50
To: vnc-list@realvnc.com
Subject: Re: VNC server stops responding after a few days
The uncommented line in the hosts file is simply:
127.0.0.1 localhost
The default gateway is setup in the Windows IP properties (along with the
other static settings) to be 192.168.0.254, which is our modem/router/DHCP
server. The modem has an external static IP that we would be connecting to
with VNC. I can connect to it on that address and the internal 192.168.0.99
... The command line on the VNC Viewer shortcut is just the default
vncviewer.exe with no options.
I just woke up one of the VNC servers/desktops that stopped working over the
weekend. I opened the web browser and it took a bit to load; was it asking
for an IP renewal? Maybe it's just the power saving options that are at
fault:
Turn off harddicks: 1hr
Standby: 1hr
Hibernate: never
James Wheaton
FloSource, Inc.
Phone: 765.342.1360
Fax: 765.342.1361
Visit us on the web: www.flosource.com http://www.flosource.com
On 11/18/2011 5:41 AM, Paul Dunn wrote:
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
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
