Garratt wrote:
> Checked today if we have a firwall which could be interfering but
> couldnt see any blocks in the Windows firewall and just to be sure I
> added the TortoiseProc, Tortoiseplink and the TSVNCache as exceptions
> but without any results.
> Did however do a wireshark test and got this:
>
> 700 7.565277000 10.0.2.93 10.0.2.201 TCP
> 4992 > http [ACK] Seq=83 Ack=5539 Win=65530 [TCP CHECKSUM INCORRECT]
> Len=0
> 730 9.208239000 10.0.2.93 10.0.2.201 TCP
> 4995 > pcsync-https [SYN] Seq=0 Win=65535 Len=0 MSS=1460
> 731 9.208450000 10.0.2.201 10.0.2.93 TCP
> pcsync-https > 4995 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460
> 732 9.208472000 10.0.2.93 10.0.2.201 TCP
> 4995 > pcsync-https [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM
> INCORRECT] Len=0
> 750 10.539282000 10.0.2.93 10.0.2.201 TCP 4995
>> pcsync-https [PSH, ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM
> INCORRECT] Len=108
> 751 10.548191000 10.0.2.201 10.0.2.93 TCP
> pcsync-https > 4995 [PSH, ACK] Seq=1 Ack=109 Win=65427 Len=1089
> 752 10.560364000 10.0.2.93 10.0.2.201 TCP 4995 >
> pcsync-https [PSH, ACK] Seq=109 Ack=1090 Win=64446 [TCP CHECKSUM
> INCORRECT] Len=198
> 753 10.566565000 10.0.2.201 10.0.2.93 TCP
> pcsync-https > 4995 [PSH, ACK] Seq=1090 Ack=307 Win=65229 Len=59
> 756 10.636184000 10.0.2.93 10.0.2.201 TCP 4995 >
> pcsync-https [PSH, ACK] Seq=307 Ack=1149 Win=64387 [TCP CHECKSUM
> INCORRECT] Len=453
>
> 10.0.2.93 is me, the other one is the server on https.
>
> It appears that for some reason the packages has an incorrect
> checksum. Does this mean anything to you?
Not neccessarily an error - check the wireshark docs on "Checksum
offloading"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-27 12:52:04 CEST