NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas NV+ Server 2008
Hey, I know this is and has been a much discussed topic on here but I'm after some clarification as to what the situation is. Basically I have upgraded the one and only domain controller on my net...
Hiya,
I am currently experiencing the same problems here.
We have 4 domain controllers, 2 are onsite with a ReadyNAS 1100 (4.1.7). Since upgrading to a 2008 R2 domain environment and decommisioning the 2003 servers we are no longer able to access the NAS. I believe it is an authentication issue with the NAS and the 2008 R2 AD. I am still able to ping the NAS by IP and hostname, I have tried rejoining it the domain several times & resetting to factory default. The NAS connects to the domain fine, i can see the computer device created in AD however not able to map the shares via hostname or IP. If I change the security mode to Share (workgroup) I am able to see it. We have a ReadyNAS 3200 running 4.2.17 where this does not happen.
I definitely think there is an issue with the 4.1.7 firmware and active directory 2008 R2. We cannot afford to rollback to 2003 though, it is not really a valid solution to the problem. Will set it to workgroup mode for the time being and hope that a firmware fix is released at some point.
Regards,
H.
I am currently experiencing the same problems here.
We have 4 domain controllers, 2 are onsite with a ReadyNAS 1100 (4.1.7). Since upgrading to a 2008 R2 domain environment and decommisioning the 2003 servers we are no longer able to access the NAS. I believe it is an authentication issue with the NAS and the 2008 R2 AD. I am still able to ping the NAS by IP and hostname, I have tried rejoining it the domain several times & resetting to factory default. The NAS connects to the domain fine, i can see the computer device created in AD however not able to map the shares via hostname or IP. If I change the security mode to Share (workgroup) I am able to see it. We have a ReadyNAS 3200 running 4.2.17 where this does not happen.
I definitely think there is an issue with the 4.1.7 firmware and active directory 2008 R2. We cannot afford to rollback to 2003 though, it is not really a valid solution to the problem. Will set it to workgroup mode for the time being and hope that a firmware fix is released at some point.
Regards,
H.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
