Thanks for the response.
I didn't have the instructions exactly right. The Date Client works with the Date Server and the Multiple Client works with the Multiple Server. The instructions are correct in the attached pic. The pic shows what the client screens should show after following the instructions for the Multiple Server and Date Server runs.
You'll see that the second run for the Multiple Client fails on the TCP Open Connection call. That is what I would expect to happen because the listener and the connection have both been closed.
For the Date Client, the second run for the Date Client succeeds the TCP Open Connection call (Post Open error out) even though the TCP connection has been closed and the server VI is in the Delay Loop. There was only one TCP connection and it was closed, so how can that port still accept connections? snoop/ethereal verifies that LabVIEW did accept the connection on the port and the subsequent read fails, which we see in the Post Close error out.
LMK if you see the same thing on your runs.
Thanks for sticking with this Sarah.
When following the instructions, do you get a screenshot that matches the one I included?
If so, then you'll see that after a TCP Listener is closed by the Mulitiple Connections mod server, then next Client Open attempt FAILS (as shown by Post Open error out in the Multiple Connections - Client.vi front panel). This is what I would expect. The server is NOT trying to accept a connection, so the Client cannot connect.
Also, after a TCP Listen is closed by the Data Server mod server, the next Client Open attemp SUCCEEDS (as shown by Post Open error out in the Data Server Client.vi front panel). The server code is not running any code at that point that would accept a connection. So why can the Client connect? It should not be able to.'
Message Edited by sarahk on 06-26-2006 09:42 PM