Re: Thin Client Time Zone not passing to server correctly any more

We do, we're covering 4 different time zones.

So, the clients actually hold the DST start and end?
Wild.
Ok, thanks.

"TP" wrote:

Hi Andrew,

Your thin clients need to be updated with the correct time
zone data. If Time Zone Redirection is enabled on the
server, then the server pulls the time zone offsets, daylight
savings start/end, descriptions, etc. from the client device
(assuming the client device/software supports it).

In other words, the time zone data is redirected from the
client to the server--if this data is incorrect, then the session's
time will be incorrect as well.

Do you have devices connecting from different time zones?
If not, set "Allow Time Zone Redirection" to Disabled via
Group Policy.

Thanks.

-TP

Andrew Bienhaus wrote:
We run some PCs, and tons of ChipPC thin clients.
Windows Server 2003, using RDP.
Very stable, solid, great little thin clients.

They have no internal clock, nor do they need one.
They are simply setup to know their time zone, and whether they wish
to participate in DST.

(you can see the question coming, but bear with me)

DST, as a result, always worked... when the TermServers flipped over
the DST date, the time was always correct.

So, the 2003 Term Servers, all have been patched, and know all about
the new DST.
If I connect from my own PC, or another XP box, time is correct and
fine.

But, if I now connect from a thin client, it's not applying the DST
correctly.

Forgive me for a stupid question, but did Microsoft do something
really stupid here, and change the way a thin client over RDP asks
for a specific time zone when connecting?

ie: if it used to connect, and say "I'd like GMT-5+DST please"
(implying GMT-5 plus invoke DST whenever appropriate).... why did
that have to change?

It smells like, they changed it to "I'd like GMT-5+NewDST".

Anyone have any thoughts, feedback, or ideas?

Yes, I've asked the thinclient manufacturer about it, but no response
yet.

Would appreciate any back-end ideas on what has changed, and whether
my theory is correct... implying that I am going to need a whole new
image for these thin clients... <sigh>

Andrew

.

Relevant Pages

  • Re: Date problem
    ... time zone of the client, ... As far as I am aware, the browser does not notify the server what ... locale they are in, nor, specifically, what timezone. ... Nor is it possible to know if the time zone setting on the ...
    (comp.lang.php)
  • Re: Thin Client Time Zone not passing to server correctly any more w/D
    ... Your thin clients need to be updated with the correct time zone data. ... If Time Zone Redirection is enabled on the server, then the server pulls the time zone offsets, daylight savings start/end, descriptions, etc. from the client device. ... DST, as a result, always worked... ...
    (microsoft.public.windows.terminal_services)
  • Re: XP Longon and time mismatch with domain controller
    ... different from the client. ... wrong time setting compounded with wrong time zone. ... Every time I login from XP client machine to ... >> domain controller machine time changes to 6 hours ahead. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Meeting Requests accross Time-zones(CST-EST) 2 hours apart
    ... time zone or DST setting on the client or server. ... We do believe we have patched all clients, OS, and server applications, ...
    (microsoft.public.exchange.admin)
  • Re: timezone missing for ftp transfers...
    ... >> FTP server have the wrong time when they are saved to ... What is the client that is in use here? ... >local time zone of the server - which means that they are ...
    (microsoft.public.inetserver.iis.ftp)
Loading