# WinSCP / no connection

**URL:** <https://community.allstarlink.org/t/winscp-no-connection/25114>\
**Category:** AllStarLink\
**Created:** [October 22, 2026, 1:22pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114 "2026-10-22T13:22:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\
**Post date:** [October 22, 2026, 1:22pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114/1 "2026-10-22T13:22:20Z")

</div>

I have just begun a 2 node ASL3 install again. Following the ' raspberry Pi appliance Installation ' up to the ' Restart Asterisk Now '. All is OK. BEFORE I continue, I want to be sure I can use WinSCP going forward. From a previous post, I am told:  
Literally none of the configuration being discussed here is needed to SFTP files from WinSCP to an ASL3 node. Enter the hostname, username, and password and it'll just work. By default, files will end up in `/home/$USER` for whatever your username is.  
I cannot connect to the Pi with WinSCP?

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [October 22, 2026, 2:40pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114/2 "2026-10-22T14:40:49Z")

</div>

You will need to provide more info. WinSCP and any SSH client will work fine. What errors are you getting? What is your config.

---

<div class="post-metadata">

**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\
**Post date:** [October 22, 2026, 5:22pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114/3 "2026-10-22T17:22:56Z")

</div>

Raspberry Pi 3b. Followed Appliance install, then node setup, then restart asterisk. Open WINScp. As instructed, File protocol SFTP. Host name is local IP address. Port set correctly. User name correct. Password correct. ADVANCED: SFTP server=default. LOGIN, searching for host, Network error: Connection to xxx.xxx.xxx.xxx timed out.

 ![NetworkError](https://community.allstarlink.org/uploads/default/original/2X/4/49708dc81e1e71f3a1d5f41104b5dec3c35a27b8.jpeg)  
 ![WinScpAdvanced](https://community.allstarlink.org/uploads/default/original/2X/1/1d2b3256ba4c6a0f026f05d04bba88b20c2a0cb2.jpeg)

---

<div class="post-metadata">

**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\
**Post date:** [October 22, 2026, 8:04pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114/4 "2026-10-22T20:04:22Z")

</div>

Fixed! Systemctl status ssh showed port 22, which DOES work. Guess I still have to change to our desired port.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [October 22, 2026, 8:36pm UTC](https://community.allstarlink.org/t/winscp-no-connection/25114/5 "2026-10-22T20:36:58Z")

</div>

22 is the default SSH port. Old systems doing random ports is an ancient security-through-obscurity that doesn’t hold up in 2026. Every port is scanned and identified. If you want to beef up security use SSH keys.
