When connecting to a server running SQL 2000 using Query Analyzer or Profiler, if I then flood my client network port (to a different machine altogether), the server drops the database connection. Why??? And if it is a valid reason, is there anyway to change this to NOT drop the connection?

The network port is only flooded for ~30 seconds.

We are getting a variety of error messages (depending how you connect to the server).

Running through query analyzer returns
Server: Msg 17, Level 16, State 1, Line 0
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Server: Msg 53, Level 16, State 1, Line 0
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

Connection Broken

Running through Profiler returns
Failed to read trace data.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead(recv()).(State 01000)(Code 10054)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. (State 08S01)(Code 11)

Running through various legacy applications (which is why we are doing this testing) returns
20021 [Microsoft][ODBC SQL Server Driver]Communication Link Failure

Thoughts? Suggestions??