Software Caused Connection Abort (10053) on Client

Sorry, but I'm really stumped and I think I have a Windows issue here.
We have a VMWare stack simulating many agents connecting to a Windows
server. We are running jobs in batches of 25 agents at a time. When a
job is sent to an agent, it then calls back to the server to post
results.

Sometimes, some or all of the 25 agents in a batch will fail with
Software Caused Connection Abort as the agent is trying to WRITE to the
server. 

My initial thought was that the backlog value was too low on the Windows
Server. However, wouldn't this give me a Connection Refused exception
rather than a Connection Abort on Write exception?!?

Taking a look at a snoop on the server, what I do notice is that after
accepting the socket from the agent, the server sends a FIN and then
immediately afterwards a RST. Normally there is an ACK in between, but
in this case the FIN doesn't even appear to wait for one before calling
RST. What causes this sort of sequence on the server socket? Could it be
the backlog or some stupid SYN ATTACK code windows has slipped into it's
2003 Server?

Any ideas appreciated. And remember this is intermittent and it only
seems to happen with Windows Servers. If I use Linux or Solaris as a
server we do not get this intermittent issue.

R.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html