Another "Could not connect to partner" bummer!

I have reviewed a lot of messages having the same or similar subject matter.  Here is my addition to the problem:

  1. Two LAN machines,
  2. personal use,
  3. ping works both ways,
  4. Windows 10 machine cannot connect to Windows 7 machine,
  5. Windows 7 machine can connect to Windows 10 machine,
  6. Re-installed TeamViewer on Windows 10 machine,
  7. Both machines run same version 15.1.3937,
  8. Re-installed TeamViewer on Windows 7 machine: no version change,
  9. Both machines restarted after manually closing all open programs,
  10. Windows 7 machine is a Dell Optiplex 990,
  11. Windows 10 machine is a Lenovo Legion Y520,

Prior to this episode I had bilateral communication between both machines.

My research on this problem shows complaints extending back in time to 2006.  Do the programmers in the IT department ever read these community messages?

I'm open to having them contact me using TeamViewer and getting (hopefully) to the bottom of this problem.

Rod

For me to believe is insufficient for you to know - rodalsa

Tagged:

Comments

  • JeanK
    JeanK Posts: 7,052 Community Manager 🌍

    Hello @rodalsa

    Thank you for your message. ?

    This might be fixed woth the latest update: TeamViewer v15.2.2756

    Could you please update your clients and try again? ?

    Many thanks in advance for your feedback!

    Cheers,

    Jean

    Community Manager

  • It has been a while since i posted the above message. I'm back with the same problem with these system parameters...

    1. Desktop's OS is Windows 7 Pro running TV version 15.13.6 (32 bit)
    2. Lenovo's OS is Windows 10 running TV version 15.13.6 (32 bit)
    3. Command prompt Pings successfully 7 to 10 and 10 to 7
    4. 7 connects to 10 as controller.
    5. 10 FAILS to connect to 7 as controller.
    6. This message has been typed at 7's keyboard while viewing 7's monitor.
    7. This message will be posted via 10's keyboard and screen.
    8. My VPN's kill switch is OFF on both systems.
    9. Where do we go from here?
  • I had a similar problem that was fixed by changing the permissions in the win fire wall. It started after an update when apparently the permision for teamview was changed. It may a good idea to check that ??

    Cheers ....... Blakey