version check failed - could not connect (especially on upnp-ed networks)
hi there,
lately i get a lot of these errors in the about dialobox (win32, latest builds) on networks with upnp routers when wuala client wants to check if theres a newer build out there...
if i close logout/restart wuala it downloads the latest build anyways even if the check in the about box failed.
would be great if the checking for a new build would be more reliable (maybe other protocol, triggering it directly with a button or a url and so on....)
maybe it has also to do with congested networks (even the local lan or the gateway to the inet), or nat-overloads at the gateway or such thing.
somehow i suspect that the versioncheck is also performed by means of udp rather than a tcp check of a browsing of some url/xml/file because the failed message turns up so very quickly/instantly on the client... there seems to be no timeout or something.
thanks.
lately i get a lot of these errors in the about dialobox (win32, latest builds) on networks with upnp routers when wuala client wants to check if theres a newer build out there...
if i close logout/restart wuala it downloads the latest build anyways even if the check in the about box failed.
would be great if the checking for a new build would be more reliable (maybe other protocol, triggering it directly with a button or a url and so on....)
maybe it has also to do with congested networks (even the local lan or the gateway to the inet), or nat-overloads at the gateway or such thing.
somehow i suspect that the versioncheck is also performed by means of udp rather than a tcp check of a browsing of some url/xml/file because the failed message turns up so very quickly/instantly on the client... there seems to be no timeout or something.
thanks.
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Loading Profile...

