The Linkstation is using SAMBA Version 3.0.30-1.4.osstech.
The Samba group announced the 3.0.0 tree in September 24, 2003, 9 years ago.
The 3.0.30 patch was announced in May 2008, and that last patch to the 3.0.x tree was 3.0.37, issued in October 2009, making the Linkstations Samba version, well, let's be nice, let' say, OLD.
Per the SAMBA.org Wiki, Windows 7 is fully supported in Samba 3.4 or later, Samba 3.3.5 or later, Samba 3.3.2, 3.3.3 and 3.3.4 (with NOTES), and Samba 3.2.12 or later
https://wiki.samba.org/index.php/Windows7
Hmmm, so the Linkstation is using OLD software, that DOES NOT OFFICIALLY SUPPORT WINDOWS 7.
Maybe I should find an adjective other then OLD to describe the SAMBA situation in the Linkstation.
Maybe I'm wrong, maybe I just had the bad luck to look in the new, just released images, full of old software.
F.Y.I.
SAMB.org just released Version 4.0.0rc1 this week.
SAMBA 3.6.0 was Announced in August of 2011
SAMBA 3.5.0 was Announced in March of 2010
SAMBA 3.4.0 was Announced in July of 2009
SAMBA 3.3.0 was Announced in January of 2009
SAMBA 3.2.0 was Announced in July of 2008
SAMBA 3.0.0 was Announced in September of 2003.
The announced patch to the 3.0. tree was 3.0.37, a security patch released in October of 2009.
FInd it hard to believe that there isnt a basic logging capability built into the devices. I could understand not having really deep, comprehensive logging due to potential performance issues, but NO LOGGING AT ALL? Come on now... and the "daily status email" thing just isnt enough.
Please add some sort of persistant logging that users can access & refer to, so that we can get a better idea of what is happening with the devices.
My setup is an old Linkstation HD-HLAN (100GB drive), Firmware 1.44, Samsung SCX4216F multifunction printer connected to the USB port, home network with Windows XP, Vista and Win 7 machines.
I just couldn't get my Linkstation connected printer to work through a TCP/IP port on the Win 7 machine. I eventually got it to work quite quickly by this connection method using a LOCAL port
1. Click ‘Devices and Printers’,
2. Click Add a Printer
3. Click 'Add a local printer'
4. Click 'Create a new port'
5 Select Local port, click Next
6. Enter port name as \\linkstation\lp then click OK
(Note: If this port does exist then click 'Use an Existing port' and select \\linkstation\lp LOCAL Port back at step 4. Important to make sure its a local port and not a TCP/IP one)
7. For driver select Samsung SCX-4x16 series (the universal print driver which is supposedly for W7 x64 doesn’t work. It simply starts the printer but then fails to print anything)
Hope this helps someone out there and this is the appropriate place to post this.
Running a 2TB LS-QL/R5 with 1.10 firmware, and a 1TB external USB drive (formatted as XFS) connected
to the rear USB port. Running the Nav client on Windows XP with six clients accessing the shares.
All working like a champ so far. There were no issues with the setup (once I got the permissions right...
would like the manual to be a little clearer about that, but that would be a different post). Now I have two
perfectly visible and usable LinkStation shares (with RAID5 protection on one share for important files
and USB protection -- RAID0, if you're being picky -- in a different share for less-important files).
However, to move individual files between the two shares (the R5 RAID Array and the external USB drive),
I have to get a client of some ilk in the mix (which downloads the file from the LS to the client, then turns
around and uploads the file from the client back to the LS). Seems like a lot more electrons being
temporarily inconvenienced than would otherwise be necessary, consuming network and client capacity
that's otherwise not really necessary.
It would be handy if this were available through the Nav interface, but I'm not particular about that.
This is a request to please add .ASP support for the web server feature on the Linkstation Duo firmware. Thank you