Somehow I replied only to Sven.
Forwarded the email.

On Mon, Sep 21, 2015 at 2:46 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

> On 21 Sep 2015, at 13:45, Andrei Chis <chisvasileandrei@gmail.com> wrote:
>
> Hi Sven,
>
> Switching from ZdcSocketStream to SocketStream fixes the problem.

Thanks Andrei & Volkert for testing. At least you have a workaround now.

> If you want I can give you access to a virtual box installation within the network.
> The easier solution would be through https://www.teamviewer.com/en/index.aspx

OK, I'll keep that in mind. But first, when I find the time, I have to compare ZdcSocketStream to ZdcSecureSocketStream, since some patches were applied to the latter to solve similar issues. This is all quite tricky stuff.

Sven

> Cheers,
> Andrei
>
>
>
> On Mon, Sep 21, 2015 at 12:07 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>
> > On 21 Sep 2015, at 11:45, Andrei Chis <chisvasileandrei@gmail.com> wrote:
> >
> > So adding #beOneShot on some networks that are behind proxies, fails the request.
>
> Well, I was already afraid that (possibly transparent) proxies were involved.
>
> The problem is, it is simply impossible for me to debug this remotely.
>
> One things that you could try is switching the socket stream implementation used by Zn,
>
>�� ��ZnNetworkingUtils default socketStreamClass: SocketStream.
>
> to no longer use ZdcSocketStream.
>
> Sven
>
> PS: Note that this is global setting
>
>
>