-debugmsg +winsock yeilds a little information, but not much. i tried a -debugmsg +all, but that filled up my hard disc and caused X to crash. What can I do to help further determine the problem?
Try a +relay trace. For something as vague as this you need to investigate further really, there is an infinite multitude of things that could be going wrong.
you can also edit dlls/winsock/socket.c and set DEBUG_SOCK_ADDR to 1, you'll get a bit more of traces A+