February 11, 2020 (edited) , KOに번역する (번역を見せる) , ENから번역されました (원본을 보여주는)
@desexyvideoclub
With iStripper Network Errors occur for three reasons
1) There was a problem somewhere between the iStripper client and Totem's server or on the server itself.
In this case there is normally nothing you can do except wait until the problem is fixed and retry. Depending on what the problem was (transient glitch or a hardware failure) the required wait may be a fraction of a second or much much longer. If it was due to a problem with your own equipment then you will have to fix it yourself which may necessitate a reboot or resetting your router.
2) Network traffic was high resulting in a slow response from the server. In this case the iStripper client may miss an expected response and declare a Network Error. Depending on just what transaction failed you may need to retry what you were doing, or manually re-synch with the servers or stop and restart the iStripper program. If you wait long enough iStripper will perform a re-synch without manual intervention. In extreme cases you may need to reboot.
3) The iStripper client was too slow resulting in a timeout. This can often be caused by other programs running at the same time which can lead either to iStripper not having enough CPU time or to network congestion. In either case the results are similar to case 2) and the range of solutions are the same.
The third case can arise if you have configured iStripper to start automatically when you boot your PC or login to an account because if you do this then on many systems there will be a lot of other programs initialising themselves some of which will be trying to contact some server or other (e.g.to check for updates). In my case, because I had a slow internet connection, this would cause iStripper to fail to synchronise with Totem's servers almost every time. Even with a good network connection it can still happen, though more rarely. For this reason I start iStripper manually well after any reboot or login has completed and the system is less busy.