Well, one of the simplest but not sure way is to unistall VNC, reboot and remove all VNC related registry keys, reboot and install again VNC.
> -----Message d'origine----- > De : Theodore Kearley [mailto:[EMAIL PROTECTED] > Envoyi : vendredi 19 mars 2004 17:56 > @ : Seak, Teng-Fong; [EMAIL PROTECTED] > Objet : RE: Failed to Connect to Server > > On the other machines it is listening on 0.0.0.0 but this one is showing > 127.0.0.1 -- that's the mystery I'm trying to solve. How can I make it > listen on 0.0.0.0? > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Seak, Teng-Fong > Sent: Friday, March 19, 2004 10:16 AM > To: [EMAIL PROTECTED] > Subject: RE: Failed to Connect to Server > > On all the machines I have, it's listening on 0.0.0.0. That's > also the address on which other servers like HTTP are listening. > > > -----Message d'origine----- > > De : Theodore Kearley [mailto:[EMAIL PROTECTED] > > Envoyi : vendredi 19 mars 2004 17:18 > > @ : Seak, Teng-Fong; [EMAIL PROTECTED] > > Objet : RE: Failed to Connect to Server > > > > Netstat is showing ports 5900 and 5800 are on IP 127.0.0.1, not the > > public IP. I can 'telnet 127.0.0.1 5900' on the NT PC and get the > > expected 'RFB 003.003' message. On what address should VNC be > > listening? Is there a way to make it listen on that address? > > > > Thanks, > > Theodore > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On > > Behalf Of Seak, Teng-Fong > > Sent: Thursday, March 18, 2004 3:47 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Failed to Connect to Server > > > > FYI, you could get the list of all listening and connected TCP > > ports by using this command: > > netstat -a -n -p tcp > > > > > -----Original Message----- > > > From: Scott C. Best [mailto:[EMAIL PROTECTED] > > > Sent: jeudi 18 mars 2004 22:16 > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: Failed to Connect to Server > > > > > > Theodore: > > > > > > Heya. Since you cannot telnet into the server while it's > > > running, there's either 1 of 3 things wrong. First, it's possible > > > that the server's not really running. On WinnT, I use the fport > > > utility to see what's actually active and listening to a port. > > > Also, please be sure you're using the very latest version of VNC > > > when you test. > > > Second, it's possible that a "software firewall" has been > > > put in place on your WinNT machine, either as part of the WinRoute > > > package, part of WinNT itself, or as a standalone application > > > (like Norton Internet Security or ZoneAlarm). To find those, you'll > > > have to closely examine the processes running on your PC. I use > > > WinTasks Pro for that. > > > Lastly, it's possible that WinVNC is running, but is > > > listening to a non-standard port. The fport utility can help trace > > > that down as well. > > > > > > Hope this helps! > > > > > > -Scott > > > > > > > I am running VNC on Windows NT that is also running Kerio WinRoute > > Pro. > > > > I had to restart the PC yesterday and since it was restarted, I > > cannot > > > > access the PC with VNC. I saw a posting that recommended trying > to > > > > telnet the PC (telnet ip 5900) and see if it would connect using > the > > > > public IP and the private IP but it would not. All of the ports > are > > > > open in the network configuration for both TCP/IP protocols. > Using > > > > www.gotomyvnc.com <http://www.gotomyvnc.com/> shows no response > > from > > > > any display adapters. I have stopped and restarted the VNC > service > > and > > > > removed it and reinstalled it (both realvnc and tightvnc) all to > no > > > > avail. The WinRoute software is working fine - I can access the > > network > > > > to get to the terminal services server and use pcAnywhere to get > to > > a > > > > host PC on the network. There is nothing to configure for VNC to > > work > > > > in the router since it has a direct connection to the WAN. > Besides, > > I > > > > cannot connect on the internal address. > > > > > > > > Any ideas as to what could be broken? > > > _______________________________________________ > > > VNC-List mailing list > > > [EMAIL PROTECTED] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list > > _______________________________________________ > > VNC-List mailing list > > [EMAIL PROTECTED] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
