Noticed I was using connect(...)!=SOCKET_ERROR...connect returns -1 or 0 based on failure or success, not a socket, still worked because SOCKET_ERROR is defined as an int of -1...but should really be connect(...)==0...  Also connect hangs if the socket is bad, got to find a way around this!