Terminal services and time synch issues.

  • Thread starter Thread starter drkc
  • Start date Start date
D

drkc

Guest
Have a client with SBS 2003 R2 running terminal services and they are using
an XP Home system to connect to it and the time is always one hour behind.

An XP system connnecting to the same Terminal Server connects fine, right
time.

Is this a function of XP Home or something else going on.

Thanks!!
 
More of a time zone issue...

More of a time zone issue...



"drkc" wrote:

> Have a client with SBS 2003 R2 running terminal services and they are using
> an XP Home system to connect to it and the time is always one hour behind.
>
> An XP system connnecting to the same Terminal Server connects fine, right
> time.
>
> Is this a function of XP Home or something else going on.
>
> Thanks!!
 
RE: More of a time zone issue...

RE: More of a time zone issue...

I would assume that the timezone would come from the server. I don't have a
lot of experience with terminal services.

This system also runs a time clock and takes the time from the session
(which is wrong) as the time that the person clocks in. It also doesn't keep
track of what clock people use so of course the local clock is right and the
remote one is wrong and well, people have figured this out and sometimes get
an extra hour of time 'worked'.

Any ideas at all? I know that sometimes a stupid question doesn't get
answered and if this one is a stupid question then someone please tell me...

Thanks...

"drkc" wrote:

>
>
> "drkc" wrote:
>
> > Have a client with SBS 2003 R2 running terminal services and they are using
> > an XP Home system to connect to it and the time is always one hour behind.
> >
> > An XP system connnecting to the same Terminal Server connects fine, right
> > time.
> >
> > Is this a function of XP Home or something else going on.
> >
> > Thanks!!
 
RE: More of a time zone issue...

RE: More of a time zone issue...

There's nothing stupid with your question. But I don't fully
understand your description of the problem, so I'm only going to
give some general remarks.

First: a SBS2003 server cannot be a Terminal Server. It's
impossible, as documented here:
828056 - The Terminal Server component is not available in the
Windows Components Wizard in Windows Small Business Server 2003
http://support.microsoft.com/?kbid=828056

So maybe the clients connect to the SBS2003 server using Remote Web
Workplace? This is a feature which is unique to SBS, has little to
do with TS and is much better asked in the sbs newsgroup.

Or maybe you mean that you have a separate Windows Server 2003 as a
member server in the SBS2003 domain, acting as a Terminal Server?
By default the time zone of the Terminal Server is used in the
client sessions. If you configure time zone redirection, than the
local time zone of the client is used.

Configuring Terminal Server for Differing Time Zones
http://technet2.microsoft.com/windowsserver/en/library//ce300cba-
f39a-48a9-b97f-88a7193f6a4c1033.mspx

Maybe you have a Time Zone redirection GPO in place and the XP Home
client isn't affected by the GPO?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?ZHJrYw==?= <drkc@discussions.microsoft.com> wrote on 03
apr 2008 in microsoft.public.windows.terminal_services:

> I would assume that the timezone would come from the server. I
> don't have a lot of experience with terminal services.
>
> This system also runs a time clock and takes the time from the
> session (which is wrong) as the time that the person clocks in.
> It also doesn't keep track of what clock people use so of course
> the local clock is right and the remote one is wrong and well,
> people have figured this out and sometimes get an extra hour of
> time 'worked'.
>
> Any ideas at all? I know that sometimes a stupid question
> doesn't get answered and if this one is a stupid question then
> someone please tell me...
>
> Thanks...
>
> "drkc" wrote:
>
>>
>>
>> "drkc" wrote:
>>
>> > Have a client with SBS 2003 R2 running terminal services and
>> > they are using an XP Home system to connect to it and the
>> > time is always one hour behind.
>> >
>> > An XP system connnecting to the same Terminal Server connects
>> > fine, right time.
>> >
>> > Is this a function of XP Home or something else going on.
>> >
>> > Thanks!!
 
RE: More of a time zone issue...

RE: More of a time zone issue...

Well, here is the story. They have SBS and Windows server 2003 standard.

I tried using w32tm to point to the sbs on the terminal server and now I
can't log into the terminal server. Something about the time being different
from the computer and network time.

The time was set to the right time and then fell back again. This is the
damnedest thing that I've come across.

I can't get the time to stay correct. I remember having a similar problem
years ago with a windows 2k server and got it to run right. The time is
exactly an hour off. The time zones are set right. This is an interesting
problem...
 
RE: More of a time zone issue...

RE: More of a time zone issue...

OK, so you mean that the sytem time on the TS is incoreect, and the
problem has nothing to do with time redirection in client sessions?

By default, member servers and clients should synchronize their
clocks with the DC. But since the DC is an SBS server, you'd better
post in the sbs newsgroup, I don't know the particulars on how to
make sure that you use the default settings in an SBS domain.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?ZHJrYw==?= <drkc@discussions.microsoft.com> wrote on 04
apr 2008 in microsoft.public.windows.terminal_services:

> Well, here is the story. They have SBS and Windows server 2003
> standard.
>
> I tried using w32tm to point to the sbs on the terminal server
> and now I can't log into the terminal server. Something about
> the time being different from the computer and network time.
>
> The time was set to the right time and then fell back again.
> This is the damnedest thing that I've come across.
>
> I can't get the time to stay correct. I remember having a
> similar problem years ago with a windows 2k server and got it to
> run right. The time is exactly an hour off. The time zones are
> set right. This is an interesting problem...
 
RE: More of a time zone issue...

RE: More of a time zone issue...

I found a document that was about setting an authoritative time server in
Windows and did the SBS server. The terminal server didn't take it up so I
did it to the terminal server too and things were great. The time stayed
until I left.

It was kb816042. I found that the knuckle head that set them up tried to
hack the settings but bungled it pretty bad.

Things work now. The true test is going to be Monday morning to see if a get
a call at 5AM...

"Vera Noest [MVP]" wrote:

> OK, so you mean that the sytem time on the TS is incoreect, and the
> problem has nothing to do with time redirection in client sessions?
>
> By default, member servers and clients should synchronize their
> clocks with the DC. But since the DC is an SBS server, you'd better
> post in the sbs newsgroup, I don't know the particulars on how to
> make sure that you use the default settings in an SBS domain.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?ZHJrYw==?= <drkc@discussions.microsoft.com> wrote on 04
> apr 2008 in microsoft.public.windows.terminal_services:
>
> > Well, here is the story. They have SBS and Windows server 2003
> > standard.
> >
> > I tried using w32tm to point to the sbs on the terminal server
> > and now I can't log into the terminal server. Something about
> > the time being different from the computer and network time.
> >
> > The time was set to the right time and then fell back again.
> > This is the damnedest thing that I've come across.
> >
> > I can't get the time to stay correct. I remember having a
> > similar problem years ago with a windows 2k server and got it to
> > run right. The time is exactly an hour off. The time zones are
> > set right. This is an interesting problem...
>
 
Back
Top