[FreeNX-kNX] Re: Fedora 14 - Windows nomachine client tmes out after "negotiating link parameters"

[Stargazer]

Stop press!
Hey now this is wierd. I've said all along Zeppelin worked - well today 
it too stopped, but heres the clue - it was right after a "yum update". 
It has definitely had nothing else done to it as its not normally 
switched on (it runs a tape backup). In fact the only reason I left it 
on was so I could use it to get into the office remotely by using it to 
get to Sabbath. Since Sabbath is the main machine it will have had the 
yum update much earlier. So, they are both Fed 14 & both were working 
fine until a recent update, and both now time out FreeNX when the final 
stage, the session negotiation, of a remote login occurs. Actually 
Motorhead hasn't been switched on since the original install and is 
still off now, I bet it if I boot it up I'll be able to connect, then if 
I do the yum update it will start to behave like the others. Or do a Fed 
14 install from the original DVD to any new machine but hold off 
updates. Surely others must be experiencing this now if I'm correct? And 
once reported, don't the package maintainers scramble to fix things so a 
later yum update makes them all work again?

-- Carl