(Msg. 4) Posted: Tue Jan 08, 2008 11:43 am Post subject:
Crazy! same thing for me. Tracert to my own router or to the www.google.com router give both on hop!! I feel much more closer to everything thanks to vista tracert!
Another interesting point is that I can't control QoS policy in the group policy editor (i.e. bandwith limitation), it just doesn't work.
Probably an important detail: I'm running vista on a virtual machine, are you guys in the same case?
(Msg. 5) Posted: Tue Jan 08, 2008 11:47 am Post subject:
I bet you are using Zonealarm.
I discovered on another forum that, sometime after Checkpoint took over Zonealarm, this behavior appeared. They appear to have no interest in fixing it because they do not respond to queries about it, and it has existed for a long time now.
(Msg. 9) Posted: Tue Jan 08, 2008 12:18 pm Post subject: [Login to view extended thread Info.]
kenjidnb wrote:
...I dont use zone alarm and I even deactivated windows firewall, but same thing.. one crazy hop.
This is a major input to this problem--that it occurs outside a zonealarm environment. And very confusing. A person on the other forum said they had the problem, uninstalled ZA, problem disappeared (tracert worked right), reinstalled ZA, back to one line results. That seemed to clearly point to ZA as the problem.
Now I don't know what to think.
Last edited by gladiator on Tue Jan 08, 2008 12:23 pm; edited 1 time in total
(Msg. 10) Posted: Tue Jan 08, 2008 12:22 pm Post subject:
I did a packet capture of what is going out when tracert is commanded, and the packets had a TTL of 128. With a tracert, it is supposed to send sequential packets with TTL at 1,2,3,4...up to whatever, until the destination machine is reached.
So the immediate cause is that tracert is somehow being forced to not work in its normal manner. Duh. We knew that.
(Msg. 11) Posted: Tue Jan 08, 2008 12:45 pm Post subject: [Login to view extended thread Info.]
gladiator wrote:
..when tracert is commanded, and the packets had a TTL of 128...
Very interesting, so according to your sniff, Vista add the ttl of 128 at the beginning? So that's why the packets go through all the hops till it can't go beyond.
I wonder why this starting ttl?
(Msg. 12) Posted: Tue Jan 08, 2008 12:53 pm Post subject:
TTL of 128 is the standard TTL for a ping, but there is a switch you can use with it to change that. Tracert is supposed to (without you ever seeing what is going on) cause sequential pings with appropriate switch settings and parameters for each time, that gives the data you see on the screen.
Somewhere, it is being caused to not do this right.
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum