On the face of it, it almost looks like a network problem, as the client thinks it has sent all the data and the server has not received it. Is there anything unusual about the network, e.g. a firewall somewhere?
Can you provide the lines from the output of "netstat" relating to port 4200 on both ends? (Sorry, I forget whether windows has netstat or what options it takes.) What would be really nice would be a tcpdump of the traffic, but that may not be easy if you only have Windows machines. If you're comfortable with gdb, perhaps you could run distccd with --no-fork, set a breakpoint somewhere in serve.c, and try to watch what happens as the request comes in. See if it really does just block waiting for network input or if something else comes in. Also, try to think of what is different about that machine compared to others that work properly. Thanks for reporting it so clearly. Regards, -- Martin Linux: The world's best text-adventure game. _______________________________________________ distcc mailing list [EMAIL PROTECTED] http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
