Write in 32-bit system: "cmd /c C:\\Windows\\system32\\nbtstat.exe -a 192.168.44.1"
Yes, but in 64 bits,
C:\\windows\\system32\\nbtstat.exe in the program, is not found.
is the cause of the 64-bit system, change the command to "cmd/c c:\\windows\\sysnative\\nbtstat.exe-a 192.168.44.1" on it.
The Magical Sysnative folder
In fact, the%windir%\sysnative folder does not exist, it is only a 64-bit Windows system provides a redirection mechanism. We already know that 64-bit Windows uses the System32 and SysWoW64 two-piece folders to differentiate between 64-bit and 32-bit system files, and when 32-bit applications try to access the System32 folder, the system automatically transfers it to the SysWoW64 folder. This allows 32-bit applications to run on both 32-bit systems and 64-bit systems (without the need to change the System32 to SysWoW64 for a 64-bit system). So there's a problem, how do 32-bit applications access the real System32 folder, the folder that holds the 64-bit system files? The answer is through the Sysnative folder. This folder does not exist, which is not found in explorer, but when a 32-bit application tries to access the folder, 64-bit Windows redirects it to the true System32 folder, providing a way for 32-bit applications to access the 64-bit system files. Please refer to MSDN for specific details. 」
64-bit Win7 system nbtstat problem