Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I just ran

C:\Windows\system32>TRACERT.EXE 8.8.8.8

From my older Windows8 box and got this:

image description

So it works for me on my Windows platform. Why doesn't it work for you? Sharing your capture file would be a big help but anyway, some possible causes:

*You have mis-identified the traffic: i.e. the traffic that you think is coming from tracert is not correct. Maybe the wrong display filter; maybe capturing on the wrong interface; maybe...

*Your Wireshark decoders are not configured correctly so they show the wrong type

*You are not using the Windows version of tracert.exe, but a third party tool that can use UDP and/or TCP and the transport layer port is decoded by Wireshark as skype (https://www.netscantools.com/nstpro_traceroute.html)

*You have a different version of Windows than I do and it does not use ICMP, but rather UDP and/or TCP which Wireshark decodes as skype

click to hide/show revision 2
No.2 Revision

I just ran

C:\Windows\system32>TRACERT.EXE 8.8.8.8

From my older Windows8 box and got this:

image description

So it works for me on my Windows platform. Why doesn't it work for you? Sharing your capture file would be a big help but anyway, some possible causes:

  • *You You have mis-identified the traffic: i.e. the traffic that you think is coming from tracert is not correct. Maybe the wrong display filter; maybe capturing on the wrong interface; maybe...

  • *Your Your Wireshark decoders are not configured correctly so they show the wrong type

  • *You You are not using the Windows version of tracert.exe, but a third party tool that can use UDP and/or TCP and the transport layer port is decoded by Wireshark as skype (https://www.netscantools.com/nstpro_traceroute.html)

  • *You You have a different version of Windows than I do and it does not use ICMP, but rather UDP and/or TCP which Wireshark decodes as skype skype