netstat very slow

[Hanan Cohen]

I think there is something wrong woth my tcp/ip settings.
When I run NETSTAT -a I get a veeeery sloooow response.
How can I check what's wrong ?

Hardware : Compaq proliant 800, 2 nics
Serverware : NT 4.0 , SP 4

Thanks

p.s. Please answer the NG and not my mail , it's broken...

--
Hanan Cohen

Qiriat-Gat Central Library http://www.qglibrary.org.il
Kibbutz Tamuz - Beit Shemesh http://www.tamuz.org.il
Bashan Systems - http://www.zikit.co.il
***Love and Peace***

[Bernd Strobel]

Hanan Cohen <han...@bashan.co.il> wrote: 37C26914...@bashan.co.il...

> I think there is something wrong woth my tcp/ip settings.
> When I run NETSTAT -a I get a veeeery sloooow response.
> How can I check what's wrong ?

I think, it tries to resolve some IP addresses to names via DNS.

Use 'netstat -an' to avoid this.

Bernd

[Eric Gisin]

Internet name resolution will be done using netbios broadcasts by default.
You have two adaptors, so it will try on each of them.

If the second NIC is for internet access, you should disable netbios/WINS
bindings for that NIC (also for security). Otherwise, I don't know what a
good solution is.

Hanan Cohen wrote in message <37C26914...@bashan.co.il>...
:I think there is something wrong woth my tcp/ip settings.

:When I run NETSTAT -a I get a veeeery sloooow response.
:How can I check what's wrong ?

:
:Hardware : Compaq proliant 800, 2 nics

:

[Hanan Cohen]

Bernd Strobel wrote:
>
> Hanan Cohen <han...@bashan.co.il> wrote: 37C26914...@bashan.co.il...

> > I think there is something wrong woth my tcp/ip settings.
> > When I run NETSTAT -a I get a veeeery sloooow response.
> > How can I check what's wrong ?
>

> I think, it tries to resolve some IP addresses to names via DNS.
>
> Use 'netstat -an' to avoid this.

Thanks. It worked.
Does it mean I have a DNS problem ? How can I find what's wrong ?

[cals...@gmx.com]

Thats not the point. At work here we tested "netstat" on many Windows 10 boxes and it is extremely slow on all. Does it resolve the host names using just "netstat", of course it does. But, it resolves the names on all the other boxes we tested too and on them it is extremely fast (Windows 7, Windows XP, Windows Server 2008 R2, Windows Server 2016). Does anyone have a reasonable answer to why only Windows 10 boxes are extremely slow at runing "netstat" with out any command line options?
Another thing that is extremely slow, only on Windows 10, is seeing all the processes( time it takes to show all the processes) in Visual Studio 2015 when attaching the debugger to a local running process.
When remotely attaching a process from a Windows 10 box to Windows 2016 server it is extremely fast.
Why?

[jupp...@gmail.com]

I guess that the dns you had written into the Network Settings, could not resolve every mac address in your Network. That's is a regular behavior, because the most private build lan's are not installed a local DNS, who is able to resolve the local ip addresses. In a company LAN environment, all required services are available to do the local Job resolve Job and Forward Outbound addresses to a public DNS.

[Dan Henderson]

While I can't speak to others' environments, I can tell you that I just tested this and had a similar experience. Almost every line in the output of netstat (with no parameters) took about 4-5 seconds. And yet, nslookup commands resolved instantly for hosts on my internal network, and almost as quickly (definitely under 200ms) for hosts on the Internet.