Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • in reply to: WinpkFilter 3.0: Wireless Access Failure #6659

    Thanks for the investigation you have performed. It is often difficult for us to ask and assist customers to uninstall existing software from their machines to help diagnose problems.

    On our side we have tracked down the second half of this problem to a line of code in our application. Once that line of code was executed, an adapter could no longer have its DHCP assigned IP address renewed. For example:

    ipconfig /release

    followed by:

    ipconfig /renew

    The problem would then remain until the network device is reset or the machine is rebooted (even after the driver is closed and the application is shutdown). The code we are using to manage a network adapter is as follows:

    public Adapter(IntPtr hDriver, IntPtr hAdapter)
    _buffer = new INTERMEDIATE_BUFFER();
    _ptrBuffer = Win32Helper.Malloc(Marshal.SizeOf(_buffer));
    _request = new ETH_REQUEST(hAdapter, _ptrBuffer);
    _event = new ManualResetEvent(false);
    /* Ndisapi.SetHwPacketFilter Locks adapter until reset */
    Ndisapi.SetHwPacketFilter(hDriver, hAdapter, (uint) NDIS_PACKET_TYPE.NDIS_PACKET_TYPE_DIRECTED);
    Ndisapi.SetAdapterMode(hDriver, ref mode);
    Ndisapi.SetPacketEvent(hDriver, hAdapter, _event.SafeWaitHandle);

    Once we commented out the ‘Ndisapi.SetHwPacketFilter’ line the problem disappeared. Having reviewed the sdk sample code, I can see that SetHwPacketFilter is only used to set and restore the device from promiscuous mode; nevertheless, I wouldn’t have expected that outcome.

    in reply to: WinpkFilter 3.0: Wireless Access Failure #6656

    Product name: Windows Packet Filter
    File: ndisapi.dll

    * I have e-mail you the system information reports for two of the workstations.

    in reply to: WinpkFilter 3.0: Wireless Access Failure #6654

    How do we detect what the cause is, and how can we avoid having similar issues?

    Do we try to isolate network providers? Bindings on Adapters? Disable device drivers such as WAN Miniport?

    Currently 5 out of 10 different notebooks either fail to connect or lock up with the driver installed.

    I am sure you understand that we cannot do this for each customer that has a different OS and/or wireless card. Would a custom build be able to remove these problems?

    I am happy with the functionality the driver provides, but we are stuck on this problem.

    Just looking for help…

    Alternatively would the Local Network Monitor be a better option for monitoring and analysing network traffic?

Viewing 3 posts - 1 through 3 (of 3 total)