ecerulm

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Custom session + floating window doesn't seem to work #825
    ecerulm
    Participant

    Nevermind by last comment

    the actual log is

    
    Session: Starting session at Wed Nov 20 08:10:11 2013.
    Info: Listening to slave connections on port 13953.
    34076 8012 08:10:11 038.810 ProxyParser/ProxyParser: WARNING! Connected to remote version 3.5.0.
    Warning: Connected to remote version 3.5.0.
    34076 8012 08:10:11 038.810 ProxyParser/ProxyParser: WARNING! Shared memory unsupported on Windows.
    Session: Session started at Wed Nov 20 08:10:11 2013.
    Info: Connection with remote peer completed.
    Info: Using link parameters 9/0/16000/25/200.
    Info: Not using stream compression.
    Info: Not using a persistent cache.
    Info: Using pack method adaptive-9 with session rootless.
    Info: Using product LASPS/LI10K00117/LASNPS/LI10K00120.
    Info: Not using delta compression.
    Info: Forwarding display connections to localhost:0.
    Info: Forwarding auxiliary display connections to localhost:0.
    Info: Listening to font server connections on port 11953.
    34076 15640 08:10:11 019.808 Connection: Stop reading after switching the connection.
    34076 8012 08:10:11 044.810 Process: ERROR! Can't set priority to 0.
    Info: Transport running with pid 8012.
    34076 8012 08:10:11 397.846 ProxySession/ProxySession: WARNING! No connect callback set by the application.
    34076 8012 08:10:22 434.949 ProxyChannel/ProxyChannel: ERROR! Failure reading from IN#928 OUT#1264.
    34076 8012 08:10:22 434.949 ProxySession/ProxySession: ERROR! Connection with the remote peer broken.
    Error: Connection with the remote peer broken.
    Error: Error is 108, 'Connection reset by peer'.
    Session: Session terminated at Wed Nov 20 08:10:22 2013.
    34076 8012 08:10:11 044.810 Process: ERROR! Error is 22 'Invalid argument'.
    34076 8012 08:10:22 473.953 ClientTransResetCallback: WARNING! The NX transport terminated with error '108' 'Connection reset by peer'.
    34076 15640 08:10:22 473.953 ClientSession: WARNING! Transport not running with reset '1' and error '108'.
    34076 15640 08:10:22 473.953 ClientSession: WARNING! Forcing transport reset.
    34076 15640 08:10:22 473.953 ClientSession: Exiting from the client transport loop.
    34076 15640 08:10:22 473.953 ClientSession: The transport closed with reset '1' error '108'.
    34076 15640 08:10:22 473.953 ClientSession: Session at 0x31d17b8 failed.
    34076 15640 08:10:22 473.953 ClientSession: Failing reason is 'The connection with the server was lost.
    
    Error is 108: Connection reset by peer.'.
    

    I think I actually managed to type the wrong password in the previous attempt. BUt now the password is ok and still the custom session with floating windows fails. The log mentions <reset “1” error “108”>. Anybody knows what it means?

    in reply to: Custom session + floating window doesn't seem to work #824
    ecerulm
    Participant

    I’m having the same problem

    
    7812 33572 07:13:15 486.289 ClientProcess: Starting command 'nxssh.exe "-T" "-2" "-4" "-p" "22" "-o" "ForwardX11 yes" "-o" "XAuthLocation \"C:\Program Files (x86)\NoMachine\bin\nxauth.exe\"" "-o" "Compression no" "-o" "EscapeChar none" "-o" "RhostsAuthentication no" "-o" "PasswordAuthentication no" "-o" "RSAAuthentication no" "-o" "RhostsRSAAuthentication no" "-o" "PubkeyAuthentication yes" "-o" "PreferredAuthentications publickey" "-i" "C:\Users\ecerulm\NXC495~1\R-E7D8D385998E8A-7812-F19C7910854B539E1886E2ECFCB8B615\keylog" "nx@esekilxxen6200.rnd.ericsson.se"'
    7812 33572 07:13:15 487.289 Process: ERROR! Can't set priority to 0.
    7812 33572 07:13:15 487.289 Process: ERROR! Error is 22 'Invalid argument'.
    7812 33572 07:13:15 618.302 ClientSession: Going to handle running children.
    7812 33572 07:13:15 618.302 ClientSession: Going to add child with pid '1276' and process at 0.
    7812 33572 07:13:15 618.302 ClientSession: Now there are 1 running children.
    7812 33572 07:13:15 629.303 Connection: Started connection at 0x57ab438.
    7812 33572 07:13:15 650.305 ClientSession: Change state to 'Started'.
    7812 33572 07:13:15 650.305 ClientSession: Started session at 0x7cc738.
    7812 33572 07:13:15 650.305 ClientSession: Created new view at 0x61b9ed0 with label 'ProgressView' and value '0x650dfe'.
    7812 33572 07:13:17 298.470 Connection: Starting the session in compatibility mode.
    7812 33572 07:13:17 298.470 ClientSession: Going to initialize connection policies list.
    7812 9048 07:13:17 299.470 SlaveServerApplication/Application: WARNING! Not waiting with FD#948 ready.
    7812 33572 07:13:17 308.471 ClientSession: Created new view at 0x62bbbf0 with label 'AuthenticationView' and value '0x650dfe'.
    7812 33572 07:13:28 233.563 ClientSession: Destroying view at 0x62bbbf0.
    7812 33572 07:13:28 948.635 Connection: Connection at 0x57ab438 failed.
    7812 33572 07:13:28 948.635 ClientSession: Runnable at 0x57ab438 caused the session at 0x7cc738 to fail.
    7812 33572 07:13:28 948.635 ClientSession: Failing reason is 'Authentication failed for user ecerulm'.
    

    at the end it says that the “authentication failed for user ecerulm” but I’m assuming is really due to the “Process: ERROR! Error is 22 ‘Invalid argument’.”

    So how do I find out what is the version installed in the server side?

    When I connect with the 3.5.0-9 with the same session it works.

Viewing 2 posts - 1 through 2 (of 2 total)