Re: NDIS IM over NDISWAN on XPSP2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Soquel Dude (ImInSoquel_at_nospam.nospam)
Date: 02/28/05 

Date: Mon, 28 Feb 2005 07:10:58 -0800

I have seen it and posted many messages to this group, but have received no
replies about this.

One suggestion: On a WAN link, make a copy of the packet you pend and
complete the send of the proginal packet. Then, send the copied packet once
you receive the ACK from the MANAGER.

"stan bell" <stan.bell@systemsoft.co.uk> wrote in message
news:uvniqMYHFHA.1996@TK2MSFTNGP12.phx.gbl...
>I have an NDISIM that polices N/W traffic by detecting 'suspect' packets,
> pending them, internally queuing them and then using a worker thread to
> call
> TDI to send a TCP message seeking sanction for the suspect packet from
> another computer (the MANAGER). The MANAGER responds with a go/nogo status
> and the IM driver releases or bounces the suspect packet.
>
> This all works OK on Ethernet and WAN links up to Windows XP/SP1 but with
> SP2 I see the following :
>
> (a) Install XP/SP1 on a machine fitted with a NIC, upgrade to SP2.
> Everything works OK. LAN/WAN traffic is policed.
> (b) Install XP/SP1 on a machine without at NIC. Everything works fine. WAN
> traffic is policed.
> (c) upgrade (b) to SP2 and the following happens :
> When a suspect packet is detected and pended, no further packets are
> presented to the IM driver.
> Meaning that the TCP message containing the sanction request cannot
> reach the MANAGER.
> Nothing proceeds until my 'emergency' timeouts fire.
>
> Has anyone else seen this, or similar, behaviour? Any suggestions for
> avenues for investigation would be welcome.
>
> TIA
>
> Stan
>
>

Relevant Pages

  • Re: Gammon steaks frozen
    ... packet from the chilled bacon section only to find it solid. ... Was going to try and see the store manager, ... But am I right in that you should not refreeze ... I spoke to the seafood manager and told him that it was ...
    (uk.people.silversurfers)
  • Error in send func of socket...............
    ... as soon as two thread (one is manager and the other is worker)client sends the packet.. ... this process died in window 2000 system.... ... " the command at 0x00403168 referred memory at 0x00000010, the memory can not be read" ... Packet size is about 800byte and sound binary packet...... ...
    (microsoft.public.win32.programmer.networks)
  • NDIS IM over NDISWAN on XPSP2
    ... I'm working on a similar NDIS IM driver and from what I ... must copy a packet AND its payload if you intend to queue ... >and the IM driver releases or bounces the suspect packet. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS IM over NDISWAN on XPSP2
    ... Unfortunately I am careful to copy packet and payload for any pended ... Trouble is I need to send a further packet in order to decide whether to ... > Look at this comment block from ptReceive in the passthru ... >>and the IM driver releases or bounces the suspect packet. ...
    (microsoft.public.development.device.drivers)
  • How does NDISWAN work?
    ... does somebody know how NDISWAN makes decisions which WAN link is best for ... "In an NDIS WAN environment, NDISWAN examines the header of the ... descriptor of a send packet and determines over which link the packet will be ...
    (microsoft.public.development.device.drivers)