[FreeNX-kNX] FreeNX 0.3.1 from Fedora rpms

[Frederik Dannemare]

On Tuesday 29 March 2005 15:26, Roderick Johnstone wrote:
> Hi
>
> I'm still seeing this problem. I'm using the most recent NoMachine
> client for linux on Fedora Core 2 and there are no colons in the
> hostname.

I'm no expert at this, but what does your port line 
in .nx/config/<session_name>.conf look like?

E.g. <option key="Server port" value="22" />

Please don't top post...

> I have another FreeNX server (but version 0.2.8) set up on an
> essentially identical system (Fedora Core 2) and connections to that
> work just fine.
>
> I'd appreciate some clue as to where to look to help diagnose the
> problem.
>
> Thanks
>
> Roderick
>
> On Wed, 23 Mar 2005, Roderick Johnstone wrote:
> > Hi
> >
> > I'm using Rick Stout's Fedora FreeNX 0.3.1 rpm on Fedora Core 2.
> >
> > I get Authentication completed. Then it waits for about 10 sec and
> > pops up a box with "Session blah failed". Clicking on detail gives:
> >
> > Loop: PANIC! Can't identify NX port in string ':'.
> > Error: Can't identify NX port in string ':'.
> > Error: NX transport initialization failed.
> >
> >
> > The end of the nxserver.log file contains:
> >
> > NX> 700 Session id: <the host I was connecting to> --
> > NX> 705 Session display:
> > NX> 703 Session type:
> > NX> 701 Proxy cookie: 06a9735e14f0d62837ecee6ce62be2e4
> > NX> 702 Proxy IP:
> > NX> 706 Agent cookie:
> > NX> 704 Session cache:
> > NX> 707 SSL tunneling: 0
> > NX> 710 Session status: running
> > NX> 105 bye
> > Bye
> > NX> 999 Bye
> > NX> 1004 Error: nxagent failed to start. Session timed out.
> >                Blocking  again ...
> > NX> 1001 Bye.
> > NX> 504 Session startup failed.
> >
> > Can anyone help me diagnose this failure please.
> >
> > Thanks
> >
> > Roderick Johnstone

-- 
Frederik Dannemare | mailto:frederik at dannemare.net
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
Key fingerprint = 30CF 7AD3 17D9 1A63 A730  ECA6 0D4C 2C97 9D9A 238E