You ever had trouble to connect to network shares?
Following situation:
You have several network shares mapped and some of them are highlighted with an X mark saying it’s not connected.
When clicking on them you get the following:
\\serverxyz is not accessible. You might not have permission to use this network ressource. Contact the administrator of this server to find out if you have access permissions. This server’s clock is not synchronized with the primary domain controller’s clock.
This was based on the following setup:
Domainserver X had wrong time, but every network share to \\DomainserverX\sharexyz worked surprisingly.
Fileserver X had the correct time, but none of the shares to \\FileserverX\sharexyz worked.
The client I was connecting from was a Windows 7 Client – not even in the domain – with the correct time (as the FileServerX)
So first of all I was simply confused cause, why can i connect to the shares of the Domainserver with the wrong time, while i can’t connect to the one with the correct time.
I tried changing the time from the Domainserver manually (knowing i NTP services usually should work…) but i couldn’t connect to the shares from my FileServerX.
I tried using the IP Adress of the FileServerX to connect to the network share. Surprisingly that worked, so i tried ipconfig /flushdns and even restarted the client where i was trying to connect from.
Nothing worked until i found the really simple solution for all the trouble.
Even if the time between DomainServerX and FileServerX was manually changed to match, i tried the following command on the FileServerX:
Net Time \\DomainServerX.FullDomainName /set
for example:
Net Time \\DomainServerX.Domain.Local /set
A message asked me if i want to overwrite the time of the FileServerX (and by doing that show’d me that i typed the command correctly 😉 ) and i pressed Yes~
And it worked! simple as that, now every network share was accessible again.
What it does is simple aswell, the FileServerX connects to the DomainServerX and overwrites his own time with the time from the DomainServerX so its really even again.
Not even a client reboot was needed, the shares just switched back to work again!
TheRealBarra 