Reply

Re: RR3312 6.10 hotfix 2 cannot be accessed by hostname

chriscpr
Initiate

RR3312 6.10 hotfix 2 cannot be accessed by hostname

Upgrade to 6.10 hotfix 2 happened last night and as of this morning when users got in, all of their mapped drives, which are mapped by group policy, are inaccessible. Giving an error that the connection has not been restored.
The shares are accessible from the IP, but not the hostname in file explorer. NSlookup is correct and it responds to ping by hostname.
Workstation DNS has been flushed and confirmed looking to the right place, machines even rebooted.
Obviously this hasnt been an issue until the update.
Any work arounds apart from changing the entire domain to start looking at the IP address?

Message 1 of 4
chriscpr
Initiate

Re: RR3312 6.10 hotfix 2 cannot be accessed by hostname

Alternatively, is there a way to roll back to 6.9.5 hotfix 1, the last known good firmware image?

Message 2 of 4
StephenB
Guru

Re: RR3312 6.10 hotfix 2 cannot be accessed by hostname


@chriscpr wrote:

Alternatively, is there a way to roll back to 6.9.5 hotfix 1, the last known good firmware image?


Netgear says not to, so there would be some risk.

Message 3 of 4
Sandshark
Sensei

Re: RR3312 6.10 hotfix 2 cannot be accessed by hostname

You are experiencing what is an all-too-common problem.  And chances are it was the re-boot of the NAS that accompanied the OS update, not the new OS version itself, that did it.

 

I also suffer from the problem (and have since well before 6.10.0, to which I have not even updated) and have yet to find a real solution.  There are two work-arounds:  add the NAS name to the computers' HOSTS files or change the drive mapping to use the IP address instead of the name.  Both of those, of course, require a non-changing NAS IP address, which it is best to do via IP reservation in your router or other DHCP device than fixed IP in the NAS.

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 511 views
  • 1 kudo
  • 3 in conversation
Announcements