But it would still be good to see what is causing this > connection issues. Hm but why does shadowing in work? The time now is 04:50. © 2015 SUSE, All Rights Reserved. Author Posts This topic was marked as closed, you can't post. http://invictanetworks.net/error-failure/error-failure-reading-file-win32-13-the-data-is-invalid.html
Password Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context. The home directory of the nx user is in a non-standard place, so SELinux stepped in and prevented the connection having access to the directory. Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ Don't forget to check the NX Knowledge Base: What can I say about the network? More Bonuses
Info: Using cache parameters 4/4096KB/8192KB/8192KB. Especially if you did not change anything. I don't know if the latest version (3.1.0-5) has a problem with Fedora 8 or is it my machine that is screwed up.
We are running Mandriva 2006 and the clients runs under > Mac OS X > > Thanks a lot > Thomas > Let me know if you need further information, or The link to that discussion is at 'NXserver stopped working after enabling Compiz [Archive] - Ubuntu Forums' (http://ubuntuforums.org/archive/index.php/t-534850.html), and the solution is > ssh to the server machine. > create a Thomas Murray Trainer Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: NX session closes with some peer proxy error Are you using a cluster or a single NX > server? > > Regards > > Murray > > > > > ________________________________________________________________ > Were you helped on
Info: Using alpha channel in render extension. I think I actually managed to type the wrong password in the previous attempt. Info: Waiting for connection from '192.168.0.100' on port '5002'. https://mail.kde.org/pipermail/freenx-knx/2007-October/006029.html Message #15 received at [email protected] (full text, mbox): From: Mike Gabriel
I've seen it also say "...on FD#11". See http://www.nomachine.com/ for more information. I would that think given the great speed of NX Server, many people in SuSE-land should have got this working and have solved various configuration issues. I've thought that turning that off by editing the config file with a text editor and turning off the low latency option might actually help make the connection more stable.
Info: Using ZLIB stream compression 4/4. https://www.nomachine.com/forums/topic/custom-session-floating-window-doesnt-seem-to-work Session: Session terminated at 'Fri Oct 26 01:30:28 2007'. Error Failure Reading From The Peer Proxy Info: Connecting to remote host 'localhost:31001'. Remove nxcleanup. (Fixes: #302, #511). - Move session file to /tmp/.x2go-$USER. (Fixes: #523). - Fix x2gostartagent failures if kbd is not "auto".
In /var/log/messages the first error written by nxserver was > ERROR: Unexpected termination of nxagent because of signal: 11 Subsequent errors in the log cascaded from that. http://invictanetworks.net/error-failure/error-failure-in-loading-assembly.html Date: Thu, 15 May 2014 07:30:49 +0000 [Message part 1 (text/plain, inline)] Hi Robert, On Fr 09 Mai 2014 15:24:10 CEST, Robert Izzard wrote: > Steps to repeat: > 1) On Error: Failure reading from the peer proxy. Matty Gilbert PS - this is the log i get from the NX session administrator tool on my linux box Code: NXAGENT - Version 3.2.0 Copyright (C) 2001, 2007 NoMachine.
Info: Not using ZLIB stream compression. Info: Accepted connection from '127.0.0.1'. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=47b1784 The issue will most likely be fixed in src:x2goserver (220.127.116.11). http://invictanetworks.net/error-failure/error-failure.html The key fingerprint is:
Acknowledgement sent to Mike Gabriel
Info: Using ZLIB data compression 1/1/32.
BUt now the password is ok and still the custom session with floating windows fails. Error: Connection with remote peer broken. Info: Using pack method 'adaptive-9' with session 'kde'. Suppress output to stdout properly. - Use if--then--else--fi during x2goagent resuming in x2goresume-session script. - More reliably sync the NX session state with the status information in the X2Go session DB.
I can > restart a session with no problem *provided I cleanly exit > x2goclient* (e.g. CTRL-C, probably also network failure or laptop sleep/wake cycle) termination of x2goclient, I cannot reconnect to the server. The client was connected to a 10 mbit hub, which plugged into a Gigabit switch which then plugged into a 100mbit port of a switch that had a 1000 Mbit port useful reference The relevant line here is *Error: Failure reading from the peer proxy.* but it's not too informative.