The copy is initiated from the client system so there is no port to open there. you run ‘cp //target/file //@/home’ to copy the file locally.
No thats what I thought, but for a particular set of users on a particular subnet can't seem to get the custom command to work.
the only reason why we've got the:
cp //%h/%p /
command in the 1st place is to allow users to pull large log file from servers to analyse better on their local machines.
The I'm using the same role as the users experiencing the issue, and it works, but the users from a different location just gets errors. so it's not the ACLs that are an issue.
all i can think of is some specific port that might be blocking this?
Are they using a nsh proxy to get to the targets or access it directly? if they do a ‘nsh here’ can they get to the target servers?
totally forgot that our NSH was pumped via another port i.e. when setting the secadmin command. Port opened and it's all working fine now.