XP Longon and time mismatch with domain controller

[Vasudev Prabhu]

I have XP professional client machines with SP1 working
with Win2k Active directory domain controller based
network. Every time I login from XP client machine to
domain controller machine time changes to 6 hours ahead.
If I forcefully change the time on client machine to match
with the either domain controller time or with local time
it refuses to logon next time. Throws error message,
as "Machine time is different from the network time
Contact network administrator". After some time machine
sets 6 to 8 hour ahead time and logon will be successful.

Please help me resolve the issue.

Following are tried already:

1. BIOS time is set to local time.
2. Machine time set to both local time which is equal
to domain controller time.
3. as machines are from Dell time related patch is
applied. (http://euro.support.dell.com time.exe file)
4. latest patch on XP is run.

Regards,

Vasudev Prabhu

 

[Ron Lowe]

I have XP professional client machines with SP1 working
with Win2k Active directory domain controller based
network. Every time I login from XP client machine to
domain controller machine time changes to 6 hours ahead.
If I forcefully change the time on client machine to match
with the either domain controller time or with local time
it refuses to logon next time. Throws error message,
as "Machine time is different from the network time
Contact network administrator". After some time machine
sets 6 to 8 hour ahead time and logon will be successful.

Please help me resolve the issue.

Following are tried already:

1. BIOS time is set to local time.
2. Machine time set to both local time which is equal
to domain controller time.
3. as machines are from Dell time related patch is
applied. (http://euro.support.dell.com time.exe file)
4. latest patch on XP is run.

Regards,

Vasudev Prabhu

Sounds like time sync is working properly, but the client
and domain controller are set to different time zones
hence the apparent 6 hour offset.

Set the time zone on both client and domain controller
to be correct for your geographical region.

 

[Vasudev Prabhu]

Hi Ron,

Thanks for the reply. As you said my domain time zone was
different from the client. But the issue here was with
wrong time setting compounded with wrong time zone.
Since domain was showing correct local time I didn't
notice the time zone. Now the problem is resolved.

Thanks and Regards,

Vasudev Prabhu