Re: Connection Error

2020-06-25 Thread Tim Worcester
Since that is working for you, be aware that they are trying to push out
the official release of 1.2.0 soon.  So keep your eyes peeled for that! :)

On Wed, Jun 24, 2020 at 11:09 PM Prince V S  wrote:

> I tried staging branch 1.2.0 and it is working fine. Thanks for help.
>
> Regards,
>
> Prince V S
> On 24/06/20 10:37 pm, Nick Couchman wrote:
>
> On Wed, Jun 24, 2020 at 7:17 AM Prince V S  wrote:
>
>> Hi,
>>
>> FreeRDP version is 2.1.1.
>>
>> We are seeing same behavior for both VNC and RDP.
>>
>> Is the issue GUACAMOLE-414
>>  fixed in staging
>> branch 1.2.0?
>>
>
> Yes, GUACAMOLE-413 is fixed in the staging/1.2.0 branch.
>
> Any log output from guacd in your syslog facility?
>
> -NIck
>
>


Re: Connection Error

2020-06-24 Thread Prince V S

I tried staging branch 1.2.0 and it is working fine. Thanks for help.

Regards,

Prince V S

On 24/06/20 10:37 pm, Nick Couchman wrote:
On Wed, Jun 24, 2020 at 7:17 AM Prince V S > wrote:


Hi,

FreeRDP version is 2.1.1.

We are seeing same behavior for both VNC and RDP.

Is the issue GUACAMOLE-414
 fixed in
staging branch 1.2.0?


Yes, GUACAMOLE-413 is fixed in the staging/1.2.0 branch.

Any log output from guacd in your syslog facility?

-NIck


Re: Connection Error

2020-06-24 Thread Nick Couchman
On Wed, Jun 24, 2020 at 7:17 AM Prince V S  wrote:

> Hi,
>
> FreeRDP version is 2.1.1.
>
> We are seeing same behavior for both VNC and RDP.
>
> Is the issue GUACAMOLE-414
>  fixed in staging
> branch 1.2.0?
>

Yes, GUACAMOLE-413 is fixed in the staging/1.2.0 branch.

Any log output from guacd in your syslog facility?

-NIck


Re: Connection Error

2020-06-24 Thread Prince V S

Hi,

FreeRDP version is 2.1.1.

We are seeing same behavior for both VNC and RDP.

Is the issue GUACAMOLE-414 
 fixed in staging 
branch 1.2.0?


Regards,

Prince V S

On 24/06/20 3:44 pm, Mike Jumper wrote:
On Wed, Jun 24, 2020 at 12:43 AM Prince V S > wrote:


Hi Ivanmarcus,

Please find the system details below. I checked the logs and found
VNC
connection error (Error writing to TLS: Error in the push
function). Is
it a configuration issue?


This sounds possibly like: 
https://issues.apache.org/jira/browse/GUACAMOLE-414


...
Freerdp version                      : freerdp2


Beware that "freerdp2" (and even something like "2.0.0") is 
unfortunately vague. There are quite a few versions of this library 
around, many actually being git snapshots. Even two packages that 
appear to have the same version number may be significantly different:


http://guacamole.apache.org/releases/1.1.0/#freerdp-200-or-later-is-now-required-for-rdp-support

Do you know what specific version of the package is installed?

Connection type                     : vnc,rdp(both)


You are seeing this behavior with both VNC and RDP?

- Mike



Re: Connection Error

2020-06-24 Thread Mike Jumper
On Wed, Jun 24, 2020 at 12:43 AM Prince V S  wrote:

> Hi Ivanmarcus,
>
> Please find the system details below. I checked the logs and found VNC
> connection error (Error writing to TLS: Error in the push function). Is
> it a configuration issue?
>

This sounds possibly like:
https://issues.apache.org/jira/browse/GUACAMOLE-414

...
> Freerdp version  : freerdp2
>

Beware that "freerdp2" (and even something like "2.0.0") is unfortunately
vague. There are quite a few versions of this library around, many actually
being git snapshots. Even two packages that appear to have the same version
number may be significantly different:

http://guacamole.apache.org/releases/1.1.0/#freerdp-200-or-later-is-now-required-for-rdp-support

Do you know what specific version of the package is installed?

Connection type : vnc,rdp(both)


You are seeing this behavior with both VNC and RDP?

- Mike


Re: Connection Error

2020-06-24 Thread Prince V S

Hi Ivanmarcus,

Please find the system details below. I checked the logs and found VNC 
connection error (Error writing to TLS: Error in the push function). Is 
it a configuration issue?


Guacamole version                : 1.1.0
OS version                             : Ubuntu server 18.04 LTS Bionic
OS type                                  : VM
Freerdp version                      : freerdp2
Connection type                     : vnc,rdp(both)
OS version(target machine)   : ubuntu 18.04 desktop,redhat 7.7,centos 7, 
windows 7, windows 2012 server


Regards,

Prince V S

On 24/06/20 10:40 am, ivanmarcus wrote:


Prince,

It would be helpful if you could provide detail on the version of 
Guacamole you have installed, the OS distribution you're using, the 
version of FreeRDP, and whether this is installed in a VM, bare metal, 
or docker?


Also, what is the connection type (eg. VNC, RDP etc), and what OS is 
the target machine running (eg. Win7, Win10, Mint etc)?


Finally, have you looked at the log files? Their location may depend 
on the OS but generally syslog and catalina.out are useful and the 
information therein may assist in narrowing down the issue.


On 24/06/2020 4:32 p.m., Prince V S wrote:

Hi,

I am new to Guacamole. I have installed guacamole in lab and testing 
the same.


I am observing " connection error" frequently. I am getting this 
error frequently when i click mouse. The same error is not seen when 
video is played in remote machine.


Please provide your suggestion to resolve this issue.

Regards,

Prince V S



-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org





-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org



Re: Connection Error

2020-06-23 Thread ivanmarcus

Prince,

It would be helpful if you could provide detail on the version of 
Guacamole you have installed, the OS distribution you're using, the 
version of FreeRDP, and whether this is installed in a VM, bare metal, 
or docker?


Also, what is the connection type (eg. VNC, RDP etc), and what OS is the 
target machine running (eg. Win7, Win10, Mint etc)?


Finally, have you looked at the log files? Their location may depend on 
the OS but generally syslog and catalina.out are useful and the 
information therein may assist in narrowing down the issue.


On 24/06/2020 4:32 p.m., Prince V S wrote:

Hi,

I am new to Guacamole. I have installed guacamole in lab and testing 
the same.


I am observing " connection error" frequently. I am getting this error 
frequently when i click mouse. The same error is not seen when video 
is played in remote machine.


Please provide your suggestion to resolve this issue.

Regards,

Prince V S



-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org





Re: Connection Error: Balancing Connection Group

2019-05-08 Thread Michael Barkdoll
> I believe this is all documented in the page I mentioned, above, which
includes the proxiesHeaders you mention, there.

You're right I didn't realize proxiesHeader defaults to "x-forwarded-by" in
tomcat's server.xml, so my problem was with the static ip address being
required.  I'll just need to use an ip range when HA work is more polished
to deploy this out to our private cloud.  You're all doing really great
work and I'm very excited about the direction the project is taking
hopefully at my university we can switch to thin clients in some places due
to everyone's hard work.

Is there anything I can maybe do to help diagnose the issue further?  I say
that with almost complete certainty that you'll finish this before the fact
that it would take me like a month or two to figure out a lot of the
underlying structure of your java code and C code :)  I really love this
project though and wouldn't mind trying to help in some sad way.

E.g., try to document a use case with docker swarm, kubernetes, maybe
demonstrate a use case with a thin client, etc..

Michael Barkdoll


On Wed, May 8, 2019 at 10:12 AM Nick Couchman  wrote:

> On Wed, May 8, 2019 at 10:44 AM Michael Barkdoll 
> wrote:
>
>> Alright, first sorry for all the noise on this thread.  I believe I have
>> uncovered a bug and I'm going to proceed with opening a bug report.
>>
>
> No worries at all - that's what the mailing list is for!
>
>
>>
>> Concerning the reverse proxy, I think I now have a better understanding
>> into my issues, I was a bit new to load-balancers so I'm sure this made
>> some peoples ears bleed... I think I now at least have the reverse proxy
>> working properly.
>>
>> Concerning client remote ip not being provided from the nginx reverse
>> proxy to the tomcat instance my issue was that :
>>
>>1. tomcat's server.xml might require hard coded ip addresses for the
>>RemoteIpValue internalProxies field for load balancing.
>>Note: I am able to specify a range of ip addresses with some wildcard
>>syntax to support multiple nginx reverse proxy load balancers.
>>
>>
> Yes, you do have to specify the IP address(es) of the Nginx proxy servers
> that are going to be talking to Tomcat.  I can't remember what the valid
> syntax is for that field, but I would imagine it supports both ranges and
> individual IPs.  There is some documentation on it, here:
>
>
> http://guacamole.apache.org/doc/gug/proxying-guacamole.html#tomcat-remote-ip
>
>
>>
>>1. My tomcat cataline.out warning about remoteIpProxiesHeader was due
>>to that value being for an Apache reverse proxy server not an nginx.
>>The documentation could be made more clear here on the apache
>>guacamole website.  I might try to open something to request it to be
>>changed.
>>Also, I modified the server.xml values to something more appropriate
>>for nginx reverse proxy load balancing below.
>>Most Notable: I added a proxiesHeader="x-forwarded-by" to "hold the
>>list of proxies that have been processed in the incoming remoteIpHeader"
>>source:
>>
>> https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/catalina/valves/RemoteIpValve.html
>>
>>
> I believe this is all documented in the page I mentioned, above, which
> includes the proxiesHeaders you mention, there.  If the documentation can
> be made more clear we'd be glad for that feedback, or a pull request to
> clean it up.
>
>
>>
>>1. The trustedProxies="nginx" is likely optional, nginx dns resolves
>>to my nginx reverse proxy so I added it just in case the 10.0.0.0/8
>>didn't catch it.
>>
>>
>> My server.xml addition:
>> >internalProxies="10\.\d{1,3}\.\d{1,3}\.\d{1,3}"
>>remoteIpHeader="x-forwarded-for"
>>*proxiesHeader="x-forwarded-by"*
>>trustedProxies="nginx"
>>protocolHeader="x-forwarded-proto" />
>>
>> The following has the conflcting apache server.xml addition:
>> https://guacamole.apache.org/doc/gug/proxying-guacamole.html
>> >internalProxies="127.0.0.1"
>>remoteIpHeader="x-forwarded-for"
>>*remoteIpProxiesHeader="x-forwarded-by"*
>>protocolHeader="x-forwarded-proto" />
>>
>>
>> My goal was to have multiple nginx reverse proxy load balancers and
>> multiple tomcat guacamole-client containers running, but it looks like that
>> isn't support inside the apache guacamole-client side.  I'm basing that
>> assumption on the fact that when my nginx reverse proxy sent some clients
>> to one tomcat server and some to another, when a client opened a connection
>> to a connection group that was of type balancing they both were connected
>> to the same vm.  So, from my point of view I'm thinking they're not
>> programmed to support multiple instances of guacamole-client running in a
>> balancing connection group, if someone can verify that it would be
>> appreciated.
>>
>
> Yeah, there is definitely some work to be done 

Re: Connection Error: Balancing Connection Group

2019-05-08 Thread Nick Couchman
On Wed, May 8, 2019 at 10:44 AM Michael Barkdoll 
wrote:

> Alright, first sorry for all the noise on this thread.  I believe I have
> uncovered a bug and I'm going to proceed with opening a bug report.
>

No worries at all - that's what the mailing list is for!


>
> Concerning the reverse proxy, I think I now have a better understanding
> into my issues, I was a bit new to load-balancers so I'm sure this made
> some peoples ears bleed... I think I now at least have the reverse proxy
> working properly.
>
> Concerning client remote ip not being provided from the nginx reverse
> proxy to the tomcat instance my issue was that :
>
>1. tomcat's server.xml might require hard coded ip addresses for the
>RemoteIpValue internalProxies field for load balancing.
>Note: I am able to specify a range of ip addresses with some wildcard
>syntax to support multiple nginx reverse proxy load balancers.
>
>
Yes, you do have to specify the IP address(es) of the Nginx proxy servers
that are going to be talking to Tomcat.  I can't remember what the valid
syntax is for that field, but I would imagine it supports both ranges and
individual IPs.  There is some documentation on it, here:

http://guacamole.apache.org/doc/gug/proxying-guacamole.html#tomcat-remote-ip


>
>1. My tomcat cataline.out warning about remoteIpProxiesHeader was due
>to that value being for an Apache reverse proxy server not an nginx.
>The documentation could be made more clear here on the apache
>guacamole website.  I might try to open something to request it to be
>changed.
>Also, I modified the server.xml values to something more appropriate
>for nginx reverse proxy load balancing below.
>Most Notable: I added a proxiesHeader="x-forwarded-by" to "hold the
>list of proxies that have been processed in the incoming remoteIpHeader"
>source:
>
> https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/catalina/valves/RemoteIpValve.html
>
>
I believe this is all documented in the page I mentioned, above, which
includes the proxiesHeaders you mention, there.  If the documentation can
be made more clear we'd be glad for that feedback, or a pull request to
clean it up.


>
>1. The trustedProxies="nginx" is likely optional, nginx dns resolves
>to my nginx reverse proxy so I added it just in case the 10.0.0.0/8
>didn't catch it.
>
>
> My server.xml addition:
> internalProxies="10\.\d{1,3}\.\d{1,3}\.\d{1,3}"
>remoteIpHeader="x-forwarded-for"
>*proxiesHeader="x-forwarded-by"*
>trustedProxies="nginx"
>protocolHeader="x-forwarded-proto" />
>
> The following has the conflcting apache server.xml addition:
> https://guacamole.apache.org/doc/gug/proxying-guacamole.html
> internalProxies="127.0.0.1"
>remoteIpHeader="x-forwarded-for"
>*remoteIpProxiesHeader="x-forwarded-by"*
>protocolHeader="x-forwarded-proto" />
>
>
> My goal was to have multiple nginx reverse proxy load balancers and
> multiple tomcat guacamole-client containers running, but it looks like that
> isn't support inside the apache guacamole-client side.  I'm basing that
> assumption on the fact that when my nginx reverse proxy sent some clients
> to one tomcat server and some to another, when a client opened a connection
> to a connection group that was of type balancing they both were connected
> to the same vm.  So, from my point of view I'm thinking they're not
> programmed to support multiple instances of guacamole-client running in a
> balancing connection group, if someone can verify that it would be
> appreciated.
>

Yeah, there is definitely some work to be done on the Guacamole side for
full HA support.  You *can* point multiple Nginx servers at multiple Tomcat
systems running Guacamole client; however, Guacamole Client currently does
not have a way to synchronize client sessions across multiple instances of
Guacamole Client, so there's no way to have it such that one Guacamole
Client session will show the remote connections from the others.  I started
working on this a few months ago but didn't make much progress.  Maybe I'll
dig that work back up...


>
> Therefore, I've now switched to only using one apache guacamole-client
> tomcat instance behind the nginx reverse proxy.
>

Probably a good idea until we sort out what might be going on, here :-).


>
> *Possible bug:*
> However, I still have the same issue that I was previously describing with
> users test, test2, test3 and connection group cg1 and virtual machines with
> xrdp connections called s1, s2.
>
> Essentially,
>
> test can connect get a session with cg1's s1.
> test2 can connect get a session with cg1's s2.
> test2 can disconnect from cg1's s2.
> test3 can connect get a session with cg1's s2.
> test2 can disconnect from cg1's s2.
> test2 can connect get a session with cg1's s2.
>
> Now if test closes the session with 

Re: Connection Error: Balancing Connection Group

2019-05-06 Thread Michael Barkdoll
Are other users experiencing this same issue?  Should I open a bug report?

Michael Barkdoll


On Fri, May 3, 2019 at 4:32 PM Michael Barkdoll 
wrote:

> Here is one more scenario that I thought was interesting:
>
> machines: m1, m2, m3
> vms: s1, s2 (in balancing connection group)
>
> m1 => user test => connectgrp => s1
> m2 => user test2 => connectgrp => s2
> m2 => user test2 => logoff s2
> m3 => user test3 => connectgrp => s2
> m3 => user test3 => logoff s2
> m2 => user test2 => connectgrp => s2
>
> # Logoff s1, (s2 is still active on m2)
> m1 => user test1 => logoff s1
> m3 => user test3 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
>
> Ok, that was expected from my previous experience, but now logoff the last
> active session on m2:
> m2 => user test2 => logoff s2
>
> Now attempt to reconnect with m3, you'd think you'd get s1 with least
> number of connection balancing, but no its s2 when it works.
> Wait 15 second (for api sync?)
> m3 => user test3 => connectgrp => s2
>
> Now attempt to connect m2,
> m2 => user test2 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
>
> Attempt to connect m1,
> m1 => user test => connectgrp => s1 (works)
>
> I have stickiness enabled on the nginx could that be related?
>
> https://github.com/michaelbarkdoll/guacamole-reverse-proxy-nginx/blob/master/nginx.conf
>
> Michael Barkdoll
>
>
> On Fri, May 3, 2019 at 4:13 PM Michael Barkdoll 
> wrote:
>
>> m1 => user test => connectgrp => s1
>> m2 => user test2 => connectgrp => s2
>> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
>> m2 => user test2 => logoff s2
>> m3 => user test3 => connectgrp => s2
>> m3 => user test3 => logoff s2
>> m2 => user test2 => connectgrp => s2
>>
>> Everything looks good right?  But, now if I disconnect from s1 on m1's
>> user test things get wanky.
>>
>> m1 => user test1 => logoff s1
>> m3 => user test3 => connectgrp =>
>> Connection Error: This connection is currently in use, and concurrent
>> access to this connection is not allowed. Please try again later.
>> m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
>> nothing)
>> m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
>> m3 => user test3 => connectgrp =>
>> Connection Error: This connection is currently in use, and concurrent
>> access to this connection is not allowed. Please try again later.
>>
>> [Optionally, I should note: If I try here to reconnect with
>> m1 => user test => connectgrp => s1 (that user connection still works for
>> that particular machine)
>> m1 => user test => loggoff s1]
>>
>> m3 => user test3 => logoff
>> m3 => user test3 => login
>> m3 => user test3 => connectgrp => s1 (now works)
>>
>> Also, I'm using an nginx reverse proxy with ip_hash load balancing
>> against two different guacamole tomcat frontends, but all the machines have
>> a separate unique ip address, so I don't think it would interfere.
>>
>> Michael Barkdoll
>>
>>
>> On Fri, May 3, 2019 at 3:47 PM Michael Barkdoll 
>> wrote:
>>
>>> Thanks so much for all the feedback, such a great community here.
>>>
>>> > If you wait ~15 seconds, does it allow you to connect?
>>> No
>>>
>>> > On the Guacamole server index.html page I added a delete session
>>> cookies on
>>> refresh or browser close forcing connections to re-authenticate, this
>>> works
>>> like a charm for our ondemand environment.
>>>
>>> Yes, if I log out and back in things suddenly work, so something appears
>>> to be related to the index.html page.
>>>
>>> Here is what concerns me:
>>>
>>> I have a balancing connection group with 2 VM's inside of it s1 and s2.
>>> I'm now using three different machines (m1, m2, m3), one uses chrome with
>>> that stupid shared profile stuff.  The other two are firefox no profile
>>> sharing, separate machines, etc...
>>>
>>> m1 => user test => connectgrp => s1
>>> m2 => user test2 => connectgrp => s2
>>> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
>>> m2 => user test2 => logoff s2
>>> m3 => user test3 => connectgrp => s2
>>> m3 => user test3 => logoff s2
>>> m2 => user test2 => connectgrp => s2
>>>
>>> Everything looks good right?  But, now if I disconnect from s1 on m1's
>>> user test things get wanky.
>>>
>>> m1 => user test1 => logoff s1
>>> m3 => user test3 => connectgrp =>
>>> Connection Error: This connection is currently in use, and concurrent
>>> access to this connection is not allowed. Please try again later.
>>> m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
>>> nothing)
>>> m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
>>> m3 => user test3 => connectgrp =>
>>> Connection Error: This connection is currently in use, and concurrent
>>> access to this connection is not allowed. Please try again later.
>>>
>>> m3 => user 

Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
Here is one more scenario that I thought was interesting:

machines: m1, m2, m3
vms: s1, s2 (in balancing connection group)

m1 => user test => connectgrp => s1
m2 => user test2 => connectgrp => s2
m2 => user test2 => logoff s2
m3 => user test3 => connectgrp => s2
m3 => user test3 => logoff s2
m2 => user test2 => connectgrp => s2

# Logoff s1, (s2 is still active on m2)
m1 => user test1 => logoff s1
m3 => user test3 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.

Ok, that was expected from my previous experience, but now logoff the last
active session on m2:
m2 => user test2 => logoff s2

Now attempt to reconnect with m3, you'd think you'd get s1 with least
number of connection balancing, but no its s2 when it works.
Wait 15 second (for api sync?)
m3 => user test3 => connectgrp => s2

Now attempt to connect m2,
m2 => user test2 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.

Attempt to connect m1,
m1 => user test => connectgrp => s1 (works)

I have stickiness enabled on the nginx could that be related?
https://github.com/michaelbarkdoll/guacamole-reverse-proxy-nginx/blob/master/nginx.conf

Michael Barkdoll


On Fri, May 3, 2019 at 4:13 PM Michael Barkdoll 
wrote:

> m1 => user test => connectgrp => s1
> m2 => user test2 => connectgrp => s2
> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
> m2 => user test2 => logoff s2
> m3 => user test3 => connectgrp => s2
> m3 => user test3 => logoff s2
> m2 => user test2 => connectgrp => s2
>
> Everything looks good right?  But, now if I disconnect from s1 on m1's
> user test things get wanky.
>
> m1 => user test1 => logoff s1
> m3 => user test3 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
> m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
> nothing)
> m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
> m3 => user test3 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
>
> [Optionally, I should note: If I try here to reconnect with
> m1 => user test => connectgrp => s1 (that user connection still works for
> that particular machine)
> m1 => user test => loggoff s1]
>
> m3 => user test3 => logoff
> m3 => user test3 => login
> m3 => user test3 => connectgrp => s1 (now works)
>
> Also, I'm using an nginx reverse proxy with ip_hash load balancing against
> two different guacamole tomcat frontends, but all the machines have a
> separate unique ip address, so I don't think it would interfere.
>
> Michael Barkdoll
>
>
> On Fri, May 3, 2019 at 3:47 PM Michael Barkdoll 
> wrote:
>
>> Thanks so much for all the feedback, such a great community here.
>>
>> > If you wait ~15 seconds, does it allow you to connect?
>> No
>>
>> > On the Guacamole server index.html page I added a delete session
>> cookies on
>> refresh or browser close forcing connections to re-authenticate, this
>> works
>> like a charm for our ondemand environment.
>>
>> Yes, if I log out and back in things suddenly work, so something appears
>> to be related to the index.html page.
>>
>> Here is what concerns me:
>>
>> I have a balancing connection group with 2 VM's inside of it s1 and s2.
>> I'm now using three different machines (m1, m2, m3), one uses chrome with
>> that stupid shared profile stuff.  The other two are firefox no profile
>> sharing, separate machines, etc...
>>
>> m1 => user test => connectgrp => s1
>> m2 => user test2 => connectgrp => s2
>> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
>> m2 => user test2 => logoff s2
>> m3 => user test3 => connectgrp => s2
>> m3 => user test3 => logoff s2
>> m2 => user test2 => connectgrp => s2
>>
>> Everything looks good right?  But, now if I disconnect from s1 on m1's
>> user test things get wanky.
>>
>> m1 => user test1 => logoff s1
>> m3 => user test3 => connectgrp =>
>> Connection Error: This connection is currently in use, and concurrent
>> access to this connection is not allowed. Please try again later.
>> m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
>> nothing)
>> m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
>> m3 => user test3 => connectgrp =>
>> Connection Error: This connection is currently in use, and concurrent
>> access to this connection is not allowed. Please try again later.
>>
>> m3 => user test3 => connectgrp => logoff
>> m3 => user test3 => connectgrp => login
>> m3 => user test3 => connectgrp => connectgrp => s1 (now works)
>>
>> Michael Barkdoll
>>
>>
>> On Fri, May 3, 2019 at 3:23 PM sciUser 
>> wrote:
>>
>>> Hello,
>>>
>>> In order to understand whats happening here, one will need to 

Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
m1 => user test => connectgrp => s1
m2 => user test2 => connectgrp => s2
m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
m2 => user test2 => logoff s2
m3 => user test3 => connectgrp => s2
m3 => user test3 => logoff s2
m2 => user test2 => connectgrp => s2

Everything looks good right?  But, now if I disconnect from s1 on m1's user
test things get wanky.

m1 => user test1 => logoff s1
m3 => user test3 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.
m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
nothing)
m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
m3 => user test3 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.

[Optionally, I should note: If I try here to reconnect with
m1 => user test => connectgrp => s1 (that user connection still works for
that particular machine)
m1 => user test => loggoff s1]

m3 => user test3 => logoff
m3 => user test3 => login
m3 => user test3 => connectgrp => s1 (now works)

Also, I'm using an nginx reverse proxy with ip_hash load balancing against
two different guacamole tomcat frontends, but all the machines have a
separate unique ip address, so I don't think it would interfere.

Michael Barkdoll


On Fri, May 3, 2019 at 3:47 PM Michael Barkdoll 
wrote:

> Thanks so much for all the feedback, such a great community here.
>
> > If you wait ~15 seconds, does it allow you to connect?
> No
>
> > On the Guacamole server index.html page I added a delete session cookies
> on
> refresh or browser close forcing connections to re-authenticate, this works
> like a charm for our ondemand environment.
>
> Yes, if I log out and back in things suddenly work, so something appears
> to be related to the index.html page.
>
> Here is what concerns me:
>
> I have a balancing connection group with 2 VM's inside of it s1 and s2.
> I'm now using three different machines (m1, m2, m3), one uses chrome with
> that stupid shared profile stuff.  The other two are firefox no profile
> sharing, separate machines, etc...
>
> m1 => user test => connectgrp => s1
> m2 => user test2 => connectgrp => s2
> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
> m2 => user test2 => logoff s2
> m3 => user test3 => connectgrp => s2
> m3 => user test3 => logoff s2
> m2 => user test2 => connectgrp => s2
>
> Everything looks good right?  But, now if I disconnect from s1 on m1's
> user test things get wanky.
>
> m1 => user test1 => logoff s1
> m3 => user test3 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
> m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
> nothing)
> m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
> m3 => user test3 => connectgrp =>
> Connection Error: This connection is currently in use, and concurrent
> access to this connection is not allowed. Please try again later.
>
> m3 => user test3 => connectgrp => logoff
> m3 => user test3 => connectgrp => login
> m3 => user test3 => connectgrp => connectgrp => s1 (now works)
>
> Michael Barkdoll
>
>
> On Fri, May 3, 2019 at 3:23 PM sciUser 
> wrote:
>
>> Hello,
>>
>> In order to understand whats happening here, one will need to understand
>> how
>> incognito mode works v.s. normal browser operations.
>>
>> Chrome incognito: Will not save any cookies, credentials, links or history
>> and deactivates extensions.  So when you close the incognito browser all
>> logged in session are gone.
>>
>> Chrome guest mode: Will give you a blank profile to anyone who is
>> temporarily using Chrome. This to is like incognito mode but you can not
>> change Chrome settings.
>>
>> Chrome normal mode: Will cache cookies, retain login credentials, session
>> information and remember history.
>>
>> I am betting dollars to donuts that your sessions are conflicting in both
>> chrome and guacamole server..
>>
>> You should test this with Firefox and Chrome so the sessions are truly
>> isolated.
>>
>> On the Guacamole server index.html page I added a delete session cookies
>> on
>> refresh or browser close forcing connections to re-authenticate, this
>> works
>> like a charm for our ondemand environment.
>>
>> Hope this helps
>>
>> Thank You
>>
>>
>>
>> --
>> Sent from:
>> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
>>
>


Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
Thanks so much for all the feedback, such a great community here.

> If you wait ~15 seconds, does it allow you to connect?
No

> On the Guacamole server index.html page I added a delete session cookies
on
refresh or browser close forcing connections to re-authenticate, this works
like a charm for our ondemand environment.

Yes, if I log out and back in things suddenly work, so something appears to
be related to the index.html page.

Here is what concerns me:

I have a balancing connection group with 2 VM's inside of it s1 and s2.
I'm now using three different machines (m1, m2, m3), one uses chrome with
that stupid shared profile stuff.  The other two are firefox no profile
sharing, separate machines, etc...

m1 => user test => connectgrp => s1
m2 => user test2 => connectgrp => s2
m3 => user test3 => connectiongrp => Expectedly fails (all vms are used)
m2 => user test2 => logoff s2
m3 => user test3 => connectgrp => s2
m3 => user test3 => logoff s2
m2 => user test2 => connectgrp => s2

Everything looks good right?  But, now if I disconnect from s1 on m1's user
test things get wanky.

m1 => user test1 => logoff s1
m3 => user test3 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.
m3 => user test3 => connectgrp =>  Reconnect link (nothing, wait 15sec,
nothing)
m3 => user test3 => connectgrp =>  Click Home, Wait 15sec
m3 => user test3 => connectgrp =>
Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.

m3 => user test3 => connectgrp => logoff
m3 => user test3 => connectgrp => login
m3 => user test3 => connectgrp => connectgrp => s1 (now works)

Michael Barkdoll


On Fri, May 3, 2019 at 3:23 PM sciUser  wrote:

> Hello,
>
> In order to understand whats happening here, one will need to understand
> how
> incognito mode works v.s. normal browser operations.
>
> Chrome incognito: Will not save any cookies, credentials, links or history
> and deactivates extensions.  So when you close the incognito browser all
> logged in session are gone.
>
> Chrome guest mode: Will give you a blank profile to anyone who is
> temporarily using Chrome. This to is like incognito mode but you can not
> change Chrome settings.
>
> Chrome normal mode: Will cache cookies, retain login credentials, session
> information and remember history.
>
> I am betting dollars to donuts that your sessions are conflicting in both
> chrome and guacamole server..
>
> You should test this with Firefox and Chrome so the sessions are truly
> isolated.
>
> On the Guacamole server index.html page I added a delete session cookies on
> refresh or browser close forcing connections to re-authenticate, this works
> like a charm for our ondemand environment.
>
> Hope this helps
>
> Thank You
>
>
>
> --
> Sent from:
> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
>


Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
Thanks, just seemed odd that two browsers on the same machine (one
incognito, one normal on separate accounts) allow the first connection to
separate VMs in the connection group.  However, an issue arrives when I
disconnect both browsers and log out back in with the incognito browser to
the same connection group it works but then the normal browser throws that
error.

Connection Error: This connection is currently in use, and concurrent
access to this connection is not allowed. Please try again later.

But, this seems like a rather minor issue when I look at it more and if it
is intended maybe it is no big deal.

Michael Barkdoll


On Fri, May 3, 2019 at 2:19 PM Mike Jumper  wrote:

> On Fri, May 3, 2019 at 8:48 AM Michael Barkdoll 
> wrote:
>
>> ...
>> Should've read:
>> Refreshing first Chrome browser *doesn't* update the connection string:
>> https://host/guacamole/#/client/MQBnAG15c3Fs
>> 
>>
>> That actually appears to be the expected behavior since this is a
>> connection group url (I'm guessing).
>>
>
> Yes, that's the expected behavior. The URL will not change. The balancing
> across underlying connections happens internally within the server. It is
> intentionally not exposed on the user facing side.
>
> - Mike
>
>


Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Mike Jumper
On Fri, May 3, 2019 at 8:48 AM Michael Barkdoll 
wrote:

> ...
> Should've read:
> Refreshing first Chrome browser *doesn't* update the connection string:
> https://host/guacamole/#/client/MQBnAG15c3Fs
> 
>
> That actually appears to be the expected behavior since this is a
> connection group url (I'm guessing).
>

Yes, that's the expected behavior. The URL will not change. The balancing
across underlying connections happens internally within the server. It is
intentionally not exposed on the user facing side.

- Mike


Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
So, at first, I had a hard time reproducing this situation.  After it
occurs one time, I have to completely close my incognito windows for the
issue to come back a second time.

Also, I had a second typo:
Refreshing first Chrome browser does update the connection string:
https://host/guacamole/#/client/MQBnAG15c3Fs


Should've read:
Refreshing first Chrome browser *doesn't* update the connection string:
https://host/guacamole/#/client/MQBnAG15c3Fs


That actually appears to be the expected behavior since this is a
connection group url (I'm guessing).

Michael Barkdoll


On Fri, May 3, 2019 at 10:18 AM Michael Barkdoll 
wrote:

> Sorry, I should be more clear, I had a typo.
>
>
>1. First Chrome Browser:
>Connect to the connection group. (works Linux s1 establishes a
>connection)
>2. Second Chrome Incognito Browser:
>Connects to the connection group. (works Linux s2 est conn)
>3. Disconnect and log out of Guacamole Tomcat instance on Second
>Chrome Incognito Browser (works)
>4. Disconnect from Linux s1 on first Chrome Browser (works)
>Still connected to Guacamole Tomcat Front End
>5. Second Chrome Incognito Browser:
>*Authenticates and logs back into Guacamole Tomcat Front end*
>Connects to the connection group. *(works Linux s1 est conn)*
>6. First Chrome Browser (still connected to Tomcat frontend):
>Connect to the connection group. (Connection Error: This connection is
>currently in use, and concurrent access to this connection is not allowed.
>Please try again later.)
>
>
> Michael Barkdoll
>
>
> On Fri, May 3, 2019 at 10:15 AM Michael Barkdoll 
> wrote:
>
>> First, thank you for a wonderful Apache Project!
>>
>> Here is what I'm facing:
>>
>> I have a Balancing type Connection Group with two Linux Ubuntu 19.04 XRDP
>> servers with XFCE running and I have some hiccups that I'm trying to iron
>> out.
>>
>> E.g.,
>>
>>1. First Chrome Browser:
>>Connect to the connection group. (works Linux s1 establishes a
>>connection)
>>2. Second Chrome Incognito Browser:
>>Connects to the connection group. (works Linux s2 est conn)
>>3. Disconnect and log out of Second Chrome Incognito Browser (works)
>>4. Disconnect from first Chrome Browser (works)
>>5. Second Chrome Incognito Browser:
>>Connects to the connection group. (works Linux s2 est conn)
>>6. First Chrome Browser:
>>Connect to the connection group. (Connection Error: This connection
>>is currently in use, and concurrent access to this connection is not
>>allowed. Please try again later.)
>>
>>
>> [image: image.png]
>>
>> Screenshot from admin showing only one session is in use from the
>> connection group.
>>
>> [image: image.png]
>> Refreshing first Chrome browser does update the connection string:
>> https://host/guacamole/#/client/MQBnAG15c3Fs
>> 
>>
>> However, I can see that both web browsers have this connection string for
>> the connection group.
>>
>> Michael Barkdoll
>>
>


Re: Connection Error: Balancing Connection Group

2019-05-03 Thread Michael Barkdoll
Sorry, I should be more clear, I had a typo.


   1. First Chrome Browser:
   Connect to the connection group. (works Linux s1 establishes a
   connection)
   2. Second Chrome Incognito Browser:
   Connects to the connection group. (works Linux s2 est conn)
   3. Disconnect and log out of Guacamole Tomcat instance on Second Chrome
   Incognito Browser (works)
   4. Disconnect from Linux s1 on first Chrome Browser (works)
   Still connected to Guacamole Tomcat Front End
   5. Second Chrome Incognito Browser:
   *Authenticates and logs back into Guacamole Tomcat Front end*
   Connects to the connection group. *(works Linux s1 est conn)*
   6. First Chrome Browser (still connected to Tomcat frontend):
   Connect to the connection group. (Connection Error: This connection is
   currently in use, and concurrent access to this connection is not allowed.
   Please try again later.)


Michael Barkdoll


On Fri, May 3, 2019 at 10:15 AM Michael Barkdoll 
wrote:

> First, thank you for a wonderful Apache Project!
>
> Here is what I'm facing:
>
> I have a Balancing type Connection Group with two Linux Ubuntu 19.04 XRDP
> servers with XFCE running and I have some hiccups that I'm trying to iron
> out.
>
> E.g.,
>
>1. First Chrome Browser:
>Connect to the connection group. (works Linux s1 establishes a
>connection)
>2. Second Chrome Incognito Browser:
>Connects to the connection group. (works Linux s2 est conn)
>3. Disconnect and log out of Second Chrome Incognito Browser (works)
>4. Disconnect from first Chrome Browser (works)
>5. Second Chrome Incognito Browser:
>Connects to the connection group. (works Linux s2 est conn)
>6. First Chrome Browser:
>Connect to the connection group. (Connection Error: This connection is
>currently in use, and concurrent access to this connection is not allowed.
>Please try again later.)
>
>
> [image: image.png]
>
> Screenshot from admin showing only one session is in use from the
> connection group.
>
> [image: image.png]
> Refreshing first Chrome browser does update the connection string:
> https://host/guacamole/#/client/MQBnAG15c3Fs
> 
>
> However, I can see that both web browsers have this connection string for
> the connection group.
>
> Michael Barkdoll
>


Re: Connection Error. You do not have permission to access this connection. Guac 1.0.0

2019-04-23 Thread VictorC
Hello,
finally solved!
Problem was in apache2 module *libapache2-mod-evasive* (DDOs protection)
After disabling this module *a2dismod evasive*, guacamole works like a
charm!
VicC



--
Sent from: 
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/


Re: Connection Error. You do not have permission to access this connection. Guac 1.0.0

2019-04-17 Thread VictorC


this is log with debug enabled:
*1) if I access tomcat directly http://server:8080/guacamole/#/ this is
WORKING everytime*
15:27:28.125 [localhost-startStop-1] DEBUG o.a.g.e.LanguageResourceService -
Merged strings with existing language: "en"
15:27:28.125 [localhost-startStop-1] INFO  o.a.g.extension.ExtensionModule -
Extension "MySQL Authentication" loaded.
15:27:28.126 [localhost-startStop-1] DEBUG o.a.g.extension.ExtensionModule -
[2] Binding AuthenticationProvider
"org.apache.guacamole.auth.file.FileAuthenticationProvider".
15:27:28.127 [localhost-startStop-1] INFO 
o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is "/etc/guacamole".
15:27:28.259 [localhost-startStop-1] INFO  o.a.g.t.w.WebSocketTunnelModule -
Loading JSR-356 WebSocket support...
15:27:28.277 [localhost-startStop-1] DEBUG o.a.guacamole.tunnel.TunnelModule
- WebSocket module loaded:
org.apache.guacamole.tunnel.websocket.WebSocketTunnelModule
17-Apr-2019 15:27:28.675 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.RESTExceptionMapper as a provider
class
17-Apr-2019 15:27:28.678 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.extension.ExtensionRESTService as a
root resource class
17-Apr-2019 15:27:28.679 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.language.LanguageRESTService as a root
resource class
17-Apr-2019 15:27:28.679 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.patch.PatchRESTService as a root
resource class
17-Apr-2019 15:27:28.679 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.auth.TokenRESTService as a root
resource class
17-Apr-2019 15:27:28.680 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.apache.guacamole.rest.session.SessionRESTService as a root
resource class
17-Apr-2019 15:27:28.680 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.register
Registering org.codehaus.jackson.jaxrs.JacksonJsonProvider as a provider
class
17-Apr-2019 15:27:28.684 INFO [localhost-startStop-1]
com.sun.jersey.server.impl.application.WebApplicationImpl._initiate
Initiating Jersey application, version 'Jersey: 1.17.1 02/28/2013 12:47 PM'
17-Apr-2019 15:27:28.786 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.RESTExceptionMapper to
GuiceManagedComponentProvider with the scope "Singleton"
17-Apr-2019 15:27:28.789 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.codehaus.jackson.jaxrs.JacksonJsonProvider to
GuiceManagedComponentProvider with thescope "Singleton"
17-Apr-2019 15:27:29.421 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.extension.ExtensionRESTService to
GuiceManagedComponentProvider with the scope "PerRequest"
17-Apr-2019 15:27:29.427 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.language.LanguageRESTService to
GuiceManagedComponentProvider with the scope "PerRequest"
17-Apr-2019 15:27:29.428 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.patch.PatchRESTService to
GuiceManagedComponentProvider with the scope "PerRequest"
17-Apr-2019 15:27:29.432 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.auth.TokenRESTService to
GuiceManagedComponentProvider with the scope "PerRequest"
17-Apr-2019 15:27:29.434 INFO [localhost-startStop-1]
com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory.getComponentProvider
Binding org.apache.guacamole.rest.session.SessionRESTService to
GuiceManagedComponentProvider with the scope "PerRequest"
17-Apr-2019 15:27:29.454 INFO [localhost-startStop-1]
org.webjars.servlet.WebjarsServlet.init WebjarsServlet initialization
completed
17-Apr-2019 15:27:29.463 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive [/var/lib/tomcat8/webapps/guacamole.war] has finished in
[4,613] ms
17-Apr-2019 15:27:29.465 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory [/var/lib/tomcat8/webapps/ROOT]
17-Apr-2019 15:27:29.927 INFO 

Re: Connection Error. You do not have permission to access this connection. Guac 1.0.0

2019-04-17 Thread Nick Couchman
On Wed, Apr 17, 2019 at 7:18 AM VictorC  wrote:

> Here is all version info:
> Ubuntu 18.04.2 LTS
> PHP 7.2.15-0ubuntu0.18.04.2 (cli) (built: Mar 22 2019 17:05:14) ( NTS )
> mysql  Ver 8.0.15 for Linux on x86_64 (MySQL Community Server - GPL)
> latest guacamole-client-1.0.0.tar.gz
> latest guacamole-1.0.0.war
> guacamole-auth-jdbc-mysql-1.0.0.jar
> mysql-connector-java-8.0.15.jar
>
>
A couple of follow-up questions for you...
- Did you also upgrade guacd (Guacamole Server) when you upgraded the
client packages?
- Did you run the SQL schema update scripts to update the SQL Schema from
the 0.9.9 version to 1.0.0?  Or did you start with a fresh MySQL DB and
import the 1.0.0 schema directly?

-Nick


Re: Connection Error. You do not have permission to access this connection. Guac 1.0.0

2019-04-17 Thread VictorC
Here is all version info:
Ubuntu 18.04.2 LTS
PHP 7.2.15-0ubuntu0.18.04.2 (cli) (built: Mar 22 2019 17:05:14) ( NTS )
mysql  Ver 8.0.15 for Linux on x86_64 (MySQL Community Server - GPL)
latest guacamole-client-1.0.0.tar.gz
latest guacamole-1.0.0.war
guacamole-auth-jdbc-mysql-1.0.0.jar
mysql-connector-java-8.0.15.jar




--
Sent from: 
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/


Re: Connection Error if no username and password is provided. [ Disabling Single sign On ] : CRITICAL

2018-01-07 Thread Nick Couchman
On Sun, Jan 7, 2018 at 8:11 AM, Amarjeet Singh  wrote:

> NLA is not enabled. Not related to NLA .
>
> Errors are as follows :-
>
>>
>> Jan  7 08:09:48 localhost guacd[11753]: Created static channel
>> "hyprint"...
>> Jan  7 08:09:48 localhost guacd[11753]: Authentication requested but
>> username or password not given
>>
>>
Okay, but this error indicates that the server is expecting some form of
authentication up-front...which is usually NLA.  Have you explicitly either
disabled NLA or enabled the lower authentication levels for RDP on the
Windows server?

Also, for the Guacamole connection, are you specifying "RDP" for the
encryption type?  Can you post the values for the connection parameters,
minus any sensitive information?

-Nick


Re: Connection Error if no username and password is provided. [ Disabling Single sign On ] : CRITICAL

2018-01-07 Thread Amarjeet Singh
NLA is not enabled. Not related to NLA .

Errors are as follows :-

>
> Jan  7 08:09:48 localhost guacd[11753]: Created static channel "hyprint"...
> Jan  7 08:09:48 localhost guacd[11753]: Authentication requested but
> username or password not given
> Jan  7 08:09:49 localhost guacd[11753]: Error connecting to RDP server
> Jan  7 08:09:49 localhost guacd[11753]: User
> "@b38ff992-d321-42e8-86fe-e90b7370dafc" disconnected (0 users remain)
> Jan  7 08:09:49 localhost guacd[11753]: Last user of connection
> "$e7aac9f0-0c85-4235-a3ae-57b7f93835e1" disconnected
> Jan  7 08:09:49 localhost guacd[11751]: Connection
> "$e7aac9f0-0c85-4235-a3ae-57b7f93835e1" removed.
>
>
On Sun, Jan 7, 2018 at 6:34 PM, Adrian Owen  wrote:

> If NLA is enabled, you have to supply username and password in connection
> parameters. There is no way to reach the logon screen.
>
> This is Windows security feature. It is not a Guacamole issue.
>
> You can disable NLA with a GPO.
>
>
>
> Sent from my Huawei Mobile
>
>
>  Original Message 
> Subject: Connection Error if no username and password is provided. [
> Disabling Single sign On ] : CRITICAL
> From: Amarjeet Singh
> To: u...@guacamole.incubator.apache.org
> CC:
>
> Hi Team,
>
>
>
> If I don't pass username and password in the parameters it gives the
> error. I want the *user to pass username and password on window itself.*
>
> It is very important  feature as well.
>
> Environment  -- > Windows Server 2012 R2
>
> NLA is disable on the Machine. *Not related to NLA*
>
>
> Please help me to resolve the above issue.
>
>
> Thanks and Regards,
> Amarjeet Singh
>


Re: Connection Error if no username and password is provided. [ Disabling Single sign On ] : CRITICAL

2018-01-07 Thread Adrian Owen
If NLA is enabled, you have to supply username and password in connection 
parameters. There is no way to reach the logon screen.

This is Windows security feature. It is not a Guacamole issue.

You can disable NLA with a GPO.



Sent from my Huawei Mobile

 Original Message 
Subject: Connection Error if no username and password is provided. [ Disabling 
Single sign On ] : CRITICAL
From: Amarjeet Singh
To: u...@guacamole.incubator.apache.org
CC:

Hi Team,



If I don't pass username and password in the parameters it gives the error. I 
want the user to pass username and password on window itself.

It is very important  feature as well.

Environment  -- > Windows Server 2012 R2

NLA is disable on the Machine. Not related to NLA


Please help me to resolve the above issue.


Thanks and Regards,
Amarjeet Singh