New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Error retrieving the MAC address of the adapter" on windows 10 #12

Open
bolso opened this Issue Jan 5, 2018 · 8 comments

Comments

Projects
None yet
6 participants
@bolso

bolso commented Jan 5, 2018

Hi,

I'm using Windows 10. Any attempt to use tracetcp is returning the "Error retrieving the MAC address of the adapter" error.

For the record here's a log

C:\WINDOWS\system32> tracetcp www.google.com
Error retrieving the MAC address of the adapter

WinPcap is installed.

Thanks!

@simulatedsimian

This comment has been minimized.

Show comment
Hide comment
@simulatedsimian

simulatedsimian Jan 7, 2018

Owner

can you attach the output of the following commands to this bug log.

ipconfig /all
route print

thanks.

Owner

simulatedsimian commented Jan 7, 2018

can you attach the output of the following commands to this bug log.

ipconfig /all
route print

thanks.

@bolso

This comment has been minimized.

Show comment
Hide comment
@bolso

bolso Jan 14, 2018

Hi, sorry but I'd rather not share that information on a public site. Is there something in particular I should look for?

Thanks.

bolso commented Jan 14, 2018

Hi, sorry but I'd rather not share that information on a public site. Is there something in particular I should look for?

Thanks.

@phutothali

This comment has been minimized.

Show comment
Hide comment
@phutothali

phutothali Jan 22, 2018

Hi,
Same herre
Windows 10, updated everything (windows, driver) reinstall Winpcap, install win10pcap
but still report:
Error retrieving the MAC address of the adapter
Regards.

phutothali commented Jan 22, 2018

Hi,
Same herre
Windows 10, updated everything (windows, driver) reinstall Winpcap, install win10pcap
but still report:
Error retrieving the MAC address of the adapter
Regards.

@compyy

This comment has been minimized.

Show comment
Hide comment
@compyy

compyy May 2, 2018

same here, doesnt work on Windows 10

compyy commented May 2, 2018

same here, doesnt work on Windows 10

@simulatedsimian

This comment has been minimized.

Show comment
Hide comment
@simulatedsimian

simulatedsimian May 3, 2018

Owner

can you attach the output of the following commands to this bug log.

ipconfig /all
route print

thanks.

Owner

simulatedsimian commented May 3, 2018

can you attach the output of the following commands to this bug log.

ipconfig /all
route print

thanks.

@compyy

This comment has been minimized.

Show comment
Hide comment
@compyy

compyy May 7, 2018

What is the option to select specific interface ? i believe it is choosing wrong interface.

compyy commented May 7, 2018

What is the option to select specific interface ? i believe it is choosing wrong interface.

@computerline1z

This comment has been minimized.

Show comment
Hide comment
@computerline1z

computerline1z Jul 26, 2018

The error is conflict version of winpcap, if you install win10pcap after npcap, just copy all the *.dll in the wow64/npcap to the directory contains tracetcp.exe, and everything will work again.

computerline1z commented Jul 26, 2018

The error is conflict version of winpcap, if you install win10pcap after npcap, just copy all the *.dll in the wow64/npcap to the directory contains tracetcp.exe, and everything will work again.

@yhnmj6666

This comment has been minimized.

Show comment
Hide comment
@yhnmj6666

yhnmj6666 Aug 22, 2018

Or you can uninstall win10pcap and install npcap on winpcap-compatible mode.
Win10pcap doesn't implement all winpcap API correctly. For example, PacketRequest function in win10pcap just return false which makes tracetcp thinking it can't get MAC Address. As a result, you see the error message mentioned in issue.
Even if you get around of this error, you will see "FATAL Bad Memory Block" every frame, this is another problem in win10pcap.

yhnmj6666 commented Aug 22, 2018

Or you can uninstall win10pcap and install npcap on winpcap-compatible mode.
Win10pcap doesn't implement all winpcap API correctly. For example, PacketRequest function in win10pcap just return false which makes tracetcp thinking it can't get MAC Address. As a result, you see the error message mentioned in issue.
Even if you get around of this error, you will see "FATAL Bad Memory Block" every frame, this is another problem in win10pcap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment