ping works but not tracert

  • Thread starter Thread starter Jeff Reid
  • Start date Start date
J

Jeff Reid

I have two systems connected to each other via ethernet through
a etherfast 10/100 switcher. There is also a cable modem hooked up
to the switcher.

The two systems can ping each other, and tcp-ip stuff works between
the systems. However, I can't do a tracert from either computer and
"see" the other? Similarly, using visual studio .net remote debugging
I can use tcp-ip debugging but not the dcom interface.

Any help here would be appreciated.
 
I have two systems connected to each other via ethernet through
a etherfast 10/100 switcher. There is also a cable modem hooked up
to the switcher.
Click to expand...

I should note that these two systems are my home systems and are part
of a workgroup, not a domain.
 
I have two systems connected to each other via ethernet through
a etherfast 10/100 switcher. There is also a cable modem hooked up
to the switcher.
Click to expand...

Also, I can't telnet between the two systems.
 
Ping/tracert by IP or computer name? One difference between ping and tracert
is that tracert attempts a reverse name resolution before sending ICMPs. If
the reverse name resolution is slow or fails, tracert will timeout.

You are using a workgroup, so broadcasting is the way to perform name
resolution. Doublecheck if the NetBIOS interface is enabled in the network
connections properties.

Ovidiu Popa
MVP
 
I have the ip name in the hosts file, so it probably doesn't matter.
Same results if I use name or the ip. I'll check the NetBios
stuff, but I think I have all the protocols installed.
 
Doublecheck if the NetBIOS interface is enabled in the network
connections properties.
Click to expand...

NetBios is enabled, but if I check the properties, I see
an internal id of 0000000, and auto-detect, should I change these?
 
Where exactly can you see "an internal id of 00000000"?

Check also the syntax in the hosts file. You don't really need to use the
hosts file, remove the mapping and try again.

Ovidiu Popa
MVP
 
This problem is related to my cable modem.

If I reboot both systems with the cable modem disconnected from
the switcher, both systems can "see" each other using the
"random" ip (169. ...) address. Both ping and tracert are working.

If I manually set the ip to to match what the cable modem sets
them to (65.... and 68...) then neither ping or tracert work.
I'm don't understand why setting the ip's is causing ping and tracert
to not work. I have NetBios set to enable also.

If I reboot with the cable modem connected, then ping works but
not tracert.
 
This problem is related to my cable modem.

If I reboot both systems with the cable modem disconnected from
the switcher, both systems can "see" each other using the
"random" ip (169. ...) address. Both ping and tracert are working.

If I manually set the ip to to match what the cable modem sets
them to (65.... and 68...) then neither ping or tracert work.
I'm don't understand why setting the ip's is causing ping and tracert
to not work. I have NetBios set to enable also.

If I reboot with the cable modem connected, then ping works but
not tracert.
 
It's not clear from your post what addresses you are using. If your subnet
mask is 255.255.255.0, then the first three numbers of the two addresses
must match (eg 192.168.0.x and 192.168.0.y)
 
Back
Top