link icon
Ask The Community

Incoming connection TeamViewer_Service.exe but not logged connection

Bunrthaler Posts: 5 ✭✭
edited December 2021 in General Questions


My Firewall reports:

"An incoming connection has been detected and allowed. Process path: C:\Program Files (x86)\TeamViewer\TeamViewer_Service.exe. Address: [removed per Community Guidelines]. Protocol UDP (17). Port: 5353"

However there is no explicit connection in the Connections_incoming.txt logged. So I am very confused what this is "incoming connection" is. Is this an internal Teamviewer process or do I need to check all the devices in my network whether one of them is compromised?





  • Bunrthaler
    Bunrthaler Posts: 5 ✭✭
    edited December 2021

    I am getting more confused. I checked and it is a tablet in my network which owns [removed per Community Guidelines]. The worst there is not even Teamviewer on it!

    As we use dynamic IP addresses it could be that 8 hours ago a different device owned that IP address or that it was free but we usually do not switch the tablet off, so I am quite sure it would have had the same IP.

    Is this normal and expected from TeamViewer_Service.exe or do I need to be worried?