error making an ssh tunnel

Question

Level 9

56,174 points

error making an ssh tunnel

I'm getting an error trying to create an ssh tunnel.

*ssh –L 10548:localhost:548 username@my.computer.at.work*

returns

*ssh: Error resolving hostname \342\200\223L: nodename nor servname provided, or not known*

normal ssh works ok so the problem is with localhost. This only happens on one of my computers. the other one connects fine using the same internet connection.

P.S. I just checked and this only happens on one user account. the rest are fine.

Message was edited by: V.K.

this thread is the continuation of [this one|http://discussions.apple.com/thread.jspa?messageID=7218912#7218912].

Message was edited by: V.K.

Mac Pro 3.2 GHz, Mac OS X (10.5.2), Mac Pro 2.66GHz, powerbook G4 1.5GHz

Posted on May 17, 2008 12:49 PM

Reply

Answer 1

Tim Haigh

Level 7

24,198 points

May 17, 2008 1:19 PM in response to V.K.

try deleting your ~/.ssh/known_hosts file.

then try the command again the very verbose flags

ssh -vvv –L 10548:localhost:548 username@my.computer.at.work

see if any errors come up.

Reply

Answer 2

V.K. Author

Level 9

56,174 points

May 17, 2008 1:24 PM in response to Tim Haigh

tried that. same result. here is the error output:

OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
ssh: Error resolving hostname \342\200\223L: nodename nor servname provided, or not known

Reply

Answer 3

deh2k

Level 4

1,871 points

May 17, 2008 1:30 PM in response to V.K.

You have the problem with just one account on one Mac? And "ssh username@my.computer.at.work" works from that account?

Reply

Answer 4

V.K. Author

Level 9

56,174 points

May 17, 2008 1:34 PM in response to deh2k

yes to both.

Reply

Answer 5

deh2k

Level 4

1,871 points

May 17, 2008 2:18 PM in response to V.K.

Very strange. I wonder what \342\200\223L means. You can create a tunnel to the same username@my.computer.at.work from another account on the same client Mac?

The localhost parameter is actually sent to the server, i.e. it means that sshd should connect port 548 on localhost. What if you put "10548:localhost:548" in quotes? Or try "*ssh –L 10548:my.computer.at.work:548 username@my.computer.at.work*". You could also try moving or renaming your local ~/.ssh folder to make sure there are no local user settings that are confusing things.

Reply

Answer 6

V.K. Author

Level 9

56,174 points

May 17, 2008 2:24 PM in response to deh2k

ok, I'll try your suggestions. Thanks. yes, it's quite puzzling why it works on one account and not on the other. Unfortunately, the account it doesn't work on is my primary account and i sure would hate to change it just because of this.

Reply

Answer 7

V.K. Author

Level 9

56,174 points

May 17, 2008 2:44 PM in response to deh2k

tried all of these and nothing worked. i also tried ssh -L to a different computer at work and that produced the same error. as before it works fine when i do it from another account.

Reply

Answer 8

BobHarris

Level 9

55,109 points

May 17, 2008 4:54 PM in response to V.K.

Just for fun, try replacing 'localhost' with 127.0.0.1

A few years ago I ran into a problem with 'localhost' being associated with IPv6 which, at that time, gave the version of ssh I was using some problems, and 127.0.0.1 is IPv4. This has most likely be resolved, but as an experiment making this substituion can't hurt.

Reply

Answer 9

V.K. Author

Level 9

56,174 points

May 17, 2008 5:03 PM in response to BobHarris

just tried it and it gives the same exact error.

Someone on another board suggested that I could be using different versions of ssh on different accounts. Don't know how that can be or how to check it...

Message was edited by: V.K.

Reply

Answer 10

deh2k

Level 4

1,871 points

May 17, 2008 5:08 PM in response to V.K.

V.K. wrote:
Someone on another board suggested that I could be using different versions of ssh on different accounts. Don't know how that can be or how to check it...

It could be. *ssh -V* will print the version number. You can also type *which ssh* to get the patch of the ssh that the account is using.

Reply

Answer 11

V.K. Author

Level 9

56,174 points

May 17, 2008 5:12 PM in response to deh2k

tried that. no dice. both are exactly the same. the shells are the same too so it's something else.

Reply

Answer 12

deh2k

Level 4

1,871 points

May 17, 2008 5:48 PM in response to V.K.

I wonder if it could be a permission problem. What does the command *nc -l 10548* do? That will just listen on the 10548 port. If it just sits there, it's working as it should and you can press ctrl-C to exit.

Reply

Answer 13

V.K. Author

Level 9

56,174 points

May 17, 2008 5:57 PM in response to deh2k

it just sits there.

Reply

Answer 14

deh2k

Level 4

1,871 points

May 17, 2008 6:21 PM in response to V.K.

I did a little surfing and I think that \342\200\223 represents some Unicode character. Not sure which. Do you use any non-ASCII characters to describe your account?

Reply

Answer 15

V.K. Author

Level 9

56,174 points

May 17, 2008 6:30 PM in response to deh2k

not that I'm aware of. Just my first and last names.

Reply