No response whatsoever to attempted connection

[JohnSTVr]

I've had TV remote control working on my home PC LAN without problems.  I wanted to test from a distant PC so I took the portable version of TV to a distant (800km!) laptop.  I entered the ID of my home PC and tried to connect.  The laptop indicated it was connected to the server.  The connect button changed to an abort button.  Other than that, nothing happened.  No messages, no authorization dialog.  Even if there were a problem with my home PC, I was expecting a message like "Remote PC is not available".  I have no ideas for troubleshooting since no feedback was given but the server was connected.

[Admin]

ive run into this on occasion and dont really have an explanation, sometimes its the internet connection it seems.  Did you "abort" and retry?

[JohnSTVr]

When I returned to the "remote" computer at home, I found Comodo firewall had recorded some events from TV which were related to TCP between 0.0.0.0 and the loopback 127.0.0.1.

It could be a firewall issue.  I'll try changing the permissions for TV to allow all traffic in and out (presently out only).  I was under the impression that TV did not need any firewall configuration.  Perhaps if someone was at my home PC they could have accepted the connection and permissions would have been set permanently.

Given that my PC gave no response, it still seems strange that no message came from the TV server.  Perhaps once the server has told the attended PC the IP address of the remote PC, it considers its job done.

[Admin]

very likely the issue.
Chnage those permissions and try it.  You can still test it using your local connection with both machines.

[JohnSTVr]

I tried it locally as suggested.  Initially I got the same problem but this time I could see both PCs.  Comodo firewall on the remote PC asked for permission for the loopback connection that I described.  I gave permanent permission and was then able to connect from the other PC via the TV server.  When I looked at the firewall log, it turns out that the culprit seeking permission was Teamviewer_Desktop.exe.

I had previously give TV services and exe permission.  The desktop exe was unexpected and is not mentioned in the manual.  If you were setting this up with no chance of testing before use, you would need to know that.

Thanks for the assistance.

[Admin]

Glad its working.  Hopefully a Teamviewer member ( this IS an unofficial forum, but several teamviewer employees read these threads) will take your troubleshooting and resolution to development.