NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

dangreen's avatar
dangreen
Aspirant
Apr 03, 2011

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 network to Server 2008 R2 my Readynas NV+ is running firmware 4.1.7. Since doing so I've lost all functionality of the NV+. I'm using domain authentication which was working fine before the upgrade but now I can't map any drives to the readynas shares. Firstly by IP address which I have read no longer works from a Windows 7 client which is fine so I try by hostname and I can't browse to the share in explorer. I have to map the drive using the local admin account on the nas box. Also I have a dreambox satellite receiver which now also can't mount to the readynas box....I find this more confusing as this itself runs linux and isn't on the domain. however when trying to mount a directory I get "failed input output error."

What are my options here I have fiddled with the NTLMv2 setting to no avail. This box is pretty much useless to me in this current state, can I just add a second DC running Server 2003 to work around all these issues as I haven't as yet raised the domain functional level? Some people seem to have some things working and others don't any suggestions would be greatly appreciated!!

Thanks

Dan.

9 Replies

Replies have been turned off for this discussion
  • I don't understand why browsing via hostname isn't working for you, as the ReadyNAS should have added it's DNS entry on the domain controller.
  • So I'm guessing there's nothing that can be done to resolve this?

    Do the Ultra 4 bay range definately work with Server 2008 domain controllers correctly?
  • The Pro series has domain mode support, the ultra does not.

    Did you verify that the DNS entry was correct like I mentioned?
  • Hey,

    Yeah that was one of the first things I checked...it creates the DNS entry correctly automatically when I join it to the domain.
  • Yeah afraid so mate, at least 6 times! lol cleard the old computer account out of AD and the DNS records and re-added and the same occurs. Succesfully adds to the domain but can't browse to it by hostname. However if I map a drive manually map a drive in Windows 7 to \\nas\os using the local admin credentials for the nas box so username : nas\admin Password : password I can then map a drive. But I can't use any AD accounts that have permissions to that share and I still can't map to it on my linux based satelite receiver...this will only map to an IP address but surely that should work ok?
  • Hey mate,

    Aprreciate the help on this but I've bitten the bullet and bought a Server 2003 DC online and decommisioned the Server 2008 DC. All's pretty much back to how it was before just got a few permission issues to sort on the nas (result of me messing about trying to get it going) so all should be sorted soon. Same it doesn't work with Server 2008 but it is an old device now so understandable!

    Cheers again,

    Dan.
  • 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.
  • NTLMv2 is used in a 2008 domain. This causes a problem with most things Linux.
    I left my domain at 2003 functional level, with the 2008 DCs.
    This involves using the adprep + forest prep utility on other 2k3 DCs first. (from the server 2008 dvd)
    I then set a group policy "send LM & NTLM - use NTLMv2 session security if negotiated" for Win7 workstations to access the NAS shares and other Linux resources.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More