• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 636
  • Last Modified:

Vm domaincontroller suddenly totally different time (2010)

Hi,

I noticed I couldn t logon to my win 2008 domain because of time issue.
Now it appears my vm dc is on date february 2010 somewhere. This same issue caused total corruption of dc last time (didn t sync and had to reinstall fully dc).

Now I setted time wright, did reboot and again time is wrong. It worked fine for a long time, now suddenly this issue. Any idea if it woyld be vmware (since phys dc doesn t have problem) or windows somrwhere?

J.
0
janhoedt
Asked:
janhoedt
  • 4
  • 4
  • 2
  • +1
1 Solution
 
Neil RussellTechnical Development LeadCommented:
Is this the ONLY DC? The DC with the PDC emulator FSMO role?

What you do will deoend on the above
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
make sure you are not syncing time using VMware Tools to host.

Sync the VM DC to Physical DC Domain Time.

your physical DC PDC emulator should be syncing with external time source.
0
 
Neil RussellTechnical Development LeadCommented:
Read this very good technot blog about 2008 domain time issues.

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/96278628-03a1-4b3d-90d9-2208a65a1210/

And as hanccocka said, make sure that vmware tools is NOT set to sync time with host.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Darius GhassemCommented:
You should uncheck the time sync with Host on the VM settings. http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/19/time-synchronization-in-hyper-v.aspx

Go through this page as well so, you can understand time in a domain.

http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/
0
 
janhoedtAuthor Commented:
I've set the physical domain controller to correct time, but now it shows:

E:\Users\administrator.domain>w32tm /monitor
DC02.domain.local[10.158.1.80:123]:
    ICMP: error IP_REQ_TIMED_OUT - no response in 1000ms
    NTP: error ERROR_TIMEOUT - no response from server in 1000ms
physdc.domain.local *** PDC ***[10.158.1.65:123]:
    ICMP: 1ms delay
    NTP: +0.0000000s offset from physdc.domain.local
        RefID: 'LOCL' [0x4C434F4C]
        Stratum: 1

I've shutdown the dc02, want to bring it up but should I point it to external source also or internal source + should I set policy for domain sync or not (best practises)?
0
 
Darius GhassemCommented:
Your DC that holds the PDC emulator role should be time source for your domian.

Why do you have DC2 down?
0
 
Darius GhassemCommented:
wrong post
0
 
janhoedtAuthor Commented:
Everything was ok, after reboot vm time is back to ... april 2010. No timesync of vmware tools.
0
 
janhoedtAuthor Commented:
FOUND THE PROBLEM!
Although vmware tools is not syncing to time of ESX, at bootup it looks to clock of ESX, this was set to 2010. Have set ESX-es to sync also to time of domain.
Strange since domain time should sync, not ESX (since not defined in vmware tools).
0
 
janhoedtAuthor Commented:
Solved it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 4
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now