Hi Camille,

seems the configurations have been very different, so comparing didn't
help much.

But I just tried to set all existing file and printer sharing rules to
"block", which did the trick. (While adding a new rule for blocking it
didn't help - seems the firewall simply stops processing rules when one
matches, so my blocking rule didn't overrule the allowing rules...)

See my comments in the issue. Seems I should have simplified the stack
traces - I didn't expect them to look so ugly because of automatic line
breaks (not sure where they come from).

I won't have time to work on a solution myself, but at least the issue
is understood now, confirmed, and assigned to an appropriate developer.

Best regards,
Malte.

MOULIN Camille wrote, On 10/13/10 15:12:
> Dear OOo Dev,
> 
> I'd like to have your opinion on the issue 105283.
> 
> http://www.openoffice.org/issues/show_bug.cgi?id=105283
> 
> In a nutshell, when working with a file using a UNC path, OOo sends a request 
> on
> port 80 and waits for an answer (at the opening and closing of the file). A
> problem occurs when the port is in stealth mode, OOo waits till the timeout,
> which means the application is frozen for 30 seconds or so, which is not
> acceptable from a user pov. 
> I became aware of the problem when one of our client switched his servers to 
> Win
> 2008 server, where stealth mode is set by default. So I imagine that the 
> problem
> will spread quickly.
> 
> Are you already aware of this? (the issue is not confirmed at the moment)
> 
> Could any of yous give me a rough estimate of the efforts to fix that?
> If you can also quickly explain why OOo behaves this way, that would also 
> help.
> 
> Thanks,
> Camille
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to