This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Some packets in a split message not being received by device on RED network

I'm investigating failure to connect to Azure SQL Database from a client connected to a Sophos RED 50.  The RED is attached to our XG, running on a VM in Azure.  I'm comparing a Wireshark trace from the client and a Packet Capture on the XG.  They agree up to the point of a TDS7 pre-login message being sent from the client and forwarded out from the XG (1).  The Azure DB then send back a large message, split over three packets (2 & 3).  The packet capture on the XG shows all three being received and forwarded to the RED.  The Wireshark capture on the client behind the RED sees only the last packet (3).

I'm not sure what to do now:

  • Have I misunderstood what's occurring?
  • Is this a known bug?
  • Are there any settings I can change to modify this behaviour?

Please help!

 



This thread was automatically locked due to age.
Parents Reply Children
  • Cheers again ManBearPig.

    The separate traces on the WAN and RED interfaces show the same thing - all three packets in that message get to my RED interface on the XG.  They still aren't received by the client, so I'm guessing that they must be discarded or lost by the RED itself.

    I'll update the support ticket I have open with these results as well, as ask for guidance on debugging the RED.

  • Most of the time, this is not an RED issue. If the packet goes correctly to the RED Interface on XG, the packet will be transferred by the RED. But most of the time, the client does something wrong with this packet. 

    You could confirm this with a wireshark dump on the client at the same time. But this dump has to be at the same time. 

  • I've been running the Wireshark trace on the client at the same time - the packet is just not seen on the client, it never seems to make it to the laptop's NIC.