Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JaysFan]

I have an issue where I can't access the Volume_1 Share via UNC

I'm able to use the DLink utility to map a drive to the share and access the data but when I try to access the share through the run box for example: 

\\192.168.x.x\Volume_1  I am prompted for a password, I've tried all the combinations of hostname\username and workgroup\username, I've added an account with the same username and password as my current Win 7 user account but no luck.

I need this type of access because my backup software (Symantec BESR 2010, takes the mapped drive as the destination but translates it to UNC and since I can't find the credentials, it doesn't work.)  I have already reset the device twice and set it up from scratch with the same result.

I'm using WIn 7 Ultimate 32 bit, another computer on the same network is using Win 7 Home 64 bit with same issue, it's not a firewall/networking issue. 

 Anyone have any ideas?

[JaysFan]

I was able out a workaround to my issue with the UNC access via hostname.  My Nas is called home-nas and I was trying to access the Volume_1 share by using \\home-nas\ at the Windows run box, it would then list the shares and prompt for a password when I tried to open any share in Windows Explorer.


If I use the IP address \\192.168.x.x , I can then double click on the share without issue.  This also works in my backup software.    I would however still like to be able to use the host name as it looks cleaner with a mapped drive and in the backup location. 

Anyone have any ideas?

[JaysFan]

Update to the issue, all of a sudden I try to access the share via the NAS and try to access it by host name, it prompts for a password and I input the credentials of a user account with access (without specifying the context i.e hostname\user) and I was able to list all the shares and access the device as I wanted to in the first place. 

I'm not able to determine what caused the issue to fix itself as no real changes were done on my home network other than changing some firewall rules on my router which reset the device (I had tried to reset previously and it didn't work).  And also the firewall rules should not affect internal access.

Anyways, I'm surprised no one even chimed in on the post

[dvdeo]

I have managed to collect more info about the same issue on Windows 8 Release Preview. When you use Storage Utility to map drive it maps drive without any problems. So I looked at the security settings. In security settings you can see following permissions:
1. Unix user\root
2. Unix group\root
So I tried to map drive using "Unix user\root" and used admin password for that - it worked. Then I tried to use "Unix user\<nasusername>" and it worked. It acts like "Unix user" is hardcoded string. I was expecting that I should use: <NASNAME>\<NASUSERNAME>. Now it is little bit stupid.

However I was trying to connect my BD player (DMP-BDT310) to the NAS. First by using DLNA. It worked fine. Then I tried to use "connect to network drive" function with the same credentials in various possible forms. No success. The difference that I can detect is that BD player use IP address - not the hostname.

Actually firmware authors could make life much more easier with support of Windows Homegroup. And try to test compatibility better on various types of home networks.
this link is interesting, though requires patience: http://www.sevenforums.com/network-sharing/3737-samba-network-share-issue-windows-7-a.html#post278259