SSH port fowarding
location: linuxquestions.com - date: April 29, 2002
Hi, I downloaded "plink" , a win32 ssh client, and I am trying to setup a port fowarding session to a remote Samba server. But everytime I try, I get a "connection refused" errror. I've tried various port numbers, but I get the same error. Here is an example of the error:
C:\>plink -L 139:remote-samba.server.com:139 localhost
FATAL ERROR: Network error: Connection refused
My machine is behind a firewall, so can't just map it normally. I've tried port 139, 80, 5000, 6000, etc...
Ubuntu 9.10 SSH (port 22 vs port xxxx problem)
location: ubuntuforums.com - date: November 11, 2009
After upgrading to Ubuntu 9.10, besides wireless problem, now I have found a problem with SSH.
The Ubuntu 9.10 box can not make a connection if the server,in my case the box is running Ubuntu 9.04, is using a different port address (not the default 22). Change back to port 22, anything is working as expected!
Any idea out there?
[SOLVED] How to solve scp ssh port 22 error ?
- date: March 27, 2015
Im trying to use scp to copy changed httpd.conf files to 2 remote machines (the script is executed in one machine from remote and the result is copied to the both).
scp -vvv [email protected]
_address:filename \[email protected]
Using RHEL 5.7 with mremote in windows 7 im getting this error:
ssh: connect to host <ip address> port 22: Connection refused
How can I solve it ? Thanks.
I am having problem creating ssh port forwarding
- date: June 4, 2015
I am using Cygwin on Windows 7 and i am trying to create port forwarding to remote Ubuntu server. I am using this command:
ssh -v -i ubuntu2.pem [email protected]
This is the output on logon concerning the port forwarding:
debug1: Local connections to LOCALHOST:9999 forwarded to remote address localhost:9999
debug1: Local forwarding listening on ::1 port 9999.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 127.0.0.1 port 9999.
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-48-generic x86_64)
But i don't think it is working because if i try to make Firefox trafic goes through port 9999 i get error message: "The connection was reset" when i try to load a page in Firefox. The manual proxy configuration in Firefox are: Socks5, host= localhost
[SOLVED] SSH port forwarding: connection closed by remote host
location: linuxquestions.com - date: May 7, 2014
I have a vpn server set up as a relay to allow me to access my home computer (that is behind an ISP firewall that I can't do anything about). It was working great until recently. I am hoping someone here can help me troubleshoot.
On my home computer, I issue the following command:
closing ssh port
location: linuxquestions.com - date: June 20, 2005
i just scanned my self and found out this:
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcind
631/tcp open ipp
i want to close the ssh service
how do i do that?...
are the other 3 ports that are open dangerus for me?
and i have another question
i have fc3 where are the firewall setting located?
the last time i sow them was a long time ago and now i dont remember where they are
SSH port forwarding ...
- date: May 8, 2014
I hope this falls under this catagory.
I have three machines - laptop (software license server), PC (openssh server & VM host), VM (running on the PC).
I want to run some software on the VM which will need to get a license from the laptop. The VM is using a NAT network configuration, and I'd like to try and keep it that way. The PC is in my home network at address 192.168.1.2 and the VMs NAT address is 192.168.122.10. The license server is mobile and can ssh to the PC from anywhere. The VM needs to request a license using port 1515 and the license server replies using port 1516. I'm pretty sure I've opened all necessary ports on all the machines firewalls. So I would like to use ssh port forwarding, initiated from the laptop (lic server), to open the lines of comms for the license request to work. This is what I've tried already with no success ...
On the laptop (using putty)...
equivalent command line would be ssh -p 1234 [email protected]
-R 151501:laptop:1515 -L 1516:
CUPS to CUPS through SSH port forwarding
- date: August 3, 2011
I have a remote machine running CUPS and managing a locally (USB) connected printer. Everything works fine as expected.
I have another machine also running CUPS for a number of printers that are either local or on the same LAN of the server. Also this works fine.
I need to be able to print from this server on the first remote machine's printer.
I managed to have a remote forwarding like this on the remote machine:
machine# ssh -C -N -T -R 192.168.0.2:631:127.0.0.1:631 [email protected]
(192.168.0.2 is a dummy interface on the server)
This means that any connection on TCP port 192.168.0.2:631 in the server will be forwarded straight to TCP port 127.0.0.1:631 on the remote machine with the printer.
On server's CUPS web UI I've tried to add a printer (with the proper driver) like this:
[SOLVED] Help with ssh port 22 connection refused
location: ubuntuforums.com - date: September 2, 2008
I am new to using ssh and wanted to try it out. I have been trying to connect to my ubuntu machine from my mac using ssh. I keep getting this error message:
$ ssh 127.0.0.1
ssh: connect to host 127.0.0.1 port 22: Connection refused
Any ideas or suggestions are much appreciated!
HOWTO: set up secure (encrypted) Remote Desktop access (using ssh port forwarding)
location: ubuntuforums.com - date: July 22, 2006
Method 1: manual ssh port forwarding
Remote box (VNC client: receives UI events):
1) Block port 5900 (vnc)
2) System->Preferences->Remote Desktop:
2.1) Check Allow other users to view your desktop
2.2) Check Allow other users to control your desktop (optional)
2.3) Check Require the user to enter this password: (preferred)
3) Open port 22 (ssh)
4) Ensure sshd is running on port 22
Local box (VNC server: sends UI events; note in remote desktop client and server are vice-versa in comparison to usual terminology):
1) ssh -L <some port/>:localhost:5900 <remote box IP/>
2) vncviewer -FullScreen localhost:<some port/>
ssh -L 5901:localhost:5900 <remote box IP/>
vncviewer -FullScreen localhost:5901
I'll let other users add other methods (such as freeNX), if they please.
Good luck to humane computing, and everything.
Page: 1 2 3 4 5 6 7 8 9 10