- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
RND4000 WIn 10 Unexpected Network error
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ReadyNas NV+ RND4000
Windows 10 Home ver 1511
I recently went through a windows update and have lost the ability to see my RND4000
When I map the drive, it sees it but upon clicking the icon to navigate to the share, I get "Y:\ is not accessible. An unexpected Network error has occurred."
When I click Network, under Storage, the icon for the RND4000 is there.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andy_Larkins,
It seems like that's our best hope of resolving this problem. Clearly, not a problem with your ReadyNAS.
Keep this thread updated on what happens.
Kind regards,
BrianL
NETGEAR Community Team
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Hi Andy_Larkins,
Welcome to the community!
Press the LCD screen to see the current IP address of your ReadyNAS. If it has an IP address that's within the range of your network, first check if you can access the admin page then try to access your files via Windows Explorer (\\NAS-IP Address). Here's an article that'll surely help.
Kind regards,
BrianL
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
First up, thank you for taking some time to help.
The IP I have is correct. I can reach the device and interact with it with web browser no problem.
When I try with Explorer, I get a
\\192.168.1.2 is not accessible. You might not have permission to use this network resourse. Contact the administrator of this server to find out if you have access permissions.
The remote procedure call fails and did not execute.
Im running Raidiator 4.1.14 on the device so my menu doesnt match the suggested things to check in the article you referenced.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Hi Andy_Larkins,
Thanks for the fast response. Are you running domain in your network? If not, check the security mode running on your ReadyNAS and make sure it is set to "User-mode". Once this is done, manually set the permissions of your shares by following this article.
Let me know if you have other questions.
Kind regards,
BrianL
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
I am not using a domain.
Following instructions, I set a user up called larks
I then used those credentials setting a mapped drive up. The error I now get is:
The network folder specified is currently mapped using a different user name and password. To connect using a different user name and passwod, first disconnect any existing mappings to this network share.
I dont see any other mappings listed
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Hi Andy_Larkins,
Set the same permission settings on the share/s as seen on these screenshots.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
ok, now Windows is prompting me to select a certificate. There are 3 shown. No matter which I choose, I am prompted for a user name and pw. The next error is "this account is not authorized to login from this station
For what it's worth, from my samsung note 5 cell phone on wifi, I can see the share and play music of videos so Im starting to wonder if the issue is my Windows 10 network settings are jacked up
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Hi Andy_Larkins,
In PC, you need to use Windows Explorer to access your files. If the permission is set to read/write with anonymous /or guest access, it shouldn't ask for a username and password. Perhaps test it with another PC or execute this command in CMD and see if it helps.
net use * /delete
Kind regards,
BrianL
NETGEAR Community Team
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
A little leary of running that command as I have 2 mapped drives at work I dont want to lose. I did just type in net use and it showed my 2 work drives and nothing else.
in Explorer I should be typing \\192.168.1.2\media correct?
After following your instructions, I am getting prompted for a UN and password and I have tried every combo I can think of.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
I was also recently upgraded to win10 1511, and I am still able to access shares on my NV+.
You might confirm that the PC and the NAS are in the same windows workgroup. If you are using the PIN log on, then log on again with your password, and see if that makes a difference.
@Andy_Larkins wrote:
A little leary of running that command as I have 2 mapped drives at work I dont want to lose. I did just type in net use and it showed my 2 work drives and nothing else.
You could alternatively reboot the PC.
@Andy_Larkins wrote:
in Explorer I should be typing \\192.168.1.2\media correct?
After following your instructions, I am getting prompted for a UN and password and I have tried every combo I can think of.
Perhaps after the reboot, try running cmd and typing
net use t: \\192.168.1.2\media /user:larks larkspassword
That will attempt to mount the media share to drive letter t:
If that fails, then try using
net use t: \\192.168.1.2\media /user:admin nasadminpassword
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Are you in Share mode? If so, I recommend switching to user mode.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Ive tried both.
Once in user mode, so I create a user that matches the login to my laptop?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
There's many solutions -- for instance, in User mode, you can leave on anonymous access and not require any users.
If you want more security, you could lock down the share more with user credentials. Whether they're the same as your computer is not really important, but Windows always sends your Windows credentials over the network to auth you into network shares.
When you switch to user mode, redo the share permissions with the nobody user and the nogroup group, and double check your access to the share.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Feels close...
The error is
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 resources and try again
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Close all explorer windows and then use the net use commands to delete all connections from command prompt
net use /delete *
Then re-establish the connection.
You can't auth as one user then auth as another user on the same connection.
The only way you can do this is trick Windows by using IP address for one connection and DNS resolution for another.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
I prefer not to remove 2 mapped drives as I use them for work. but I was able to type /delete \\192.168.1.2\IPC$ and it returned that was deleted successfully. I then tried the net use t: \\192.168.1.2\media /user etc etc....tried both larks and admin and bother gave me this error:
System error 58 has occurred
The specified server cannont perform the requested operation
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
That's fine.
@Andy_Larkins wrote:
I prefer not to remove 2 mapped drives as I use them for work.
Can you post the last few lines of smbd.log?
@Andy_Larkins wrote:System error 58 has occurred
The specified server cannot perform the requested operation
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Im a little foggy on where that log file is.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
I don't have a RAIDiator box near me but if you use the UI to download the set of logs, then it should be there. It would either be called smbd or samba or smb.log. Maybe even something with "cifs"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
[2016/02/01 13:08:40, 0] smbd/server.c:1143(main)
smbd version 3.5.22 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2016/02/01 13:26:16.532809, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:26:16.625555, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:26:16.625895, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:26:17.281687, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:26:17.347839, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:26:17.348180, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:32:32.223651, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [admin] -> [admin] -> [admin] succeeded
[2016/02/01 13:32:32.291006, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:32:32.291326, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:32:32.711346, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [admin] -> [admin] -> [admin] succeeded
[2016/02/01 13:32:32.773390, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:32:32.773711, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:35:10.053070, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:35:10.104092, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:35:10.104413, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:35:10.491968, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:35:10.558781, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:35:10.559102, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:35:28.723611, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:35:28.779182, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:35:28.779503, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
[2016/02/01 13:35:29.182088, 2] auth/auth.c:304(check_ntlm_password)
check_ntlm_password: authentication for user [larks] -> [larks] -> [larks] succeeded
[2016/02/01 13:35:29.250685, 0] lib/util_sock.c:474(read_fd_with_timeout)
[2016/02/01 13:35:29.251006, 0] lib/util_sock.c:1441(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Do you have Jumbo Frames (mtu 9000) configured on the NIC?
Is this problem only happening with Windows 10? Do you have another Windows PC to try connection to?
If it is the Windows 10 with the problem, it might require some registry changes...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Would that be on the NIC on the Win 10 machine or on the NAS (or both)
I dont have a non W10 machine anymore to check it other than I can get to the NAS no problem from my Note 5 Cell phone
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Jumbo frames on the W10 machine are currently disabled.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RND4000 WIn 10 Unexpected Network error
Hi Andy_Larkins,
Could you post some screenshots of these certificates that your PC shows when trying to access your shares? Also, I would like you to try to create a new share in your ReadyNAS with guest (read-write) access and see if the same behavior shows.
Looking forward to your response.
Kind regards,
BrianL
NETGEAR Community Team