Author Topic: Cannot connect to TV computer  (Read 5627 times)

mipial

  • Newbie
  • *
  • Posts: 2
Cannot connect to TV computer
« on: December 20, 2015, 09:33:00 AM »
Hello all. I'm a newbie. I just downloaded and installed TV on three computers. All of them are Windows 7 64-bit.
First I installed it to my mediacenter/fileserver using VNC from a laptop. It went OK. Then I installed it to the computer I was VNC'ing from.
I don't know it the install went right, because it did not show me the presentation screen after installing (as it did back with the mediacenter), but the icon was there and it let me control the mediacenter PC.
Then I installed it to another laptop that I had beside me. Upon testing I noticed it was able to control the mediacenter but not the other laptop. It said "connecting" for a while and then "ready to connect". The screen in laptop 1 would blink for a moment but then it went back to normal. File transfer works only from laptop 2 to laptop 1, but not the other way round. Invitations from laptop 2 to laptop 1 work, though. I have installed TV on my android phone and the same happens: It can control both laptop 2 and mediacenter, but not laptop 1.

I have tried it with laptop 1's windows firewall up and down. I have also unistalled TV completely from laptop 1 using revo and reinstalled both normally and in administrator mode. Sometimes laptop 2 says "connecting" and then "ready to connect". Once in a while it will say "protocol negotiation failed" regardless of the firewall status.

So, the only thing I have left is reinstalling laptop 1, an idea I don't like at all. It's the kids' computer, so I'd like to control it.

I hope someone can help me about this problem. Thank you very much.

mipial

  • Newbie
  • *
  • Posts: 2
Re: Cannot connect to TV computer
« Reply #1 on: December 20, 2015, 10:28:27 AM »
This is the log from the last connection attempt (via Android APP)

2015/12/20 18:22:40.117  3356  3596 S0   Activating Router carrier
2015/12/20 18:22:40.117  3356  3596 S0   CommandHandlerRouting[33]::CreatePassiveSession(): incoming session via server21802.teamviewer.com, protocol Tcp
2015/12/20 18:22:40.117  3356  3596 S0   Starting desktop process for ID 727125661 in session 2
2015/12/20 18:22:40.148  3356  3596 S0   CTerminalServer::getPathToApplicationExe(): Choosing filename from partner process.
2015/12/20 18:22:40.148  3356  3596 S0   Filename for desktop process is c:\program files (x86)\teamviewer\TeamViewer_Desktop.exe
2015/12/20 18:22:40.148  3356  3596 S0   CToken::GetSystemToken() set session 2
2015/12/20 18:22:40.164  3356  3596 S0   Desktop process started, PID=6500
2015/12/20 18:22:40.164  3356  3596 S0   CTerminalServer::StartGUIProcess() Not starting GUI, reusing existing
2015/12/20 18:22:40.164  3356  3596 S0   ConnectionGuard: incoming remote control in sessions: 2(1)
2015/12/20 18:22:40.164  5144  5540 G2   Connection incoming, sessionID = -1602656119
2015/12/20 18:22:40.554  3356  5448 S0   CAcceptServer::HandleAccept: new connection from 127.0.0.1:51732
2015/12/20 18:22:40.554  5144  3792 G2   Received Control_InitIPC processtype=4
2015/12/20 18:22:40.554  3356  3596 S0   CInterProcessNetwork::SetDyngateIDforSession() id=727125661 session=2 ptype=2
2015/12/20 18:22:40.554  3356  3596 S0   CInterProcessNetwork::SetDyngateIDforSession() id=727125661 session=2 ptype=4
2015/12/20 18:22:40.678  3356  5460 S0   Negotiating session encryption: client hello received from 727205503, RSA key length = 2048
2015/12/20 18:22:40.694  3356  5460 S0   Negotiating session encryption: server hello sent
2015/12/20 18:22:40.164  6500   776 D2   Logger started.
2015/12/20 18:22:40.507  6500   776 D2   TeamViewerDesktop started, PID=6500
2015/12/20 18:22:40.522  6500   776 D2   Monitors: Generic PnP Monitor, \\.\DISPLAY1, 1600x900 (0,0), flags=3, dpi=96
2015/12/20 18:22:40.554  6500   776 D2   MachineHooks: Initialized Shm
2015/12/20 18:22:40.554  6500   776 D2   MachineHooks: refcount = 10
2015/12/20 18:22:40.554  6500   776 D2   MachineHooks: x64 Machine detected
2015/12/20 18:22:40.554  6500   776 D2   InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
2015/12/20 18:22:40.554  6500   776 D2   Opening local TCP connection to 127.0.0.1:5939
2015/12/20 18:22:40.554  6500   776 D2   Local TCP connection established
2015/12/20 18:22:40.554  6500   776 D2   SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
2015/12/20 18:22:40.569  6500   776 D2   Received Control_InitIPC_Response processtype=1
2015/12/20 18:22:40.569  6500   776 D2   Received Control_InitIPC_Response runningProcesses=7
2015/12/20 18:22:40.569  6500   776 D2   Received Control_InitIPC_Response processtype=2
2015/12/20 18:22:40.569  6500   776 D2   Control_InitIPC_Response: all processes 7 completely initialized
2015/12/20 18:22:40.866  6500   776 D2   InterProcessBase::SecureNetwork created
2015/12/20 18:22:41.022  3356  5460 S0   Negotiating session encryption: client handshake received
2015/12/20 18:22:41.037  3356  5460 S0   Negotiating session encryption: server handshake sent, encryption established with AES key length 256
2015/12/20 18:22:41.131  3356  3596 S0   UDP: ProcessHandshake: (*)
2015/12/20 18:22:41.131  3356  3596 S0   Initializing transmission control v1
2015/12/20 18:22:41.458  3356  5448 S0   UDP: sending master pings ...: (*)
2015/12/20 18:22:41.568  3356  5448 S0   UDP: connectivity: a=79.150.135.241 p=54843: (*)
2015/12/20 18:22:41.568  3356  5448 S0   UDP: punching: (*)
2015/12/20 18:22:41.568  3356  5448 S0   UDP: PingOK.PunchInit: (*)
2015/12/20 18:22:41.755  3356  5460 S0   UDP: SendUDPPunches: (*)
2015/12/20 18:22:41.770  3356  4448 S0   UDP: punch received a=192.168.1.102:57548: (*)
2015/12/20 18:22:41.770  3356  4448 S0   UDP: send UDPFLOW_PUNCHRECEIVED: (*)
2015/12/20 18:22:41.770  3356  4448 S0   UDP: SendUDPPunches: (*)
2015/12/20 18:22:41.770  3356  4448 S0   UDP: received punch: (*)
2015/12/20 18:22:42.067  3356  5448 S0   UDP: punch ignored a=192.168.1.102:57548: (*)
2015/12/20 18:22:42.067  3356  5448 S0   UDP: send UDPFLOW_PUNCHRECEIVED: (*)
2015/12/20 18:22:42.129  3356  3596 S0   UDP: send UDPFLOW_MTUTESTRECEIVED (size = 448): (*)
2015/12/20 18:22:42.129  3356  5456 S0   UDP: send UDPFLOW_MTUTESTRECEIVED (size = 1008): (*)
2015/12/20 18:22:42.160  3356  5456 S0   UDP: send UDPFLOW_UDPSENDPOSSIBLE: (*)
2015/12/20 18:22:42.160  3356  5448 S0   UDP: send UDPFLOW_UDPSENDPOSSIBLE: (*)
2015/12/20 18:22:42.160  3356  5460 S0   UDP: send UDPFLOW_UDPSENDPOSSIBLE: (*)
2015/12/20 18:22:42.160  3356  5460 S0   UDP: send UDPFLOW_UDPSENDPOSSIBLE: (*)
2015/12/20 18:22:42.176  3356  5448 S0   UDP: send UDPFLOW_MTUTESTRECEIVED (size = 448): (*)
2015/12/20 18:22:42.176  3356  5456 S0   UDP: send UDPFLOW_MTUTESTRECEIVED (size = 1008): (*)
2015/12/20 18:22:42.270  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5456 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5456 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5456 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.301  3356  5448 S0!  UHP.DispatchCmd: ignore ccmd type 64
2015/12/20 18:22:42.332  3356  5456 S0   UDP: UDP prepare switch received: (*)
2015/12/20 18:22:42.332  3356  5456 S0   UDP: create udp connection was successful: (*)
2015/12/20 18:22:42.332  3356  3596 S0   CarrierContainer.SendCarrierSwitch: state=1, carrier=2
2015/12/20 18:22:42.363  3356  5456 S0   UDP: delegate received datagram: (*)
2015/12/20 18:22:42.504  3356  5456 S0   CarrierContainer.ProcessCarrierSwitch: state=2, carrier=2
2015/12/20 18:22:42.504  3356  5456 S0   Activating UDP carrier ...
2015/12/20 18:22:43.426  3356  5456 S0!! CTcpProcessConnector::HandleRead error 10054 reading from process 6500: An existing connection was forcibly closed by the remote host
2015/12/20 18:22:43.426  3356  5456 S0   CTcpProcessConnector::CloseConnection(): PID=6500
2015/12/20 18:22:43.426  3356  5456 S0!! CInterProcessNetwork::NewInterProcessDataAvailable(): ReadFailed session=2 ptype=4
2015/12/20 18:22:43.442  3356  5456 S0   UpdateOnlineState newOnlineValue 1
2015/12/20 18:22:43.442  3356  6560 S0   Process 6500 in session 2 has terminated
2015/12/20 18:22:45.845  3356  3596 S0   Estimated RTT to Router: 97 ms, Reliability: 2, Carrier: 1
2015/12/20 18:22:48.435  3356  3596 S0   SessionInformationManager[33]::TerminateWindowsSession(): terminating TVSession -1602656119 in WindowsSession 2 isOutgoing: 0
2015/12/20 18:22:48.435  3356  5460 S0   CarrierContainer.SendCarrierSwitch: state=2, carrier=1
2015/12/20 18:22:48.435  3356  5460 S0   UdpCarrierDeactivationState::DiscloseStateToCarrier: empty send buffer is not flushed
2015/12/20 18:22:48.435  3356  5460 S0   Activating Router carrier
2015/12/20 18:22:48.435  3356  5456 S0!  UdpConnection[48]: UDP statistics: nb=23
2015/12/20 18:22:48.513  3356  5460 S0!  Carrier[33]::EndCarrierInternal: Discarded 1 commands, ClientID 727205503, ShutdownGracefully 1, SessionType_RoutingSession
2015/12/20 18:22:48.513  3356  5460 S0   ConnectionGuard: no restrictions
2015/12/20 18:24:49.371  3324  6844 H32  unlocker1.9.2.exe: dll can unload now
2015/12/20 18:25:13.390  6424  6028 H64  unlocker.exe: dll can unload now
2015/12/20 18:25:25.293  4180  1864 H32  chrome.exe: dll can unload now
2015/12/20 18:26:07.143  6776  6832 H64  defraggler64.exe: dll can unload now

Admin

  • Administrator
  • Sr. Member
  • *****
  • Posts: 456
Re: Cannot connect to TV computer
« Reply #2 on: December 20, 2015, 12:31:12 PM »
sometimes there a glitch that causes connection issues.
Ive found that clicking on "connect" waiting a second or two then clicking abort connection then reconnecting can help
make sure you don't already have another connection going at the same time.

parker5678

  • Newbie
  • *
  • Posts: 1
Re: Cannot connect to TV computer
« Reply #3 on: December 26, 2015, 08:19:45 PM »
:)

 

anything