| || |
Socket connection abort: timeout?
We just moved into a new building, and our corporate LAN isn't completely reliable yet. I'm running remote testing (ST local, agent remote, both Windows NT variants), and it runs fine until the network drops out.
Once data has been dropped, it seems like the remote agent drops the connection (is available for use again) but the local machine thinks it keeps on churning, and will just do nothing on either the remote or local end. Once I abort the run manually, I get the error "Socket Connection Abort".
Is there a setting I'm overlooking? It'd be nice if the local host was smart enough to reconnect, but if it can't it'd be okay if it would at least timeout. If there is a combination of server/agent I could use that avoids this problem, that'd be good input too.