Steffen Sledz wrote:
> Hmmmm? That's a pity. But as seen in the mailing lists i'm not the only one
> with such problems. May be there is generic workaround for this? Or a guide
> line how to identify the dodgy app?
Unfortunately this is not a very easy task. The failures are provoked in
different ways by different interfering applications, and what works around
one has no guarantee of working for another. Figuring out the responsible
application often involves attaching a debugger to the process while an error
occurs and trying to get a look at the stack, to see any OS hooks that might
have been inserted.
You might get interesting results by running "netsh winsock show catalog" in
a cmd.exe window, as that will show us if there is some other layered service
provider potentially interfering with your networking.
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
