Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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 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 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 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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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 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 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/500035a3-9814-17f9-916f-b16ef94e5...@ggisoft.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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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 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 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_Ju=dawluvcswtxv8+qczsdaw6sdckbcjm94jwwzz40k...@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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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 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/e45986a7-75b4-ce39-8dc6-8a2dd6878...@ggisoft.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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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 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/5gv6fdhrvcsh6i9ihjlna5t05n43lpb...@4ax.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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 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/0f1c40ea-d6ee-fa9e-e81f-478faa5b8...@ggisoft.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.
Re: Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
Try enabling "SMB 1.0/CIFS File Sharing Support" in "Windows features". Gianni On Wed, 9 May 2018 16:23:49 -0500, Mike 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 ___ 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/gct6fdd2vg9q9kupbpojgno2q5vd8sm...@4ax.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.
Re: Windows 10 April 2018 Update & ADS Server
"hold off the regular monthly updates for up to 30 days", god! I had forgotten what Wd$ was all about. Thanks for the reminder. On 09/05/18 17:03, Ted Roche wrote: One of my clients had to recreate all their RDP settings. Whether that was related to this change, or just because the target machine changed its DNS name and that didn't show until the monthly reboot, well, we may never know. The post I made earlier about blocking the "April Update" also had some suggestions on settings you could use to hold off the regular monthly updates for up to 30 days, to let someone else beta-test them :) I set that up here on the couple of machines running Pro versions of Windows. Not that I paid for them ;) On Wed, May 9, 2018 at 3:41 PM, Fred Taylor wrote: Thanks Paul. Now maybe I'll have to talk someone through how to change it, since it's a remote site. Fred On Wed, May 9, 2018 at 12:12 PM, Paul Hill wrote: On 9 May 2018 at 20:00, Fred Taylor wrote: We don't use Advantage, but we had a problem with a machine trying to use remote desktop after the latest update for W10. Had to uninstall it. It kept saying something about security corruption. The old 'Allow remote connections to this computer' is enabled in system settings and firewall is OK. There is now a new setting 'Enable Remote Desktop On/Off' in Settings -> Remote Desktop. Thanks Microsoft. I installed this update remotely and now I'm locked out. -- Paul [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/27a142b6-c855-bb7b-9fc7-915889026...@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.
Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
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 ___ 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/e65c7564-c916-c3d4-4c20-c9dbb5fc0...@ggisoft.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.
Re: Windows 10 April 2018 Update & ADS Server
One of my clients had to recreate all their RDP settings. Whether that was related to this change, or just because the target machine changed its DNS name and that didn't show until the monthly reboot, well, we may never know. The post I made earlier about blocking the "April Update" also had some suggestions on settings you could use to hold off the regular monthly updates for up to 30 days, to let someone else beta-test them :) I set that up here on the couple of machines running Pro versions of Windows. Not that I paid for them ;) On Wed, May 9, 2018 at 3:41 PM, Fred Taylor wrote: > Thanks Paul. Now maybe I'll have to talk someone through how to change it, > since it's a remote site. > > > Fred > > On Wed, May 9, 2018 at 12:12 PM, Paul Hill wrote: > >> On 9 May 2018 at 20:00, Fred Taylor wrote: >> > We don't use Advantage, but we had a problem with a machine trying to use >> > remote desktop after the latest update for W10. Had to uninstall it. It >> > kept saying something about security corruption. >> >> The old 'Allow remote connections to this computer' is enabled in >> system settings and firewall is OK. >> There is now a new setting 'Enable Remote Desktop On/Off' in Settings >> -> Remote Desktop. >> >> Thanks Microsoft. I installed this update remotely and now I'm locked out. >> >> -- >> Paul >> [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/CACW6n4s9-=nnci7amjnmfmstl312_rqgdnx7kesb0evovyc...@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.
Re: Windows 10 April 2018 Update & ADS Server
Thanks Paul. Now maybe I'll have to talk someone through how to change it, since it's a remote site. Fred On Wed, May 9, 2018 at 12:12 PM, Paul Hill wrote: > On 9 May 2018 at 20:00, Fred Taylor wrote: > > We don't use Advantage, but we had a problem with a machine trying to use > > remote desktop after the latest update for W10. Had to uninstall it. It > > kept saying something about security corruption. > > The old 'Allow remote connections to this computer' is enabled in > system settings and firewall is OK. > There is now a new setting 'Enable Remote Desktop On/Off' in Settings > -> Remote Desktop. > > Thanks Microsoft. I installed this update remotely and now I'm locked out. > > -- > Paul > [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/CAJCBksq+vEZ=nPB7CGyB1LJWk4=j+my56ty26gcf0kgwbjc...@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.
RE: Windows 10 April 2018 Update & ADS Server
We also had some fall-out from the Windows updates just released. This link seems to describe the root cause: https://itluke.online/2018/03/29/solved-authentication-error-function-not-supported/ -- rk -Original Message- From: ProfoxTech On Behalf Of Paul Hill Sent: Wednesday, May 09, 2018 3:13 PM To: profoxt...@leafe.com Subject: Re: Windows 10 April 2018 Update & ADS Server On 9 May 2018 at 20:00, Fred Taylor wrote: > We don't use Advantage, but we had a problem with a machine trying to use > remote desktop after the latest update for W10. Had to uninstall it. It > kept saying something about security corruption. The old 'Allow remote connections to this computer' is enabled in system settings and firewall is OK. There is now a new setting 'Enable Remote Desktop On/Off' in Settings -> Remote Desktop. Thanks Microsoft. I installed this update remotely and now I'm locked out. -- 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/dm5pr10mb1244c0004fb3a2923b47fb48d2...@dm5pr10mb1244.namprd10.prod.outlook.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.
Re: Windows 10 April 2018 Update & ADS Server
On 9 May 2018 at 20:00, Fred Taylor wrote: > We don't use Advantage, but we had a problem with a machine trying to use > remote desktop after the latest update for W10. Had to uninstall it. It > kept saying something about security corruption. The old 'Allow remote connections to this computer' is enabled in system settings and firewall is OK. There is now a new setting 'Enable Remote Desktop On/Off' in Settings -> Remote Desktop. Thanks Microsoft. I installed this update remotely and now I'm locked out. -- 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++ccxpfqlm9mhynf0s5mwwim3zw8ndav5wmxcj0srr...@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.
Re: Windows 10 April 2018 Update & ADS Server
We don't use Advantage, but we had a problem with a machine trying to use remote desktop after the latest update for W10. Had to uninstall it. It kept saying something about security corruption. . Fred On Wed, May 9, 2018 at 11:26 AM, Paul Hill wrote: > Hi Guys, > > Just a heads up. I currently have 5 legacy sites running Advantage > Database Server down after installing the latest Windows 10 update. > > Tried the usual tricks (firewall, anti-virus etc) but no joy. > > Not sure if there are any Fox folks using this, but it's commonly used > with xBase++. > > -- > Paul > [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/CAJCBkspLqFqD3=dnjzu2m8qpy76687nfszg3h6ar5mgtbk5...@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.
Windows 10 April 2018 Update & ADS Server
Hi Guys, Just a heads up. I currently have 5 legacy sites running Advantage Database Server down after installing the latest Windows 10 update. Tried the usual tricks (firewall, anti-virus etc) but no joy. Not sure if there are any Fox folks using this, but it's commonly used with xBase++. -- 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++igahnvoyb7yv6q3s6bee5nhbzwag1i6p+l3voaq1...@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.
Re: Fun with date calculations in VFP
On Tue, May 8, 2018 at 5:39 PM, Richard Kaye wrote: > I owe you a Scotch next time you're in the area. > Deal! -- Ted Roche & Associates, LLC http://www.tedroche.com ___ 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/cacw6n4tiw068o_fbcffjqfcvckmbox1kmqquesry5mo1gbv...@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.
