Why netstat so slow




















Do you have any idea what would cause netstat to run so slow. I believe that this is related to the failure of the third party product getting the read fail stream socket errors. It socondary attempts to connect are tried the product will connect. The machine is booted every sunday, so leftover socket connections, garbage memory etc are cleaned up each week.

If you wait long enough the netstat does complete. So it's not really hanging just running extremely slow. Tags: netstat.

All forum topics Previous Topic Next Topic. Hi Alan, From the symptoms you describe, I would suspect "netstat -rn" should also be quick compared to "netstat -r". This would indicate hostname resolution problems, i. DNS not working properly? Rgds, Robin. Steve Steel If you want truly to understand something, try to change it. Kurt Lewin. Thanks guys, The problem was with DNS server.

Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. It seems counter-intuitive since the second command actually produces more information.

Anyone know why this is? Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? How satisfied are you with this reply?. Thanks for your feedback, it helps us improve the site. Thats not the point. At work here we tested "netstat" on many Windows 10 boxes and it is extremely slow.

Does it resolve the host names using just "netstat", of course it does. And don't answer that Windows should be exactly like Windows 10 boxes because it is not! 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 when attaching the debugger to a local running process.

When remotely attaching a process from a Windows 10 box to Windows server it is extremely fast. This is a Consumer-specific forum.

You will find appropriate support for Windows 10 in the IT Pro-specific forums:. Thank you for completely ignoring the question.



0コメント

  • 1000 / 1000