DrLarch

Different netstat output: cmd line vs script

5 posts in this topic

Not sure why this is happening - when I run netstat -abn from a command line I get this:

 [svchost.exe]
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
 Can not obtain ownership information
  TCP    0.0.0.0:5000           0.0.0.0:0              LISTENING

But when I run it from this script:

#RequireAdmin

Local $str = ''
Local $pid = Run(@WindowsDir & '\system32\netstat.exe -abn', '', @SW_HIDE, 2)
While ProcessExists($pid)
    $str &= StdoutRead($pid)
WEnd

FileWrite(@ScriptDir & "\portdump.txt",$str)

Exit

... I get this:

 [system]
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
 Can not obtain ownership information
  TCP    0.0.0.0:5000           0.0.0.0:0              LISTENING

I'm missing the executable in the brackets via the script, instead I just get "System". I thought #RequireAdmin would help, but no change. I also tried using RunAs with my admin credentials (even though I'm running the script from my account), but no difference.

Any ideas?

Share this post


Link to post
Share on other sites



Have you tried

Run(@ComSpec & " /c " & 'commandName', "", @SW_HIDE)

as described in the help file?


My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2017-04-18 - Version 1.4.8.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX (NEW 2017-02-27 - Version 1.3.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2015-04-01 - Version 0.4.0.0) - Download - General Help & Support - Example Scripts
Excel - Example Scripts - Wiki
Word - Wiki
PowerPoint (2015-06-06 - Version 0.0.5.0) - Download - General Help & Support

Tutorials:
ADO - Wiki

 

Share this post


Link to post
Share on other sites

I can't duplicate that problem, I'm getting the program name when I run the script.


If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.
Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag Gude
How to ask questions the smart way!

I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from.

Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays.  -  ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script.  -  Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label.  -  _FileGetProperty - Retrieve the properties of a file  -  SciTE Toolbar - A toolbar demo for use with the SciTE editor  -  GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI.  -   Latin Square password generator

Share this post


Link to post
Share on other sites

Well one thing I found is that if I run the syswownetstat.exe from a command line I don't get the exe names, but the one in my system32 folder works fine. I changed the path in the script to use the system32 one, but no difference. And water, yes, I just tried changing it to use @ComSpec & " /c " but no difference. If no one can reproduce this, then maybe it's some security settings in our domain perhaps. But that still doesn't make sense as I can get the proper output from a command line.

Share this post


Link to post
Share on other sites

Ok, I found it. I actually ran into this before with W7/64 redirecting registry read/writes to syswow64, but didn't realize it did this with directories as well. After I changed the path directly to C:\Windows\System32\netstat.exe and ran the script as x64 it works.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now