READYNAS CANNOT JOIN TO DOMAIN

Question

CANNOT CONNECT TO ACTIVE DIRECTORY SHOW TIME&nbsp;OFFSET BETWEEN THE SYSTEM AND SERVER IS TOO LARGE .BUT TIME IS CORRECT .&nbsp;FIND THE SCREENSHOT FOR DETAILS

DEADDEADBEEF · Answer

The error says what the issue is, the time difference on ReadyNAS vs your domain is too large.. Check your NTP settings and make sure to sync up the time

ALOKESH · Answer

Already Check our&nbsp; NTP settings and make sure to sync up the time.All are ok .Please tell me how can&nbsp; i resolved the issue&nbsp;

StephenB · Answer

ALOKESH&nbsp;wrote:
Already Check our&nbsp; NTP settings and make sure to sync up the time.All are ok .Please tell me how can&nbsp; i resolved the issue&nbsp;

I don't use AD, so I can't help with the main problem.&nbsp; But I am thinking that you might want to configure the NAS to use same NTP server as your domain controller.

Sandshark · Answer

Selecting the wrong time zone on one can also cause this problem, I believe.

schumaku · Answer

The NAS DNS config must only use the AD DNS, the AD account requires the appropriate privileges, the NAS must be able to resolve and ping the domain (like ping netgear.local) and then the server (like ping ad1.netgear.local), ...&nbsp;When I have it right there is a domain_join.log file created by the frontview (Web UI) somewhere in a ReadyNAS log or logs folder - this contains the insight&nbsp;what is going wrong.Note: Have no ReadyNAS on an AD as of writing, so can't check and test the details. Issues are similar on Syno or QNAP btw - all plain standard SAMBA under the hood.

Forum Discussion

READYNAS CANNOT JOIN TO DOMAIN

5 Replies

Related Content

Orbi local domain name?

Region (Regulatory Domain) Came Wrong... How to escalate case?

Anonymous Access To Domain Joined ReadyNAS

ReadyNAS 314 Inaccessible from domain controllers

Local Domain Routing

NETGEAR Academy

ProSupport for Business