Perhaps this is in the category of muddying the waters vs. thickening the
soup, but I have a simple TCL script that implements a socket server for
simple string transfers. I can send you script (only a few lines of code),
if that would help. It would perhaps help you isolate the problem to either
the server or the client.

I do recall checking the client/server code against C examples in a network
book I have. I will try to dig up the reference and post it. The reference
to handling WSAEWOULDBLOCK sounds awfully familiar: probably a good place to
start.

-----Original Message-----
From: Gene LeFave [mailto:gene_at_tekdata.com]
Sent: Friday, May 10, 2002 11:01 AM
To: sftalk_at_forth.com
Subject: [sftalk] Re: THICKER TCPIP SOUP

Suggestions:

Be sure that the recv on the client handels the WSAEWOULDBLOCK
status differently then other errors.

Verify that the two machines are actually in the expected states, that the
client issued the recv, and the server issued the send.

Double check the network masks, you should be able to ping both ways.

Verify that you are not expecting the packet boundaries to remain intact
over a network. For example, a client might send two 10 byte packets,
but the server might receive a single 20 byte packet. The converse can
also happen, the client can send a 20 byte packet, but the server could
receive this as two packets. A good thing to look for is if the client or
server has two sends or recvs in a row. This is a flag for a common
programming error.

Gene

On 10 May 2002 at 10:51, Dr. Roger Dube wrote:

>
> Let me just thicken the TCPIP soup a bit, following my previous posting...
>
> hostname = localhost on client
> Client and Server on same machine
> All two-way communication works fine.
>
> hostname = IP address on client,
> Client and Server are still on the SAME machine
> All two-way communication works fine
>
> hostname = IP address on client
> Client on second machine on the LAN
> Server still at first machine with IP address used to set
hostname
> on Client
> Connection is made, conversation stops when Server tries to send
a
> response back to Client.
>
>
> ????
>
> I'm only changing the physical machine on which Client is operating...
> seems to me. Sorry, that's the experimental physicist in me trying to use
> experiments to locate the problem.
>
> Again, any ideas would be most welcome.
>
>
>
>
> ----------------------------------------------------------------------
> Dr. Roger Dube
> rdube_at_gate-tech.com
> President
> Gate Technologies International, Inc.
> http://www.gate-tech.com
> Executive Offices:
> 3700 Airport Road Suite 307
> TEL +1.561.392.7404
> Boca Raton, FL 33431-6409
> FAX +1.561.392.7405
> ----------------------------------------------------------------------
>
> This E-mail message and any attachments have been scanned for viruses and
> are believed to be free of any virus or other defect that might affect any

> computer system into which it is received and opened. However, it is the
> responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by Gate Technologies International, Inc. for
any
> loss or damage arising in any way from its use.
>
> This message contains information which may be confidential and
privileged.
> Unless you are the addressee (or authorized to receive for the addressee),

> you may not use, copy or disclose to anyone the message or any information

> contained in the message. If you have received the message in error,
> please advise the sender by reply e-mail to rdube_at_gate-tech.com and delete

> the message.
> Thank you very much.
>
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
> For help with listar commands, send subject "help" to listar_at_forth.com
> Archives are located at http://www.forth.com/sftalk -- check them out!
> Search the archives! Visit http://www.forth.com/search for details.
>

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives! Visit http://www.forth.com/search for details.
Received on Fri May 10 2002 - 11:40:43 PDT