> So it's not a network timeout or anything like that. That’s exacty what it is (a network issue). Proxying issue somewhere possibly, used to see them in cases where both the client and server were behind proxies, and there were TCP handshake issues. -- Scott