03-20-2012 02:27 PM
We are still working on the issue. The issue has been escalated to our engineers to try and resolve the issue. We apologize for the delay.
03-21-2012 09:41 AM
Durr sorry my mistake of course the webpage is viewed thru the browser..
and btw I only have IE (8 and 9) tried both, same issue.. old NAS no, new NAS yes.
03-24-2012 02:53 AM
I own the LS-WVL/R1 and have had the same problem updating the dtcp-ip firmware, no matter what I try. I even returned it to the store and received a new one, which suggests that it is not a hardware problem.
I hope this problem gets fixed. I'm posting here to reinforce the point that this is not a limited problem, but is likely more common than is believed.
Is there no way to get a detailed log that might provide a clue to the problem?
04-20-2012 09:13 AM
The option to update DTCP-IP does not update the media server, it verifies the DTCP-IP key. This key is not used in the USA - only used in Japan. The next versions of the FW, will update the media server.
FW 1.58 incorporates bug fixes.
04-20-2012 09:45 AM
So despite everyone making it quite clear what our problem is and the issue in hand you manage to completly avoid answering the question you know we will all want answering. Has the DTCP-IP error been fixed in 1.58?
This is the error we have "While firmware updating, Media Server update can not be updated completely. Please click 'Update DTCP-IP' button after establishing Internet connection"
Looking at the Release note I can see you have fixed this... "Fixed an issue appearing "Media Server update can not be updated completely" warning and error message when configuring Media Server."
If I update to 1.58 will I still have the same error problem... "While firmware updating, Media Server update can not be updated completely. Please click 'Update DTCP-IP' button after establishing Internet connection"
Or do I need to wait for the next version?
Or do we have to test that for you?
04-20-2012 11:25 AM
So let me get this straight.... all Buffalo did was hide the error warning message? But the actual error itself still exists?? Please tell me I'm mistaken.
Has anyone with this issue updated to 1.58 and resolved the issue? I'm going to try this weekend.
04-20-2012 05:24 PM
This is a preventative measure, not a fix.