en't already, I suggest you try the trunk
version. Maybe you already have.
Thank you.
Regards,
Rich
> -Original Message-
> From: Martin [mailto:mpr...@gzunder.homeip.net]
> Sent: Tuesday, October 19, 2010 9:02 AM
> To: xrdp-devel@lists.sourceforge.net
> Subject: Re:
Duzenbury, Rich writes:
> I've attached a horrible, hacky patch that seems to barely get the job done.
Hi Rich, et al...
Although a lot of this thread is common with my symptoms, it differs in that I
get a "Connection failed" every time. But willing to to try anything, I had a go
at adding your
2010/8/17 Duzenbury, Rich :
>
> I've attached a horrible, hacky patch that seems to barely get the job done.
> I am just falling back on trying the connect routine multiple times, which
> seems to work.
>
Don't worry, I have also done, let's say, not elegant hacks :)
Moreover because I am a C n
> Mmhmm seems to be performance issues...
> try to run sesman -nodaemon. It will tell you some more informations.
> Maybe you catch some timeouts waiting for Xvnc or something else...
>
> --
> Nicola
Hi,
I've attached a horrible, hacky patch that seems to barely get the job done. I
am just fal
Hello,
The previous log for the broken session startup was incomplete, I'm very sorry.
I've included it at the end of this message.
Is this the relevant bit? "client ... gone"
16/08/2010 14:05:19 Listening for VNC connections on TCP port 5913
Could not init font path element /usr/X11R6/lib/X1
> Mmhmm seems to be performance issues...
> try to run sesman -nodaemon. It will tell you some more informations.
> Maybe you catch some timeouts waiting for Xvnc or something else...
>
> --
> Nicola
Hi Nicola,
Per your suggestion, I attempted to connect to the VNC backend the first time
and c
>
> Now, in the case of the Xvnc backend, it now throws an error when I connect
> by either rdesktop or mstsc:
>
> connecting to sesman ip 127.0.0.1 port 3350
> sesman connect ok
> sending login info to sesman
> xrdp_mm_process_login_response: login successful for displa
> started connecting
> con
> Ok, at this point it seems to be a xrdp problem (not sesman problem).
> I suggest you (as you compiled all with --enable-xrdpdebug) to run
> xrdp in foreground (./xrdp -nodaemon >> logfile) to see what's
> happening.
>
> Note1: xrdp-sesman.log is actually only written by sesman, so is
> sesman l
Hi Nicola,
> No, better to know how many bytes.
>
> Use this:
>
> xrdp_tcp_send(struct xrdp_tcp* self, struct stream* s)
> {
> int len;
> len = s->end - s->data;
> DEBUG("in xrdp_tcp_send, gota send %d bytes", len);
> if (trans_force_write_s(self->trans, s) != 0)
> {
> DEBUG("
2010/8/12 Duzenbury, Rich :
> Ok, I have a bit more information. I reinstalled the latest CVS version once
> again and enabled --enable-xrdpdebug I think I had mistyped it as
> --enable-debug before.
yes, the correct option is --enable-xrdpdebug
>
> Well, first I had to hack over a compile er
2010/8/13 Duzenbury, Rich :
> Ok, this is of course better. I have no understanding of the xrdp codebase,
> and I just wanted to get it to compile, so I hacked over this particular
> problem. Any idea why the debug version shouldn't already compile out of the
> box? Just a small oversight, pe
>
> How can I troubleshoot this, please?
>
Ok, I have a bit more information. I reinstalled the latest CVS version once
again and enabled --enable-xrdpdebug I think I had mistyped it as
--enable-debug before.
Well, first I had to hack over a compile error in libxrdp/xrdp_tcp.c, since the
2010/8/11 Duzenbury, Rich :
>
> Is http://server1.xrdp.org/xrdp/ the correct location for project files?
>
> I see xrdp-sp3-fix.tar.gz at http://server1.xrdp.org/temp/ but no mention
> anywhere I can find. Does this solve the issue? What version is this?
>
> Anything I can do to get this going?
> > Anything I can do to get this going?
>
> Hi, try to compile lastes cvs sources. See:
> http://sourceforge.net/projects/xrdp/develop
>
> bye
> Nicola
This had no effect. I checked out the sources, compiled them, installed them,
then restarted the machine. I receive the same error message
Hi,
I've installed xrdp on Suse Linux Enterprise Server 10.3. Up until recently,
mstsc could connect and work. Apparently, there was some sort of update to the
windows version of mstsc, and now, after the password is entered, it throws
this message:
Because of a protocol error, the session w
15 matches
Mail list logo
