I think I follow you for the most part... You're saying to enter that code with my username on the htpc, into the terminal on my Linux-Rig (office computer). Correct?

Only thing is, I thought that the username was simply "htpc". I don't remember being asked to create any real username except for that. I guess I'm too big of a linux newbie here, but it must have asked me at some point. However, it says that the user name is "HTPC" in all caps. You can see it just by clicking the "start menu" or launch menu in the bottom left hand of the taskbar. Just like when I click it here on my Linux-Rig, it shows the username to be "Justin".

All that said, when I enter your code into the terminal on my office computer, it returns:

"bash: sftp://HTPC@192.168.104: No such file or directory"

It's the same if I get rid of the caps, and just use "htpc" instead of "HTPC"

If 192.168.1.104 is the IPv4 address of your remote HTPC system and htpc is the username there, then open the file manager on your desktop system (probably Dolphin if I am following along correctly), press ctrl-L, and then enter the following into file manager's (Dolphin's) location bar:

Otherwise substitute in the correct host name or IP address for the other computer. That would be the one you connect to, not the one you connect from.

The references there must be for the remote system not the local system. So the first part is the protocol (sftp) to connect to the remote system. The second part (htpc@) will be the user name on the remote system. The third part (192.168.1.104) must be the network address of the remote system. The fourth and final part is the path to the directory you wish to start in on the remote system if it connects.

1 members found this post helpful.

When I enter that address, I get the red bar below the address bar in dolphin, and it says "Connection refused".

I've been at this for more than 8 hours now lol, I think I may need to hire a linux guy from craigslist to come to my house. At least I'll learn exactly what the issue was and how to fix it. Nothing like having an in-person teacher.

I had a problem once with SFTP. Then, after a change of the distro, the certificates of the machines didn't fit anymore and I had to delete them. Now, I'm absolutely no expert here. Perhaps one of the gurus here could consider whether this might be a cause here and perhaps offer a solution to the OP.

Certificates or keys? Either way, if the host keys or host certificates were not valid any more then there would be a pronounced error message to that effect. So it is most unlikely the problem here. If it is, it would be encountered after establishing connction first but that has not happened yet.

It might be that OpenSSH-server has not been turned on at the remote host yet.

Let's back up a bit: can you ping the HTPC at the address we're thinking it's at from whatever machine you're trying to connect with? Are you running a firewall on one/both of the machines involved here?