Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

19451

September 24th, 2009 11:00

Server's clock is not synchronized

Hi,

When we try to connect to the CIFS share from a desktop, we get a pop up box that says:
"\\csapps2 is not accessible. You might not have permission to use this network resource. 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"

Our Windows administrator has verified that the permission's are correct. And I have verified through the Celerra Manager that the date and time is correct and that it is connected to an NTP server.

How can I fix this issue because right now we are unable to mount any shares.

Thanks

Andrew

2 Intern

 • 

20.4K Posts

September 25th, 2009 06:00

you need to figure out what's wrong with NTP but in the mean time you can set date/time manually, IE:

server_date server_2 0904041542

year/month/date/hour/minutes

366 Posts

September 24th, 2009 11:00

Hi,

could you please post the output of the following command ?

[nasadmin@CONTROL_STATION ~]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 2, misses= 0, first poll hit= 1, miss= 0
Last offset: 0 secs, -3672 usecs
Current State: Running, connected, interval=60
Time sync hosts:
0 1 10.1.1.1
0 1 10.1.1.2


Gustavo Barreto.

2 Intern

 • 

20.4K Posts

September 24th, 2009 11:00

can you run server_date ALL ..just to confirm the time/date from cli. Time difference between datamovers and domain controllers should not exceed 5 minutes.

September 25th, 2009 06:00

Hi,

Here are the outputs from the two commands:

[nasadmin@ifcdasd2a nasadmin]$ server_date ALL
server_2 : Fri Sep 25 09:12:55 EDT 2009
server_3 : Fri Sep 25 08:35:37 EDT 2009
[nasadmin@ifcdasd2a nasadmin]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 11734, misses= 3045, first poll hit= 1, miss= 0
Last offset: 0 secs, 197701 usecs
Current State: Running, disconnected, interval=60
Time sync hosts:
0 1 192.168.22.100

It looks to me like there is a problem seeing that the two datamovers are over half an hour out of sync and the "Current State" of the second command shows "disconnected". I unfortunately don't know how to fix either of these issues.

Any ideas?

Thanks

Andrew

September 25th, 2009 11:00

Hi,

Thanks for all the help. Once I modified the time of the two data movers to match each others and our networks, I can now access the share.

Thanks again.

Andrew

1.5K Posts

September 28th, 2009 12:00

It's nice to see that your problem is solved now. But I suspect whether your NTP is working properly. Since you manually adjusted the Time on the data mover and the NTP status shows disconnected - I suspect you may have issues later of again manually adjusting time.

It seems to me that the NTP server IP Address may be an issue - please check the NTP server IP address configuration. If the NAS data movers are using 192.168.1 network for internal IP addressing - it can be a routing issue to connect to the NTP server (IP address in the 192.168.22.100).

My delayed 2 cents :)
Thanks,
Sandip
No Events found!

Top