Falling's problem sounds exactly like mine! i tried the 'netsh winsock reset' in cmd prompt. before that though, i used the 'netsh winsock show catalog' to see the before & after of resetting the catalog to find out whether any entries were removed and which ones these were.

Before:
Address Family: 17
Max address length: 20
Min. address lenth: 20
socket type: 2
protocol: -3
protocol chain length: 1

After is the same.

I also tried the 'netsh int ip reset resetlog.txt'
& here's the results:-


reset Linkage\UpperBind for PCI\VEN_8086&DEV_103D&SUBSYS_05221014&REV_81\4&39A85202&0&40F0. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for PCI\VEN_8086&DEV_4220&SUBSYS_27128086&REV_05\4&39A85202&0&10F0. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for MF\PCMCIA#XIRCOM-CREDITCARD_ETHERNET_10/100_+_MODEM_56-C027\1#CHILD0001. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

<completed>

<completed>