slow networking response using tasklist on a remote pc

I was wondering if anyone could point me in the right direction here. I am
running a remote tasklist command in a cmd window between two windows server
2003 boxes with syntax similiar to the following:

tasklist /s 192.168.x.x /u username /p password ...

If I use the netbios computer name in place of the ip address above, the
results are returned immediately. However when I use the ip format above,
the results come back in roughly 20 seconds. Does anyone know of why this
would be? I can post ipconfig, or nslookups if anyone cares to see them.

Cheers

Hi Rick,

That's weird. It happens on one of my servers too but only when multi-homed.
FQDN DNS works instantly. NetBIOS name works instantly. But as you and I
observe - IP is S L O W.
Network trace shows tasklist command sending NetBIOS name service requests
first on one network - then on the other - then on the original. It seems
happy with the correct response from the IP I entered - but keeps asking the
_wrong_ subnet until some timeout occurs.
Perhaps some IP guru can help us here.

CreateWindow
http://justpageprobe.com
The FREE Web page utility you always wanted.
Keep your router connected.
Email your IP to where you need it.
Monitor your enterprise Web Servers.


"Rick Westmacott" <(E-Mail Removed)> wrote in message
news:0wa_h.139$Vi6.101@edtnps82...
>I was wondering if anyone could point me in the right direction here. I am
>running a remote tasklist command in a cmd window between two windows
>server 2003 boxes with syntax similiar to the following:
>
> tasklist /s 192.168.x.x /u username /p password ...
>
> If I use the netbios computer name in place of the ip address above, the
> results are returned immediately. However when I use the ip format above,
> the results come back in roughly 20 seconds. Does anyone know of why this
> would be? I can post ipconfig, or nslookups if anyone cares to see them.
>
> Cheers
>
>
>
>