NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
No DNS Name disappear, only accessible through IP with Windows 10 (2004)
Hi Netgear community,
I am really satisfy with the Netgear customer Service and the amazing qualoty of my old but still reliable NAS.
Now, suddenly I am not able anymore to reach folders per DNS name. I am always oblige to use the IP address.
Environnement:
> home network with 2 px (1x Windows 7 Pro) 1 Windows 10 Pro (2004) 1x router
> no personal settings, everything installed and used as a lamda user. Firewall and AV from Microsoft, standard installation
> no special feature installed on the NAS, just used out od the box.
Because I can still reach from the Windows 7 my NAS through DNS name, I believe Windows 10 made again, and again, and again, some background update which could (must?) be the reason.
I had checked the SMB1V installation and activation and it seems to be reactivated on W10 (2004).
I added the static IP address in the host file, restarted the service and nothing had changed.
1) Does anyone has some idea how I can reactivate the ability of Windows 10 to use again the DNS-NAS-Name?
2) Can I upgrade the software to use a more recent Version of my NAS? If yes, how?
Hoe is still present!
Many thanks in advance and kee healthy,
Daniel
BIOS: 09/08/2010 ReadyNAS-ProUltra2 V1.4
I have put some parts of the logs of the NAS, could probably help a little bit?
[2020/11/05 10:37:21.525260, 0] smbd/process.c:525(init_smb_request)
init_smb_request: invalid wct number 255 (size 248)
[2020/11/05 10:37:21.530810, 0] smbd/process.c:525(init_smb_request)
init_smb_request: invalid wct number 255 (size 248)
[2020/11/05 10:37:21.536127, 0] smbd/process.c:525(init_smb_request)
init_smb_request: invalid wct number 255 (size 248)
[2020/11/05 10:37:21.541603, 0] smbd/process.c:525(init_smb_request)
init_smb_request: invalid wct number 255 (size 248)
[2020/11/05 10:37:21.547265, 0] smbd/process.c:525(init_smb_request)
init_smb_request: invalid wct number 255 (size 248)
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.10 for ServerName
[Thu Oct 22 08:58:02 2020] [warn] RSA server certificate CommonName (CN) `192.168.125.116' does NOT match server name!?
[Thu Oct 22 08:58:02 2020] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
[Fri Oct 23 09:40:54 2020] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Mon Oct 26 20:54:03 2020] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.10 for ServerName
[Mon Oct 26 20:54:07 2020] [warn] RSA server certificate CommonName (CN) `192.168.125.116' does NOT match server name!?
[Mon Oct 26 20:54:08 2020] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
When I tried to change and renew Ip Address on the NAS:
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Withdrawing address record for 192.168.0.10 on eth1.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.10.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Interface eth1.IPv4 no longer relevant for mDNS.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Interface eth1.IPv6 no longer relevant for mDNS.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Leaving mDNS multicast group on interface eth1.IPv6 with address 2a02:21b0:644f:c4e0:a221:b7ff:fec1:1283.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Withdrawing address record for 2a02:21b0:644f:c4e0:a221:b7ff:fec1:1283 on eth1.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.10.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: New relevant interface eth1.IPv4 for mDNS.
Nov 1 15:58:36 nas-C1-12-82 avahi-daemon[3080]: Registering new address record for 192.168.0.10 on eth1.IPv4.
Nov 1 15:58:41 nas-C1-12-82 avahi-daemon[3080]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::a221:b7ff:fec1:1283.
Nov 1 15:58:41 nas-C1-12-82 avahi-daemon[3080]: New relevant interface eth1.IPv6 for mDNS.
Nov 1 15:58:41 nas-C1-12-82 avahi-daemon[3080]: Registering new address record for fe80::a221:b7ff:fec1:1283 on eth1.*.
Nov 1 15:58:42 nas-C1-12-82 ifplugd(eth1)[2627]: SIGUSR2: Daemon resumed (#1)
Nov 1 15:59:26 nas-C1-12-82 avahi-daemon[3080]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::a221:b7ff:fec1:1283.
Nov 1 15:59:26 nas-C1-12-82 avahi-daemon[3080]: Joining mDNS multicast group on interface eth1.IPv6 with address 2a02:21b0:644f:c4e0:a221:b7ff:fec1:1283.
Nov 1 15:59:26 nas-C1-12-82 avahi-daemon[3080]: Registering new address record for 2a02:21b0:644f:c4e0:a221:b7ff:fec1:1283 on eth1.*.
Nov 1 15:59:26 nas-C1-12-82 avahi-daemon[3080]: Withdrawing address record for fe80::a221:b7ff:fec1:1283 on eth1.
RAIDiator 4.2.31
1 Reply
Replies have been turned off for this discussion
Daniel_ReadyNas wrote:
2) Can I upgrade the software to use a more recent Version of my NAS? If yes, how?
You can convert Pro and Ultra models to OS-6 firmware. The process requires a full backup, as the disks need to be reformatted as part of the process.
The steps are:
(Optionally) make sure the latest BIOS is installed before you do the conversion. To do this you install http://www.readynas.com/download/addons/x86/4.2/BIOS_Update_Package_0.5-x86.bin as an add-on and reboot the NAS. Do this after you backup the NAS. This isn't necessary, but if you so want to update the bios it is easiest to do it prior to converion
Basic instructions for the conversion itself are
- BACKUP, BACKUP, BACKUP
- Upload PREPR4TOR6_0.1-x86.bin as an add-on using the ReadyNAS web gui, but do not reboot afterwards (avoids the need to do manual factory resets)
- Upload R4toR6_6.9.5.bin using the ReadyNAS web gui firmware update
- After you upload the addon+firmware and reboot, it will update the firmware and start a factory default.
- Go through the setup process on the converted NAS
- Update the NAS to the current OS 6 (check for updates will work).
- Restore files from the backup.
Netgear won't provide paid support on a converted NAS, so that is one consideration. There is a small risk that the process could fail, and if that were to happen it might not be possible to get the NAS running again.
If you do decide to convert your NAS, then you should also consider increasing the RAM. Shipping OS-6 NAS have at least 2 GB of RAM, your NAS only has 1 GB. It will work, but it would be sensible to match the resources in the currently shipping NAS. The upgrade is inexpensive, and is simple to do.
Daniel_ReadyNas wrote:
I added the static IP address in the host file, restarted the service and nothing had changed.
1) Does anyone has some idea how I can reactivate the ability of Windows 10 to use again the DNS-NAS-Name?
Entering the name and IP address in the Windows 10 host file should have done the trick. Maybe check that you entered correctly, and if it still doesn't work try rebooting the PC. Putting the name in the hosts file bypasses any network lookups, so it's not anything in the NAS settings or your router.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
