Tag Info

New answers tagged

1

After discussing this in a chat and debugged the issue, it turned out that the required directive PermitTunnel yes was not in place and active. After adding the directive to /etc/ssh/sshd_config and reloading sshd by service sshd reload this was resolved. We added -v to the ssh command to get some debugging information and from that we found: debug1: ...


1

I had this problem when trying to connect via SSH with a user that was only authorized to connect using SFTP. For example, this was in the server's /etc/ssh/sshd_config: Match group sftponly ForceCommand internal-sftp ChrootDirectory /usr/chroot/%u [...] Match So in this case, to use SSH, you will have to either remove the user from the ...


0

Try the this command: ssh -f ubuntu@ubuntu -L 9000:localhost:23 If this works, it may be a host file issue


0

ssh works at the application layer whereas a VPN works at the transport or network layer. As a VPN works at the lower layers it can configure routing etc so that your remote computer works as if it were connected to your LAN. A ssh tunnel can't do this at the application layer therefore the remote user has to configure the tunnel manually to listen on a ...


1

From an IT standpoint, your VPN provider will have to push routes to your system to access the SAN or application servers the network is running. If RDP is pushed through another firewall or NAT, then you'll have to ask your system admin. If your IT team is smart, their firewall may block traffic from the VPN network to the server network. Which is why ...



Top 50 recent answers are included