[
https://issues.apache.org/jira/browse/GUACAMOLE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198553#comment-16198553
]
MingTao Lou commented on GUACAMOLE-399:
---------------------------------------
HaHa,,,Maybe it has been solved.........I use FreeRDP 1.1 instead of
1.0.2.....maximize not always 1024*768....
like https://issues.apache.org/jira/browse/GUACAMOLE-125
{quote}
What do you mean by "some code to control the parameters that connect guacd"?
Can you describe exactly what has been done and what you're using?
{quote]
The parameters such as remote app dir location,domain username,domain
password,domain,width,height,dpi....These are assembled into packets and sent
to guacd.Just like above.
My predecessors write Node client instead of Java client,rewrite a scoket that
connect page js and a tcp connect guacd.
I think it's just a transfer of data, and it's still going to be sent to the
page.(the js has not rewrited).
If these affect the project, I'm really sorry.
{quote}
Guacamole parameters are name/value pairs. A raw "connect" instruction has no
meaning without the corresponding "args" instruction which the client is
supposed to use to determine which value corresponds to which position within
"connect".
Do you have the set of name/value pairs which you are passing?
{quote}
Yes.the date from guacd:
{code:none}
4.args,8.hostname,4.port,6.domain,8.username,8.password,5.width,6.height,3.dpi,15.initial-program,11.color-depth,13.disable-audio,15.enable-printing,12.enable-drive,10.drive-path,17.create-drive-path,7.console,13.console-audio,13.server-layout,8.security,11.ignore-cert,12.disable-auth,10.remote-app,14.remote-app-dir,15.remote-app-args,15.static-channels,11.client-name,16.enable-wallpaper,14.enable-theming,21.enable-font-smoothing,23.enable-full-window-drag,26.enable-desktop-composition,22.enable-menu-animations,16.preconnection-id,18.preconnection-blob,11.enable-sftp,13.sftp-hostname,9.sftp-port,13.sftp-username,13.sftp-password,16.sftp-private-key,15.sftp-passphrase,14.sftp-directory,14.recording-path,14.recording-name,21.create-recording-path,13.resize-method,18.enable-audio-input,9.read-only;
{code}
then wo send answer:
{code:node}
7.connect,13.192.168.8.179,4.3389,12.********.com,7.*****,6.*****,4.1920,3.945,2.96,0.,0.,0.,0.,4.true,0.,4.true,0.,0.,0.,3.any,4.true,0.,11.WINWORD.exe,42.C:\Program
Files\Microsoft
Office\Office14,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.;
{code}
{quote}
When you encounter a bug in something, it is necessary to determine what is
actually causing that bug. In your case, this means you may well need to
temporarily do something your project isn't aimed at. It doesn't matter that
your project is ultimately meant to leverage RemoteApp; the idea is to
determine whether RemoteApp is related to the problem you're encountering, or
if something more fundamental is wrong.
{quote}
We use a Centos without desktop as a server, guacamole and RDP all installed on
it, I have not tried after I remote connection to the server, use xfreerdp
again to connect to the remote desktop. But there is a direct link to the
desktop in our project, and the effect is the same.
I think FreeRDP 1.0.2 only returns the size value as the size of the display to
the socket, instead of size as the actual desktop size. This feature was
improved in 1.1.
If it is a freerdp error, would you specify 1.1 as the actual version of the
document in the document?
> Remote App maximize always 1024*768
> -----------------------------------
>
> Key: GUACAMOLE-399
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-399
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Affects Versions: 0.9.13-incubating
> Environment: CentOS Linux release 7.2.1511 (Core)
> RDP : xfreerdp 1.0.2
> Reporter: MingTao Lou
>
> In Guacamole Server installation :
> Command: ./configure --with-init-dir=/etc/init.d
> ------------------
> checking for rdpSettings.SupportDisplayControl... no
> -----......--------
> checking for rdpSettings.Width... no
> checking for rdpSettings.Height... no
> ------------------
> These outputs are the key to the problem,is it?
> Is there any solution to this problem?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)