Windows 8 won't connect to ReadyNAS NV+

Nope, ToggleMasterBroswer didn't work.

I'm very reluctant to install Firefox. Already have Chrome and IE due to some work related applications that require them. Really don't want another browser for a specific task.

Is there any other way to get the certificate installed than the one above?
Could these two things be related?
Any more ideas why I cannot browse the shares?

Certificate resolved. I saw that the issue was issued by "Issued by: avast! Web/Mail Shield Untrusted Root". Took down the web shield and re-installed the certificate and got it issued by the Readynas instead. Now works as it should. As long as I have avast web shield down... I'm not sure I would like to have those shields off all the time so the prio 2 question would be; how can I have Frontview and Avast live together peacefully and in harmony?

Prio 1 question is however to get the browse functionality back so that I can backup my HD. Tried to inactivate Avast totally but that didn't help.


Does the following mean anything? When SyncbackPro was running i got this:
net use * /delete
There are no entries in the list.

net use t: \\192.168.0.193 /user:admin
System error 1219 has occurred.
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When SyncbackPro is not running I get:
net use t: \\192.168.0.193 /user:admin
System error 53 has occurred.
The network path was not found.

swehjo wrote:
Does the following mean anything? When SyncbackPro was running i got this: net use * /delete There are no entries in the list.

It must means that the NET utilities don't have any connection open. It's not a problem.

swehjo wrote:
net use t: \\192.168.0.193 /user:admin System error 1219 has occurred. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

It means that SyncbackPro has a connection open to the NAS - and that is it not using admin as the username.

swehjo wrote:
When SyncbackPro is not running I get: net use t: \\192.168.0.193 /user:admin System error 53 has occurred. The network path was not found.

This shouldn't be happening. Does the NAS respond to ping when this happens?

Syncback is (trying to?) login in with my Readynas userid and pw which is not the same as my win userid and pw.

And yes I can ping and Frontview the Readynas from my Win 8.1 PC. But not browse in file explorer.

I can logon with my Readynas userid and pw with my Samsung Note and ES file explorer.

I think it has logged in, that explains the 1219 error message.

The 53 error is the one that needs fixing.
Did you check that the NAS and the WIN8 system are set to the same workgroup? And that the win8 system has the network set to "private"? Disabling internet security suites/firewalls on the win8 system might also be worth a try.

NAS: WORKGROUP
Win 8.1: WORKGROUP
Private Network
Windows Firewall disable when on Private Network
Disabling Avast, which is the only AV I have in use (Defender disabled), makes me able to view Frontview without the annoying certificate message but doesn't make me able to browse the files.

No, I don't see that Syncback is succeeding either. The backup doesn't work and that is how I noticed this error (I normally don't logon "myself"). If I open and Modify a Syncback Profile there is a Test network connection feature and it also gives me a "The network location cannot be reached. For information about network troubleshooting, see Windows Help". Last successfull backup was 26/1 and sometime mid week I noticed that something was wrong. And here we are....

Problem solved. Googled the error and - as normally - found a bunch of more or less complicated solutions that worked for some and not for others. Checked what they said but skipped to implement them since my experience is that they normally worsen things, especially further problem analysis, and do not go for the root cause. On Microsoft I however learnt a new thing while reading their suggestion concerning a fairly common solution regarding this issue, delete and re-install everything under Network adapters: in Device manager you can "Show hidden devices". And voila, there I found maybe 200 dimmed out entries of one of my adapters. Something is, or has been wrong, with that adapter. Removing all these (took me some time...) and then rebooting the machine got my shares back. Now backing up!

Will keep an eye on this adapter. I assume Win 8.1 managed to handle this error up to a certain point and then it "crashed".

Thanks for sharing the solution.