[Winpcap-users] Vlan tagged traffic not capture on 64 bitWindows

[Pushkar Tiwari]

Thanks for your prompt response.
On Windows 2k3 (32 bit) device name is shown as *Intel(R) PRO/1000 MT Dual
Port Network Connection, *while on Windows 2k8(64 bit) device name is shown
as *Intel(R) PRO/1000 MT Dual Port Server Adapter.*
*
*
*In Advanced properties section for  Intel(R) PRO/1000 MT Dual Port Server
Adapter device there is a property Priority & VLan and its value is Priority
& VLan Enabled.
*
Do you think should I change it to some other value?

Thanks,
Pushkar
On Sat, Oct 9, 2010 at 12:33 AM, Guy Harris <guy at alum.mit.edu> wrote:

>
> On Oct 9, 2010, at 12:00 AM, Pushkar Tiwari wrote:
>
> > On both the box I am using Intel Ethernet adapter.
>
> Intel have many different Ethernet adapters:
>
>
> http://download.intel.com/network/connectivity/products/prodbrf/252454.pdf
>
> so, even though both the boxes might have Intel Ethernet adapters, they
> might be *different* Ethernet adapters (for example, a desktop adapter on
> the 32-bit machine and a server adapter on the 64-bit machine), and the
> adapters and their drivers might treat VLAN-encapsulated packets
> differently.
>
> What precise types of Intel Ethernet adapters do you have on the two
> machines?
>
> > On 32 bit platform it works perfectly fine and even my application is
> also able to capture the traffic.
> > But on 64 bit platform neither my application nor wireshark captures the
> traffic. And since both of these application uses winpcap library therefore
> I believe it could be an issue with winpcap.
>
> ...or it could be an issue with the Ethernet adapter on the server machine,
> or its driver.
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-users/attachments/20101012/1fa9d045/attachment.htm