RE: [Xen-users] Re: VNC not on Localhost

["Dirk Pol" <dirkpol@xxxxxxxxxxxx>]

Hello,

I worked it out! I am using a Windows machine to manage the farm. I found
out that PuTTy on windows can also do the tunnel trick.

Following this document:
http://www.cs.uu.nl/technical/services/ssh/putty/puttyfw.html

Makes the DomU vncserver port available on my management machine.
Where I can connect to localhost:590x for my domU "out-of-band" management.

Thanks Jan for Hinting me in the right direction...The framebuffer solution
was too complex for me.

Regards,


Dirk Pol




Dirk Pol wrote:
> What I mean is:
> 
>  
> 
> [root@localhost auto]# netstat -na
> 
> Active Internet connections (servers and established)
> 
> Proto Recv-Q Send-Q Local Address               Foreign
> Address             State
> 
> tcp        0      0 127.0.0.1:5900             
> 0.0.0.0:*                   LISTEN
> 
>  
> 
> it is bound to 127.0.0.1:5900 and I want to bind it to 0.0.0.0 so that i
> can reach it from my management LAN
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Dirk Pol:
> 
>  
> 
>> I am looking for a way to bind the vncserver of xen machine not to
> 
>> localhost but to my management LAN.
> 
>  
> 
> Just start the vncserver on a host of your management LAN.
> 
>  
> 
> Greetings, Mark Weinem  
> 
>  
> 
> 
> 
> Met vriendelijke groet,
> 
> Dirk Pol
> 
Hi Dirk,

        you definitely do not want to do that: it's as insecure
as you can make it.

        As a solution do from your local client :

        user@client$ ssh -f -N -L localhost:5900:localhost:5900
username@userdomain

        user@client$ xvnc4viewer localhost:0

Sincerely,

Jan.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users