I suggest there is no track for the feature request about Windows 2008 TS Session Broker support, am I right?
The main request is to redirect connections. I reviewed the repo, tried some revisions, mostly hoped for r1563. But the session halts on redirection.
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Is there some update concerning this ?
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Is someone taking this up ? I'm really stuck with that Connection Broker thing ... :-(
Yeah, we're here in Garden Route, South Africa and we are having quite the tough time getting a work around going.
Any update on this? We will test and provide feedback very quickly.
R
I'm also wondering if someone can look into this?
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
I am also interested in this feature. I just recently discovered the RDP over HTTPS feature using my company's Terminal Server running Windows Server 2008. I'd like to be able to use this from Linux
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Please see: https://sourceforge.net/tracker/?func=detail&aid=3575645&group_id=24366&atid=381349 (tracker patch 3575645). We use these patches since few weeks with success. .. (but have not got any reply from rdesktop developers about ...)
Cheers
Jarek
The server redirection has been rewritten and verified against 2003 and 2008r2 using session directory / broker.
redirect connecton failed when server redirection PDU doesn't contains flag: LB_TARGET_NET_ADDRESS(0x00000001) and doesn't contains field: TargetNetAddress. The mstsc.exe in Windows will reconnect to the server which send this redirection PDU. And I think rdesktop should behave the same way. The quickly fix in rdp.c is:
in rdesktop.c:
Last edit: leeyiw 2013-12-06
it does feel strange that you would receive a redirection PDU wihout information about the target you should connect to. Did you get the warning in console about PDU_REDIRECT_HAS_TARGET_NETBIOS or alike ?
Could you apply this patch and send me redirect_pdu.raw, be aware that your password would be plain text in this packet dump:
Last edit: Henrik Andersson 2013-12-09
I think the reason the redirection PDU doesn't contain TargetNetAddress is
because there is a NAT between RDP client and server, and this field is
optional in the RDP protocol. I will send you a redirect_pdu.raw on monday.
and because the RDP protocol document doesn't describe this scenario,
rdesktop should behave like mstsc.exe.
2013/12/6 Henrik Andersson hean01@users.sf.net
Related
Feature Requests:
#146and I'm not get any warning in console when receive the redirection PDU
2013/12/6 李毅为 leeyiw@gmail.com
Related
Feature Requests:
#146Sorry, I'm late.
Here is the redirect_pdu.raw, It looks like it's only contains a redirect
session ID and the username and passwod
2013/12/6 leeyiw leeyiw@users.sf.net
Support for server redirection using TS Session Broker (2008 / 2012) is now implemented and extensively tested. However rdesktop does not support connecting to a farm using RDS gateway.
I found that 1.8.2 is released. but still didn't handle correct when g_redirect_flags didn't contain PDU_REDIRECT_HAS_IP. can it be fixed in next version? I can upload an patch
Hi,
Yes, could you please create a new bug describing the use-case and attach the patch. I'm not sure how to fix your issue, seems like it's about implementing a new feature, RDS gateway support.
Hi,
I have create a new bug [bugs:#385] and the patch is tested work perfectly on my computer. Please take a look at it, Thanks.
Related
Bugs: #385