hi there, i ain't a networking guy but i got a problem with a network
running in a company i'm working for. the situation is

- network is a private one running some client-server application
services without any connection to the Internet
- client terminals can ping to servers or other clients fine with <1ms
responses
- when i tried running "tracert Server_node" or "tracert
Client_nodes", i had to wait for over 10 secs before there's any
response popped up on the screen
- when i tried running "tracert -d Server_node" or "tracert -d
Client_nodes", instant response showed up on screen with the
destination reached in a split-second

could anyone point out if this is an abnormal behaviour or what could
it have possibly gone wrong? i haven't seen such slow response from
executing the tracert command before, even on another network inside
the company (the one connecting to the Internet), when i ran "tracert
public_node", hops responses were spotted instantly and popping up one
by one with RTT. also the "Tracert -D" kinda skipped the DNS server
and when it was executed, hops were popping up as fast as on any other
network.

any advice would be much appreciated.

thanks

<macanno@gmail.com> wrote in message
news:1177439299.822711.284530@b40g2000prd.googlegr oups.com...
> hi there, i ain't a networking guy but i got a problem with a network
> running in a company i'm working for. the situation is
>
> - network is a private one running some client-server application
> services without any connection to the Internet
> - client terminals can ping to servers or other clients fine with <1ms
> responses
> - when i tried running "tracert Server_node" or "tracert
> Client_nodes", i had to wait for over 10 secs before there's any
> response popped up on the screen
> - when i tried running "tracert -d Server_node" or "tracert -d
> Client_nodes", instant response showed up on screen with the
> destination reached in a split-second
>
> could anyone point out if this is an abnormal behaviour or what could
> it have possibly gone wrong? i haven't seen such slow response from
> executing the tracert command before, even on another network inside
> the company (the one connecting to the Internet), when i ran "tracert
> public_node", hops responses were spotted instantly and popping up one
> by one with RTT. also the "Tracert -D" kinda skipped the DNS server
> and when it was executed, hops were popping up as fast as on any other
> network.
>
> any advice would be much appreciated.
>
> thanks
>

Name resolution is timing out, which is why the -d option runs much quicker.
Try doing a name lookup (nslookup) on any one of the devices along the way
that was taking a long time and you'll find that it times out. Very often,
people do not put network devices in their dns tables.

Hope that s,

Jim