G
Guest
I recently noticed that tracert (the DOS command that allows to trace the
route between the computer and another one on the Internet) does not work
anymore correctly on my VISTA machine.
When launched, tracert does not trace the route but simply seems to ping the
computer and no inforation is displaye as to the path followed.
For example, for a short route to my ISP, tracert on my XP machine will show
5 hops (starting from my ADSL router and going through 3 relays between my
router and my ISP), whereas the same command on my VISTA machine will only
show the last hop (the target machine).
I know tracert worked correctly before installing ZoneAlarm and a few MS
updates, since I used it to check the route from various ISP when travelling.
Has anyone seen this and could it be traced to Zone Alarm ? Yet, the
problem persists if I unload ZASS, but I wonder whether this definitely
rules ZASS as the culprit. I indeed noticed that the installation of
ZoneAlarm included the installation of new drivers which may have changed the
way tracert works and are not unloaded when unloading ZASS.
This is not a critical problem but is annoying since it doe snot allow me to
check easily the change of route when starting my VPN.
route between the computer and another one on the Internet) does not work
anymore correctly on my VISTA machine.
When launched, tracert does not trace the route but simply seems to ping the
computer and no inforation is displaye as to the path followed.
For example, for a short route to my ISP, tracert on my XP machine will show
5 hops (starting from my ADSL router and going through 3 relays between my
router and my ISP), whereas the same command on my VISTA machine will only
show the last hop (the target machine).
I know tracert worked correctly before installing ZoneAlarm and a few MS
updates, since I used it to check the route from various ISP when travelling.
Has anyone seen this and could it be traced to Zone Alarm ? Yet, the
problem persists if I unload ZASS, but I wonder whether this definitely
rules ZASS as the culprit. I indeed noticed that the installation of
ZoneAlarm included the installation of new drivers which may have changed the
way tracert works and are not unloaded when unloading ZASS.
This is not a critical problem but is annoying since it doe snot allow me to
check easily the change of route when starting my VPN.