RN104 Unable to access admin page - Firmware 6.7.3

[mocoyn]

Hi

After install the firmware 6.7.3 I can't access to admin page with the name of the NAS. I can only access with the IP.

Too, I've detected I can't access by FTP after install the firmware.

Any suggestion? Any idea?

Thanks

[Skywalker · Accepted solution]

"nas_home" is not a valid hostname, so you'll probably want to rename it to something like "nas-home".  See https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames.

[JennC]

Hello mocoyn,

Does it still show on the RAIDar the hostname of the NAS? Can you stil also ping the hostname?

Regards,

[mdgm-ntgr]

Also, which web browser are you using?

Are any other services affected e.g. SMB?

[mocoyn]

The hostname appear as my "nas_home" and when I try ping to this hostname, it respond correctly.

Appear the next text:

C:\Users\IBM_ADMIN>ping nas_home

Pinging nas_home [192.168.1.251] with 32 bytes of data
Reply from 192.168.1.251: bytes=32 time=1ms TTL=64
Reply from 192.168.1.251: bytes=32 time=2ms TTL=64
Reply from 192.168.1.251: bytes=32 time=3ms TTL=64
Reply from 192.168.1.251: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.251:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms

[mocoyn]

I use Firefox and Chrome. And the service SMB is affected too 😞

This morning, I updgraded to 6.7.4 but the issue persist. I think the new firmware could solution the issue but not 😞

[StephenB]

Just to clarify:  I am thinking all services are working correctly when you use the IP address, but some are not connecting if you use the host name.

Is that a correct summary?

[mocoyn]

It's correct the resume

Sorry, I push the button as "Accepted solution" by error 😞

[mdgm-ntgr]

You may wish to see Self signed certificate error in Chrome 58

Can you download the logs?

[mocoyn]

Sorry, I don't understand you. What have I do? Can you indicate me step a step?

Thanks

[StephenB]

He wants you to provide logs.  See https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderators

[mocoyn]

Thanks for the explanation.

I've send the logs request now, as indicate the url.

I'll expect answer.

Thanks

[Skywalker · Accepted solution]

"nas_home" is not a valid hostname, so you'll probably want to rename it to something like "nas-home".  See https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_hostnames.

[mocoyn]

I've changed the hostname and I can access now, although my hostname (nas_home) had been working a few years before.. :S

Many thanks

[StephenB]

---

@mocoyn wrote:

I've changed the hostname and I can access now, although my hostname (nas_home) had been working a few years before.. :S

---

I'm not doubting that it worked before, but it is still illegal - it looks like it eventually caught up to you.

[Skywalker]

Going forward, the admin GUI will prevent you from setting a bad hostname.  As OS compontents (in both Windows 10 and ReadyNASOS) continue to get updated over time, it's likely more things will cease to work with invalid hostnames.