That is actually a correct behavior. If you connect through an internet-ID server, the Host is "invisible" for the Viewer. The ID server doesn't translate the IP address to the Viewer, and in most cases there is no point to do that - by definition the Internet-ID connection is used when you want to reach a remote computer located behind a router and/or firewall. Therefore, the IP address of the Host in this case will be the IP address of the router.
The file which is falsely detected is rutview.exe, it's the Viewer executable file. It can be found in C:\Program Files\Remote Utilities - Viewer\. You need to zip the file before uploading - the form doesn't allow files more than 10Mb to be attached.
This would stop any rouge users fr om gaining access without the end user noticing?
Informational messages won't stop anyone, of course. No one can protect the user enough, if they don't want to protect themselves and follow even the basic "don'ts" such as "don't click on links in emails received from strangers".
The purpose of the message is rather different. They target users who are aware of the dangers of the "Interwebz" and are capable to protect themselves if warned. So such message will gently notify the user about software that they may or may not have authorized and provide guidance on what to do in the latter case.
The Issue is with actual installation, where there is a large group of users we prefer to not to harass them with popups or prompt wh ere it could inundate a support person with 100's of calls to ask whats going on etc.
In the new 6.6 update the whole process is going to be much less intrusive. And the most important thing is that an admin will be able to connect right away without waiting the user's input. The single informational message is supposed to replace two other messages currently shown - the one that asks for permission to send an email and the message that warns about Internet-ID being generated.
It's one thing to make rogue software from legitimate software by patching it or putting it in a wrapper - either way is in itself illegal and violates our EULA. We bear no responsibility for the consequences of such abuse of our program, and that is clearly stated in our EULA.
And it's an entirely different thing to provide perfect rogue software out-of-the-box. We don't do that and never will. Remote users must always know that they are being monitored or are about to be monitored. Why would an admin want to hide that fact from a user? An organization must have rules and procedures that allow IT department to remotely log in to employee's computers for maintenance, support etc. So the employees shouldn't be surprised when they see a warning message.
Regardless of how many customers or contracts we may lose, we won't make completely silent rogue-like software. We respect user's privacy, as well as local and international laws. I wouldn't say this is a short sighted strategy. Money is important, but law and respect for ordinary folk is above the money.
Update on this issue. In the upcoming release 6.6 we decided to implement it differently. The program will be installed without requiring a user to accept anything and you 'll be able to get access right away. There will only be an informational message in the bottom right corner that says the program was installed.
That message is necessary to at least somehow let the user know. Once they click "Got it" in the message it'll disappear and will no longer be shown. Their clicking or not clicking the "Got it" button, however, doesn't affect your ability to connect right away. As I said, it's just a warning/informational message.