Remote Control Windows does not appear

[el_joca]

Hi!

The connection to the TV client seems to have any problem, but the remote control window dos not show. By the behavior of the TV main window I can say that everything it's working fine, except the point I mentioned...

Does anyone had this problem before?

Another point that sometimes happens to me is when the client is on a session lock state. TV connects but it goes down immediately and an error message shows, where I can read that problem is on the locked session state on the client's side.

Any help will be really useful!

Thank's a lot!

[ERS]

what do you mean by the remote control window does not show?  Do you mean the window on your side showing the desktop of the remote machine?
Have you been able to see the window prior to this?  How long has this been happening?

[el_joca]

Hello.

Yes I mean the window on my side, showing the remote machine's desktop. Apparently TV is connected, as it doesn't show any error message.

THis happened first yesterday, but on the day before I was able to connect without any problems.

Thanks!

[ERS]

Sometimes its just the internet connection.  Give it a day or two, also can you have the remote machine rebooted?
reboot and modem or router as well.( power cycle)
Be sure as well that the remote machine is not set to go in to hibernation.

[tarpanet]

I too, have seen this problem.  Restated, When attempting to establish a session from my local PC to a remote PC, the session is "established", however, what I see on my screen is, the local TV panel goes away, and I see NO view of the remote PC.  Typically, I will acquire a view of the remote on the 3rd connection attempt.  Then, I notice 3 active sessions in the remote's TV panel.  I have been disconnecting the top 2 sessions, and carrying on with my tasks.  But this is annoying.  So far, I see no way to prevent this from occurring.  Note, that this particular remote is running Windows XP, and it is the only one of 4 PCs exhibiting this issue.

[tarpanet]

It dawned on me that changing from UDP to TCP might resolve the problem.  So, I made the change, and tested connecting to the one PC which I'd been having trouble with.  It seems to have resolved my issue.  The setting is under; Extras/Options/Advanced/Advanced Network Settings/ --- Uncheck "Use UDP (recommended)".  I'd venture to guess that UDP is recommended because it normally results in higher performance than TCP.  However, TCP provides guaranteed packet delivery, whereas UDP does not.

You're not going break anything by trying this.  The worst that can happen is you "might" notice the remote's mouse doesn't move around quite as fast.  Of course, the real test is, does this fix the problem of establishing a session, and actually seeing the remote's display?

[matt]

Today I have one machine that I can't create a 'visible' connection to.

Tried in Ver6 and Ver 7.

Other machines seem to connect fine.

This one machine looks like it is connecting, but the connection window just doesn't show.

The logs show
2011/12/19 16:36:49.666  3148  5048 S0   Reading partners public key
2011/12/19 16:36:49.666  3148  5048 S0   Encrypting and signing session key with RSA
2011/12/19 16:36:49.669  3148  5048 S0   Sending encrypted session key
2011/12/19 16:36:49.772  3148  5048 S0   Encryption confirmed by partner

Which is the place it stops when asking for the connection password to the machines that work.

I tried entering the password, in case the 'TeamViewer Authentication' window was 'hidden' or of the screen, but no connection success.

I also tried forcing TCP rather than UDP as suggested above, but still no success.

I'll try a restart of the remote machine next...

[DaPsycho]

It dawned on me that changing from UDP to TCP might resolve the problem.  So, I made the change, and tested connecting to the one PC which I'd been having trouble with.  It seems to have resolved my issue.  The setting is under; Extras/Options/Advanced/Advanced Network Settings/ --- Uncheck "Use UDP (recommended)".  I'd venture to guess that UDP is recommended because it normally results in higher performance than TCP.  However, TCP provides guaranteed packet delivery, whereas UDP does not.

You're not going break anything by trying this.  The worst that can happen is you "might" notice the remote's mouse doesn't move around quite as fast.  Of course, the real test is, does this fix the problem of establishing a session, and actually seeing the remote's display?

I had this problem too, but your advice made it work, thanks a lot!!

[samurye]

Had this problem just now. ALT + TAB fixed it.

[gonzzza]

Teamviewe 8.0.16642 (had the same issue with TW7), Vista 32bit - I have the same problem. After establishing connection the window with remote PC desktop does not appear.

Alt-tab, disabling UDP - didn't help. Looking for a solution.