topic Proper syntax for copy run smb: in Network Security

Proper syntax for copy run smb:

ciscocharger — Mon, 11 Mar 2019 18:08:14 GMT

Hi,

I have a Cisco ASA and want to backup my config to a windows share.

I can't find any docs on the proper syntax for the "copy run smb:" parameters.

I'm promted for the address of the dest host and the dest filename....wher does the share auth info come in (smb://user:pass@server/share??)? do I use CIFS-like syntax for the share?...ie //sharename/folder?...

Can someone post a specific example on how to do this?

Thanks alot

Re: Proper syntax for copy run smb:

Nagaraja Thanthry — Tue, 06 Jul 2010 16:22:46 GMT

One of the ways you can backup the config to a specific share is by using TFTP and setting your share folder as the TFTP root folder. If you are using TFTPd32, set the working directory to your share folder where you would like to backup the configuration. Then go to the firewall and issue "copy run tftp." Follow the wizard and once the transmission is complete, you should have the file in your shared folder. You can also do this via ASDM. Hope this helps.

Re: Proper syntax for copy run smb:

tbrooks1 — Tue, 03 Feb 2026 16:41:04 GMT

https://www.iana.org/assignments/uri-schemes/prov/smb#:~:text=(last%20updated%202022%2D08%2D,semantics:%20Accessing%20SMB/CIFS%20shares

(last updated 2022-08-09)

Resource Identifier (RI) Scheme name: smb 
Status: provisional

Scheme syntax:
   smb://[<user>@]<host>[:<port>][/[<path>]][?<param1>=<value1>[;<param2>=<value2>]] or 
   smb://[<user>@]<workgroup>[:<port>][/] or
   smb://[[<domain>;]<username>[:<password>]@]<server>[:<port>][/[<share>[/[<path>]]][?[<param>=<value>[;<param2>=<value2>[...]]]]]
   example: smb://workgroup;user:password@server/share/folder/file.txt

Scheme semantics:
   Accessing SMB/CIFS shares

Encoding considerations:
   Unknown, use with care.

Applications/protocols that use this scheme name:

Interoperability considerations:
   Unknown, use with care.
   May be unsuitable for open use on the public internet.
Security considerations:
   Unknown, use with care.
Contact:
   Registering party: Dave Thaler <dthaler&microsoft.com>
   Scheme creator: IETF Draft
Author/Change controller:
   Either the registering party or someone who is verified to represent
   the scheme creator.  See previous answer.
References:
   http://en.wikipedia.org/wiki/Server_Message_Block, http://www.jarvana.com/jarvana/view/org/samba/jcifs/jcifs/1.2.19/jcifs-1.2.19-javadoc.jar!/jcifs/smb/SmbFile.html, https://datatracker.ietf.org/doc/html/draft-crhertel-smb-url


(file created 2012-09-23)