FTP and Web Shell

If you need another good GUI based traceroute, go to www.analogx.com and download HyperTrace, it is easy and works very fast/well.

[antic]

It's not being vewy fwiendly to me.. this is the result I've been getting from tracert since I first discovered Vortech:

1 199 ms 179 ms 173 ms i014-016.nv.iinet.net.au [203.59.14.16]
2 280 ms 179 ms 185 ms per-qv1-core2.iinet.net.au [203.59.49.163]
3 293 ms 179 ms 191 ms 203.59.49.170
4 233 ms 239 ms 238 ms IINET-PERTH-so-1-0-2.ar1.SYD1.gblx.net [203.192.
166.209]
5 231 ms 396 ms 394 ms pos2-1-155M.cr2.LAX1.gblx.net [203.192.136.66]
6 496 ms 455 ms 462 ms so2-0-0-2488M.cr1.PAO2.gblx.net [67.17.93.109]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.

To quote Yul Brynner - "etceterahh.. etceterahh.."

What does this mean exactly? (Not the etceterah thing.. the other thing..)

well obviously it is working better than THAT or you would not be here now. Looks like after LAX the PAO(not sure, that might be Palo Alto(sp?) in CA), the router seems to be blocking the requests