|
|
|
|
||||||
| comp.security.ssh SSH secure remote login and tunneling tools. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I can do "ssh -X foo" where foo is a local machine on the same network and
from there forward X back to my desktop. However, I have another machine that I have to access using a proxy: ssh -X -o "ProxyCommand ./connect.exe -S socks-proxy:1080 other_machine 22" other_machine After I login this way, my DISPLAY variable is set correctly (localhost:10.0) but when I try to start an X session it says nu usable address for localhost:6010 and also Error: can't open display: localhost:10.0 I assume this has something to do with the proxy. Anyway to get X working through the proxy? thanks, Todd |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
>>>>> "TAD" == Todd A Anderson <drtodd13@comcast.N0SPAM.net> writes:
TAD> I can do "ssh -X foo" where foo is a local machine on the same TAD> network and from there forward X back to my desktop. However, I TAD> have another machine that I have to access using a proxy: TAD> ssh -X -o "ProxyCommand ./connect.exe -S socks-proxy:1080 TAD> other_machine 22" other_machine TAD> After I login this way, my DISPLAY variable is set correctly TAD> (localhost:10.0) but when I try to start an X session it says nu TAD> usable address for localhost:6010 and also Error: can't open TAD> display: localhost:10.0 TAD> I assume this has something to do with the proxy. Anyway to get TAD> X working through the proxy? TAD> thanks, TAD> Todd It shouldn't have anything to do with the proxy. Try using 127.0.0.1 instead of "localhost". -- Richard Silverman res@qoxp.net |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
> It shouldn't have anything to do with the proxy. Try using 127.0.0.1
> instead of "localhost". That did the trick. Thanks. |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
In article <466dnTMrsaWNhc_YnZ2dnUVZ_tmdnZ2d@comcast.com>,
Todd A. Anderson wrote: >> It shouldn't have anything to do with the proxy. Try using 127.0.0.1 >> instead of "localhost". > >That did the trick. Thanks. > Now check your name resolution and particularly /etc/hosts, since localhost is apparently not resolving to 127.0.0.1, which is a recipe for further trouble. -- Christopher Mattern "Which one you figure tracked us?" "The ugly one, sir." "...Could you be more specific?" |
|
![]() |
| Outils de la discussion | |
|
|