NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Domain controller restart requires domain rejoin on NAS Pro
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 ...
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?
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?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
