SMB1 and next Windows 1709 (RS3)

This forum is for general support of Xbase++
Post Reply
Message
Author
User avatar
Auge_Ohr
Posts: 1405
Joined: Wed Feb 24, 2010 3:44 pm

SMB1 and next Windows 1709 (RS3)

#1 Post by Auge_Ohr »

SMB1 is not used in Windows World since Vista and will be "stopped" in next Windows 1709 (RS3) Release.
https://blogs.technet.microsoft.com/fil ... sing-smb1/
Update June 30, 2017 – You have probably seen me announce this on twitter and in other public venues: Windows 10 RS3 (Fall Creators Update) and Windows Server 2016 RS3 have SMB1 uninstalled by default under most circumstances. The full removal has begun. Make sure you check https://aka.ms/stillneedssmb1 for products that may require updates or replacement to be used without the need for SMB1.

Update July 7, 2017: if your vendor requires disabling SMB2 in order to force SMB1, they will also often require disabling oplocks. Disabling Oplocks is not recommended by Microsoft, but required by some older software, often due to using legacy database technology. Windows 10 RS3 and Windows Server 2016 RS3 allow a special oplock override workaround now for these scenarios – see https://twitter.com/NerdPyle/status/876880390866190336. This is only a workaround – just like SMB1 oplock disable is only a workaround – and your vendor should update to not require it. Many have by now (I’ve spoken to some, at least) and their customers might still just be running an out of date version – call your suppliers
but be aware while some Apps still use SMB1 (like some Xbase++ Developer do)
https://blogs.technet.microsoft.com/fil ... ringhouse/
greetings by OHR
Jimmy

Cliff Wiernik
Posts: 605
Joined: Thu Jan 28, 2010 9:11 pm
Location: Steven Point, Wisconsin USA
Contact:

Re: SMB1 and next Windows 1709 (RS3)

#2 Post by Cliff Wiernik »

We use the smb2 fix from Alaska to set the timeouts to 0 by default at it stops some intertasks things from seeing the file being available. For example, xbase++ apps runshells to call report writer to generated PDF file and exits. Xbase++ application then calls Xbase++ email function to send and attach this file. Without the SMB2 Alaska fix, from time to time, it does not yet see the file being available.

When you say some Xbase++ programs use SMB1, what do you mean and how do you know if you are using it.

User avatar
Auge_Ohr
Posts: 1405
Joined: Wed Feb 24, 2010 3:44 pm

Re: SMB1 and next Windows 1709 (RS3)

#3 Post by Auge_Ohr »

Cliff Wiernik wrote:When you say some Xbase++ programs use SMB1, what do you mean and how do you know if you are using it.
how do you use USE ?
SMB1 use UPD Port 135 - 139 while SMB2 use Port 445.
greetings by OHR
Jimmy

Cliff Wiernik
Posts: 605
Joined: Thu Jan 28, 2010 9:11 pm
Location: Steven Point, Wisconsin USA
Contact:

Re: SMB1 and next Windows 1709 (RS3)

#4 Post by Cliff Wiernik »

use filename driver 'ADSDBE' index filename alias FILENAME

For connection to both an ADSSERVER from windows workstation on a windows or OES-SLES environment.

IF we did not have an adsserver, it would be via adslocal.dll, but identical code.

User avatar
Auge_Ohr
Posts: 1405
Joined: Wed Feb 24, 2010 3:44 pm

Re: SMB1 and next Windows 1709 (RS3)

#5 Post by Auge_Ohr »

ADS is different while you use IP-Adress or Localhost.

i mean NET.EXE and "map" Drive which use Lanmanager with SMB1
For IT Administrators, the new SMB PowerShell supersedes the older NET.EXE tools for all share-related operations.

Here’s a table that compares the old NET.EXE command lines with the new PowerShell cmdlets:

Code: Select all

    NET.EXE command 	Equivalent SMB PowerShell

    NET SHARE 		Get-SmbShare
			           New-SmbShare
    			       Set-SmbShare
    			       Remove-SmbShare
    NET FILE 		 Get-SmbOpenFile
    			       Close-SmbOpenFile
    NET SESSION 	 Get-SmbSession
    			       Close-SmbSession
    NET USE 		  Get-SmbMapping
    			       New-SmbMapping
    			       Remove-SmbMapping
    NET CONFIG 	  Get-SmbServerConfiguration
    			       Set-SmbServerConfiguration
    			       Get-SmbClientConfiguration
    			       Set-SmbClientConfiguration
greetings by OHR
Jimmy

User avatar
Auge_Ohr
Posts: 1405
Joined: Wed Feb 24, 2010 3:44 pm

Re: SMB1 and next Windows 1709 (RS3)

#6 Post by Auge_Ohr »

https://support.microsoft.com/en-us/hel ... rsion-1709
Windows 10 Home and Windows 10 Professional still contain the SMBv1 client by default after a clean installation. If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.
greetings by OHR
Jimmy

User avatar
PedroAlex
Posts: 229
Joined: Tue Feb 09, 2010 3:06 am

Re: SMB1 and next Windows 1709 (RS3)

#7 Post by PedroAlex »

Auge_Ohr wrote:https://support.microsoft.com/en-us/hel ... rsion-1709
Windows 10 Home and Windows 10 Professional still contain the SMBv1 client by default after a clean installation. If the SMBv1 client is not used for 15 days in total (excluding the computer being turned off), it automatically uninstalls itself.

Hi, Jimmy.
many thanks for advise.

What problems can we have with this change?
Alaska 2.0 need SMBv1 and SMBv2?
Pedro Alexandre

User avatar
Auge_Ohr
Posts: 1405
Joined: Wed Feb 24, 2010 3:44 pm

Re: SMB1 and next Windows 1709 (RS3)

#8 Post by Auge_Ohr »

comercial wrote:What problems can we have with this change?
Alaska 2.0 need SMBv1 and SMBv2?
xBase (all Version) need some SMB when "share" Files.
if you still use SMB1, with Drive Letter, you will get NO Connection to Server which use SMB2x or SMB3x. :!:
greetings by OHR
Jimmy

Post Reply