TRACERT time out

  • Thread starter Thread starter amphi66
  • Start date Start date
A

amphi66

I have no difficulty connecting to a specific website
(www.mbmgcc.org) that I serve locally, but yet a tracer consistantly
times out after the 2nd hop, which happens to be the ISP for both
myself and the server, which located at another IP address down the
strreet.

With a good connection, how can there be a timeout?

--LarryS
 
amphi66 said:
I have no difficulty connecting to a specific website
(www.mbmgcc.org) that I serve locally, but yet a tracer consistantly
times out after the 2nd hop, which happens to be the ISP for both
myself and the server, which located at another IP address down the
strreet.

With a good connection, how can there be a timeout?

--LarryS

Somewhere in the trace is a node/computer that won't let you do it twice.
 
Hello,

I would suggest that you use a Network Monitoring tool to actually see what
is going on inside the line as far as protocol traffic is concerned.
Microsoft Network Monitor 3.0 works well. Copy and paste the output here,
but not all of the raw output. Turn the monitoring software on and run
tracert and then quickly turn off the networking monitor. You can then
export the data as text. Its a good place to start with problem like this.
 
Hello,

I would suggest that you use a Network Monitoring tool to actually see what
is going on inside the line as far as protocol traffic is concerned.
Microsoft Network Monitor 3.0 works well. Copy and paste the output here,
but not all of the raw output. Turn the monitoring software on and run
tracert and then quickly turn off the networking monitor. You can then
export the data as text. Its a good place to start with problem like this.







- Show quoted text -

Well, I joined, downloaded and recorded the Trace. Unfortunately, not
knowing exactly how to run things I couldn't seem to export the trace,
however it did not seem to show anything except the same IP address
over and over. I'll try again.

--Larry
 
Back
Top