Disconnects with 4.1

[Dennis Bathory-Kitsz]

At 11:30 AM 12/13/05 -0000, James Weatherall wrote:
>Can you try running VNC Server with the "Log" parameter added, set to
>"*:file:100"?  This will create a log file in C:\temp\winvnc4.log, which
>will include messages indicating why the server was unable to listen for
>connections.

Just for chuckles, I changed the port to 5904. Now it works. Here's the log
with my comments. I'm happy to run it on port 5904, though I don't know
what it suggests, or if I'm in for trouble later:

**Original start:**
Tue Dec 13 08:35:20 2005
 Config:      set immutable Log
 main:        WinVNC service destroyed
 main:        WinVNC process quitting
 (10048)
 ManagedListener: unable to bind listening socket:  (10048)

**Changed to accept local machine only:**
Tue Dec 13 08:51:35 2005
 SocketManager: Unable to track address changes

**Changed back to accept connections IP address range:**
Tue Dec 13 08:52:01 2005
 ManagedListener: unable to bind listening socket:  (10048)

**Changed to port 5904:**
Tue Dec 13 09:02:35 2005
 SocketManager: Unable to track address changes

**Connnection from another machine works:**
Tue Dec 13 09:03:14 2005
 Connections: accepted: 192.168.244.3::1520

**I stopped and restarted the service and got this:**
Tue Dec 13 09:08:44 2005
 Config:      set immutable Log
 main:        WinVNC service destroyed
 main:        WinVNC process quitting

**But still got this:**
Tue Dec 13 09:09:39 2005
 Connections: accepted: 192.168.244.3::1521

The tray icon now reads "VNC Server (Service): 192.168.244.2"

(It reminds me that for a long time my old WinVNC 3.3.3 wouldn't accept
Screen 0 on one of the machines. It would uncheck "accept connections"
until I changed it to screen 1. I never did figure that out either, but
kept Screen 1.)

Dennis