|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#31
July 30th 04, 01:44 AM
|
|||
|
|||
ping works but not tracert
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 "Jeff Reid" wrote in message news:b3nLc.6111$fB4.2058@lakeread01... 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. 
|
| Ads |
|
#32
July 30th 04, 02:40 AM
|
|||
|
|||
|
ping works but not tracert
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 "Jeff Reid" wrote in message news:BEALc.6197$fB4.4088@lakeread01... Doublecheck if the NetBIOS interface is enabled in the network connections properties. NetBios is enabled, but if I check the properties, I see an internal id of 0000000, and auto-detect, should I change these?
|
|
#33
July 30th 04, 03:55 AM
|
|||
|
|||
|
ping works but not tracert
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 "Jeff Reid" wrote in message news:b3nLc.6111$fB4.2058@lakeread01... 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.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
