Jonathan, The problem is that WinVNC is unable to listen on any ports in the range 5900-5998, so it ends up picking display 98 (the last one it tries) btu can't actually listen on it.
Check that nothing else is using those ports (using netstat). Also check that your TCP/IP stack is really properly working, and that you have an IP address configured. Can you run other TCP/IP based programs, e.g. telnet? Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Herz-Midler > Sent: 09 July 2004 14:32 > To: [EMAIL PROTECTED] > Subject: Win VNC Not Listening > > I have found an e-mail in the archives with the EXACT same > problem that we are having right now with Win VNC version > 3.3.3 running on Windows 98 Second Edition. As far as I could > tell, however, there were no answers to this question. > Hopefully now someone will be able to help us get past this. > Here is the original e-mail: > > Hi, I have a peculiar problem. I cannot set WinVNC Server to > accept socket connection. No matter how many times I've > ticked it on. It automatically reverts back to the off state > once I reopen the Properties page again. The greyed-out > display number box has "98" written in it. > This can be changed (to 1 for example), however > reinstallation of VNC reverts the setting back to 98. All > other parameters can be changed successfully. Here's what i > have tried so far. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
