Yesterday I attempted to remote desktop session to my customer from my Mavericks Mac to their (probably yosemite) Mac. Teamviewer was getting all the way through the connection handshake to the point that it was minimizing & scooting the initial Teamviewer screen to my dock. ...But-it was not putting up the window with my client's screen, even though she said her end claimed it had succeeded.
I retried/restarted my end a couple of times, had her re-download the Ver 7 QS for Mac off the TV website again, all no go. Finally bailed, and did it the hard way.
Today, I noticed that my Little Snitch firewall had several Teamviewer outbound attempts to different ports on 192.168.0.7, even though my own mac is on the 192.168.1.0/8 network, not the 192.168.0.0/8 network. I had approved the connections the day before without looking at them closely, TV always causes a rush of this crap. (And I call it crap because as far as I have been able to find,there is NO correct documentation for what port ranges and IP addresses or domains to allow through.) In any case, I should have looked more carefully at the time, because I would have noticed this fishy private IP address.
I conjecture that what I am seeing is actually the private IP address for the remote Mac I was trying to establish the connection with, which was of course unreachable from my end.
I have never had trouble with TV before, though I'm hardly a pro. What I am not sure about is whether I have ever actually used it to connect to another Mac. Almost all of my customers use PCs. Note with the attached logs, that I actually did start making the connection attempts until 13:01:45.
I'd love to hear ideas... was this due to a goofy configuration on my client's end?
Thanks,
-Dave
