Windows socket scripts can be and usually are horrendous to work with & i woud suggest best avoided unless this is the only method of capturing your transactions.
I would suggest though that if you have to use Windows Sockets that you ensure EVERYTHING which does not have to be running and all un-necessary applications be switched off. I once had a problem with a socket being opened to an IP address that wasn't on our hosts table and it turned out to be the exchange mail server as we still had an e-mail client enabled.
Best of luck.
[This message has been edited by coling (edited 01-16-2002).]