KB4100403 - runing exe from shared folder

[mLipok]

Together with MS Windows Update: KB4100403 on Windows 10, I encountered a problem when running programs from a shared resource.
Both SQL, FTP and SMTP connections can not be established if the program is run directly from the network resource.
If the same program starts with, for example, a desktop, there is no problem - it works correctly.

When started program from a network resource, windows blocks the connection as if it was FIREWALL to cut off the connection.
Blocks mean program is run but this program can not connect to SMTP server to SQL Server to FTP Server.

Do you can show me some solution  to this problem ?

 

 

[orbs]

you can add the network share as a "Trusted Site". although it is designed for web sites, a network share is also supported. if you can do that via Group Policy (even local) as described here, i'd like to know, as i never tried that method before.

or, you can wait for another update to fix this issue but screw other stuff, for your amusement.

b.t.w look at the page describing this KB update, here. in the "Known issues in this update" section, it says:

Symptom	Workaround
Some users running Windows 10 version 1803 may receive an error "An invalid argument was supplied" when accessing files or running programs from a shared folder using the SMBv1 protocol.	Enable SMBv2 or SMBv3 on both the SMB server and the SMB client, as described in KB2696547. Microsoft is working on a resolution that will be available later in June.

i find it hard to believe this is related, but it demonstrates how unimportant we are to Microsoft.

 

[mLipok]

 

https://stackoverflow.com/questions/50155482/after-windows-10-update-1803-my-program-cant-open-a-socket-when-running-from-ne

Quote

You can try to move your program to a SMBv2 or SMBv3 compatible server to check it.

 

 

Another interestning links:

https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/

https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

 

[orbs]

and...?  does it fix the issue?

[mLipok]

I just checked this and ... no  issue still exist.
But I'm not sure that I do all what I need properly, as this was only quick check.

 

Edited June 12, 2018 by mLipok

[Earthshine]

i disabled smbv1

whats the point? i read it was not so secure and since i have nothing that needs it, it got uninstalled 

Edited June 12, 2018 by Earthshine

[mLipok]

Using SMBv1 you are using old technology, which i buggy, so Microsoft starts treating this as a issue.
And drop all connection from shared folders to remote hosts.

 

[Earthshine]

I guess I'm just confused because I didn't think anything use that anymore it's so old

   Believe it's considered a security risk too so it would be better to install the newer SMB versions to the servers no?

Edited June 12, 2018 by Earthshine

[mLipok]

I think.
Default all old servers was designed to be compilant with older PC Station so there was by default SMB1 instead SMB2.

I'm not sure how Windows 2016 is configured by default.

 

[orbs]

first off, i'm not at all certain that the SMB version has anything to do with your issue.

second, have you first discovered which version of SMB you are actually using? i read that SMBv1 is not installed by default in Windows 10, and is deprecated on many other systems. so, are you actually using it?

also, did you try the "Trusted Site" option i suggested?

[mLipok]

Yes I add this \\192.168.1.199 to "Trusted Site" with no success.

as to this URL which you provide:

Quote

Applies to: Windows 10 version 1803Windows Server version 1803Windows 10 version 1709

I'm wondering Is it mean that in recent update SMB1 was disabled by installer ?
It might be the problem, I mean It was enabled previously and disabled recently by installer/updater .

 

[Earthshine]

smb1 is installed by default on win10 unless they just changed it. you have to uninstall it, you can turn on and off windows features.

welp, you guessed it, they CHANGED IT 2 released builds ago they are on version 1803.

SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions

enabling that Windows feature should fix ya!

Edited June 12, 2018 by Earthshine

[mLipok]

related:

 

[orbs]

this discussion at the MSDN forum suggests that you enable SMB v3 at the server side hosting the shared folder, which may be hell of a hassle if you need to reconfigure dozens of servers or Linux-based NAS/SAN devices.

this, however, was suggested before MS released another update: KB4284848, which (among other fixes included) states that it

Addresses an issue where some users may receive an error when accessing files or running programs from a shared folder using the SMBv1 protocol. The error is "An invalid argument was supplied".

and it is confirmed (by users in said discussion) that this update fixes the issue.

since personally i try to keep away from the infestation named "Windows 10" (and if i must, i keep it as outdated as possible), i cannot confirm this myself. help yourselves gentlemen, its an open buffet.