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 <m...@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 <m...@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-a69e7847c9b8/ > >>> Gianni > >>> > >>> On Wed, 9 May 2018 17:35:52 -0500, Mike <m...@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 <m...@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] _______________________________________________ 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/CAGQ_JukEJvFgrPHRubiZ89Tfy0=s7gjzmqytcitbnqmei-h...@mail.gmail.com ** 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.
