Sponsored Content
Top Forums Shell Programming and Scripting Unable to transfer files from Windows 2000 Server to Sun Solaris.. Post 302411927 by curleb on Friday 9th of April 2010 10:23:00 PM
Old 04-09-2010
Only caveat with methyl's approach is the password is stored in plain-text on the windows machine. If scp is already present and functional and you're going to write a batch file anyway, why not keep it in play? It offers the capacity for automation without cause for security concerns, while eliminating the need to resurrect FTP services that were disabled...for good reason.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Transfer files from Unix server to Windows using FTP

Dear Friend, I don't know much about unix.I am an VB6.0 Programmer.I need to move an text files as aaa.txt from unix server to windows "D: " driver using the FTP protocol.Is it possible to do this with help of unix shell script.If possible please give some sample codes. Please answer as early... (1 Reply)
Discussion started by: gjsaravanan
1 Replies

2. Solaris

Copy Folders from Sun Solaris to Windows server.

Hi, I have a folder with diff subfolders in my Unix box and now I want to ftp all the floders into my Windows machine. Is there any easy way to do that. When I use the "mget " cmd and try to FTP the files, it throws an error that the sub folder name does not exist. Can you someone help in... (3 Replies)
Discussion started by: chandu_kalari
3 Replies

3. Solaris

Transfer files from Solaris to windows

Please let me know a efficient way to transfer files from a solaris to a windows machine. Total size of data is 800GB. (3 Replies)
Discussion started by: pingmeback
3 Replies

4. Shell Programming and Scripting

Transfer files from linux server to windows using secure ftp (sftp)

HI, I have to transfer files from linux server to windows using secure ftp (sftp) .Kindly help me out. (3 Replies)
Discussion started by: manushi88
3 Replies

5. Solaris

Transfer files from windows to solaris with winscp (file protocol:SFTP)

Hello, I have a couple of zip files to be copied from my local drive to a folder in solaris10 residing in a VM ware. i am using WINSCP, I tried to get hold of the solaris hostname or ip using ifconfig -a , hostname|nslookup etc. when i create a new session in WINSCP using that IP and port... (6 Replies)
Discussion started by: herbich1985
6 Replies

6. IP Networking

How to transfer files from UNIX server to windows machine or vice versa using ftp or sftp commands?

hi, i want to write a shell script code which transfers files from a directory in unix server to a directory in a windows machine.. can any1 give me a sample code which uses ftp or sftp command.. thanks very much, (3 Replies)
Discussion started by: Little
3 Replies

7. Shell Programming and Scripting

Script to transfer files from Solaris to windows

Hi All Please can you help, I´ve wrote the following script on a solaris 10 server to transfer files to a windows machine. #!/usr/bin/sh cd /moneta_polled01/download HOST=10.100.4.72 USER=user1 PASSWD=V7stop /usr/bin/ftp -v $HOST <<EOF user $USER $PASSWD cd tmp binary put... (7 Replies)
Discussion started by: fretagi
7 Replies

8. Shell Programming and Scripting

Do I require remote login access to a windows server to transfer files from a UNIX server

Hi All I need to transfer a file from a UNIX server to a windows server. I saw that it is possible to do this using scp command by looking at the forum listed below: ... (2 Replies)
Discussion started by: vx04
2 Replies

9. Shell Programming and Scripting

Help with a script to transfer files from Solaris to windows

Hi Please can you tell me what could be wrong with the following scriptto transfer files from solaris 10 to windows machine: #!/bin/sh HOST=<IP> USER=administrator PASSWD=xyz123zyx /usr/bin/ftp -inv <<EOF connect $HOST user $USER $PASSWD cd Documents binary mput *.sh bye EOF (23 Replies)
Discussion started by: fretagi
23 Replies
DUPLOAD.CONF(5) 						  Debian Project						   DUPLOAD.CONF(5)

NAME
dupload.conf - configuration file for dupload DESCRIPTION
The configuration file is rather straight forward Perl code as it's included by the dupload script via "do $config". The config file is read as Perl code! Any dupload.conf must begin with "package config;" because "config" is the namespace expected by dupload. For examples of the configuration please refer to the global configuration file /etc/dupload.conf. It contains associative arrays, each indexed by the nickname (see --to option of dupload), for the following items: fqdn [required] The fully qualified domain name (FQDN) of the nickname. method [optional] The transfer method. The available methods are: "ftp" (which is the default), "scp", "scpb" and "rsync" (over SSH). If you are using an upload queue, use FTP because it's fast. If you are using an authenticated host, always use scp or rsync via SSH, because FTP transmits the password in clear text. For scp and rsync to work properly, you have to setup the remote and local host to establish a ssh/slogin connection using .shosts/.rhosts or the files in ~/.ssh/. If you don't want or can't do that, you may find the scpb more convenient since it uploads in batch, reducing the number of password prompts. The only major caveat of the rsync and scpb options is that the files are processed in a batch mode, i.e. not separately, so in case of an error dupload won't be able to detect which part of the transfer failed, and just delete the .upload file completely. login [optional] The account name used to log into the FTP server. The default is "anonymous", should work with firewall logins too. incoming [required] Incoming directory, the directory we try to upload to. queuedir [optional] The directory we move the uploaded files to (after successful upload to incoming. Usually necessary only with some special upload queues. mailto [optional] Email address where the announcement about stable packages is sent. mailtx [optional] Email address where the announcement about unstable and experimental packages is sent. cc [optional] Email address where to send a copy address of the announcement. fullname [optional] Your full name, one that should appear in the announcement; If you leave this setting empty, the default will depend on your mail system. Usually the full name will be copied from the GCOS field in /etc/passwd. visibleuser [optional] Your username that should appear in the announcement. Defaults to "getlogin()". visiblename [optional] The host/domain name that appears as the part to the right of the @ character in the from-part of the announcement. Defaults to the value your local MTA likes. passive [optional] Set the passive mode for FTP transfers. Since dupload uses Net::FTP, you can also use the environment variable FTP_PASSIVE. options [optional] String that will be added verbatim to the command line of any scp or rsync calls done. dinstall_runs [optional] Tells dupload that the remote host runs dinstall (or equivalent) so that dupload won't send a duplicate announcement mail. The default is 0 (false), set it to 1 to enable it. nonus [optional] Tells dupload that the remote host is a valid destination for packages with non-US in their Section field, so that dupload doesn't warn about it. The default is 0 (false), set it to 1 to enable it. archive [optional] If set to 0 (false), adds a "X-No-Archive: yes" header in the announcement. The default is 1 (true). The configuration files also contain the following global variables: default_host [optional] The default host to upload to. The default value of this variable is unset. no_parentheses_to_fullname [optional] Prevents dupload to add parentheses around the full name when making mail announcements. Default is 0 (false), set it to 1 to enable it. HOOKS
Hooks are a powerful way to add actions which will be run before or after a dupload (like the preinst and postinst script of dpkg). You have two sort of hooks: pre-upload and post-upload. Both are simple shell commands (executed by "sh -c" so you can use any shell tricks). Pre-uploads are always run (even in dry mode) and stop dupload if they fail (failure being mesured by the hook's exit status). Post-uploads are only run when you are not in dry mode and only if the uploading succeeded. Both sorts of hooks are run for a given category: changes, sourcepackage, package, file or deb. changes This hook is run once per "changes" file (given as an argument to dupload) with the filename as its parameter. sourcepackage This hook is run once per "changes" file with the source package name and its version as its two parameters. package This hook is run once per binary package (a "deb" file) with the package name and its version as its two parameters. file This hook is run once per uploaded file, with the file name as its parameter. deb This hook is run once per binary package (a "deb" file) with the filename as its parameter. Syntax Hooks are defined in two Perl hashes, %preupload and %postupload, each indexed by category. In addition to the global hashes, each host entry has two fields with the same names, for the host-specific hooks. The shell command will be substituted first: %1 will be replace by the first argument, etc. Per-host or global hooks A hook can be global (for all the hosts) or it can be for a specific host. If there is no specific hook, for a given category, the global one is used. Examples This one runs lintian before uploading. It is global and guarantee that you will always upload lintian-free packages (thanks to lintian return status). $preupload{'deb'} = 'lintian -v -i %1'; This one just display the name and versions of successfully uploaded packages. $postupload{'package'} = 'echo PACKAGE %1 %2 uploaded'; Unlike the two others, this one is specific to one host, master. $cfg{master}{preupload}{'changes'} = "echo Uploading %1"; LOCATION
The configuration is searched as following: /etc/dupload.conf ~/.dupload.conf The latest entries override the former. ENVIRONMENT VARIABLES
Those of Net::FTP for the FTP method: FTP_FIREWALL FTP_PASSIVE AUTHOR
Heiko Schlittermann <heiko@lotte.sax.de> Stephane Bortzmeyer <bortzmeyer@debian.org> dupload 2.7.0 February 2011 DUPLOAD.CONF(5)
All times are GMT -4. The time now is 06:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy