From: Maximum V. <ven...@ms...> - 2011-02-28 17:27:33
|
hi John i've tried netstat like you said. the list is not very long and port 21 and 80 certainly do not show up. the error the viewer gives comes in a message box with the title "TightVNC info" and having the text "Failed to connect to server(ip:port)" where ip and port are what what i entered. the message takes some time to appear when i connect through the internet. it's almost immediate when i use the 127.0.0.1:80 Subject: Re: viewer not connecting to port 21 and 80 Date: Tue, 1 Mar 2011 05:08:41 +1300 From: John_Serink@Trimble.com To: ven...@ms...; vnc...@li... Do you have a webserver running on port 80 already? What does event viewer tell you? Are ther any errors? With the tightvnc server off, do you see anything on port 80 from this command: Netstat -a -p tcp -n -o If you do see something on port 80, use the pid to identify the process...its likely the default webservice. Turn that service off and tvnc will work on port 80. Cheers, John From: Maximum Venom To: vnc...@li... Sent: Tue Mar 01 04:10:54 2011 Subject: viewer not connecting to port 21 and 80 i'm using TightVNC 2.0.2 on Windows 7. the viewer seems to have trouble connecting to port 80. the viewer will not connect with a loopback to 127.0.0.1:80 but it will connect with a loopback to 127.0.0.1 (using the default port 5900). i have tested this with my router using port forwarding with connections from the outside.- public port 5900 -> private port 80 (so vnc server on port 80) works- public port 80 -> private port 5900 (so vnc server on port 5900) not working so i think the viewer has a problem with connecting to port 80. port 21 seems to have exactly the same issue. a few other ports i have tried seem to work fine. what's the problem? |