Re: XP Longon and time mismatch with domain controller

From: Vasudev Prabhu (vdp_at_hotmail.com)
Date: 06/01/04


Date: Tue, 1 Jun 2004 06:18:41 -0700

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

>-----Original Message-----
>"Vasudev Prabhu" <vdp@hotmail.com> wrote in message
>news:12d1301c44350$3a5266e0$a301280a@phx.gbl...
>> 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.
>
>--
>Best Regards
>Ron Lowe
>MVP - Windows Networking
>
>
>
>
>
>.
>



Relevant Pages

  • W2003 Active Directory + DNS - Can not join machine
    ... I'm trying to join a client machine to the DC. ... The client is a standalone Windows 2003 machine, ... DNS was successfully queried for the service location resource record ... - Host records that map the name of the domain controller to its IP ...
    (microsoft.public.windows.server.dns)
  • Re: Domain controller not respond
    ... controller with Windows 2003 server and the other is Windows XP client. ... I´ve promoted the Windows 2003 to domain controller. ... I have connected both machines with a cross-over wire and if ping address ... What can I do to enter the XP client machine into domain?. ...
    (microsoft.public.windows.server.general)
  • Re: Client performance problem windows 2003 server...
    ... In addition, if you have the same problem with non-English client, please ... >Subject: Re: Client performance problem windows 2003 server... ... >>>Deploying Active Directory for Branch Office Environments ... >>>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: Client performance problem windows 2003 server...
    ... there and install an english client to be doing the errorsearching on. ... to the Windows 2000 server in site A that is a English ... >>be a DNS replication issue. ... >>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: AD Site Topology
    ... authenticating with a domain controller in a different physical ... to a GC outside of it's physical location resulting in Outlook ... local infrastrcuture i.e. DC's/F&P but not exchange. ... client side is a good point though although I thought MS improved the ...
    (microsoft.public.win2000.active_directory)

Loading