I am trying to upgrade the firmware for my Linkstaztion EZ LSLGL 534
I downoaded the new firmware( version 2.01) but when I try to install it I get a message; "buffalo linkstation updater has stopped working" Windows Vista says that the program has encountered a problem .
Anyone know how to fix this?
If you mean it can't find you drive anymore, Same here. I've tried it from 2xp machines and a windows 2008 server.
I have figured this one out. The problem with the ini file. just delete or rename the lsupdater.ini , depending on you folder settings it may just say lsupdater with type configuration file.
TheDealMan
check out this how to
http://forums.buffalotech.com/buffalo/board/message?board.id=0101&message.id=277&query.id=43783#M277
Have you selected any of the options in the program bar?
right click on the program bar and choose the debug mode.
also make sure all your firewall and antivirus software is disabled.
I 'm not sure what you mean by changes, just delete it. ( or rename it.) post if it work for you.
I too am having this problem trying to update to 1.02 on a new 1TB Linkstation Live.
As soon as I run the LSupdater.exe, I get the windows message "BUFFALO linkstation updater has stopped working".
I've tried editing the .ini file for a force update but it doesn't even get that far to bring up the taskbar icon.
Compatability mode does not work either!
I am running Vista Home premium (SP1).
I dont know if its related but i also occasionally get the windows message "COM Surrogate has stopped working" ever since i've had the unit on the network.:smileymad:
Unfortunately this didn't work either. Exactly the same thing happened as before.
I tried with the NIC and drive both on a 192.168.11.xxx subnet and 192.168.0.xxx subnet.
It seems to me that its a software issue, maybe with Vista, as the error is produced instantly after running the LSUpdater?
I managed to get the Updater to start on an XP SP2 machine using direct connection and got to the stage of passing and writing the firmware, but it bailed after it said it couldnt get a response from the unit after writing.....
I am going to try a Gigabit connection next as this was only 100MBit/sec.
Any ideas? I dont want to be stuc with FW1.01 forever as i'm waiting for a fix so i'm able to write to my BitTorrent folder properly too!
Unfortunately this didn't work either. Exactly the same thing happened as before. I tried with the NIC and drive both on a 192.168.11.xxx subnet and 192.168.0.xxx subnet. It seems to me that its a software issue, maybe with Vista, as the error is produced instantly after running the LSUpdater? I managed to get the Updater to start on an XP SP2 machine using direct connection and got to the stage of passing and writing the firmware, but it bailed after it said it couldnt get a response from the unit after writing..... I am going to try a Gigabit connection next as this was only 100MBit/sec. Any ideas? I dont want to be stuc with FW1.01 forever as i'm waiting for a fix so i'm able to write to my BitTorrent folder properly too!Make sure there both on the same subnet, and you can boot the unit into EM mode, (with the unit off, hold down the rest button and power up the unit). Then with all of your anti virus and firewall software disabled run the firmware force.
for vista follow the steps below.
Causes: Vista defaults to only send the more secure NTLMv2 protocol, which these NAS devices / Samba do not support.
Fixes: Go to Start -> Run -> "secpol.msc". Then goto Local Policies -> Security Options. Find "Network Security: LANManager authentication level". Change the setting from "Send NTLMv2response only" to "Send LM & NTLM - use NTLMv2 session security ifnegotiated". Save the setting and then reboot the computer.
Note: Buffalo has a download that does the same thing,but it involves messing with the registry by incorporating a ".reg"file. It is much better (and probably easier) to just use the abovesteps.
New Note: Seems some copies of Vista do not have"secpol.msc", probably the Home versions(Home Basic and Home Premium).These users will either need to use the download from Buffalo or go into their Registry editor.
Causes: Possibly due to cached passwords or different password/name resolution in Vista.
Fixes: Try connecting to "\\IPAddress" instead of"\\NASName". Also, try using "WorkgroupName\UserName","\\NASName\UserName", or "\\NASIPAddress\UserName".
Fixes: Try going into the command prompt and entering(without quotes) "NET USE \\[IP or NetBIOS name of NAS]\[folder that isbeing restricted] /d" and then try logging into the share again.
Causes: Some versions of Memeo do not work correctly in Vista.
Fixes: Have the customer download the following versionNotice .info domain: http://www.memeo.info/download/memeo/BT/Memeo.exe
Causes: Client for Microsoft Networks is installed but is not configured by default.
Fixes: Go to Control Panel->Network andInternet->Network and Sharing Center. Once Network and SharingCenter opens click on the 'Manage Network Connections' in the left handside of the 'Network and Sharing Center' window. Right-click on theadapter being used and choose Properties. Go to the Properties ofClient for Microsoft Networks and set the Name Service Provider toWindows Locator. It defaults to nothing in Vista, meaning no local nameresolution...
Has some one proven solution to this?
I have the same issue with LSUpdater shutting down immediately after clicking the icon with an error "LS Updater has stopped working". It doesn't even get to opening a new screen or anything.
I am running Vista Home. I have tried connection via WLAN as well as direct connection to PC. If I do direct connection I can see the Linkstation. As far as I am concerned I have disabled firewall, antivirus, windows defender, user account control. I have extracted files, tried Win2000 compatibility change as well as registry change LMcompatibility. Changing ini files doesn't help, since I do not get far enough for this to matter.
Any other ideas? It seems to be Vista Home specific.
I have just done the update successfully through another Win2K machine. No issues at all. Looks like Vista compatability issue.
Hi,
I had this problem
First i ve done the the "secpol.msc" stuff that Paul is telling , to low the security of authentication.
I figured out that when disabling wifi , and connect with ethernet cable - it worked ok with Vista -
I wonder whether it's linked to WEP or WPA authentication stuff from the wifi but as long as wifi is enabled i had the same message.
So .. if u're using wifi .. u know what to do.
I was having the same issue with the lsupdater.exe not running correctly in Vista Home Premium.
I tried running it in Compatibility Mode (XP S2) with no success.
I tried a direct Lan connection (disabled wifi, and connected my Vista Laptop directly to the Router that the Linkstation is connected to) and it worked!!!
Now i can access all of my files on the Linkstation..
What is weird is this firmware is dated 1/9/2009 but i was able to browse to the drive without any issues until i moved.