-
Notifications
You must be signed in to change notification settings - Fork 45
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
Windows Traceroute timeout. #11
Comments
I executed the trace route command directly from windows and it works |
Hi, Can you confirm if this is a local address? Also, can you please provide a packet trace of the outgoing and incoming packets? Thanks Steve |
Not it's not a local address. Is the output of the DNS of eventtia.com ( I ran the same command in my Mac and it works like a charm) The other thing... How can I provide you that data? Wireshark? |
You can use Wireshark to provide the data. |
Hello I attach the files you are asking for. I ran the commands |
Looking at the packet trace I do indeed see ICMP time exceeded messages, which should be passed back to you. If I execute the trace-route command it works for me, I use Windows 7:
Could it be that you have a firewall or some program that prevents the response messages from receiving your program? Steve |
No more information from the user. |
This bug still present.
From wireshark: Windows tracert work fine:
System:
|
Problem in Windows Firewall. |
Hello i have been trying the module in linux, os x and windows and it works great... but in windows the ping works, the traceroute works but it just give a timeout in each hop except in the last one.
![capture](https://cloud.githubusercontent.com/assets/6225534/11969729/f2f624e4-a8eb-11e5-8d09-a7013cf2343f.PNG)
Here is the output
The text was updated successfully, but these errors were encountered: