[ rdesktop-Bugs-1694389 ] Incorrect Time Displayed in Terminal Server session

Bugs item #1694389, was opened at 2007-04-04 10:34
Message generated for change (Comment added) made by jamundso
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=1694389&group_id=24366

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Internals
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect Time Displayed in Terminal Server session

Initial Comment:
Hi - I applied the DLST patch to my Windows Server 2003 host. When a client logs in using rdesktop 1.5.0 the Windows clock for their session is still on Standard Time, but the server shows the correct time. However, after April 1st (The original Daylight Savings Time) the time is now correct for rdesktop sessions into the server. Is rdesktop's code set up to interpret when Daylight Savings should occur? I am probably safe to assume that when October 28th rolls around the client's time will be off for 1 hour until the new DLST goes into affect on November 4th...

Thanks,
Eric Fritsch
[email protected]

----------------------------------------------------------------------

Comment By: Jerry Amundson (jamundso)
Date: 2011-03-22 19:35

Message:
This is an actual problem, and has been since March 2007, in US and Canada
anyway, when DST was extended.
http://www.timeanddate.com/news/time/us-daylight-saving-extended.html

----------------------------------------------------------------------

Comment By: Sean E. Millichamp (seanmil)
Date: 2008-10-15 11:43

Message:
Okay, for whatever reason I can't find a way to attach a file to this
report.  So I have submitted the patch on 2168898.


----------------------------------------------------------------------

Comment By: Sean E. Millichamp (seanmil)
Date: 2008-10-15 11:36

Message:
I found this problem in the US Eastern timezone.  When they changed the DST
rules a couple of years ago it broke the hardcoded values in rdesktop.

IMPORTANT: This does not only impact the time visible in the system clock,
but also all times calculated forward or backward in time based on
timezones (such as Outlook meeting requests).

Note that this problem is only visible if (as another poster stated) you
have a Group Policy with the setting:

Computer Configuration/Administrative Templates/Windows
Components/Terminal
Services/Client/Server data redirection = Allow Time Zone Redirection:
Enabled

Otherwise Windows ignores the fields in question which rdesktop isn't
properly reporting.

I have a patch which dynamically detects the timezone boundaries and sends
them to Windows in the RDP login packet.  It is mostly based off of Wine
code (since they had to handle the Unix/Windows timezone thing already). 
Let me see if I can figure out how to attach the patch to this report...


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-25 20:26

Message:
Logged In: NO 

We are having the timezone redirection problems with the rdesktop 1.6.0
To reproduce the problem you need to make a Group Policy with the setting:
Computer Configuration/Administrative Templates/Windows Components/Terminal
Services/Client/Server data redirection = Allow Time Zone Redirection:    
Enabled
Set the timezone on the reminal to anything we use here in Australia or NZ
and set the correct timezone on the server. Now connect to the server using
rdesktop and you have the timezone on the rdesktop showing some wierd time
zone called "GTB, Sommartid" and it is always 1 hour offset from the time
it should be.
I have found no way to fix that. and changing the time on the machine to a
wrong time zone will not work since the same machines also run the Citrix
client that redirects the time zone correctly, so that would make them
display the wrong time.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-08-25 20:26

Message:
Logged In: NO 

We are having the timezone redirection problems with the rdesktop 1.6.0
To reproduce the problem you need to make a Group Policy with the setting:
Computer Configuration/Administrative Templates/Windows Components/Terminal
Services/Client/Server data redirection = Allow Time Zone Redirection:    
Enabled
Set the timezone on the reminal to anything we use here in Australia or NZ
and set the correct timezone on the server. Now connect to the server using
rdesktop and you have the timezone on the rdesktop showing some wierd time
zone called "GTB, Sommartid" and it is always 1 hour offset from the time
it should be.
I have found no way to fix that. and changing the time on the machine to a
wrong time zone will not work since the same machines also run the Citrix
client that redirects the time zone correctly, so that would make them
display the wrong time.

----------------------------------------------------------------------

Comment By: Ryan G (ryan_great)
Date: 2007-07-05 02:26

Message:
Logged In: YES 
user_id=1836707
Originator: NO

I can't comment for the original author, but we are having similar
problems, except it is now OUTSIDE the DST period and we are still getting
errors.

TZ = Australia/Melbourne
UTC-10

[gre02@ryang-fc6 ~]$ date -u
Thu Jul  5 07:08:34 UTC 2007
[gre02@ryang-fc6 ~]$ date
Thu Jul  5 17:08:52 EST 2007

When I rdesktop to a Windows 2003 server (with all updates, including
recent DST changes), the TZ is set to "(GMT+10:00) Brisbane" AND the time
is put forward an hour.  Changing TZ to "(GMT+10:00) Canberra, Melbourne,
Sydney" results in the correct time, and, to make this truly bizarre,
setting the TZ back to Brisbane results in the correct time as well.

----------------------------------------------------------------------

Comment By: Ilya Konstantinov (ikonst)
Date: 2007-06-06 08:56

Message:
Logged In: YES 
user_id=335423
Originator: NO

>From a look at the code, rdesktop reports its timezone to the server. It
probably doesn't care whether this timezone is result of DST or not.

Windows Server internally counts time in GMT/UTC and your session adds the
timezone offset. When rdesktop connects, it tells the Windows machine its
timezone (e.g. so if you connect from a PC in Japan, you see the real
time). If your Unix timezone is updated with the recent US timezone
changes, you should have no problem.

(Note: This is from a quick skim over the code I did now. Are you having
an actual problem here, or can I mark this issue as solved?)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=1694389&group_id=24366

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar