Oh, if it drops the packets, which sometimes happens
naturally on one of the last links... you'll see asterisks *.
To see what I mean, type the following:
tracert microsoft.com
You'll see valid numbers all the until the last hop...
the Microsoft servers do not pass the ICMP messages back
to you so you'll end up with a bunch of asterisks (meaning in
this case the servers are dropping the packets on purpose).
In such a case, it will be the hops going out to the server that
will be of interest. You shouldn't see any asterisks at all until
the last server, and then it will all be asterisks, as in the
microsoft.com case above.
In your case, the servers are NOT dropping the packets. So
the trace should go through just fine and IF you do see asterisks,
the area where the asterisks are appearing could be a problem.
tracert will stop working after 30 tries in the Microsoft thing,
but you can stop it before that if you'd like by pressing CTRL+C
in the Command Prompt window.
Some hosting companies leave the ICMP processes running
for diagnostic help. Some companies turn ICMP off. If you
run a tracert to spiderwebwoman.com you'll see that they
turn it off like microsoft.com does.
So what you'll want to watch in those cases when ICMP is
turned off on the last hop, are the hops in all the way out to
the last hop. Sometimes you'll see problems on the way out
to the server where some packets are being dropped/lost
and if that's the case it may NOT be a HOSTING problem,
but just an Internet problem.
Another thing to watch are the first two or three initial hops
(or maybe a four or five hops), which should belong to your
ISP (Internet Service Provider). If those are being problematic,
you'll need to contact your ISP.
The tracert tool is just a simple tool that can help pinpoint
where problems are occuring, and the information should
be relayed to appropriate company to help them figure out
what their problem is. ;-)
--
Jim Carlock
Post replies to newsgroup.
Jim,
I ran a tracert from my computer but I'm not sure what all of the numbers
are indicating. I see that they all end in ms but how do you distinguish if
there are any lost packets? The tracert I ran looks pretty much like the one
you have except for the last one of the second run I did which showed 158ms
(last entry) Could you please explain what I am looking at and why too since
I went to another server (different host) did I end up with the same results?
To me this would indicate as problem either with FP or perhaps the DSL I'm
using.
Jim Carlock said:
You might want to run a tracert to the website inside of
a DOS prompt to see if any packets are being dropped...
12 68 ms 66 ms 70 ms 216.200.249.141.available.ipowerweb.com [216.200.249.141]
13 70 ms 68 ms 71 ms 66.235.211.108
Inside of a DOS command prompt, type:
tracert
www.adsforus.com
or
tracert 66.235.211.108
I'm posting this not to be argumentative... I don't know,
but if anyone else wants to comment or compare, that
would be great...
I've had no recognizeable problems with a website of
100MB using FrontPage...
884 files, 186 folders
95611.84KB (97906523 bytes)
Size: 95.1 MB (99,734,270 bytes)
Size on disk: 99.6 MB (104,443,904 bytes)
1788 files, 355 folders
Other sites have gone up to about 40 and 60 MB with no
problems.
I'm not presenting this to be argumentative. I don't have any
problem connecting and downloading the whole site, nor
any problems uploading, although the HOST company had
a server issue which wouldn't allow me to connect via FTP
through Internet Explorer recently... but they resolved that
(took them two or three weeks to resolve it, though). ;-)
--
Jim Carlock
Post replies to newsgroup.
You are right Ben, My website just went up to 41megs, but right now the
problem is not being able to connect. I have noticed though that I have had
to connect several times to finish an upload. So that's another problem I
need to tackle. Thanks for your advice I'll be breaking it down. Wish I had
known about this before, sure would have made things a lot easier. Thanks Ben.
:
Any ideas will be gladly