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
