I am trying to provide remote support to our customers that are running under terminal services. However, I am encountering some bizarre problems with a couple of experiments I am trying with our local terminal server. If I launch the VNC server in user mode by issuing the following command: winvnc4.exe -noconsole and then hover over the VNC icon with my mouse, I see the words: "Not accepting connections." Now, this makes sense, because we already have the VNC server running under the console session using port 5900. However, if I specify a different port by issuing the command: winvnc4.exe -noconsole -portnumber 5901 and then hover over the VNC icon with my mouse, it shows the IP address of the terminal server. What is weird, though, if I right click on the VNC icon and go to the options menu and then select the connections tab, the program states it is accepting connections on port 5900, not 5901. Why the discrepancy? Furthermore, if I attempt to initiate a reverse VNC connection from the terminal services session to another computer on the LAN, I receive the message "read: Connection reset by peer (10054)" from the listening VNC viewer. Is there a way to perform a reverse VNC connection from within terminal services? Thank you for your help.
Vincent _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
