Wireshark-users: Re: [Wireshark-users] TCP retransmit, HTTP and web page not loading
From: Gerald Combs <[email protected]>
Date: Wed, 25 Jun 2008 09:21:21 -0700
I think Frank might be on the right track here. Inbound packets from
206.191.131.51 max out at 1018 bytes. This seems suspiciously low.

Frank Bulk wrote:
> That's good information.
> 
> If you compare packet traces from the same laptop at the office to that
> website, and then at the customer's site, where does it look different?
> Considering only a layer-2 link is in between the first thing that comes to
> mind is MTU.
> 
> Frank
> 
> -----Original Message-----
> From: Steve Bertrand [mailto:[email protected]] 
> Sent: Wednesday, June 25, 2008 8:41 AM
> To: [email protected]; Community support list for Wireshark
> Subject: Re: [Wireshark-users] TCP retransmit, HTTP and web page not loading
> 
> Frank Bulk wrote:
>> Do the fiber and ADSL connections use different IPs?  Sometimes there are
>> subnet/block-specific issues that cause the problems you describe.
> 
> Yes, they have different IP's.
> 
>> Can you try from the fiber connection on a different block?
> 
> Well, I could, however if I bring the same laptop back to my office and
> 'bypass' the fibre link, give the laptop the same IP as the site on the
> other end of the fibre has (after disconnecting the fibre link), it
> works fine.
> 
> I know that this is due to a problem somewhere between here and the
> remote site, but I haven't found out what. I'm quite confident it's not
> an IP/routing issue, per the test above, and the fact that this is
> literally the one and only HTTP site they have problems with (at least
> so far).
> 
> Although I can't tell for certain, I keep thinking it has to do with the
> retransmission. However, even after reviewing each frame, I'm not
> knowledgeable enough at that level as to understand why the retran is
> happening, whether the packets are ultimately received (not
> knowledgeable enough....yet, that is ;)
> 
> Steve
> 
> _______________________________________________
> Wireshark-users mailing list
> [email protected]
> https://wireshark.org/mailman/listinfo/wireshark-users