Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
Someone on the Italian TechNet Forum had a similar problem but with SQL server.
May be you can find something useful in the discussion.
Problemi connessione SQL dopo l'aggiornamento di Aprile 2018 https://social.technet.microsoft.com/Forums/it-IT/38a6727a-7dce-48ef-8c3e-a6...
Gianni
On Wed, 9 May 2018 17:35:52 -0500, Mike mike@ggisoft.com wrote:
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
Thanks, Gianni. That's a dead-on exact match for what I've run into.
But, the TechNet article you referenced seems to point the finger at SMBv1, or higher not being available.
While this might be the case, it's obvious that Windows 10 1803 is now applying additional restrictions when the EXE is launched from a shared drive instead of local. My EXE connects to MariaDB perfectly if the same EXE connects to the same server, when started from the local drive.
While this might be something in the network stack, low-level, it makes more sense (to me) that it would be a difference in the firewall (tried disabling it) or security policy settings. I've looked through the local security policy options (I'm NOT on a domain!) and nothing seems to apply.
The 'answer' in the Technet Forum discussion you sent seems to be to move the EXE file to a different server (Win Serv 2012 instead of 2008) but I don't have Windows Server anything...I'm 100% Linux (Samba) servers.
Microsoft, love to hate them.
Mike
Gianni Turri wrote:
Someone on the Italian TechNet Forum had a similar problem but with SQL server.
May be you can find something useful in the discussion.
Problemi connessione SQL dopo l'aggiornamento di Aprile 2018 https://social.technet.microsoft.com/Forums/it-IT/38a6727a-7dce-48ef-8c3e-a6...
Gianni
On Wed, 9 May 2018 17:35:52 -0500, Mike mike@ggisoft.com wrote:
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
Hi Mike:
If you suspect that the problem could be because of a new restriction policy, you may try to find the full description of what did include this update.
El jue., 10 may. 2018 5:33, Mike mike@ggisoft.com escribió:
Thanks, Gianni. That's a dead-on exact match for what I've run into.
But, the TechNet article you referenced seems to point the finger at SMBv1, or higher not being available.
While this might be the case, it's obvious that Windows 10 1803 is now applying additional restrictions when the EXE is launched from a shared drive instead of local. My EXE connects to MariaDB perfectly if the same EXE connects to the same server, when started from the local drive.
While this might be something in the network stack, low-level, it makes more sense (to me) that it would be a difference in the firewall (tried disabling it) or security policy settings. I've looked through the local security policy options (I'm NOT on a domain!) and nothing seems to apply.
The 'answer' in the Technet Forum discussion you sent seems to be to move the EXE file to a different server (Win Serv 2012 instead of 2008) but I don't have Windows Server anything...I'm 100% Linux (Samba) servers.
Microsoft, love to hate them.
Mike
Gianni Turri wrote:
Someone on the Italian TechNet Forum had a similar problem but with SQL
server.
May be you can find something useful in the discussion.
Problemi connessione SQL dopo l'aggiornamento di Aprile 2018
https://social.technet.microsoft.com/Forums/it-IT/38a6727a-7dce-48ef-8c3e-a6...
Gianni
On Wed, 9 May 2018 17:35:52 -0500, Mike mike@ggisoft.com wrote:
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on
a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local
folder, no help.
Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
Fernando,
Would love to.
Where to start?
Mike
Fernando D. Bozzo wrote:
Hi Mike:
If you suspect that the problem could be because of a new restriction policy, you may try to find the full description of what did include this update.
El jue., 10 may. 2018 5:33, Mike mike@ggisoft.com escribió:
Thanks, Gianni. That's a dead-on exact match for what I've run into.
But, the TechNet article you referenced seems to point the finger at SMBv1, or higher not being available.
While this might be the case, it's obvious that Windows 10 1803 is now applying additional restrictions when the EXE is launched from a shared drive instead of local. My EXE connects to MariaDB perfectly if the same EXE connects to the same server, when started from the local drive.
While this might be something in the network stack, low-level, it makes more sense (to me) that it would be a difference in the firewall (tried disabling it) or security policy settings. I've looked through the local security policy options (I'm NOT on a domain!) and nothing seems to apply.
The 'answer' in the Technet Forum discussion you sent seems to be to move the EXE file to a different server (Win Serv 2012 instead of 2008) but I don't have Windows Server anything...I'm 100% Linux (Samba) servers.
Microsoft, love to hate them.
Mike
Gianni Turri wrote:
Someone on the Italian TechNet Forum had a similar problem but with SQL
server.
May be you can find something useful in the discussion.
Problemi connessione SQL dopo l'aggiornamento di Aprile 2018
https://social.technet.microsoft.com/Forums/it-IT/38a6727a-7dce-48ef-8c3e-a6...
Gianni
On Wed, 9 May 2018 17:35:52 -0500, Mike mike@ggisoft.com wrote:
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored on
a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local
folder, no help.
Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
I don't know if you can find something here :
https://technet.microsoft.com/en-us/security/bulletins.aspx
El jue., 10 may. 2018 7:22, Mike mike@ggisoft.com escribió:
Fernando,
Would love to.
Where to start?
Mike
Fernando D. Bozzo wrote:
Hi Mike:
If you suspect that the problem could be because of a new restriction policy, you may try to find the full description of what did include this update.
El jue., 10 may. 2018 5:33, Mike mike@ggisoft.com escribió:
Thanks, Gianni. That's a dead-on exact match for what I've run into.
But, the TechNet article you referenced seems to point the finger at SMBv1, or higher not being available.
While this might be the case, it's obvious that Windows 10 1803 is now applying additional restrictions when the EXE is launched from a shared drive instead of local. My EXE connects to MariaDB perfectly if the same EXE connects to the same server, when started from the local drive.
While this might be something in the network stack, low-level, it makes more sense (to me) that it would be a difference in the firewall (tried disabling it) or security policy settings. I've looked through the local security policy options (I'm NOT on a domain!) and nothing seems to
apply.
The 'answer' in the Technet Forum discussion you sent seems to be to move the EXE file to a different server (Win Serv 2012 instead of 2008) but I don't have Windows Server anything...I'm 100% Linux (Samba)
servers.
Microsoft, love to hate them.
Mike
Gianni Turri wrote:
Someone on the Italian TechNet Forum had a similar problem but with SQL
server.
May be you can find something useful in the discussion.
Problemi connessione SQL dopo l'aggiornamento di Aprile 2018
https://social.technet.microsoft.com/Forums/it-IT/38a6727a-7dce-48ef-8c3e-a6...
Gianni
On Wed, 9 May 2018 17:35:52 -0500, Mike mike@ggisoft.com wrote:
Have already tried that. No change.
To be more precise...it's not that the EXE won't run, it's that the EXE can't connect to my Maria DB server.
BUT! Since the same application CAN connect to Maria DB if the EXE is run locally, this appears to be a security policy issue. I am NOT on a Domain!
Still troubleshooting...
Thanks Gianni!
Mike C
Gianni Turri wrote:
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows
features".
Gianni
On Wed, 9 May 2018 16:23:49 -0500, Mike mike@ggisoft.com wrote:
Heads up...
After updating to Win 10 Pro 17134 (last night) apps that are stored
on
a network share (Samba server) will no longer run. Move the EXE file to
a
local drive and it works fine.
Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local
folder, no help.
Move EXE file to a local folder, runs fine.
Same application has run for years as a share, even over a VPN link.
Mike Copeland
[excessive quoting removed by server]
https://stackoverflow.com/questions/50172067/sqlconnection-error-if-exe-is-e...
Looking at the above it seems to indicate that you can no longer run EXEs from shared locations when the protocol is SMB1. Having said that SMB1 was superseded in 2007 and deprecated in 2014. Samba supports up to SMB3.
I'm placing my bets on your deduction, Alan.
Now to make sure my Samba servers are all up-to-date!
Thank you!
Mike
Alan Bourke wrote:
https://stackoverflow.com/questions/50172067/sqlconnection-error-if-exe-is-e...
Looking at the above it seems to indicate that you can no longer run EXEs from shared locations when the protocol is SMB1. Having said that SMB1 was superseded in 2007 and deprecated in 2014. Samba supports up to SMB3.
Alan,
Confirmed. Many thanks!
But I still love to hate Windows.
Mike
Alan Bourke wrote:
https://stackoverflow.com/questions/50172067/sqlconnection-error-if-exe-is-e...
Looking at the above it seems to indicate that you can no longer run EXEs from shared locations when the protocol is SMB1. Having said that SMB1 was superseded in 2007 and deprecated in 2014. Samba supports up to SMB3.
On Thu, May 10, 2018 at 4:14 AM, Mike mike@ggisoft.com wrote:
But I still love to hate Windows.
Everyone needs a hobby.
On 10 May 2018 at 08:53, Alan Bourke alanpbourke@fastmail.fm wrote:
https://stackoverflow.com/questions/50172067/sqlconnection-error-if-exe-is-e...
Looking at the above it seems to indicate that you can no longer run EXEs from shared locations when the protocol is SMB1. Having said that SMB1 was superseded in 2007 and deprecated in 2014. Samba supports up to SMB3.
Good catch!
When SMB2 first arrived we had lots of problems so disabled it in some sites. This is what is causing my ADS Server problem I posted about.
Thanks Alan!!
p.s. found a nice powershell command: Get-SmbConnection Shows all your drive mappings and what SMB version they are using.
IMO despite some initial problems with CDX corruption and SMB2 there has been no reason not to use it for over 10 years since those problems were fixed. If nothing else it is orders of magnitude faster than SMB1.
I wonder when those problems were actually fixed, Alan. MS said multiple times that the problem was fixed with this Windows update or that Windows update. After being burned by file corruption multiple times, I stopped believing MS when they said that issues with the newer versions of SMB had addressed the problems with file-based databases like VFP, Access, Paradfox. Plating Russian roulette with my client's databases was just too risky.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Alan Bourke Sent: Thursday, May 10, 2018 7:19 AM To: profoxtech@leafe.com Subject: Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
IMO despite some initial problems with CDX corruption and SMB2 there has been no reason not to use it for over 10 years since those problems were fixed. If nothing else it is orders of magnitude faster than SMB1.
Ceased to be an issue for us by 2010 IIRC
Hi Gang,
Does anyone know if MS released a changelog for this Windows release? I'm seeing odd network issues that are unrelated to my previous problems.
e.g. can't connect to SQL server, access denied errors when creating a listening socket.
So much fun, isn't it?
The only problem we've seen (so far) is the can't connect remote desktop. Changing the server setting to uncheck the requirement for a secure connection at least lets that work. Connecting to SQL server has been noproblem.
Fred
On Tue, May 29, 2018 at 10:48 AM, Paul Hill paulroberthill@gmail.com wrote:
Hi Gang,
Does anyone know if MS released a changelog for this Windows release? I'm seeing odd network issues that are unrelated to my previous problems.
e.g. can't connect to SQL server, access denied errors when creating a listening socket.
-- Paul
[excessive quoting removed by server]
All connection problems disappeared once we updated both VM, VM Host and TS Client OS's to the latest release.
Certainly no problems connecting to SQL (Server 2012 with SQL 2012).
Dave Crozier Software Development Manager Flexipol Packaging Ltd.
--------------------------------------------------------------- This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. If you have received this e-mail in error you must not copy, distribute or take any action in reliance on it. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
Flexipol Packaging Ltd. has taken every reasonable precaution to minimise the risk of virus transmission through email and therefore any files sent via e-mail will have been checked for known viruses. However, you are advised to run your own virus check before opening any attachments received as Flexipol Packaging Ltd will not in any event accept any liability whatsoever once an e-mail and/or any attachment is received.
It is the responsibility of the recipient to ensure that they have adequate virus protection.
Flexipol Packaging Ltd. Unit 14 Bentwood Road Carrs Industrial Estate Haslingden Rossendale Lancashire BB4 5HH
Tel:01706-222792 Fax: 01706-224683 www.Flexipol.co.uk ---------------------------------------------------------------
Terms & Conditions:
Notwithstanding delivery and the passing of risk in the goods, the property in the goods shall not pass to the buyer until the seller Flexipol Packaging Ltd. ("The Company") has received in cash or cleared funds payment in full of the price of the goods and all other goods agreed to be sold by the seller to the buyer for which payment is then due. Until such time as the property in the goods passes to the buyer, the buyer shall hold the goods as the seller's fiduciary agent and bailee and keep the goods separate from those of the buyer and third parties and properly stored protected and insured and identified as the seller's property but shall be entitled to resell or use the goods in the ordinary course of its business. Until such time as the property in the goods passes to the buyer the seller shall be entitled at any time
-----Original Message----- From: ProFox profox-bounces@leafe.com On Behalf Of Paul Hill Sent: 29 May 2018 18:49 To: ProFox Email List profox@leafe.com Subject: Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
Hi Gang,
Does anyone know if MS released a changelog for this Windows release? I'm seeing odd network issues that are unrelated to my previous problems.
e.g. can't connect to SQL server, access denied errors when creating a listening socket.
-- Paul
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CADwx0+L93==XRBnecQ3EeqkfnuK0pKHRPNMh... ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Homegroup was removed in 1803, if you're not using a Windows domain due to your servers being Linux I don't know if that is relevant.
-
Alan Bourke -
Dave Crozier -
Fernando D. Bozzo -
Fred Taylor -
Gianni Turri -
Mike -
Paul Hill -
Richard Kaye -
Ted Roche