The error usually points to an SMB negotiation failure — often because the target Windows share/server has disabled SMBv1 (which is insecure and commonly turned off nowadays), and the component's underlying library (jcifs-ng or similar) doesn't fully support SMBv2/3 properly, or the negotiation gets dropped early.

Switch to a more modern connector that supports SMB2/3.  

   Try the File System Forge component: 

https://www.outsystems.com/forge/component-overview/68/filesystem-o11  

   Or build a custom integration via REST to an API that handles file writes (e.g., Azure Files, AWS S3, or your own .NET service with modern SMB).

If it's OutSystems Cloud → on-prem share: Double-check firewall/VPN rules, NTLM auth, and that the share allows connections from cloud IPs. Sometimes it's a transient negotiate timeout.

Hello,

Since Shared Folder version 2.0 supports SMB 1.0, SMB 2.0, SMB 2.1 and SMB 3.0.

I remember we considered using a FileSystem in the past, but there was something that prevented it.

Note: We are in OutSystems Cloud and we write files on-prem.

Thanks,

Pedro Oliveira

Hi @Pedro Oliveira 

Since you're running in Outsystems Cloud and writing to an on-premises shared folder, you can investigate whether anything changed on the network or file server side around the beginning of the year. Shared Folder 2.0 supports SMB 1.0, 2.0, 2.1, and 3.0, so if this was working since 2021 and started failing recently, you can check:

• Windows Server updates affecting SMB negotiation.
• Changes to SMB protocol settings (e.g., SMB1 disabled, SMB signing requirements, SMB hardening policies).
• Firewall or VPN changes between the OutSystems Cloud infrastructure and the on-prem network.
• Changes to the service account permissions or authentication mechanism.
• Antivirus/security software inspecting or blocking SMB traffic.