Thanks for your reply, and thanks to the other respondent as well. I didn't realize it yesterday but it turns out that I am in fact having intermittent packet loss /connectivity issues and will have the ISP work on correcting it.
I will also have my developer change the hosts settings as you describe.
OK. I *think* this may be what I want. Over the weekend I will have a server available to test on. The scenario I need to support is where I have approximately 10 or more users who all remote into a terminal/rdp server for their daily work.
In the case of [censored] there is a "console 9 character ID" that is assigned to the "machine itself", and if you connect to that then it's as if you are sitting at the console of the server. However, each RDP / session (or user profile) also has its own separate 9 character ID. I think it is assigned per user profile?
So if I want to support a particular user they just tell me their TV ID and I connect to it, and so I am connected to their session and I am on the same desktop.
I want the same functionality in RU - I want to do a support session with them on their desktop. I *don't* want the RDP behavior of taking over a session and kicking the exisitng user off their session.
I think TV's way of doing this only works for Internet 9 character connections, not for direct IP connections, because the server will (usually) just have one IP for all users?