SMB

How it works

SMB is sharing more than transfer. Locks, partial writes, and directory listings are normal. A copy off the share is the transfer. An open handle on the share is not a finished copy. Encryption is optional on older dialects and expected on newer ones.

A edit bay writes 8 GB to a share. The render node reads the same path 10 minutes later and gets a short file because the write handle is still open. A copy-then-rename into the watched folder fixes it. The render sees the final name only when the bytes are complete.

How it differs

SMB is not SFTP and not a browser link. It needs a LAN or a VPN that allows the ports.

Guest SMB on an open Wi-Fi share is a public folder.

Require a current dialect and a user.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For smb, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive smb files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.