I am on 1.63 Firmware and the drive is joined to the domain.
shahidemran (4th February 2013)
shahidemran (5th February 2013)
It is a very strange problem we are seeing, I have referred it back to buffalo support, because I cannot see how its an issue with how we have the network, we use the same build, only have 3 types of PC on site, have everything turned off firewall wise internally on our network, all machines are using the same image, it just plainly works and maps fine for some staff and refuses to for others.
Well guys we manage to resolve this problem by disabling the Security Signature in registry. It was enabled by default when deploying image through MDT. Here is the complete path to the registry key to set the value to 0.
HKEY_LOCAL_MACHINE>System>CurrentControlSet>Servic es>Lanmanserver>Parameters>enablesecuritysignature =0
...another mystery is now history.
rich_tech (1st March 2013)
Is the fxed ip address on the drive set correctly.
Are you using different subnets.
Is there a limited number of connects for your nas drive?
What happens if you do a \\ nasname\sharename?
I had the same problem with QNAP TS-410. I was not able to access with \\172.18.184.42. It is about username and password. I have created a user name similar to a domain username. It works now. Domain authentication does not work. From Windows XP machine it always works. Windows 7 is the problem. It is a known issue. If you logon to a domain machine with a username and password and create an identical username and password in QNAP then it will allow to map network drive. It is about authentication problem. It is more to do with Windows 7. Windows 2003 server also faces no problem. Windows 7 and Windows 2008 Server struggles to map network drive. QNAP says domain authentication works but it does not. So, my finding is, it is an authentication issue.
Last edited by sultan966; 1st March 2013 at 12:09 PM.
ours is now solved, there were four registry entries that we had to set with GPP now and the device is visible properly and maps without issue.
Subnets were always fine with us, the Linkstation was always visible even on machines it refused to map, it could be pinged fine, just point blank refused to map.
Those are the settings for those wondering that have solved it for us.
Last edited by mac_shinobi; 1st March 2013 at 01:35 PM.
I forgot to mention earlier on, that we use this buffalo as small Media drive and share it on our network without using credentials on this particular share for our staff only, which probably has bearing on my replies in the thread, we basically wanted the device to work in exactly the same manner as our previous buffalo linkstation worked (no authentication on the share with it just sharing the directories), what I changed in the registry has worked for our NAS device and we are checking everything for any problems to date, but havent found anything amiss since we made those changes, aside from the buffalo being properly mapped finally to our site.
There are currently 1 users browsing this thread. (0 members and 1 guests)