Connection Aborted (10053 error)

[Karl Juul]

I have searched the archives without finding a solution...

I'm running free-RealVNC on a WIN2K (SP4) headless file-server (an older
Pentium 4 machine with a large hardware Raid 1 array).  The server is on my
small wired LAN, but is physically in a remote building.  VNC is set to run
as a service on that machine.

Everything has been working OK for several weeks, but now I'm getting
frequent "connection aborted" errors when I try to connect remotely.  The
problem seems to occur when I haven't used VNC in several days.  When the
"connection aborted" problem happens, the server is still accessible over
the network for file transfers.

The situation is requiring frequent trips to the remote building to reboot
the server, which restores VNC functionality for one to four days, then the
cycle repeats.

Is any of this sounding familiar to anybody?

Thanks-

Karl