Buffalo Linkstation Access
Just installed Win 7 RC two days ago and all is good EXCEPT I cannot see one of my NAS drives. I have two NAS drives both of them are Buffalo LinkStations that are different vintages. I have no issues with newer NAS drive (1 TB) but the older NAS drive is visible in Win7 but not accessable. When I attempt to access it I get an error (not accessable / not authorized). Althought I tried the enableing the Win7 Homegroup feature I do not currently have the new Win7 Homegroup feature enabled as the other computers on my network are Vista and this feature did not seem to help with the access to the problematic NAS drive. The name of my network is HOME and I have configured Win7 (Right click Computer / Properties / Change Settings / Change button - and I selected and set the WORKGROUP name to HOME. Both NAS Drives are members of the HOME group and I have no issues accessing either drive from the Vista machines. Both NAS drives have a static IP and I can ping both NAS drives with no problems. I tried to MAP A NETWORK Drive (Right click Computer / MAP Network Drive and I get the same error "\\BACKUP1 is not accessible. You might not have permission to use this network resource. Contact the administraor of this server to find out if you have access permissions. The account is not authorized to log in from this station" I ran across a thread that mentioned a winsock issue, i reset winsock and rebooted but the problem persisted. I researched this issue that seems to be an issue for several to no advail (http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/e7ed1e4f-fb8c-423f-a842-b45aebd1e30d) What is strange is that my newer (Buffalo) NAS drive has no issue, it is only the older Buffalo 500 GB drive that is visable but not accessable.I upgraded the firmware on the NAS drive tothe latest versionfrom the Buffalo website(V1.61)and I have tried disabling firewall and antivirus and that did not help, I'm running McAfee Beta version (Win7 compatable beta). Thanks in advance for any help with this issue.
July 5th, 2009 4:29pm

But did you "dumb down" windows??It is not windows at fault here, It issamba which needs an update (and has needed a LONG time)You can dumb down (weaken security)windows so it will talk to the NAS boxes / print serversfromthe thread you linked tothread....click the start button and type secpol.msc in the search function to start. Quote----Hi, It should be compatibility issue between the network drives and Windows 7 beta. I suggest that you change the authentication level on in Windows 7 beta. You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\, open Network security: LAN Manager authentication level in the right pane. Change the level to Send LM & NTLM responses. If the issue still occurs, I suggest that you access the device manufacturers websites and try to find firmware upgrade. Arthur Xie - MSFTEnd quoteWe had to this in Vista as well.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2009 7:53pm

Thanks for the response, however I have already tried this to no advail, I'm currently running Windows 7 RC (not beta) and in the RC the Local Sec Policy is found either via (Start -> secpol.msc) or via control panel ->Administrative Tools -> Local Security Policy -> Local Policies -> Security Options --- in the right panel find "Network security: LAN Manager authentication level" double click it and in the pull down I selected "Send LM & NTLM responses" Even with this enabled I still cannot access one of my NAS drives (the older one). Any other ideas?
July 6th, 2009 3:08am

Hi Win7user. I have exactly the same problem. I think it has only appeared in the last couple of weeks as a result of applying a Win7 update. It was working fine! I've altered the local security policy, just like you, to no avail. I'll let you know if I find a solution. But you're not alone!
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2009 12:49am

Try disconnecting all the drives and then adding them back in using the static IP address of the device eg \\192.168.0.20\share_name. Only a workaround but seems ok
July 13th, 2009 1:10am

I see said the blind man..I always use IP so I disconnected and then gave the UNC path it worked fine.I then rebooted and tried UNC path, it failed.I then used the IP address with success and the Name works after that.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2009 5:42pm

Update - I added a "network location"(rightclickCOMPUTER and ADD A NETWORK CONNECTIONusing the (\\192.168.0.20\share_name) method and rebooted. The network resource that a connected then appeared and was accessable after the reboot. However, under NETWORK the drive appears in the list but it is not accessable get error message (\\SHARE is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in from this station.)I can MAP a the drive (via right click on COMPUTER -- MAP NETWORK DRIVE and click the CONNECT USING DIFFERENT CREDITIALS and provide a valid username and password for the drive, the drive is then mapped and magically the drive is also accessable via the NETWORK panel. This has never been an issue with VISTA.
July 14th, 2009 3:45am

I've encountered the exact same problem being unable to connect with my D-Link NAS device after doing a Windows update a couple of weeks ago. As I recall the Windows update had a number of Office 2007 updates in it. Fortunately I'm now able to map to the drive using the IP address/share name. Definitely looks like a nasty little bug to me.
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2009 7:37am

I have the same problem starting today 7-16 after a windows update. with 7 RC
July 16th, 2009 3:47pm

I fixed this. The "Windows Live ID Login Assistant" program needs to be uninstalled. Clearly something in yesterday's update for that broke connectivity for some NAS devices, including my Dlink DNS-323. I'll quote my other thread just so you know exactly everything that I tried prior to stumbling onto the fix, if it helps troubleshoot the update itself: [quote]I have this exact problem as well after some updates yesterday. I have a Dlink DNS-323 on my network. It's share name is \\DNS\ (not a great name, granted, but it works). I've had it on my network for a year now. When I installed Windows 7 I had no problems accessing the device. Yesterday, after 4 updates, it is no longer accessible through my current methods. Links to programs on it (\\DNS\sharename) style links do not work, saying the standard "drive or network connection unavilable" message. Going to start->Run \\DNS\ results in this error: "\\DNS\ is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions. *The account is not authorized to log in from this station.*" (*'s mine for emphasis). Here's where it gets weird: I can get to it by typing the IP address in the run dialog. I can map drives using the IP address. If I enter the IP and name into the lmhosts file it does NOT work. It still behaves exactly as described. I have done the following: Ensured network discovery is on. Set "Send LM & NTLM response if NTLM2 isn't agreed" or whatever. It should work that way. The device no longer appears as a computer on the network, only as a Network storage device, but if I double click it, it only takes me to the box's configuration web interface. The box DOES work fine with other Vista boxes still. I have no logins required for the device. I have used the tool from DLink, it behaves as normal. I have installed the Dlink upnp-x driver, all that did was change the icon to a picture that looked like my device. One detail: I *can* ping the device using the device name, not the IP. That works fine. I'm really, really stumped. I'm 99% sure an update yesterday caused this. Here are the list of updates I did: Security Update for Microsoft Office Publisher 2007 (KB969693)Cumulative Security Update for ActiveX Killbits for Windows 7 Release Candidate for x64-based Systems (KB973346)Windows Live EssentialsUpdate for Microsoft Office Outlook 2007 Junk Email Filter (KB971933)Office Live add-in 1.4 Any help would be appreciated. I've never before seen an issue like this. Update: Removing KB973346 did not help. It's either Live Essentials or an Office Update that caused this.[/quote]
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2009 10:35pm

Thanks Aphex242 I uninstalled Windows Live Login Assistant and all works now. THANKS!
July 19th, 2009 4:37am

This worked for me too, that has been bugging for the last 2 weeks, it affected not only the mappings, but any app like Syncback which tried to access NAS drives. Brilliant! But MS need to fix this methinks.
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2009 11:05pm

THANKSI have 3 computers with WIN 7RC installed and have been struggling with accessing a Maxtor NAS from one of the computers. Uninstalling" Windows Live Login Assistant" solved the problem - I now can access the Maxtor NAS again.
October 9th, 2009 11:40am

I had the same problem. Buffalo has released firmware updates that solve this problem. http://www.buffalo-technology.com/support/downloads/ Worked for me. Good luck!
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2009 2:04am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics