In article <00D67DC4-93ED-4668-8210-(E-Mail Removed)>, Subu Anantharam
wrote:
> I have a .NET app that connects to a third-party server on a socket and sends
> data. This works with a test server on the local network, but does not work
> across the frame connection to the third-party server. They see a connection,
> but never see any data coming across.
>
Have you tried capturing the data with something like Ethereal to see what's
actually being sent? It's quite common for TCP "messages" to be delivered in
pieces in a WAN environment. That often causes problems in the application code
dealing with the socket.

Why aren't you using the .NET framework networking classes?

Hope this helps.

Mike

Ethereal shows the data going out. I have done this using System.Net.Sockets.
When I use the .NET classes, the third-party server sees a connection, but no
data. From a pure Win32 app, they see the data as well.
Ethereal shows the connection being made and an ack from the server. Then
the data goes, but never gets acknowledged. So there is a TCP retransmission.
From the server side, they see the connection, but never see any data coming
through.

Thanks
Subu

Mike Blake-Knox" wrote:

> Have you tried capturing the data with something like Ethereal to see what's
> actually being sent? It's quite common for TCP "messages" to be delivered in
> pieces in a WAN environment. That often causes problems in the application code
> dealing with the socket.
>
> Why aren't you using the .NET framework networking classes?
>
> Hope this helps.
>
> Mike
>
>