NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Pro system RNDP6000 , acessing AdminGUI fails from a Windows 10 client.
Hi,
I own a ReadyNAS Pro system RNDP6000 (running RAIDiator V4.2.31), equipped with three WesternDigital NAS disks.
Since begin this year I am unable to use the WebAdmin GUI on the NAS from my Windows10 PC (running Version1803 (OS Build 17134.285).
I am able from Win10 to access the HomePage, log myself in, but then ~15% of the menu items in the left column give good result. The rest shows nothing or give an error message. So the GUI is practically unusable like this. All shares defined earlier on the NAS are perfectly accessible from the same Windows10 sysytem!
I read several articles telling me to re-enable SMBv1 protocol on Win10 and I did.
Currently SMBv1 & SMBv2 are enabled on my Windows10 system. I also read some article telling Netbios over TCP/IP should be enabled?
Finally I did ran the connection and content test from my good old Compaq Evo Portable still running WindowsXP Pro SP3. From there the Admin GUI is 100% usable. So the problem does not rely on the NAS, but on the client system accessing the Admin GUI.
Any thoughts on how correctly/fully enable SMB1, NETBIOS over TCP/IP, other things?
I would rather stick to SMBv2 on Win10 as Microsoft abandoned SMBv1. Had any of you success on how using the Admin GUI fully over SMBv2?
Many, many thanks,
Erik.
steukers001 wrote:
I guess a similar problem is the certificcating when trying to logon to 192.168.0.14/admin .
The Chrome browser then signals "The protection certificate of the server is not being trusted by the OS of your system"
This is a different problem. The NAS uses self-signed certificates. That's enough to get an encrypted connection, but (by definition) the PC has to trust that the NAS is the device it claims to be. A certificate issued by a certificate authority like verisign can be verified, but the self-signed certicate can't be.
Unfortunately many fake web sites use self-signed certificates, so the browser folks have had to respond by adding these warnings.
The simplest work-around is to click-through them when you are accessing the NAS. But if you ever see these warnings when you are connecting somewhere else (for instance your bank's web pages) then you shouldn't do that. Also, it's best to go directly to those websites in your browser, and not click on links in emails (which may be malicious).
12 Replies
Replies have been turned off for this discussion
SMB v1 is needed to access the NAS with file explorer. It's not used when you are accessing the web ui through a browser.
What browser are you using?
steukers001 wrote:
I would rather stick to SMBv2 on Win10 as Microsoft abandoned SMBv1.
Again, this is aboult file explorer.
There is experimental support for SMBv2 in the NAS, but it requires SSH to enable it. It's also very old, and might have it's own security or performance issues. Though some have gone that route, I don't recommend it myself.
You can use NFS instead of SMB. Look for an NFS client in the "turn windows features on or off".
It is also possible to convert your NAS to run OS 6. That is not supported by Netgear, and the process is destructive (requiring a factory default and reformatting the drives). But it gives you SMB v3 support that is up to date.
Though if you are running XP, you are stuck witn SMB v1 anyway, since that's all that XP supports. So you might as well enable SMB v1in Windows 10.
Dear Stahan,
Thanks for your answer.
>>> Browser usage
On the Win10 platform I did try two browsers, latest version Google Chrome and Mozilla Firefox. (Google Chrome did work fine before)
On the WinXP platform I did use an old version of Mozilla Firefox.
>>>SMB v1 is needed to access the NAS with file explorer.
I guess SMB v1 works, since I can browse the fies and usem them from the NAS.
As said, I have enabled SMB v1 and SMB v2 on the Win10platform, but dont arrive to have a full functioning WebAdmin .
Erik.
I don't see this with Chrome and Mozilla on my Win10 systems. I just click through the security exception and get to Frontview.
Try clearing the browser cache, and see if that helps. Also, if you are using the https://nas-name/admin in the browser address bar, then try https://nas-ip-address/admin
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
