Hello,
We are using Shared Folder since 2021 without problems, but since the begining of this year, we started recieving and error "transport closed in negotiate" when trying to write a file from our app.
Does anyone have an ideia of the problem?
Thanks,
Pedro Oliveira
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.
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.