WinSCP Connection through Wallix Bastion Failure but Works with PuTTY

Are you having trouble connecting to a server using WinSCP through Wallix Bastion? You're not alone. Many users have reported issues with this specific configuration, but the good news is that there are solutions available.

In this article, we will explore the reasons why WinSCP connection through Wallix Bastion might fail, and what you can do to resolve this issue. We will also compare this with a successful connection using PuTTY, and provide some troubleshooting tips to help you get started.

Why does WinSCP connection through Wallix Bastion fail?

WinSCP connection through Wallix Bastion might fail due to several reasons. One of the most common reasons is that the Bastion host does not allow connection to the target server using the SSH protocol on the default port (port 22).

Wallix Bastion is a secure access solution that provides a secure gateway between the user's device and the target server. It is designed to provide an additional layer of security by restricting access to the target server using specific protocols, ports, and authentication methods. By default, Wallix Bastion only allows access to the target server using the RDP protocol on port 3389. However, you can configure Wallix Bastion to allow access to the target server using other protocols, such as SSH, by creating a new connection policy.

Another reason why WinSCP connection through Wallix Bastion might fail is due to incorrect configuration of the connection policy. If the connection policy is not configured correctly, it might prevent the connection from being established. For example, if the authentication method is not set to "Password" or "SSH Key", the connection will fail.

Why does WinSCP connection through PuTTY work?

WinSCP connection through PuTTY works because PuTTY is a more flexible SSH client than WinSCP. PuTTY allows you to specify the port number and authentication method, which makes it easier to connect to a target server through a Bastion host. Additionally, PuTTY provides more options for configuring the SSH client, such as enabling compression and setting the cipher.

To connect to a target server using PuTTY through a Bastion host, you need to create a new session in PuTTY and specify the Bastion host as the SSH server. Then, you need to create a new SSH tunnel from the Bastion host to the target server. Once the tunnel is established, you can connect to the target server using the SSH client in PuTTY.

Troubleshooting WinSCP connection through Wallix Bastion

If you are experiencing issues with WinSCP connection through Wallix Bastion, here are some troubleshooting tips that you can try:

• Check if the connection policy is configured correctly. Make sure that the protocol is set to "SSH", the port number is set to the correct value, and the authentication method is set to "Password" or "SSH Key".
• Check if the Bastion host allows access to the target server using the SSH protocol. You can test this by connecting to the Bastion host using PuTTY and then creating a new SSH tunnel to the target server.
• Check if the target server is configured correctly. Make sure that the SSH server is running and that the firewall is configured to allow incoming connections on the SSH port.
• Check if there are any network issues. Make sure that the user's device is connected to the network and that there are no issues with the network connection.

WinSCP connection through Wallix Bastion might fail due to several reasons, such as incorrect configuration of the connection policy or restrictions on the Bastion host. However, there are solutions available to resolve this issue. By using PuTTY as an alternative SSH client, you can connect to the target server through the Bastion host using a more flexible SSH client. Additionally, by following the troubleshooting tips provided in this article, you can identify and resolve any issues with the WinSCP connection through Wallix Bastion.

References