Ok, i generated some ecdsa keys from the ubuntu client. I have imported the key to my windows ssh server and file zilla connects from ubuntu so i know i have connectivity.

Now, when i use the command line

ssh user@x.x.x.x:xxxx

Could not resolve hostname x.x.x.x:xxxx Name or service not known

i have no idea what to do next

thanks

That's because you are specifying the port along with the IP address together (x.x.x.x:xxxx). You need to specify the port using the -p port when using the command line. From the man page:

So if I wanted to connect to 12.12.123.12 at port 56 the command would look like:

ohhhhhhhhh. ok, let me try again in the morning. im super tired right now haha

When using that format, you need to also include the protocol:

That possibility has been around since OpenSSH 7.7

ok, i knew i was close to the correct syntax. I forgot about the -P option and the sftp://x.x.x.x:xx

ill give it a try and see what happens

Ok, i FINALLY got it to work. I can now ssh into my windows server via CLI from my ubuntu client. FINAL issue i need to resolve. When i click on the home folder of my ubuntu client, and i click "other locations" on the left hand side, i then type sftp://x.x.x.x:xxxx and i get a permission denied. How do i use this other connections box to conect via sftp using the username for the account?

thanks

You can use a ssh config file (~/.ssh/config)
Host myhost
HostName x.x.x.x
User name
Port xxxx
IdentityFile ~/.ssh/your_ecdsa.key


https://linuxize.com/post/using-the-ssh-config-file/

In your file browser use sftp://myhost
From the cli use ssh myhost

ok, thanks guys. I got the file manager to connect. I had wrong syntax again hahaha. sftp://user@IPort is what i needed. Once i did this, it all connected just fine.

now onto the next project, syncthing, duplicacy, and rclone

rsh $RHOST -l $XUSER "$*"

if you don't have rsh ask yourself why it's been removed and replaced with BLOAT. it's built for raw speed, nearly an RPC (network mainframing) speed. it can be secured using vpn if outside-of-lan shell is needed.

Sorry, no...it's been replaced because it is incredibly insecure, and if you can tell from a terminal which commands are a millisecond faster, good luck. It's plain bad, needs ports opened that otherwise do NOT need to be opened, and can be brute-forced easily.
https://en.wikipedia.org/wiki/Remote_Shell

car020 your spam post/link has been reported.

rsh is one of the most insecure means to connect to a remote system. Every byte that travels between the two systems (including the username & password) is sent in cleartext and is vulnerable to MITM (Man in the middle) and sniffing attacks. Suggesting that you can secure it by putting a VPN for out of lan connections ignores the possibility of insider threat or even the fact that an attacker could have breached the network firewall and is listening to the network traffic to steal your secrets & data. Running RSH is like leaving your house keys under the welcome mat.

You are assuming that your attacker will be stopped at the shell (or outskirts) of your network and that is all you need to secure your systems, this is the coconut way of securing (hard shell on the outside, with open access once you are in) but is not a secure setup at all.