Raphion
join:2000-10-14
Samsara
| reply to Raphion
Re: The most secure way to use Windows Remote Desk
Confusion over  I uninstalled and reinstalled COPSSH, and now I can login just fine. Must've messed something up accidentally first time. Like being too lazy to actually logout and back into an admin account, and just using "runas" for the install, and then not bothering to reboot before messing with stuff.
I see the necessity and function of port forwarding now too. Have to do that even just to access the server machine over RDP I see. I'm able to access multiple machines on my network over the tunnel now.
I'm going to try making my RSA keys next.
Can you tell me how to change the port number that COPSSH uses? |
|
Raphion
join:2000-10-14
Samsara
2 edits | [edit] It seems I actually do NOT know how to change the port. I did get my keys setup, and password authentication off.
I noticed that both ssh_config and sshd_config have the passwordauthentication line. Should it be NO in both?
I saw the line "port" in ssh_config, but changing it breaks it. How do I change the port?
[edit yet again]I did figure it out after all, change the port in sshd_config not ssh_config. |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
1 edit | reply to SoonerAl
said by Sooner :
AlWell, no I have not seen that error before...
Really?! Well, you haven't lived until you've scoured the databases looking for definitions to cryptic crap like this.
10053 or WSAECONNABORTED and other error messages extremely similar to these were all the rage in the mid 90s. ... before search engines were good.
App writers didn't want to take the time to translate the error, so they just popped it up to the user interface.
And, naturally, Joe Public was confused by this.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~
---
[Mod Note: Edited to fix broken quote. --kc] |
|
SoonerAl
Old Enough To Know Better
Premium,MVM
join:2002-07-23
Norman, OK
1 edit |  reply to Raphion
An alternative to changing the port in the /etc/sshd_config file on the server, and one that I use, is to keep the server listening on TCP Port 22 but redirect a high number port through your firewall/NAT/router to TCP Port 22 on your server. When calling from a remote location use the new high number port. See the attached image for an example of that...
Glad its working for you...
--
"When all else fails, read the instructions..." |
|
