Thanks for your prompt response.<div>On Windows 2k3 (32 bit) device name is shown as <b>Intel(R) PRO/1000 MT Dual Port Network Connection, </b>while on Windows 2k8(64 bit) device name is shown as <b>Intel(R) PRO/1000 MT Dual Port Server Adapter.</b></div>
<div><b><br></b></div><div><b><span class="Apple-style-span" style="font-weight: normal;">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.</span><br>
</b><br></div><div>Do you think should I change it to some other value?</div><div><br></div><div>Thanks,</div><div>Pushkar<br><div class="gmail_quote">On Sat, Oct 9, 2010 at 12:33 AM, Guy Harris <span dir="ltr"><<a href="mailto:guy@alum.mit.edu">guy@alum.mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On Oct 9, 2010, at 12:00 AM, Pushkar Tiwari wrote:<br>
<br>
> On both the box I am using Intel Ethernet adapter.<br>
<br>
</div>Intel have many different Ethernet adapters:<br>
<br>
<a href="http://download.intel.com/network/connectivity/products/prodbrf/252454.pdf" target="_blank">http://download.intel.com/network/connectivity/products/prodbrf/252454.pdf</a><br>
<br>
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.<br>
<br>
What precise types of Intel Ethernet adapters do you have on the two machines?<br>
<div class="im"><br>
> On 32 bit platform it works perfectly fine and even my application is also able to capture the traffic.<br>
> 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.<br>
<br>
</div>...or it could be an issue with the Ethernet adapter on the server machine, or its driver.<br>
<div><div></div><div class="h5">_______________________________________________<br>
Winpcap-users mailing list<br>
<a href="mailto:Winpcap-users@winpcap.org">Winpcap-users@winpcap.org</a><br>
<a href="https://www.winpcap.org/mailman/listinfo/winpcap-users" target="_blank">https://www.winpcap.org/mailman/listinfo/winpcap-users</a><br>
</div></div></blockquote></div><br></div>