11-24-2019
Connect direct - SFTP - List of servers that I can connect
Greetings Experts,
I am working for a bank client and have a question on connect-direct and SFTP.
We are using Linux RedHat servers. We use connect-direct to transfer (NDM) files from one server to another server. At times, we manually transfer the files using SFTP from one server to another server. We have a portal for connect-direct to check the list of nodes/servers configured to send/receive the files on a specific server.
With above given information..
I had a requirement to transfer a file from SIT environment to PROD environment (I know its not correct way, but due to un-avoidable situation did it). I had checked whether the connect-direct is configured between the 2 servers and confirm that they are not configured (verified netmap entries also). As no other alternative, I tried SFTP and transferred the file using SFTP successfully.
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.
I am not able to understand on below. Can you please help to explain.
Questions:
1. As SFTP successful, how can I know the list of servers I can successfully transfer through SFTP. Is there any file which contains the list of servers that can be connected to. Or is that I can connect to any servers through SFTP without any issues if I have the passwords.
2. Does SFTP also use the public and private keys for connections and transmission.
3. For SFTP, will it refer to both specified user-id home-directories on source and target servers or only on source server or only on target server.
4. Is there any way to restrict the users have SFTP access and allow only the specified users to have SFTP access.
5. Does connect-direct also use the public and private keys for connection establishment.
Thank you for your valuable suggestions and time.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
rsockd
RSOCKD(8) System Manager's Manual RSOCKD(8)
NAME
rsockd - SOCKSified SOCKS server
SYNOPSIS
rsockd [ -ver | -i | -I ]
DESCRIPTION
rsockd is the SOCKSified version of the SOCKS server sockd. Functionally rsockd is identical to sockd except that it may (though not nec-
essarily has to) make use of other SOCKS servers to reach some destinations. A number of rsockd's can be strung together or organized in a
cascade or other more complicated structures to serve the needs of a particular network configuration and restrictions. Obviously this
complicates the issues and make the setup and maintenance of the firewall more difficult. So use sockd instead whenever you can.
This document only describes the features of rsockd that are different from sockd. You should read sockd(5) carefully to gain a basic
understanding of of how the SOCKS server works.
When rsockd receives a request, it checks the request again its configuration (in exactly the same way that sockd does) to decider whether
the request is to be accepted. The primary difference between sockd and rsockd is in how they establish connection to the destination host
of a accepted request. sockd assumes that it can connect directly to the destination host and proceeds to do so. rsockd makes no such
assumption. Instead, it consults another configuration file to decide whether it can connect directly to the particular destination host or
whether it has to use a proxy connection through another SOCKS server. In other words, it behaves just like a versatile SOCKS client in
this regard. Therefore rsockd requires not only the SOCKS server configuration file /etc/sockd.fc or /etc/sockd.conf to decide whether to
accept or reject a request, but also the client configuration file /etc/socks.fc or /etc/socks.conf to decide how to reach the destination
host. If it is a multi-homed version and supports RBIND, it also needs the route file /etc/sockd.fr or /etc/sockd.fr to decide which net-
work interface to use for a connection.
Look at it in a different way, you can think of sockd as a special case of rsockd, one which can connect directly to all destination hosts.
In fact, an rsockd using the client configuration consisting of only this line
direct ALL 0.0.0.0
is functinally identical to the regular sockd.
Anther thing to mention is related to the use of identd. Only the SOCKS server which the requesting host directly connects to can find out
the identity of the real user. Suppose user x on host C connects to rsockd on server B which in turn connects to sockd on server A in order
to reach destination z. Host B can query identd on host C to find out whether the user is indeed x. To host A, the request appears to orig-
inate from user x on host B. An identd query from Host A to host B returns the userid that owns the rsockd process on host B, not the real
user x.
OPTIONS
See sockd(8).
EXAMPLES
The follwoing is an example of the client configuration file. See related man pages for examples on server configuration and route files.
# /etc/socks.conf for rsockd of domain rnd.xyz.com
#
# Use proxy connection through SOCKS server on socks.market.xyz.com
# to reach hosts within market.xyz.com
sockd @=socks.market.xyz.com .market.xyz.com 0.0.0.0
#
# Use direct connect to all other hosts within xyz.com
direct .xyz.com 0.0.0.0
#
# Use proxy connection through SOCKS server on gateway.xyz.com
# to reach all others
sockd @=gateway.xyz.com ALL 0.0.0.0
FILES
/etc/sockd.fc, /etc/sockd.conf, /etc/sockd.fr, /etc/sockd.route, /etc/socks.fc, /etc/socks.conf, /etc/inetd.conf, /etc/services,
/var/adm/messages, /etc/syslog.conf
SEE ALSO
sockd(8), socks_clients(1), sockd.conf(5), sockd.route(5), socks.conf(5), make_sockdfc(8), make_sockdfr(8), dump_sockdfc(8),
dump_sockdfr(8)
AUTHOR
Ying-Da Lee, ylee@syl.dl.nec.com
May 6, 1996 RSOCKD(8)