Re: 0xc0040017 FWX E TCP NOT SYN PACKET DROPPED
From: Yossi Attas [MSFT] (yossia_at_online.microsoft.com)
Date: 09/05/04
- Next message: David Norris-Hill: "Re: Windows Update v5 issues and workaround"
- Previous message: Yossi Attas [MSFT]: "Connectivity issues under a SYN flood"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 5 Sep 2004 16:23:02 +0300
Hi Lex,
The error code that you describe usually appears when either side of the
connection end points sends a packet (to the other side) after the
connection has already been closed (from ISA's pov).
To drill down into this issue and link it to the file server connectivity
issue i would suggest that you do the following:
1. Create an ISA log query to show you all the packets that were dropped
with this result code (
0xc0040017 FWX E TCP NOT SYN PACKET DROPPED).
2. Choose one packet and construct an ISA log query to show you the entire
connection history for this packet. You can do it by creating a log query
based on client ip, source port and time.
3. If the issue is what i think it is, you will see that ISA dropped the
packet (0xc0040017) after the connection has already been terminated.
4. The interesting thing would then be to understand whether the connection
was terminated gracefully or abortively.
Can you please provide the above details so we can decide how to continue?
Thanks
Yossi Attas [MSFT]
"penrose.l" <anonymous@discussions.microsoft.com> wrote in message
news:2c8f01c48eb1$add48c40$a501280a@phx.gbl...
> btw : this is not a hacker attempt or anything.
> It's our own clients that copy files from their computer
> to a server , and if they copy large files of around 10 or
> 20 megabytes or more , they will fail during copy ( every
> time at a different % done ).
>
> LexP
- Next message: David Norris-Hill: "Re: Windows Update v5 issues and workaround"
- Previous message: Yossi Attas [MSFT]: "Connectivity issues under a SYN flood"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|