- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: READYNAS CANNOT JOIN TO DOMAIN
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
READYNAS CANNOT JOIN TO DOMAIN
CANNOT CONNECT TO ACTIVE DIRECTORY SHOW TIME OFFSET BETWEEN THE SYSTEM AND SERVER IS TOO LARGE .BUT TIME IS CORRECT . FIND THE SCREENSHOT FOR DETAILS
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: READYNAS CANNOT JOIN TO DOMAIN
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: READYNAS CANNOT JOIN TO DOMAIN
Already Check our NTP settings and make sure to sync up the time.All are ok .Please tell me how can i resolved the issue
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: READYNAS CANNOT JOIN TO DOMAIN
@ALOKESH wrote:
Already Check our NTP settings and make sure to sync up the time.All are ok .Please tell me how can i resolved the issue
I don't use AD, so I can't help with the main problem. But I am thinking that you might want to configure the NAS to use same NTP server as your domain controller.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: READYNAS CANNOT JOIN TO DOMAIN
Selecting the wrong time zone on one can also cause this problem, I believe.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: READYNAS CANNOT JOIN TO DOMAIN
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), ...
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 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.