NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
readynas 314 cant access via network places
hi all, i hope someone can help as ive spent a lot of time trying to figure this out and not getting any success
basically, in windows > network places, i can see the nas (Mysight-cloud) but when you try to open it, its that normal windows error that you may not have permisions etc.....
it use to work well for over half a year, i recentely installed a VPN app so it made it easy to access from elsewhere. that works fine
we can access it via typing in the address or creating a shortcut on desktop ( \\192.168.1.245 ) that works.
i can also map network drive in my computer and that works
to what ive noticed is if i try to access it via \\192.168.1.245 then it works, but under network places it will try to access it via \\mysight-cloud\ and it dont work, network places does find the nas within two seconds of looking so im not sure what gone wrong, i know that network places does go by name rather than ip but i just dont know whats gone wrong
there is a reason why i need access to it via network places rather than the other ways that do work, i work for a chairty that helps people with visual impairments and also staff and volunteers need access to this NAS, as not everyone is computer literate so i need it to be simple to access even for the staff that use screen reading software or magnificaion.
i can provide what ever info you guys may need in helping me with this
thanks
alan
readynas 314 - os 6.5.1
thanks Stephen, i have now bonded the NIC's using ALB, that's working perfectly now, have access to 192.168.1.245 and \\mysight-cloud\.
it did break the vpn, i told the vpn to use bond0 - didn't work, then told it to use eth0, still didn't work, but then told it to use eth1 and It works,
thanks very much for your help, if its still working in a few days then i know i have definitely cracked it
25 Replies
Replies have been turned off for this discussion
Can you try running cmd with
net use * /delete
net use t: \\mysight-cloud\data /user:admin nasadminpassword
and let us know what happens? The first command ends any open network sessions (if it prompts you, let it proceed). The second attempts to map the NAS data volume to drive letter t.
Use the real nas admin password of course.
ive tried this as you suggested as a test, heres the results
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\Nic>net use * /delete
There are no entries in the list.
C:\Users\Nic>net use t: \\mysight-cloud\
System error 53 has occurred.The network path was not found.
C:\Users\Nic>net use t: \\mysight-cloud\ /user:admin password
System error 1244 has occurred.The operation being requested was not performed because the user has not been au
thenticated.
C:\Users\Nic>net use t: \\mysight-cloud\managers\ /user:admin password
System error 59 has occurred.An unexpected network error occurred.
the admin account password is different to whats above, but obviously wouldnt be wise to disclose it, lol,
alanh-mysight wrote:
ive tried this as you suggested as a test, heres the results
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\Nic>net use * /delete
There are no entries in the list.
C:\Users\Nic>net use t: \\mysight-cloud\
System error 53 has occurred.The network path was not found.
C:\Users\Nic>net use t: \\mysight-cloud\ /user:admin password
System error 1244 has occurred.The operation being requested was not performed because the user has not been au
thenticated.
C:\Users\Nic>net use t: \\mysight-cloud\managers\ /user:admin password
System error 59 has occurred.An unexpected network error occurred.
This particular command needs a share as the target, the machine name alone won't work.
You didn't try net use t: \\mysight-cloud\sharename /user:admin password until perhaps the end. Note that the share needs to be a public share, not a home share.
If you never changed the NAS admin password, please try doing that (and use the new password in the command). Perhaps try it with net use t: \\mysight-cloud\data /user:admin password
It is also good to repeat the net use * /delete between attempts.
- Ok thanks for that. I'll try that in the morning when in office. If that was to work,would I have to do it on all 15 pc's to get it to work under network places?
Mapping the drive does work. But as I'm not always in the office we do have staff and volunteers that ain't that clued up so I am hoping to get it working in network places as that seems to work best for the others knowledge of computers.
alanh-mysight wrote:
If that was to work,would I have to do it on all 15 pc's to get it to work under network places?I'm suggesting this as a test.
If it does work, it suggests that you would need to enter NAS credentials into the Windows Credential Manager on all the PCs. This wouldn't need to be NAS admin credentials of course.
- Ok. If adding to the Windows credentials works I'd be only able to do that on half the computers as the rest are hot desking and we don't bother with multiple accounts as all work is saved on cloud with every one having there own log on details so we just have the one account to log onto windows. I have quite a relaxed policy for a admin. I'll let them do what they want and all accounts on all computers have full admin controls. No corporate nonsense here.
I will try all your suggestions tomorrow to see what happens. More things to try and play with the better.
alanh-mysight wrote:
Ok. If adding to the Windows credentials works I'd be only able to do that on half the computers as the rest are hot desking and we don't bother with multiple accounts as all work is saved on cloud with every one having there own log on details so we just have the one account to log onto windows.All PCs can use the same ReadyNAS credentials (they would also share the same "home" folder).
- We have one account that all volunteers use but staff do have there own as they have private stuff in there home folder. Data protection and stuff like that.
I'll let you know how I get on tomorrow with the Suggestions You have provided.
Thanks. - Ok. Thanks Brian. I'll have a look at that. Kinda wish I asked for help sooner. It's been rattling my brain now for 3 weeks. Always to to fix it my self using what other people posted but google wasn't finding much for me.
- Had a look Brian. But I don't think that will help. Not one PC out of the 15 can access it via network places. But as we hotdesk. It is set to not remember username and passwords to the nas anyway.
That other thread tho does describe my problem. I can access it using the IP address but can't via it name.
I'll still try what StephenB has suggested in the morning. And let you know resultsHi alanh-mysight,
My apologies. But at least you found another thread that is similar to your problem. Just let us know the results as soon as you've tried it.
Kind regards,
BrianL
NETGEAR Community Team
restarted pc, no joy this time
did net use t: \\mysight-cloud\data /user:admin ****
error 53 path not found
did net use t: \\mysight-cloud\mysight /user:admin **** like i did earlier that worked but nopeerror 53 again
alanh-mysight wrote:
restarted pc, no joy this time
did net use t: \\mysight-cloud\data /user:admin ****
error 53 path not found
did net use t: \\mysight-cloud\mysight /user:admin **** like i did earlier that worked but nopeerror 53 again
Ok. What happens if you enter
ping mysight-cloud
Do you get a good reply, and is that reply from 192.168.1.245 ?
Also, is the NAS using DHCP or a static IP address?
- Think I might have found the problem. I have it set to static for both cables that are plugged in. So eth0 is 192.168.1.245
Eth1 is 192.168.1.246
Been playing and it seems to be the router being the issue. I think. It is showing both in the list of connected devices. But if I click on the one that's eth0. It says 245 dhcp.
Other one eth1 says 246 static.
So under eth0 on my router it says always use same IP. I tick it and Apply. And then the IP address completely changes to something like 65 not 245 like the nas is static to. So I'm correctly contacting the provider of our router. It's a technicolor router. Not really keen on this router at tho mo.
I'll let you know if I manage to fix it. Or if any one has any info on this with this type of router then feel free to let me know.
alanh-mysight wrote:
Think I might have found the problem. I have it set to static for both cables that are plugged in. So eth0 is 192.168.1.245Start by disconnecting the second cable for now. After you get reliable connectivity we can talk about NIC bonding.
You might need to reboot the router and then reboot the NAS to get the DHCP binding to stick.
think ive fixed it, thanks stephen, i did start with just the one cable to begin with
if only one cable connected, then IP or hostname works so network places does find it, brilll, but breaks VPN connection
the way that seems to work is
eth0 is set to static 192.168.1.245
eth1 is set to dynamic - currently 192.168.1.82
VPN is set to use eth1
all seems to work, router accepts eth0 now being static, bit werid but if both are set to static my router doesnt like it.
i have had a look at the bond settings but if i do it it seems to break the vpn, im using the vpn server app the uses softether.
biggest test, im about to turn it all off, then back on and see if it all can work normal
- Yes that's what I thought was werid too. The package is installed on the NAS. the router doesn't have that facility.
alanh-mysight wrote:
The package is installed on the NAS. the router doesn't have that facility.Is there a reason the VPN can't also use eth0?
Then you could probably bond the NICs (using the ALB method). With 15 local users, you likely would see some performance boost.
thanks Stephen, i have now bonded the NIC's using ALB, that's working perfectly now, have access to 192.168.1.245 and \\mysight-cloud\.
it did break the vpn, i told the vpn to use bond0 - didn't work, then told it to use eth0, still didn't work, but then told it to use eth1 and It works,
thanks very much for your help, if its still working in a few days then i know i have definitely cracked it
- Do like the idea of performance boost.
I did try sending the vpn to eth0 but for some reason it breaks access to 245.
For all I know I might have something setup wrong on the VPN. I'm not sure.
I could try the bond you said. But won't be able to do that till Friday now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
