TCP connection on windows 10

[rolfk]

Well, there might be some extra security in Windows 10 when executing a remote executable. Windows does not implement Samba but SMB (and lots more). Samba is an implementation of SMB (and parts of the lots more) for non-Windows platforms. Is your server by any change a Linux computer running Samba? That could explain why Windows 10 refuses to let a process that is hosted on this computer to get network connections when run remotely.

In addition there might be some weird dependency problems where the exe tries to reference DLLs in respect to the exe file location which obviously will fail.

[Ola_A]

Hello bateme01, I have similar problems since a few days with labview, mysql connector and windows 10. Details are in my post ( https://forums.ni.com/t5/LabVIEW/MySQL-connector-suddenly-giving-error-2147467259-on-windows-10/td-p... )

But you nailed it!

If I run the .exe on my samba file server as I am used to do (only one place to update code) I get this error, when I move the code locally it works!

If anyone finds more info on this + workarounds I would appreciate, quite irrirating!

[pincpanter]

IF (I am not sure) the problem is due to the recently removed support to SMB 1.0/CIFS, it's possible to overcome it by reinstalling this Windows functionality through the Win7-style Control Panel.

I had to do this to get back file sharing with some legacy WinXP machines.

To be honest, I don't know to which extent this can actually harm system security.

[Ola_A]

Paolo, I tried to enable SMB v1, but still same result.

Is it this setting, sorry for the Swedish?

Client was already enabled, but adding server did not improve things.

[pincpanter]

In fact, I meant only the klient part .

I'm sorry it did not help.

[Ola_A · Accepted solution]

I found this more direct answer to the question about running exe files on smb v1 share.

https://stackoverflow.com/questions/50155482/after-windows-10-update-1803-my-program-cant-open-a-soc...

[JensG69]

Port 3306, so you try to connect to a MySQL database.

Did you install the correct ODBC-driver version - the one your original executable expects to use? And did you install the 32bit version of the ODBC driver?

I usually connect to a MySQL database using a connection string and that usually includes a very specific naming of the ODBC-driver. So just installing a arbitrary MySQL ODBC driver probably will not solve your problem.

BTW, your TCP-Open should work in that format. I have no problem at all to doing exactly the same (i.e. opening a TCP-connection to a remote MySQL-server with LabVIEW in Windows 10).

Regards, Jens

[rolfk]

The problem, as shown by Ola_A, is that the latest Windows 10 version does not allow a process to use Winsock, if it was started from an SMB v1 share. Solution is to either install the executable locally and run it from there, or to reconfigure the server computer hosting the share to use SMB v2 instead.