LimeRidge29
asked on
TightVNC on a 2008 Terminal Server With Custom Ports
Hello All,
I had a great idea (or so I thought). I installed TightVNC 2.0.4 on a 2008 Terminal Server. I did CHANGE USER /INSTALL first. Then I created a bunch of local users, and assigned each one a separate port for TightVNC, and updated the individual TightVNC settings accordingly. I also added the necessary NAT entries on the firewall.
The goal was to be able to allow multiple internal users to be able to RDP to the terminal server, and share their desktops with external users. It seemed to work well with two users. But the third user could not get an external user connected to his desktop.
TightVNC stores its port number in the registry under HKEY_CURRENT_USER/Software /TightVNC/ Server/Rfb Port. But I am unclear as to how HKEY_CURRENT_USER works on a terminal server. If there can only be one set of TightVNC settings in the registry at any given time, then how can TightVNC work with two simultaneous users? And if it works for two, why not three or more?
What am I missing here?
Baffled,
Chris
I had a great idea (or so I thought). I installed TightVNC 2.0.4 on a 2008 Terminal Server. I did CHANGE USER /INSTALL first. Then I created a bunch of local users, and assigned each one a separate port for TightVNC, and updated the individual TightVNC settings accordingly. I also added the necessary NAT entries on the firewall.
The goal was to be able to allow multiple internal users to be able to RDP to the terminal server, and share their desktops with external users. It seemed to work well with two users. But the third user could not get an external user connected to his desktop.
TightVNC stores its port number in the registry under HKEY_CURRENT_USER/Software
What am I missing here?
Baffled,
Chris
ASKER
I understand that TightVNC is not secure, and maybe not the best solution. However, it does provides the flexibility to share the TS desktop externally, or to control a remote user's desktop from the TS, even if that user does not have a publicly accessible RFB IP/Port. It also allows multiple connections to the same session. Both of these features are extremely helpful for our various support scenarios.
For example, if our client needs support, they run VNC Server, and Attach Listening Viewer (our IP/Port) so that we can see/control their desktop from our TS RDP session. Then if we need to involve a third party, we run VNC Server from the TS RDP session, and they can connect via the same IP/Port. We see and control the entire process.
Unfortunately, the whole thing falls apart with more than 2 TS sessions.
I am looking for any VNC-type solution that will meet the criteria above AND work on a Terminal Server. Is TeamViewer worth looking at? Is there something else?
For example, if our client needs support, they run VNC Server, and Attach Listening Viewer (our IP/Port) so that we can see/control their desktop from our TS RDP session. Then if we need to involve a third party, we run VNC Server from the TS RDP session, and they can connect via the same IP/Port. We see and control the entire process.
Unfortunately, the whole thing falls apart with more than 2 TS sessions.
I am looking for any VNC-type solution that will meet the criteria above AND work on a Terminal Server. Is TeamViewer worth looking at? Is there something else?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.itedge.net/blog/2005/04/19/allow-terminal-server-users-to-shadow-users-rdp-sessions/