Slamtilt
08-05-2010, 10:43 PM
We just bought the Valkyrie NAS from our distributor, we sticked inside two WD5000AAKS and powered it up, since that moment the nightmare started...we don't want to be drastic, but this NAS it's quite poor...that's why it's the cheapest NAS we could find around from our distributors, however we don't really need a powerfull product, we just need a properly working NAS with raid1 and printer server. After a couple of disk setup, format in FAT and then Ext2, after couple of access problems and after figured out how to access and setup the unit correctly, we found a new FW: the release 3...flashed the unit and after a unit reboot we decided to reformat the drives with raid1 config and Ext3. After that we re-setted the users and folders and since that every thing was quite ok except for the printer, it works only for some hours and then no more printing, this is the unique actual heavy problem, we don't really care about the speed of the file transfers, we need a working printer server, we decided to buy this nas cos it's cheap and on the paper was offering all that we need: network storage with raid1 possibility, and a printer server where we have to connect a laser printer: an HP LaserJet 1018. We don't think this configuration have special needs. So, after this preamble, now after flashed again with the release 4 FW, the storage is working properly and without problems till now, but the printer will still have the same issue: after some hours it will stop printing, under Windows XP and 7 the process seem to be sent to the printer correctly but then nothing happen, under Ubuntu 10.04 in the printer property you click on test page and the error appears: "NT_STATUS_ACCESS_DENIED opening remote spool test page" and after that a windows asking the username and password popup, i put the username only (in the NAS the user is with "No pass needed" checked) but the windows that ask me the password keep poppin' up and the test page will not be printed. If i disconnect and reconnect the USB printer the problem will not vanish. I figured out, reading this forum, that the problem is probably caused by the bidirectional communication issue as written on dgusa thread. I read on that thread that this problem is not only on this NAS but also in some others NAS. I hope this could be fixed with a FW fix. I don't think someone from Patriot itself would, after have read this thread, do something for fixing this issue, i noticed as lot of other users did, that the official support is quite absent, Patriot "use" the forum community to fix the problems and give support: thumbs down for Patriot, thumbs up for the community and expecially for BadIntentions that taken the source and literally upgrading and step by step giving us a decent, usable, and most important of all, working software to use this piece of hardware. Thanks BadIntentions,imho your nick wouldn't suit your intention :D Sorry if my english isn't perfect. Cya ;)