Interesting...

We tried what you said, with some definately odd results:

Started server, started client A.
Ctrl-C'd client A and restarted it.
Got the same result we had been getting. It says it connects, sends a message, and sits waiting for an ACK.

Then, we started client B on another machine. It also says it connects, sends a message, and waits for an ACK.

Now...if I understand sockets correctly, you can't have 2 connections made to the same port, unless you are handing off connections to another handler for processing, and leaving the original port open for new connects, right?

Since I'm not doing any of that....how can this be?

Is this a client problem?
Is the OS (Win32) doing some internal stuff I'm not aware of?


-HaB


hword.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.