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

Forum Discussion

dtarin's avatar
dtarin
Luminary
Dec 15, 2013

AFS and CIFS access not working but ReadyNAS remote works

I'm puzzled.

I have a readynas nvx running firmware 4.2.25.

CIFS and AFS have been working flawlessly for years for me and all of a sudden this morning none of my OSX or PC machines could access the server anymore. I thought something ominous had happened but I'm able to log in to the admin console over http and the health check is all good. There are no errors in the logs. None of my machines can connect though.

Curiously I tried ReadyNas remote from an OSX machine not on the local network and it works! I can access all the shares.

I'm not sure how to proceed. Any advice on what I can check?

6 Replies

Replies have been turned off for this discussion
  • I did upgrade to 4.2.25 a couple of days ago. Maybe it has a bug?

    I'm considering rolling it back to what I had before. Is rolling back to an earlier firmware as easy as finding an older firmware file and loading it up?
  • Okay so I reverted to 4.2.22 and some of my OSX clients can access the shares now. (haven't checked all of them yet).

    None of my windows machines can access the server yet though. Seems like some sort of NetBIOS issue?? No idea how to debug this sort of thing..
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    What happens if you open windows explorer, and enter \\NASIP\sharename (where NASIP is the IP address of the NAS, and sharename is a shared folder).
  • Not at the computer at the moment but I did try using both host name and ip and I received an error along the lines of "can not access network path". I'm able to access FrontView just fine.

    I also tried accessing the C share using \\NASIP\C and got the same error.

    For kicks I decided to try and telnet to the smb port on the ReadyNAS to test if the port was open and receiving connections and I was able to connect. I don't recall the port number I tried (I think it was 445?)
  • Windows 7 machines primarily. The issue is now gone and it was a Windows 7 specific problem. I unmapped all network drives. I then went in to the networking section and reinstalled the network driver. I remapped the network drives and then I was able to access the drives again. Not sure exactly what was wrong but the network driver reinstalled fixed it. ReadyNas back to running latest version.

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