Trace route to router

  • Thread starter Thread starter Daniel Tan
  • Start date Start date
D

Daniel Tan

Does tracing route to internal router same as ping to the router ? My
problem is sometimes i can even tracert (Request timeout) to my
internal router. Anyone got any idea why ? Thanks.

Regards,
Daniel
 
Does tracing route to internal router same as ping to the router ? My
problem is sometimes i can even tracert (Request timeout) to my
internal router. Anyone got any idea why ? Thanks.
Click to expand...

Traceroute requests echo signals from every hop(router) the traffic
passes on its way to destinationand from the destination, while ping
only requests an echo signal from the destination.
I guess that would be the same for you (the pinging/tracing host
directly connected to the router).
If you want a continued ping like in linux to your router just type
ping -t <IP-address> or type ping /? to see what else you can do with
ping.
Those timeouts may be caused by a bad cable or plug, but also from too
many collisions happening within your LAN. I don't know how many host
you have in your LAN and if or how you segmented it. If you have more
than 1 host you should use a switch to interconnect hosts and router,
because otherwise collisions may occure and your whole LAN slows down.
There are more possible reasons for timeouts, but without some more
information I can't tell what causes them in your case.

regards
André
 
Franke, i use switch in my LAN. This problem just came 2 days ago.
But it is intermittent.

Regards,
Daniel
 
Franke, my network is using star topology connected with switch to a
router , around 30 users. Just installed wins server recently, but not
all user using it. Internet connection using NAT.

Regards,
Daniel
 
Franke, my network is using star topology connected with switch to a
router , around 30 users. Just installed wins server recently, but not
all user using it. Internet connection using NAT.
Click to expand...

Ok, that tells a bit more. My guess is that because not all hosts are
using WINS for netbios name resolution (nbnr) there are at least two
nbnr methods working concurrently. It would be a good idea to let
either all stations use WINS or none. Especially if you didn't assign
static IP adresses there will be a lot of traffic since the hosts have
to verify that their netbios cache entries are still valid. Even the
WINS server if it works dynamically and not based on a static list
will have to ceck requently if its table is still up-to-date. Thus
every non-WINS host and the WINS server frequently ask around like
this:
"Hey, <IP-address> is your name still <hostname>?
No?
What is your hostname right now?"

and that they do for every IP address they remember.
Imagine a room where everyone calls out such questions simultaneously.
Ok, since you have a switch the analogy would be a city where everyone
needs to call every number of his telephone register to see if the
number for that name is still valid, while the employees of an
information service do the same. You can imagine that sometimes you
won't get a connection, since there is no such thing as a conferencing
session implemented.

Add your non-WINS hosts to your WINS set the update timer of WINS and
DHCP (lease time eg. 30 days) to a somewhat higher value or if you
dont use DHCP, create a lmhosts file that maps all IPs to the
corresponding netbios names. Put a copy of that file on every host
(Just put it where the lmhosts.sam file is found. The lmhost.sam is a
sample file to show you how it works.)

To verify what I said, get a copy of "ethereal" and sniff around a bit
to see what traffic runs trhough your network.

regards
André

PS: My name is André Franke, where Franke is the last name. Just in
case you missed that. :)
 
Back
Top