SFTP Error "No terminal authorization granted"

[M.Thomas]

Hi All,
we are getting the below error while doing sftp. Please help to me to fix this issue.
Thanks in advance.

debug: Ssh2AuthPubKeyClient/authc-pubkey.c:1940: Public key authentication was successful.
debug: Ssh2/ssh2.c:965: Returning user input stream to original values.
debug: Ssh2Common/sshcommon.c:768: num_channels now 1
debug: SshTtyFlags/sshttyflags.c:294: Not a tty. (fd = 0)
debug: Ssh2ChannelSession/sshchsession.c:2915: Requesting subsystem sftp
debug: Ssh2Common/sshcommon.c:166: DISCONNECT received: No terminal authorization granted
Disconnected (remote); protocol error (No terminal authorization granted).
debug: Ssh2Common/sshcommon.c:733: num_channels now 0
debug: Got session close with exit_status=0
Disconnect reason 2, exit code = 66

[Steven E. Protter]

Shalom,

Ideas:
1) Maybe the ssh deamon needs a restart on the target server.
2) Check the /var/adm/syslog/syslog.log on the target server.
3) Check permissions and ownership on .ssh and the files within.

http://www.hpux.ws/?p=10

SEP

[M.Thomas]

Hi SEP,
In remote node syslog i am able to find "Disconnecting: No terminal authorization granted" error message.

Permision for .ssh & authorized_keys2 is correct.

Please advice.

[M.Thomas]

Please advice is there any impact on existing connection if I restart ssh daemon.

[James R. Ferguson · Accepted solution]

Hi:

You can stop and restart the 'sshd' daemon without impact to user sessions that already exist. Do:

# /sbin/init.d/secsh stop
# /sbin/init.d/secsh start

Regards!

...JRF...

[Thomas Sluyter]

The error message in this case did not indicate a problem with your client or the SSH server software.

"Boks_sshd" is a version of OpenSSH which is included with FoxT's BoKS Access Control software. Using BoKS you can completely close access to your servers so only certain people are allowed very specific access.

The error message "No terminal authorization granted" means that your account was in fact NOT granted access to use SSH on this particular server. It could be that the security guys on the server did in fact allow your account to login, but that you were coming from a different IP address than usual.

In order to make sure that you can always log in, please contact the security folks in charge of the server you're trying to reach.

For more details on troubleshooting BoKS and login problems, see my personal website -> http://www.kilala.nl/Sysadmin/index.php?id=1255

Cheers,


Thomas Sluyter