Forum Discussion
Solved
Unable to access ReadyNAS RN202 by hostname following firmware 6.7.1 update
Following the 6.7.1 firmware update I am no longer able to access my RN202 system using its host name (which I changed from the default). When I try, it returns a "Bad Request" page message. Howeve...
Hello LucAce01
Host names are restricted to letters, digits, hyphens, and parentheses. Please see Restrictions on valid hostnames at https://en.wikipedia.org/wiki/Hostname.
Regards,
So http is working fine. Which protocol are you having issues with?
Is this from e.g. a Windows 10 PC?
I should have been more clear. I can access the admin gui when using either http or https if I provide the IP address and when the host name is the default of "ReadyNAS" I can use http or https using the host name. When I change the host name to something other then "ReadyNAS", for example to "readynas_rn202" when I use either http or https using the new hostname I get the Bad Request page. This occurs even after rebooting both the NAS and my PC.
So in summary:
Hostname (default): ReadyNAS
http://readynas/ => Workshttps://readynas/ => Works
http://<IP ADDRESS>/ => Works
https://<IP ADDRESS>/ => Works
Hostname: ReadyNAS_RN202
http://ReadyNAS_RN202/ => Bad Requesthttps://ReadyNAS_RN202/ => Bad Request
http://<IP ADDRESS>/ => Works
https://<IP ADDRESS>/ => Works
Based on further testing, it appears to be assocaited with underscore character that was in the hostname before I updated to firmware 6.7.1. Removing the underscore or using a hypen appears to be a work around.
LucAce01 wrote:
Based on further testing, it appears to be assocaited with underscore character that was in the hostname before I updated to firmware 6.7.1. Removing the underscore or using a hypen appears to be a work around.
Underscores aren't legal characters in hostnames, although most systems don't enforce that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
