SAP B1 Install: Problems to access Shared Folders from Windows Version 1803

[former_member547648]

Hi,

I am trying to install the Windows Components for SAP Business ONE / HANA on a Windows 10 (version 1803).

I had already successfully installed these components, but the there was some problem with the windows server and the server got reinstalled.

When I try to install the windows components I get to the screen where I a supposed to choose the components to install, but I cannot install them because another screen opens informing me that it cannot access the shared folders.

I checked on the server and it seems that shared folders are ok:

As the newer versions of windows 10 (since 1709?) don't support samba v1 per default, since it is a security risk. The Administrator's Handbook states:

Make sure that your Windows machine can connect to Samba protocol version 1. If you enforce using Samba protocol version 2 or higher on the Windows machine, you need to install your Linux components on SUSE 12.

It would have been nice to know what components to install on SLES 12. But I have already 4.6.14+ that is why I think it should support version 2 or newer.

Therefore I edited /etc/samba/smb.conf

[global]
.... other stuff
min protocol = SMB2
max protocol = SMB3
client min protocol = SMB2
client max protocol = SMB3

I am not sure whether this neccesary, because I read that per default if no version is specified version 3 or newer is assumed. But I am not sure whether this applies to SLES 12.

I restarted samba. Checked the validation on the server which showed that the shared folders are okay. But unfortunately I still get the same error.

Any advice appreciated.

Best regards

Nils Stritzel

[former_member547648]

Ok, I think I got working. I change the smb.conf so that contained:

[global]
.... other stuff
min protocol = NT1
max protocol = NT1
client min protocol = NT1
client max protocol = NT1

..other stuff

Not sure why this works. If somebody can enlighten me, I would be grateful.

[chaiyongs]

Please try to change this value by Registry Editor, it's working.

Configured registry value: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:1

[oscarp]

In Windows 10, version 1709, Windows 10, version 1903, Windows Server, version 1709, Windows Server, version 1903, and later versions of Windows, the SMB2 client no longer allows the following actions:

• Guest account access to a remote server
• Fallback to the Guest account after invalid credentials are provided

If you want to enable insecure guest access, you can configure the following Group Policy settings: Computer configuration\administrative templates\network\Lanman Workstation "Enable insecure guest logons"

Note By enabling insecure guest logons, this setting reduces the security of Windows clients.

https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows...

[ndonzis]

Hi all,

Any update on this problem? We've tried the suggestions but none of them worked.

Thanks and regards,

[Andre_S]

Hi,

we could temporary solve it with "Enable insecure guest logons" setting which was suggested by Oscar. We raised also a SAP ticket but without proper result.

[Andre_S]

Hi all,

we're facing the same error message when installing B1 10.0 PL02 on a Windows Server 2019 machine. Did anyone solve it so far? Or is it worth raising a SAP ticket?

@Oscar Perez where do you have this solution from? Was it suggested by SAP?

Regards

[anandrd]

Hi andre.seiss

Hope you and team doing good!

Does the solution proposed by Oscar Perez helps to solve the error?

If no, provide your inputs as well.

Best Regards,

Anand Ramachandran

[Andre_S]

Hello anandrd

yes it solved it as workaround.
We raised also ticket to SAP but they did not release official configuration proposal yet.

[anandrd]

Thanks andre.seiss

Have a nice weekend

Best Regards,

Anand

[greg_niecka]

Hi All,

for me, I had to enable this feature on windows Guest access in SMB2 disabled by default in Windows and run windows updates and windows restart. I had also this windows feature enabled

Regards

GN

[lucca_mello]

Hi Nils,

We currently saw that a few partners were facing the same issue. You can try to follow the steps of the SAP Note 2372080 - Unable to access samba shared folders to see if the issue is solved;

There are two other notes that are link to the main note above:

• 2359442 - Validation - shared folder b1_shf
• 2523271 - Validation - Technical User b1service0

Hope the notes above can lead you to resolve the issue 🙂

Thanks and regards,

Lucca Mello

[hendraprakasa]

Hi,

I'm facing this issue also when upgrading SBO 10 PL 1 to PL 2

it detect error accesing shared folder

I'm upgrade from win server 2019, i've tried to run above suggested, but no work

--- try to change this (no work)

min protocol = NT1
max protocol = NT1
client min protocol = NT1
client max protocol = NT1

try microsoft web - no work

https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows...

please help how to solve this ?

Thanks & Regards,

Hendra

[carolina0509]

thank you, this works for me

regards