Re: How do I port forward through 2 remote hosts?
From: james@his.placeDate: 02/28/02
- Next message: Jason Sigurdur: "sshd "DId not receive identification string from""
- Previous message: Nico Kadel-Garcia: "Re: sFTP accounts, but not shell."
- In reply to: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Next in thread: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Reply: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: james@his.place Date: Thu, 28 Feb 2002 00:29:00 +0000
On 26 Feb 2002 22:41:36 -0500, slade@shore.net (Richard E. Silverman)
wrote:
>:
>:James, I am going to spell this out in excruciating detail. I feel
>:compelled to comment, though...
>:
>: james> I have read through the manual after typing ssh man at the
>: james> prompt. I tried to save it, no good.
>:
>:This has nothing to do with SSH; it means you are not familiar enough with
>:Unix to do this. If you're going to use a thing, you have to learn about
>:it.
>: james> I did manage to print a few pages, but it was just as techie as
>: james> the answers I have been receiving.
>:
>:The answers are "techie" because you're asking technical questions about a
>:technical topic, in a technical forum. This is comp.security.ssh, not
>:your local helpdesk or an introductory class on how to use computers
>:without electrocuting yourself. This really should not be terribly
>:surprising.
I accept the admonishment. I am no techie, never will be. Anything
above winding my watch and I'm in trouble ;)
>: james> If this is SSH, I give it up.
>:
>:This is, of course, your call. If you don't feel like putting in the
>:effort to understand the tool and concepts at hand, you will not receive
>:their benefits.
Well that was written in a moment of despair. I have been struggling
and struggling.
>:Now...
>:
>:1) Start SecureCRT on box W.
>:
>:2) File->Connect
>:
>:3) Right-click the Sesssions folder, and choose "New Session". Give it a
>: name, select appropriate SSH protocol version you want to use, fill in
>: the remote hostname for host A and your username there, and select the
>: authentication method you want to use.
I have not used SecureCRT for some time. Nevertheless, I fired it up
just to ensure I was looking at the same screens, etc.
Right clicking does not show the option "new Session". However, I
clicked on top left menu item titled "New Window" Now the third icon
from left on the Menu in the "New Window" showed up as "New Session".
Surely the same thing - I assume.
>:4) Choose random port numbers p and q both between 1024 and 65535. It is
>: possible that you will happen to choose one already in use, in which
>: case there will be an error in step 8 and you will have to choose
>: another one and try again.
I assume these should be different? I chose randomnly port 1299 and
then 1399.
>:5) In the left-hand panel, select "Port Forwarding." Give the forwarding
>: a name, fill in local port p and remote port q. Do not check
>: "destination host is different from the SSH server."
"Give the forwarding a name.." Mmm. I put in "Benelux" When that
didn't work, I tried inputting the name of the second remote host. Is
this important?
No check box for "destination host is different from the SSH server"
on my version of SecureCRT (3.1.1)
>:6) Click OK, bringing you back to the "Connect" dialog. Select your new
>: session, and click "Connect". You should then log into host A.
Yes, so far so good.
>:7) Once on host A, type "ssh -L q:C:119 B", where:
>: - C is the name of the news server host
>: - q is the port number chosen above
>: - B is the name of the second intermediate host
I did this precisely as above, carefully observing case and spaces.
It connected, asking me for my remote host B password, which it then
accepted. Ah, I thought, success at last. Unfortunately, no.
When I attempted your little test below....
>:8) To test, on W do "telnet localhost 2001". You should see a welcoming
>: banner from the news server, something like:
I received,
Trying to connect to 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Oh dear, :((
>: 200 news.shore.net -- http://www.shore.net/ -- support@shore.net (Typhoon v1.2.2)
>:
>: That's all; type "quit" <return> to disconnect.
"quit" returned the error:
bash: quit: command not found
>:9) Set your newsreader on W to access an NNTP server at host localhost,
>: port p (again, this is a variable defined above).
I do not have any options with my newsreader (Agent 1.9) to assign any
port numbers, only "localhost" for the name of the server.
When I try to connect with my News reader I get:
Error reported by winsock driver: Connection refused by server (Error
10061): Connecting to 127.0.0.1
????
Despite my inability to again manage to do this supposedly simple
thing, I still wish to thank you for your help.
If, however, there is a glaring error in something I have done, please
tell me. I will still go on experimenting, but despite several dozen
attempts (using different smallchanges) my news reader is still
refused a connection.
James
- Next message: Jason Sigurdur: "sshd "DId not receive identification string from""
- Previous message: Nico Kadel-Garcia: "Re: sFTP accounts, but not shell."
- In reply to: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Next in thread: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Reply: Richard E. Silverman: "Re: How do I port forward through 2 remote hosts?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
