Linkstation HD-H250LAN; Firmware version 2.3 Windows 7 When I try to map the Linkstation as a network drive, it asks for a username and password. It appears like Windows 7 puts in a domain or computer name before the user name; i.e. Computername username. Had this issue with XP but it allowed me to log in using different user name. In Windows 7 it allows to login using different credentials but it still appears like it puts in the computer name before the username; Need help mapping the network drive - any suggestions? Solution: Follow this instruction to allow Windows 7 to communicate to the older Buffalo NAS: Step by step follow these instructions,press on Start / Control Panel / System and Security / Administrative Tools / Local Security Policy / Local Policies / Security Options Within Security Options search and change: 'Network security: LAN Manager authentication level' to: 'Send LM & NTLM responses' To login to the Share use the following: Press on Start and fill the search box with IP of your NAS and use the following to login: User name: Host name User name Password: Password Information from. I have finally found the solution to this problem on the social.technet.microsoft.com forum.
There are other users with exactly this same problem when using Windows 7 Home and Home Premium editions, for which the suggested solution above simply doesn't work, since the Home editions don't have the network connectivity tools required to generate Local Security Policy. These tools are ONLY available for the Ultimate, Professional and Business versions. It gets a bit messy with Windows 7 Home editions since you have to manually edit the Registry, using regedit. Before you do this I suggest you set a System Restore Point, in case anything goes seriously wrong (not likely but it's better to be safe than sorry). This can be a bit difficult to find in Windows 7. Click the Start button and select 'Control Center System and Security System'. On the left you will see 'Advanced System Settings'.
You will now have a new window called 'System Properties' with five tabs, one of which is called 'System Protection'. At the bottom you will find an item 'Create a restore point right now for drives that have system protection turned on' and next to it a button labelled, 'Create.' A pop-up window will ask you for a name for this Restore Point, by which you will recognise it if you need it. Do that and click the 'Create' button. A Restore Point will now be created. You're now ready to modify the Registry.
Replacing fan on Linkstation HD-H250LAN. I have a client with a Linkstation HD-H250LAN that stopped working. The diagnosis confirms that the fan has stopped working and I need to replace it. The specs, as sent to me by Buffalo are: 40mm x 10mm 12V fan. The Buffalo LinkStation is a network storage center. This device offers 250GB of network-attached storage via wired or wireless connections. Installation is.
To do this in Windows 7 you have to go to the Start button and click 'All Programs Accessories Command Prompt'. A 'Command Prompt' window will now open and where the cursor is flashing type 'regedit' and hit the 'Enter' button on the keyboard. Windows will ask you if you want to let the program make changes to the computer, to which you reply you do, by clicking 'Yes'.
The Regedit Window will now open. Double click down to HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Lsa in the left-hand pane. When Lsa is finally highlighted, in the right-hand pane you will see a number of keys already created. Look down the list and see if one for LmCompatibilityLevel already exists. It probably won't. It didn't in my case. What you now need to do is create this key.
From the menu bar at the top of the screen click on 'Edit New DWORD (32 bit) value'. Give this new key the name 'LmCompatibilityLevel' and a value of 1. If the key does already exist and has a value other than 1 then you need to click: 'Edit Modify.' Instead, and change the existing value to 1. Click 'File Exit'. You must then Shutdown and restart your machine for the new value to take effect.
The value of 1 is described by Microsoft as meaning: 'Use NTLM 2 session security if negotiated. Clients use LM and NTLM authentication, and use NTLM 2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLM 2 authentication.' This is what you want in order to get your old BuffaloTech NAS device to accept the old network security protocols for logon. Since Buffalo Tech doesn't seem interested in supporting its faithful customers by providing a firmware update to enable these devices to accept the latest network security protocols, this is the only other solution. This works for me and I can now access the NAS drive and all the folders it contains, using my new Windows 7 Home Premium machine.
Hopefully, yours will too. Reference: Reference. Thanks.very.
much, grahamt! That solved the problem for me. I had this problem (Buffalo LinkStation HD-HLAN and Windows 7 Home Premium results in incorrect username / password error upon network connection) for a very long time. I scoured the tech sites several times and even tried some different regedit advice to no avail. You (not the Buffalo tech people) really settled this issue. Thanks again.
A tip for other newbies: When I first selected HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Lsa in the left-hand pane, I saw only one entry ('default') in the right pane, and when I created a new DWORD value, it appeared to work but didn't 'stick,' that is, when I reopened the file with regedit, my change had not been saved. You must.click. on 'Lsa' in the left pane until, as grahamt says, 'When Lsa is finally highlighted, in the right-hand pane you will see a number of keys already created.'
Then do your editing following grahamt's instructions.
I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS. On shutting down recently I have noted several times that Windows is installing updates which is allowed. On restarting I find that all of the internet and other sevices are available including my wifes Vista Laptop; but although I can see Buffalo - Win7 refuses to open it giving me an 0x80070035 code. When this first happened I did a restore and got my system working again - this did not work the second time! What has gone wrong and what am I doing wrong which is more important - My Vista Backups complete reside on the NAS Kaypee. That error is: ERRORBADNETPATH winerror.h # The network path was not found.
Some questions: Where do you see this error? Do you get the same error in Windows Explorer and CMD using NET USE or NET VIEW? If you recently installed windows updates, which ones were they (networking updates happen fairly often for some vendors) - does uninstalling the updates have any affect? Does the same issue occur when you boot in safe mode with networking support? Ned Pyle MSFT - MS Enterprise Platforms Support - Beta Team.
Hi sorry to keep you waiting. I read your message carefully and checked the updates but can find nothing relevant over the period. I shut down totally and re-booted both the Cable modem and router according the specifications - before restarting first the Buffalo and then the two computer stations.
Buffalo apears on both but can only be accessed by the Toshiba of my wife running Vista Home Premium I can see Buffalo in Explorer but as soon as I try to expand I get the Cannot access check file name etc and then of course the error code. Net use initially says no entries in list but Net View Shows my Wifes Computer and My Acer plus an entry for Buffalo a space and then Link Station - so it is apparently there. Do I have to physically tell it to use by command or is there something deeper I am missing? I also note that similarly to when Vista first appeared - connectable recognized stations all appeared in the top panel but older machines did not. Similarly when looking at network view Buffalo is noted under the line but with no information on how to connect or re-connect with the other stations and networks.
I can connect easily with my Wifes Toshiiba - it is only Buffalo and W7beta which seem to be having a problem. Looking forward to your reply laterin the day. Regards Kaypeene.
I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS. Do you know the IP address that is assigned to the Buffalo? If you have manually assigned an IP address use that or check the router table to see what it is passing out. Try using explorer and log into the Buffalo defalt page 192.168.x.xxx with user name = root, password = (blank, no password).
This should bring up the opening page for managing the Buffalo. I just tried this from Win7 to the Buffalo on a Vista network and it sees it right off.
Gib Macs of the Lumber Cartel said: I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS. Do you know the IP address that is assigned to the Buffalo? If you have manually assigned an IP address use that or check the router table to see what it is passing out. Try using explorer and log into the Buffalo defalt page 192.168.x.xxx with user name = root, password = (blank, no password). This should bring up the opening page for managing the Buffalo. I just tried this from Win7 to the Buffalo on a Vista network and it sees it right off.
GibI, too am having this problem with a LanServer NAS drive. I posted about this in another thread with no resolution. You can get to the NAS by typing the path in the address bar but not by clicking on it in the network browser. Below is the message I get: 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. Network error (1208) I don't have any such problems from Vista Ultimate, XP Home, or Kubuntu Linux.
I have a couple of suggestions of a Registry Edit and a Policy Edit change to the network security, neither worked. I assume that means you tried using the path I specified and still had an issue? So are you saying that if you put in a UNC name everything works perfectly and you can access all data without issue, but if you browse your way through the share then you have an issue? BTW, I just noticed that you showed up in this thread with a different symptom and errors and weren't the original poster. You'll need a network trace to figure out your issue. Use NETMON 3.2 or Wireshark to get network captures of this working from another machine and failing from thie machine, match the frames, and post the differences here where things break down. Or share out the working and failing captures somwhere we can get to.
Ned Pyle MSFT - MS Enterprise Platforms Support - Beta Team. Ned Pyle MSFT said: I assume that means you tried using the path I specified and still had an issue? So are you saying that if you put in a UNC name everything works perfectly and you can access all data without issue, but if you browse your way through the share then you have an issue? BTW, I just noticed that you showed up in this thread with a different symptom and errors and weren't the original poster. You'll need a network trace to figure out your issue.
Use NETMON 3.2 or Wireshark to get network captures of this working from another machine and failing from thie machine, match the frames, and post the differences here where things break down. Or share out the working and failing captures somwhere we can get to. Ned Pyle MSFT - MS Enterprise Platforms Support - Beta Team Don't understand what your $nocsc$ is for but it doesn't work when I have it in the path. I don't have any trouble accessing the share when I enter the path in the explorer address bar. The problem is when I click on the servername in the 'Network Browser'.
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 - MSFT. Arthur Xie said: 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 - MSFT Thanks Arthur, The Security Policy change is one of the first things I did. I will check to see if I can find a firmware upgrade for my device. I will post back.
I have just come back to this again after a week back on Vista to do some much needed backups. I have tried everything suggested to get the NAS on line but no deal. All the drivers and firmware are up to date but have no effect. In desperation I went to the top and asked Buffalo what the score was. ANSWER: It's a Beta and we ain't going to support it until it gets released!!
Didn't we seem to get the same reaction when Vista came out with drivers etc being unsupported? Wouldn't it be great if we were all singing from the same hymn sheet? Come on Microsoft - can't you put a rocket up someones butt - Please. I have just come back to this again after a week back on Vista to do some much needed backups. I have tried everything suggested to get the NAS on line but no deal. All the drivers and firmware are up to date but have no effect.
In desperation I went to the top and asked Buffalo what the score was. ANSWER: It's a Beta and we ain't going to support it until it gets released!! Didn't we seem to get the same reaction when Vista came out with drivers etc being unsupported?
Wouldn't it be great if we were all singing from the same hymn sheet? Come on Microsoft - can't you put a rocket up someones butt - Please. Is there still no solution for this problem? I now have installed the Windows 7 RC 32 Bit - and the problem persists:( My extra-problem is, that I have password-protectet smb-shares on my NAS.
I once managed to access it. But I was never able to repeat this. Is there still no solution for this problem?
I now have installed the Windows 7 RC 32 Bit - and the problem persists:( My extra-problem is, that I have password-protectet smb-shares on my NAS. I once managed to access it. But I was never able to repeat this.
Don Hans I just installed the Windows 7 RC1 last night and I am having the same problem.I can not access an older Buffalo LinkStation from the Win7 RC1 system. I can see and access all the other Windows 2000 and XP systems on my home network, but when I click on the LinkStation icon in the Network folder, it wants a user name and password. I use the supposed user name and password I have set up on the LinkStation, but Win7 will never connect. I even set up a new user account with a password on the LinkStation and Win7 will not connect. I won't connect via a command prompt 'net use z: linkstationname sharename' either, it just keeps asking for a user name and password.
This is strange, as I can bring in a 'foreign' XP system, point it at the LinkStation and it will connect with out asking for a user name or password. IIRC, even a Vista system will connect with out asking for a user name or password. So, seems MS has broken basic networking again.managed to make something that USED to be simple.impossible. Is there still no solution for this problem?
I now have installed the Windows 7 RC 32 Bit - and the problem persists:( My extra-problem is, that I have password-protectet smb-shares on my NAS. I once managed to access it. But I was never able to repeat this.
Don Hans I just installed the Windows 7 RC1 last night and I am having the same problem.I can not access an older Buffalo LinkStation from the Win7 RC1 system. I can see and access all the other Windows 2000 and XP systems on my home network, but when I click on the LinkStation icon in the Network folder, it wants a user name and password. I use the supposed user name and password I have set up on the LinkStation, but Win7 will never connect. I even set up a new user account with a password on the LinkStation and Win7 will not connect. I won't connect via a command prompt 'net use z: linkstationname sharename' either, it just keeps asking for a user name and password.
This is strange, as I can bring in a 'foreign' XP system, point it at the LinkStation and it will connect with out asking for a user name or password. IIRC, even a Vista system will connect with out asking for a user name or password. So, seems MS has broken basic networking again.managed to make something that USED to be simple.impossible. I too, had problems with this on the public beta. Could not access the drive in the network browser. Had to type the path in the windows explorer address bar.
But I have a new NAS and it's working perfectly on the RC (no username or password requests). My new NAS is a LaCie HipServ. I have just come back to this again after a week back on Vista to do some much needed backups. I have tried everything suggested to get the NAS on line but no deal.
All the drivers and firmware are up to date but have no effect. In desperation I went to the top and asked Buffalo what the score was.
ANSWER: It's a Beta and we ain't going to support it until it gets released!! Didn't we seem to get the same reaction when Vista came out with drivers etc being unsupported? Wouldn't it be great if we were all singing from the same hymn sheet? Come on Microsoft - can't you put a rocket up someones butt - Please. Is there still no solution for this problem?
I now have installed the Windows 7 RC 32 Bit - and the problem persists:( My extra-problem is, that I have password-protectet smb-shares on my NAS. I once managed to access it. But I was never able to repeat this. Don Hans Hi - sounds familiar I am afraid.
I too am now running the RC because I love W7 for all the good things about it! Microsoft Please take note!
I refuse to go out and buy yet another piece of expensive equipment to overcome what is probably a minor glitch - after all - the other Windows systems operate happily with the Buffalo regardles of what internal OS it is running. There is nothing in the Buffalo instructions to aid in the search either - and my original mails indicate there is unlikely to be anything soon, although the outing on the general public of Win 7 RC should be shaking someones tree! I had hoped that after the correspondence of all of us suffering similar problems there would have been some response - if only a promise of a future solution but it seems as if silence is golden for all the wrong reasons. I am currently backing up my computer in extreme compressed format to my wifes Toshiba over the network (she runs VistaHome) and then copying the files from her machine to the Buffalo server to my storage folders.!! Restore would follow a similar route. This is not what home networks were designed for, folks! Anyone had better luck recently?
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 - MSFT OK, progress! I tried the above suggestion.stumbled around in Administrative Tools, Local Security Policies, Security Options, Lan Manager authentication level, and changed it from whatever it was (didn't make note of it) to 'Send LM & NTLM responses' and applied it. I then double-clicked on my LinkStation in the Network folder in Windows Explorer and when it prompted me for a user name and password, I put in what is the matching pair that should have worked.it didn't. I then used the alternate account login option.and put in the new user name/password pair I set up the other evening, and it connected me to the LinkStation and all the shares on it. So now I can map a drive letter to the main storage area on it.
I will test logging off and then re-connecting and report back shortly. OK, back.upon logging back in, the mapped drive wouldn'.