03-29-2017 01:58 PM
Hello,
We have an application written in LabView 2012 and works fine on Windows 7. The application starts in Windows 10 Pro without problems but this application extensively uses the TCP/IP stack/Network communication to devices connected locally. In Windows 7 Pro all we did was edit the firewall rules and the application worked fine, in Windows this does not work. We have disabled the firewall, added rules, tried the "super admin" account and still having issues. The LabView application can successfully ping the devices but cannot "talk" to them beyond a ping. Does anyone have any suggestions besides upgrading to LabView 2015?
Thank You
SD
03-29-2017 02:48 PM
I am not that familiar with Windows 10, mainly because I don't like it as much as Windows 7 (a different topic for a different day). But is there some sort of built-in malware program (Defender) or anti-virus software that is preventing the communication? What sort of devices are you communicating with? When you say that you can ping them, are you using a System Exec VI within Labview to do that?
03-29-2017 03:23 PM
Hi aputman,
To answer your questions:
- there are no malware/av software running
- these are DAQ devices with Ethernet
- we can ping using system Exec VI within Labview and standards windows command prompt command
03-29-2017 04:03 PM
Have you tried right-clicking the EXE and running as administrator?
03-29-2017 04:07 PM
yes makes no difference
03-29-2017 09:45 PM
Hi SD,
I'm afraid the news is not what you would like.
Please check this link: Windows Version Compatibility with LabVIEW
steve