Bugzilla

(In reply to mark from comment #8)
> So, as I understand it, the workaround is to take TB off-line, then change network connections, then bring TB back on-line. Did I get that right?  Thx.

I did myself encountered such issue with TB when using vpn especially in work environent where IP of mail server (or other intranet services) change due to vpn connection to an internal ip (traffic routed via vpn) vs external IP (direct Internet access).

Upon network interface change events (such as connection/disconnection), I noticed that putting TB offline and back online never sorted the issue because it does not clear/update/invalifate TB internal DNS cache, nor ipconfig /flushdna on Windows does (because TB uses its own cache mechanism, it seems), nor clesring TB cache.

Workarounds always been to exit TB and restart it or wait for TTL to expire (internal IP TTL set to 5mn to reduce inconvenience) but none of those are ideal. TB should be able to detect changes in network connevtivity and "adapt" autonatically to the environnent.

This issue has already been reported but never been fixed. I am glad to see it is reported here and that there is now a glimpse of explanation about the possible cause. My view on the matter is that it should be considered as a bug not as a feature request ;-)

(In reply to mark from comment #8)
> So, as I understand it, the workaround is to take TB off-line, then change network connections, then bring TB back on-line. Did I get that right?  Thx.

I did myself encountered such issue with TB when using vpn especially in work environent where IP of mail server (or other intranet services) change due to vpn connection to an internal ip (traffic routed via vpn) vs external IP (direct Internet access).

Upon network interface change events (such as connection/disconnection), I noticed that putting TB offline and back online never sorted the issue because it does not clear/update/invalifate TB internal DNS cache, nor ipconfig /flushdna on Windows does (because TB uses its own cache mechanism, it seems), nor clearing TB cache.

Workarounds always been to exit TB and restart it or wait for TTL to expire (internal IP TTL set to 5mn to reduce inconvenience) but none of those are ideal. TB should be able to detect changes in network connevtivity and "adapt" autonatically to the environnent.

This issue has already been reported but never been fixed. I am glad to see it is reported here and that there is now a glimpse of explanation about the possible cause. My view on the matter is that it should be considered as a bug not as a feature request ;-)

(In reply to mark from comment #8)
> So, as I understand it, the workaround is to take TB off-line, then change network connections, then bring TB back on-line. Did I get that right?  Thx.

I did myself encountered such issue with TB when using vpn especially in work environent where IP of mail server (or other intranet services) change due to vpn connection to an internal ip (traffic routed via vpn) vs external IP (direct Internet access).

Upon network interface change events (such as connection/disconnection), I noticed that putting TB offline and back online never sorted the issue because it does not clear/update/invalifate TB internal DNS cache, nor ipconfig /flushdna on Windows does (because TB uses its own cache mechanism, it seems), nor clearing TB cache.

Workarounds always been to exit TB and restart it or wait for TTL to expire (internal IP TTL set to 5mn to reduce inconvenience) but none of those are ideal. TB should be able to detect changes in network connectivity and "adapt" automatically to the environnent.

This issue has already been reported but never been fixed. I am glad to see it is reported here and that there is now a glimpse of explanation about the possible cause. My view on the matter is that it should be considered as a bug not as a feature request ;-)