hello,
we had problems to install x2go:
we made a big mistake
* we comment the lo interface, it was so silly that we don't see
this mistake long time: the result was that the machine work, but
the next boot, it was no nfs ...
now it is going well. as i told you before i think, it will be better to make a install script, because you can control if it's really work. the documentation has mistakes and for the installer they can be sure, they don't make a tipping / copy mistake. we have done such a script and we can give to the community, if desired.
now we have tried to make x2go as a xen virtual machine. it is at the moment not working, we get following mistake
something like: in login (without ldap): cannot connecting to host "localhost:30001" proxy
with nmap 192.168.0.250 we dont have port 30001 open tcpdump on eth1 where is the dhcpserver try from the client to reach the x2go server / 13:27:03.666347 IP 192.168.0.106.3088888606 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.679034 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3088888606: reply ok 116 getattr [|nfs] 13:27:03.666594 IP 192.168.0.106.930 > x2goserver.planetexpress.de.nfs: . ack 1669475119 win 41915 <nop,nop,timestamp 274543 293666> 13:27:03.668053 IP 192.168.0.106.3105665822 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668130 IP 192.168.0.106.3122443038 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668161 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3105665822: reply ok 116 getattr [|nfs] 13:27:03.668218 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3122443038: reply ok 116 getattr [|nfs] 13:27:03.668424 IP 192.168.0.106.3139220254 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668471 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3139220254: reply ok 116 getattr [|nfs]/
some idea, where is the mistake?
michel
kamerun@immerda.ch schreef:
hello,
we had problems to install x2go:
we made a big mistake
- we comment the lo interface, it was so silly that we don't see this mistake long time: the result was that the machine work, but the next boot, it was no nfs ...
Nice to hear!
now it is going well. as i told you before i think, it will be better to make a install script, because you can control if it's really work. the documentation has mistakes and for the installer they can be sure, they don't make a tipping / copy mistake. we have done such a script and we can give to the community, if desired.
Making an install script would be nice, I think.
But realize that people have different environments, so I would look at it like at a manual. Copy some lines, do other lines my way...
now we have tried to make x2go as a xen virtual machine. it is at the moment not working, we get following mistake
something like: in login (without ldap): cannot connecting to host "localhost:30001" proxy
with nmap 192.168.0.250 we dont have port 30001 open
Normally x2goclient connects to the server on port 22 (ssh).
But x2go also makes some tunnels for sound, filesharing, printers. Not shure about them.
Maybe you can try to copy the error?
Or try the same without sound, filesharing, printers?
Paul.