Network shares problem, looks like it's down to time not synchronising!

hi guys,

We're having major problems. At our remote site, people are unable to access the network share to the AD/file server which is local to them. I can't access the network share either across the WAN either. If I RDP to this box, I am able to access its own network share from the run command. So it can see its own shares. But nobody else can see it.

I've checked and it looks like it is related to the time's not synchronising.

We have around 5 domain controllers all Windows 2008 R2 and Windows 2012.

How can I get the time sychronised, so that they can see the correct time and synchronise with one another? Right now, when I run w32tm /query /source it comes back with Local CMOS clock on all of them! Something has been modified and I need it to revert back again.

Thanks for helping guys

Yashy



In DC with FSMO role run from cmd:

w32tm /register /config /manualpeerlist:"external_ntp_server" /syncfromflags:MANUAL

This will register NTP as service and will syncronize domain clock with an ntp external server (time.windows.com, or pool.ntp.org, etc. You can add more servers between quotes separated by space)

On the server which are not DC's, or workstations, from cmd run:
w32tm [/register] /config /syncfromflags:DOMAINHIER

https://technet.microsoft.com/en-us/library/w32tm.aspx

Best regards!



In DC with FSMO role run from cmd:

w32tm /register /config /manualpeerlist:"external_ntp_server" /syncfromflags:MANUAL

This will register NTP as service and will syncronize domain clock with an ntp external server (time.windows.com, or pool.ntp.org, etc. You can add more servers between quotes separated by space)

On the server which are not DC's, or workstations, from cmd run:
w32tm [/register] /config /syncfromflags:DOMAINHIER

https://technet.microsoft.com/en-us/library/w32tm.aspx

Best regards!



Awesome, thanks.

Sorted the problem out.







Share this

Related Posts

There was an error in this gadget