NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Windows Domain and Active Directory
255 TopicsDomain Join Issue - Information
I have found some helpful information for people that have issues joining the domain. The points to check when configuring the ReadyNAS to join the domain, and an additional option with logs to see why it is not able to join the domain. Basic configurations should be checked: Routes - Check to see if the server is able to access the ReadyNAS DNS - Configure one of the DNS Settings to the Local domain server NTP - Configure to the NTP to the domain server or same NTP server as the domain Domain settings - Make sure the security mode settings are matching the domain that is being joined There is a log option that you can use when joining an ADS known as the “domain_join.log”. Logs downloaded from Frontview- /Status/Logs/ (top-right) 'Download All Logs' Bottom of this log shows addition information with the following circumstances: When you have a bad username or password: Failed to join domain: failed to lookup DC info for domain 'MY.DOMAIN.LOCAL' over rpc: Logon failure When you have a bad NetBIOS Name: Failed to join domain: Invalid configuration ("workgroup" set to 'YOUR', should be 'MY') and configuration modification was not requested I have noticed that this is not always the name of the server, but can also be the sub-domain name for the server. When you have a bad Domain Name (FQDN): Failed to join domain: failed to find DC for domain MY.DOMAIN.LOCAL2 Example Logs were based on the following (security mode) domain configuration: Domain Type: ADS NetBIOS Name: MY Domain Name (FQDN): MY.DOMAIN.LOCAL Note on the log: I have seen in some scenarios were the domain_join.log not show up, but switching the domain to user mode and back to domain mode helps generate this log.19KViews0likes19Comments
Can’t change permissions – “The parameter is incorrect”
I have three ReadyNAS Pro Business boxes on Windows Server 2003 domain. Just noticed that there are some issues with changing permission on Windows machines. Basically if a user creates a folder and then he or an administrator tries to change some permissions (add additional user, propagate permissions to child objects, allow or disallow inheritance) this fails with error “An error occurred applying security information to: <path/folder> The parameter is incorrect” Or: “Unable to save permissions changes on <foldername> The parameter is incorrect” The same happens for the domain administrator account which was used to add ReadyNAS to a domain. If I try to add additional user this actually works even after the error is displayed, however it doesn’t propagate down and only affects one folder. This definitely used to work so I suspect problem occurred after one of the recent firmware updates. I am currently on 4.2.13, but the same was happened on 4.2.12 (just upgraded hoping this would sort the problem). Also, this seems to affect only newly created folders. With old folders everything works fine. Any ideas how to fix this?16KViews0likes137Comments
RN 2120 Active Directory "Import Error"
I have two office locations, each of which has a ReadyNAS 2120 set up for storing location-based backups as well as serving up home folders for users. Both devices have been live for over a year and connected to our domain. For the sake of this discussion, Location A is where the primary DC (Server 2003) is located and Location B houses the secondary DC (Server 2008). Since Day 1, both NAS devices have pointed to the primary DC at Location A for the Directory Server Address. Time server and DNS settings were pointed to their respective DCs. First-thing Monday morning, employees at Location B were unable to connect to their individual home folders. I reviewed the Accounts > Authentication page and it shows "Import error" under the "Authentication" heading. For the past two days, I have been trying to troubleshoot and resolve this issue, but to no avail. Beyond what I know from working with these in the past, I've done quite a bit of searching online for answers to this problem and have tried all of the suggestions that I found, but nothing has gotten this issue fixed. Here is a list of things that I have tried: - Location A's RN is working fine. So, I mimicked its DNS, time, and authentication settings. - I removed the RN from the domain and then re-added it. It successfully joins the domain, but it fails while importing users and groups (i.e., "Import error") - Instead of using information from the primary DC at Location A (i.e., original settings), I decided to use the secondary DC at Location B. So, DNS, time, and authentication settings all pointed to the secondary DC - Everything in-between the three troubleshooting steps above I also downloaded and reviewed the logs. I specifically focused on the ADS.log file. I believe the lines below are indicative of the problem, but I do not know where to go from here... [16-05-24 11:48:12] 1918 rndb_account.c:963 info: 278 domain user found [16-05-24 11:48:15] 1918 rndb_account.c:989 info: 100/278 users imported so far [16-05-24 11:48:17] 1918 rndb_account.c:989 info: 200/278 users imported so far [16-05-24 11:48:19] 1918 rndb_account.c:1204 info: 278/278 users imported in 9104ms. [16-05-24 11:48:19] 1918 rndb_account.c:2262 error: Error. Fail to insert $home_folder/$user/$group/$group_has_user [16-05-24 11:48:19] 1918 rndb_account.c:2405 error: rndb_ads_account_import() ==> 3 (12360ms) [16-05-24 11:48:19] 1918 rndb_api.c:956 error: rndb_import_nolock() ==> 3 (12362ms) At this point, I'm left scratching my head. I'm not sure what else to try other than backing up the data and doing a factory reset. Before I go that route, though, does anyone have any insight regarding additional troubleshooting steps I can take? I appreciate any and all assistance. Thank you in advance and take care. - Chris13KViews0likes71CommentsActive Directory issues after 6.5 upgrade
So after the the 6.5 update on our ReadyNAS 516 we are experiencing some weird issues with active directory permission to the NAS. Some users can get right on while other users it just keeps prompting for a username and password. When they type in there credentials it just asks them again. While still some other users get an error that says "A device attached to the system is not funtioning". I did an OS reinstall to see if that would help and it didn't.Solved12KViews0likes21CommentsLose LDAP Connection - Active Directory Domain Services
HI! I've just upgraded to FWV 6.7.1 to check if that issue persists - it does. Since a few days we have an event on the server logs from the active directory domain service, that the Readynas loses the LDAP connection every half an hour or so. We've double checked the connection cables - all fine. The nas is joined to the domain as well. I've also left the domain and re joined it again but the issue persists. has anyone experience with this error? Readynas 202 on FWV 6.7.1 On the serverlogs it says: "Internal event: An LDAP client connection was closed because of an error. Client IP: 192.168.1.XXX:46266 Additional Data Error value: 1236 Die Netzwerkverbindung wurde durch das lokale System getrennt. "The connection was closed by the system due to an error.." Internal ID: c060382 Regards, HinzeSolved11KViews0likes4CommentsNetwork error code: 0x80070035
Hi I am unable to upload any files to the NAS since downloading windows 10. Every time I click on the NAS folder in the network it advises that windows can not access my NAS displaying error code 0x080070035 network pathway nopt found. Action taken: A default reset with still the same outcome with the NAS is working in the ready cloud and NAS settings. I feel that it is just a network setting issue and have tried changing file access settings and static IP address to no effect. I hope you can help as I have spent 2 days trying to fix the problem. Cheers10KViews0likes22Comments
Unable to add trusted domain user/groups to CIFS share perms
I joined my ReadyNAS NV+ (RAIDiator 4.1.7 1.00a043) to an Active Direcotry domain "MYDOMAIN". This domain is in trust relationship with another domain "TRDOMAIN". During the join phase, in the Security->Security Mode page, I chekded the box "Display users from trusted domains....". Under "User & Group Accounts" I can now see all users and gorups of both domains. Users and groups of MYDOMAIN are not prefixed by the domain name. Users and groups of the trusted domain are correctly prefixed with TRDOMAIN\ Also then samba command "wbinfo -g" correctly displays all gorups of both domains. When I try to setup share permissions in the web interface (Shares->ShareListing-> CIFS) I enter "TRDOMAIN\mygroup name" in "Read-only gorups". The system accepts it, despite autocompletion is not correctly working, but after I click "apply", the domain name is stripped, and the field just shows "mygorup name". And in /etc/frontview/samba/Shares.conf I can see the wrong domain name: read list = "@MYDOMAIN\mygroup name" write list = "@MYDOMAIN\video","admin","MYDOMAIN\Administrator" valid users = "@MYDOMAIN\mygroup name","@MYDOMAIN\video","admin","MYDOMAIN\Administrator","nobody" there is no TRDOMAIN here !!! :( :( And the share access is not working for members of TRDOMAIN\mygroup name. I can edit Shares.conf, change MYDOMAIN with TRDOMAIN before mygroup name, restart samba and share access works fine. Is it a bug of the web interface ? Any workaround ?8.9KViews0likes10CommentsFAILED with error NT_STATUS_NO_SUCH_USER
Our ReadyNAS 2120 (6.2.2) is joined to AD, and we are getting a bunch of entries in the smbd log that look like this: [2015/04/09 09:25:37.852262, 2] ../source3/auth/auth.c:315(auth_check_ntlm_password) check_ntlm_password: Authentication for user [BMiller] -> [BMiller] FAILED with error NT_STATUS_LOGON_FAILURE [2015/04/09 09:25:37.875888, 2] ../source3/auth/auth.c:315(auth_check_ntlm_password) check_ntlm_password: Authentication for user [BMiller] -> [BMiller] FAILED with error NT_STATUS_NO_SUCH_USER and then a moment later it will succeed, looks something like this: [2015/04/09 09:25:33.010802, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [BMiller] -> [BMiller] -> [TENPLUS\bmiller] succeeded [2015/04/09 09:26:30.264147, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [BMiller] -> [BMiller] -> [TENPLUS\bmiller] succeeded Anyone have some ideas on what is going on?7.9KViews0likes3Comments
Unable to join Win 2008 R2 ADS
Just bought a 4200 NAS box and trying to join it to our Windows Active Directory 2008 R2. Forest and Domain both running in Native mode. I have updated the firmware to RAIDiator-x86 4.2.17. On attempting to join the domain we get the following errors in the logs Thu Jul 14 14:57:21 GMT 2011 Unsuccessful starting CIFS winbind service. Thu Jul 14 14:57:21 GMT 2011 Unsuccessful joining domain IC. Thu Jul 14 14:56:51 GMT 2011 Unsuccessful starting CIFS winbind service. Thu Jul 14 14:56:51 GMT 2011 Unsuccessful joining domain IC. We bought this unit on the basis that it should join to the domain - if it can't or won't then I will be returning it for a full refund! Anyone got any ideas - I've tried setting the name in the general settings to a fully qualified name, etc.7.7KViews0likes2Comments
