On a morning after our DC (MS SBS 2008) reboots due to automatic updates, we arrive at work to find that no-one can access any shares on the NAS. We need to rejoin the domain (this morning we had to enter the wrong password, have it be unsuccessful, then enter the correct domain controller password). We then have to restore the share permissions from a config backup. After that, we are OK until next time our DC reboots.This is a critical issue to us and is bringing into question our use of the NAS, which we only purchased within the last month or so, the issue has already happened twice, and results in significant productivity loss.Assistance please?Thanks, Tim AllenDetails of our NAS:Model: ReadyNAS Pro Business Edition [X-RAID2]Firmware: RAIDiator 4.2.15 Memory: 1024 MB [4-5-5-15 DDR2]IPv4 address: 1: 172.16.1.12IPv4 address: 2: Not ConnectedVolume C: Online, X-RAID2, 2 disks, 70% of 1754 GB used

Please don't post your ReadyNAS's serial number. If you wish to identify your NAS, you can do so by opening a tech support case and posting your case number.

Hi mdgm,Why not? What's it hurt?Anyway, anyone have any input into the actual issue? Would it be better if I open a case with Negear?Thanks,Tim

The main reason would be that if you haven't registered your device, someone could register it using your serial number. You don't want that to happen. Also knowing the serial number poses a security risk in some circumstances.This forum is a community forum visited by fellow users like myself, as well as some NetGear support personnel and the Jedi (i.e. senior members of the business unit at NetGear devoted to the ReadyNAS). Hopefully someone comes along and can answer your question. I'd suggest opening an online support case and posting your case number here. That way either the forum or support will answer your question first.

Makes sense now re the serial number.Additional info to my issue:We arrived at work this morning to find there was no connectivity to the NAS, however this time the circumstances were slightly different to the previous two.1. There was no reboot of the DC overnight this time.2. After re-entering the domain admin password and applying, the NAS still seemed to have the access permissions for each share set (ie which groups in the domain have access) when the domain info had refreshed. (Previously we had to reenter this info for each share.)Additionally:If I look in the event viewer on the domain controller (Windows SBS 2008), every half an hour I see a message like this:DCOM was unable to communicate with the computer nas2.transtech.internal using any of the configured protocols.This happens whether the NAS is working or not. This even happened during at least a week or two or continuous uptime.I did wonder omehow the NAS is only communicating with the domain when I put the password in, then tries every half hour for some period of time, then gives up? Not sure this is right on the money,as why did it give up after 24 hours or so today whereas before has stayed connected for at least a week?Anyway, things are looking a little less clear cut.Anyone able to assist?

Send me your logs, the info is in my signature.

Domain controller restart requires domain rejoin on NAS Pro

17 Replies

Replies have been turned off for this discussion

Grievous
Aspirant
Jan 21, 2011
Because with our current firmware, the NTP server only syncs every 4 hours, if it were to happen to do that while the domain controller is unavailable(unlikely, but possible), it would sync to the next one on the list, and if the domain controller isn't synced the same as the NTP server that the ReadyNAS is synced to and you have a time skew issue, you end up with problems.

The other thing to try would be to install the latest beta.
timallen
Aspirant
Jan 21, 2011
We reliably can reproduce the problem whenever the DC reboots, so the four hours things seems unlikely.

I'm not really keen on running beta in a production environment.

We really need to get this sorted as we're going to pull the pin and move to something else if the NAS can't sustain a domain connection.

Do you have any other ideas?

Tim
Grievous
Aspirant
Jan 21, 2011
Well the beta does include a number of updates, and you'd be bringing a non-working system to a working state with the risk of leaving a non-working system(based on your description) in it's current state, so that's up to you.
TeknoJnky
Hero
Jan 21, 2011
keep in mind though, if you got to 4.2.16 beta you can not go back to any earlier version, due to GPT partition changes
timallen
Aspirant
Jan 21, 2011
Hi Grievous,

Had a look at the list of changes for the latest beta and none of them relate to my issue.

Where do you think I should go from here? Is there any way to get some better support from Netgear - should I raise a support ticket?

I must say I'm really disappointed that such critical functionality is flakey.

Are there people out there who have got domain security (using domain groups for access control) working reliably? Anyone who has Small Business Server as the DC working reliably?

Thanks,
Tim
Grievous
Aspirant
Jan 21, 2011
Well if you don't want to troubleshoot(and I did give an option besides the beta) we can't help you. Off the top of my head one other thing to try would be to make sure none of your backup jobs are running during the DC reboot. The next step beyond that would likely involve giving us remote access to the ReadyNAS so we can see exactly what's going on.
pushpavs
Aspirant
Oct 19, 2011
We had problems with AD permissions on NAS probably due to a similar NTP issue when I used by ReadyNas pro with 6.67 TB of data. It would take for ever to apply permisssions once the NAS connected to the domain. In the mean time users had problems with saving files. After a month, I gave up and bought a Dell NX 3000 NAS box with windows 2008 storage server and it is working great! I use the Netgear for backing up the production Dell NAS now!

Forum Discussion

Domain controller restart requires domain rejoin on NAS Pro

17 Replies

Related Content

PC Restart Required

RAX45 Access Control Not Persistent - Allowed Devices get Blocked upon Router Restart

Nighthawk R7000 keeps restarting

CAX80 Restart loop

RBR750 regular reboot required since firmware update

NETGEAR Academy

ProSupport for Business