(any previous logfile_old is erased when this occurs).This document cannot cover all cases where an error occurs. When this reaches the maximum size, this becomes logfile_old and a new logfile is started. Because of this, the amount of time covered by the logfiles is limited. The password is checked locally on the client.Always remember that logfiles are designed for troubleshooting. TeamViewer does not see or know the password and will never see it. The passage in Stage 3 is a massively oversimplified description to follow the plot of the example and does not reflect how the TeamViewer password validation works. To keep it as simple and as understandable as possible, we decided to use a parable as an example.What is being described below happens within milliseconds and basically not noticeable for users.
In the interest of transparency and people feeling safe and secure we have established a guide to help end-users read the logfiles on a basic level to identify successful and unsuccessful connection attempts for incoming connections.⚠DisclaimerThe following descriptions and information given are massively oversimplified and can never reflect how TeamViewer sessions are actually created.This article intends to provide some basic and limited knowledge that is understandable for everyone. When opening the log files you may find them overwhelming and confusing as there is a lot of data included. However, the log files are accessible for end-users too. GeneralThis article applies to all TeamViewer users.TeamViewer writes log files for TeamViewer staff to identify historical actions, technical troubleshooting and bug find in TeamViewer.In general, these log files are intended for TeamViewer staff and not for end-users. Log file reading - Incoming connection - TeamViewer Support
0 kommentar(er)
