Bug where Daylight Saving not recognised on Servers

  • Thread starter Thread starter dutch0703
  • Start date Start date
D

dutch0703

There is an issue with the 2X Remote Desktop client for Android and for iPad / iPhone relating to Daylight saving.
Our server is in a different state of Australia (Queensland) to myself (NSW). NSW observes Daylight Saving in the summer, Qld does not. During winter, both states are in the same time zone.

When logging onto the server using the 2X client during non daylight saving times, the time on the Terminal Server session shows as 1 hour ahead of the real time.

This error only manifests itself when using the 2X client on any platform (Android or Apple device). All other Mobile device RDP clients do not give this error. I have tried contacting 2X directly about this bug but no one wants to know about it. This is a pity because 2X is the best RDP client for mobile devices available and I have tested several.
If anybody would like to comment or make a suggestion or, help in getting 2X to recognise that there is a flaw in their application, I would be grateful.
 
..i don't get the same... for me it works perfectly...
are u sure is not specific to your installations? i am only saying that as the client has been around for quite a while and if it was a bug somebody else must have noticed that already?

cheers!
 
dutch0703 said:
When logging onto the server using the 2X client during non daylight saving times, the time on the Terminal Server session shows as 1 hour ahead of the real time.
Click to expand...

Do you have the timezone on the Android device set correctly?
 
Those of you that posted that the client works perfectly are partially correct. In most cases and on most servers, it does work OK.
The situation to which I am referring relates to a server which has Timezone recognition enabled. That is, where users log onto the Terminal server from different timezones, the time that the user sees on the server is their own timezone, not the timezone in which the server is located.
I have tried several Remote Desktop clients for Android and iOS. None of the others exhibit this problem. Only the 2X client.
 
I realize this is an old post but I'm trying to use the 2x client for Android to connect to a 2008 R2 Remote Desktop server. I'm experiencing trouble when time zone redirection via group policy is applied same as you describe. The server session is 1 hour less than it is on the android device. I have tried with multiple Android hardware models of tablets & phones and all exhibit this behavior. If i connect to the server using a computer it functions properly. I have had a few other Android client apps work while others have this problem too. I was wondering if you had any luck solving this problem.
 
Did you ever get this problem resolved? I am having the same problem when connecting to a 2008 R2 server with time zone redirection enabled through group policy. It happens on initial connection and reconnection. When I run from command prompt “tzutil /g” I receive message “failed to get the system time zone id”. I've tried several phones and tablets and all exhibit this behavior. Other RDP apps for Android do not have this problem but I like the 2x client. I created a new 2008 R2 server just in case something could be wrong on our production server but the problem exists on the new one too.
 
I personally dont get this problem with the GPO applied and connecting through my Android client. It could be maybe environmental?
 
You must log in or register to reply here.
Back
Top