You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then wait 60+ seconds and stop the trace, I can convert the etl file to a pcapng file and I can open it in Wireshark and see the packets.
Hoping I might be able to help resolve why these captures fail on some servers, but not others. Clearly, the packets are there and they can be captured.
The text was updated successfully, but these errors were encountered:
Below shows the results of trying to capture CDP info and its failing on all interfaces for particular servers.
If I run Wireshark the CDP packets are there:
![CDP Packets Example](https://private-user-images.githubusercontent.com/119334889/304852419-6eaba51d-fb46-4251-9cfb-b8d23a5ff324.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ2NDc4NzUsIm5iZiI6MTcyNDY0NzU3NSwicGF0aCI6Ii8xMTkzMzQ4ODkvMzA0ODUyNDE5LTZlYWJhNTFkLWZiNDYtNDI1MS05Y2ZiLWI4ZDIzYTVmZjMyNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyNlQwNDQ2MTVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02NjIwZjM5ZjJlNmM1OWE1MmYwMzc2ZjYzNjIzMDg5OGM2NDM5ZDVmZjkyNDhhYjFhOGYyYTQ5Yjg1ZWU1YTc4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.9UH1kF5PAQ4wBc3PYESAvTM9r9E3GXTInYLneG3fs9E)
If I try to run etl2pcapng.exe on the tmp201.etl file to convert it to Wireshark format, it errors out with "Opentrace failed with 2"
However, if I capture my own packets:
netsh trace start capture=yes IPv4.Address=10.70.65.209 tracefile=C:\Users\Username\AppData\Local\Temp\Trace.etl
Then wait 60+ seconds and stop the trace, I can convert the etl file to a pcapng file and I can open it in Wireshark and see the packets.
Hoping I might be able to help resolve why these captures fail on some servers, but not others. Clearly, the packets are there and they can be captured.
The text was updated successfully, but these errors were encountered: