Sponsored Content
Top Forums UNIX for Advanced & Expert Users Connect direct - SFTP - List of servers that I can connect Post 303041452 by Chubler_XL on Sunday 24th of November 2019 03:39:11 PM
Old 11-24-2019
I believe IBM connect direct uses a proprietary protocol which is separate to and incompatible with SFTP.

Quote:
I was under the impression that SFTP will be successful between the servers only for which connect-direct is configured (atleast at server-level and not user-id level) between them.
SFTP runs over SSH and is used on thousands of systems around the world that don't have connect direct installed or configured.

Here are some answers to you specific numbered questions.
  1. SFTP is just a file transfer mechanism that runs over the SSH protocol. If you have SSH access to a computer you would normally also have SFTP access. If you have a password for an account on a remote computer that's running SSH and PasswordAuthentication is enabled (Servers can be configured to only allow public key authentication), and the User/Group is enabled for SSH access the you will be able to use SFTP. There is no file that lists all the servers you can access, but for each server you can check if password authentication is allowed and which users/groups have access.
  2. SFTP uses SSH for connection and transmission authentication can be configured to use password or public/private keys or both.
  3. What do you mean by refer? The starting directory for SFTP is configurable but defaults to the local account's home directory.
  4. Yes in the sshd_config on the target machine you can specify DenyUsers DenyGroups AllowUsers AllowGroups to control which accounts have access.
  5. direct connect uses it's own protocol which many have public/private keys but I would expect these would be separate to the SSH public/private keys.
These 3 Users Gave Thanks to Chubler_XL For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to direct-connect two UNIX boxes

Hello, I have a V880 and a 420 running Solaris 9. Each box has more than one NIC card. I'd like to know how to configure the network on the two boxes so that I can directly connect the NIC cards. Meaning, I don't want a switch or router between the two. I just want to run a CAT5 cable to each... (3 Replies)
Discussion started by: agcodba
3 Replies

2. Shell Programming and Scripting

need script to connect sftp servers

Dear friends, i need to connect sftp server from my home directory using script . Please can anyone help me on this. (1 Reply)
Discussion started by: kittusri9
1 Replies

3. Shell Programming and Scripting

Problem using connect direct

Hi, I have a script in which i'm using ndm connect direct to fetch data from the client server..syntax i'm using is ./con_using_connectdirect /load/nctrl nctrl $xhost where con_using_connectdirect is the script which establishes connection load/nctrl is the path from where data... (4 Replies)
Discussion started by: Sheema
4 Replies

4. Solaris

Connect direct configuration on Solaris

Hi, I am configuring Connect direct on Solaries 6.0, but whenever i am giving the below command cdpmgr -i /export/app/cdunix/ndm/cfg/khello/initparm.cfg i am getting the message Component <cdpmgr ndmcmgr ndmsmgr ndmumgr cdstatm> permissions are not set. Please follow instructions in the... (3 Replies)
Discussion started by: sidd
3 Replies

5. Red Hat

IBM Connect:Direct Error

Hi to all, I've installed IBM Connect:Direct 4.1.00 on Red Hat Enterprise Linux Server release 5.5, but when I try to execute the "direct cli", I obtain the following error: $ ./direct *********************************************************** * ... (2 Replies)
Discussion started by: f.vietti
2 Replies

6. Shell Programming and Scripting

Connect:Direct

Hello all, I have a requirement to transfer files to mainframe usinf NDM connect:direct. So can anybody provide me a sample shell script on how to call a connect;direct script by providing filename as a parameter please? Thanks, Ajay (0 Replies)
Discussion started by: ajaykumar4534
0 Replies

7. Shell Programming and Scripting

Connect direct script for unix

I want to connect direct a xml file and a excel file each separately from unix system to another unix system.The size of the xml file and excel file may vary each time. Below is the possible connect direct script to transfer the files.Please check if it is correct? Also does DCB parameter... (4 Replies)
Discussion started by: bk_12345
4 Replies

8. Red Hat

Linux to Connect direct transfer

I am transfering a file using connect direct from Linux to Mainframe. Its a point to point transfer but its failing with below error: **** Error from CONNECT:Direct API - ndmapi_recvresp_c error Can we do PTP transfers? code tags for code, please. (1 Reply)
Discussion started by: gerryperillo
1 Replies

9. UNIX for Dummies Questions & Answers

Issue with Connect direct ndmcli

Hi.. We are using connect direct to transfer the files between servers. The CD scripts run on HP UX. Below is the code using ndmcli. ndmcli -x << EOJ submit maxdelay=0 proc1 process snode=$3 step1 ... (1 Reply)
Discussion started by: anijan
1 Replies

10. AIX

Lenovo v3700 v2 direct connect to AIX

i have directly connect AIX pwer 7 to lenovo v3700 v2 without San through fiber card. but i cannot see the WWPN to add AIX as host in management console. (10 Replies)
Discussion started by: khalid khanAIB
10 Replies
Net::SFTP::Foreign::Constants(3pm)			User Contributed Perl Documentation			Net::SFTP::Foreign::Constants(3pm)

NAME
Net::SFTP::Foreign::Constants - Constant definitions for Net::SFTP::Foreign SYNOPSIS
use Net::SFTP::Foreign::Constants qw(:tag SSH2_FILEXFER_VERSION); print "Protocol version is ", SSH2_FILEXFER_VERSION; DESCRIPTION
Net::SFTP::Foreign::Constants provides a list of exportable SFTP constants: for SFTP messages and commands, for file-open flags, for status messages, etc. Constants can be exported individually, or in sets identified by tag names. Net::SFTP::Foreign::Constants provides values for all of the constants listed in the SFTP protocol version 3 draft; the only thing to note is that the constants are listed with the prefix "SSH2_" instead of "SSH_". So, for example, to import the constant for the file-open command, you would write: use Net::SFTP::Foreign::Constants qw( SSH2_FXP_OPEN ); TAGS
As mentioned above, constants can either be imported individually or in sets grouped by tag names. The tag names are: :fxp Imports all of the "SSH2_FXP_*" constants: these are the constants used in the messaging protocol. :flags Imports all of the "SSH2_FXF_*" constants: these are constants used as flags sent to the server when opening files. :att Imports all of the "SSH2_FILEXFER_ATTR_*" constants: these are the constants used to construct the flag in the serialized attributes. The flag describes what types of file attributes are listed in the buffer. :status Imports all of the "SSH2_FX_*" constants: these are constants returned from a server "SSH2_FXP_STATUS" message and indicate the status of a particular operation. :error Imports all the "SFTP_ERR_*" constants used to represent high level errors: "SFTP_ERR_LOCAL_ALREADY_EXISTS", "SFTP_ERR_LOCAL_CHMOD_FAILED", "SFTP_ERR_LOCAL_OPEN_FAILED", "SFTP_ERR_LOCAL_READ_ERROR", "SFTP_ERR_LOCAL_STAT_FAILED", "SFTP_ERR_LOCAL_UTIME_FAILED", "SFTP_ERR_LOCAL_WRITE_FAILED", "SFTP_ERR_REMOTE_BAD_PACKET_SEQUENCE", "SFTP_ERR_REMOTE_BAD_PERMISSIONS", "SFTP_ERR_REMOTE_BAD_TIME", "SFTP_ERR_REMOTE_BLOCK_TOO_SMALL", "SFTP_ERR_REMOTE_CLOSE_FAILED", "SFTP_ERR_REMOTE_FSETSTAT_FAILED", "SFTP_ERR_REMOTE_FSTAT_FAILED", "SFTP_ERR_REMOTE_LSTAT_FAILED", "SFTP_ERR_REMOTE_MKDIR_FAILED", "SFTP_ERR_REMOTE_OPENDIR_FAILED", "SFTP_ERR_REMOTE_OPEN_FAILED", "SFTP_ERR_REMOTE_READDIR_FAILED", "SFTP_ERR_REMOTE_READ_FAILED", "SFTP_ERR_REMOTE_REALPATH_FAILED", "SFTP_ERR_REMOTE_REMOVE_FAILED", "SFTP_ERR_REMOTE_RENAME_FAILED", "SFTP_ERR_REMOTE_RMDIR_FAILED", "SFTP_ERR_REMOTE_READLINK_FAILED", "SFTP_ERR_REMOTE_SYMLINK_FAILED", "SFTP_ERR_REMOTE_SETSTAT_FAILED", "SFTP_ERR_REMOTE_STAT_FAILED", "SFTP_ERR_REMOTE_WRITE_FAILED" and "SFTP_ERR_REMOTE_HARDLINK_FAILED". Note: these constants are not defined on the SFTP draft. :ext Import all the "SSH2_FXE_*" constants: there are the constants defined for usage with SFTP extensions. Currently, these are supported: "SSH2_FXE_STATVFS_ST_RDONLY", "SSH_FXE_STATVFS_ST_NOSUID". There is one constant that does not fit into any of the tag sets: "SSH2_FILEXFER_VERSION", which holds the value of the SFTP protocol implemented by Net::SFTP::Foreign. AUTHOR &; COPYRIGHTS Please see the Net::SFTP::Foreign manpage for author, copyright, and license information. perl v5.14.2 2012-05-11 Net::SFTP::Foreign::Constants(3pm)
All times are GMT -4. The time now is 09:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy