I've been trying to use my Buffalo Drivestation Flexnet as a SVN repository, running the SVN server on a different machine on the network. I keep getting a 'Network Access Denied' when trying to work with it.
So I researched this some more- turns out from a command prompt
c:\mkdir \\drivestation\share\a\b\c - gives me the exact same error.
Also, using the network share mapping (say if I create a network share on my xp workstation mapping it to Z:\ gives the same error. C:\mkdir Z:\a\b\c also fails. It's not just because I'm in C:\. Even Z:\mkdir a\b\c fails with the same error.
However, I can do
C:\mkdir \\drivestation\a
C:\mkdir \\drivestation\a\b
C:\mkdir \\drivestation\a\b\c
Whats funny is that mkdir \\pluto\c$\a\b\c works where pluto is another xp machine on my LAN.
However, if I plug the drivestation into usb (mapped to say I:), mkdir I:\a\b\c works.
Not sure what is going on. Any help would be appreciated.
Thanks.
So I went to BestBuy and purchased a Maxtor Central Axis - the mkdir \\maxtor\share\a\b\c\d works perfectly in that drive.
Don't know what the difference is between both these drives :(
Thanks for the quick response. I tried it with the IP as you said, but I get the same error :
C:\>mkdir \\192.168.0.151\share\a\b\c
Network access is denied.
Would this work on a Linkstation? Without this, I cannot use the Drivestation as a SVN repository since the SVN uses the mkdir commands all the times and blow up.
Would a firmware upgrade or something work? I'm on
Model Name HD-CELU2
Firmware Version BUF-CELU2-1.4T3 LOADER 3.5 W1.7
I just unpacked a Buffalo DriveStation NAS (HD-CE5000LU2). My first task was to transfer files from an old USB external disk - I used robocopy from the windows reskit - and hit the same issue as above. Reproduced with mkdir - same problem.
Spent a significant amount of time searching the web looking for Vista issues with other network devices and tweaking vista network settings in the vain hope of finding some obscure OS based fix before finding this post.
I am *deeply* unimpressed that this device doesn't support mkdir - I've never heard of anything so crazy for a NAS which presumably has Windows as one of its key target client platforms. This will cause me significant pain over the lifespan of the device, but it's not like a can send it back to the vendor and get a refund for lack of mkdir support.
So, now that I'm stuck...
1) What are my best options for command line batch transfer/mirroring of files that will work? I'm guessing with mkdir out of the equation most common windows utilities will fail too?
2) Is this mkdir issue ever likely to get addressed and, if so, when?
But I like to end on a positive, the device does look nice, which will be comforting while spending the next few hours dragging and dropping files.
Any chance we can get a firmware hotfix since this drive is pretty much unusable for my specific needs without the ability to support this? I understand if it's a no but let me know so that I can buy an alternate (the Maxtor ran too hot and was returned) and sell this one.
Thanks for the support. Appreciate it.
I have to apologise, earlier I was on a bit of a rant after the instant disatisfaction I received on opening the box.
For anyone who cares about this, of which I doubt there are many, you can copy files/trees fine from the command line using xcopy - it seems to have no reliance on the mkdir Command Extensions. It's just if you want to do something a bit clever when it might all break down.
Still, it would be nice if this did work as it would take all risk out of "will utility 'x' be able to copy directory trees onto this disk over a LAN".
I am planning to use DiskStations for backup of all my PCs (couple of TB like probably the most of us with a few itunes running) and long term "family storage" (I liked the fact of it being just a simple and compact file server at a fair price without, webserver, torrent, and other unnecessary addons like other products on the market).
I have implemented my own backup scripts and robocopy solution which runs prefectly on local and USB disks.
Unfortunately I then came across exactly the same "robocopy/mkdir/nested folders" problem explained in this forum thread.
You are now suggesting using Robocopy instead of xcopy... what puzzles me... (?!)
Is a patch available now?
Which firmware version do we have to install to fix this problem?
Do you have other similar products which do not suffer from this problem and support Robocopy and mkdir with nested folders properly?
Thank you!
I've the same problem on Win 7.
Using robocopy over LAN does not work, with USB there is no problem.
I've a HD-CELU2 drive with latest firmware 1.4.7.
I can copy files with in the shell with "copy \\BUFFNAS\share\test.txt", but ive file has long filename, this wont work over LAN.
The dir Command does not show any filenames over LAN
D:\NAS_Sicherung>dir \\BUFFNAS\share
Datenträger in Laufwerk \\BUFFNAS\share: ist SHARE
Verzeichnis von \\BUFFNAS\share
01.01.2008 00:01 <DIR>
01.01.2008 00:01 <DIR>
26.09.2008 18:56 1.105.920
11.12.2009 20:40 148
09.12.2009 22:04 <DIR>
10.12.2009 15:36 <DIR>
11.12.2009 07:03 <DIR>
11.12.2009 20:07 <DIR>
2 Datei(en), 1.106.068 Bytes
6 Verzeichnis(se), 848.008.380.416 Bytes frei
But with the /X Command it does:
D:\NAS_Sicherung>dir \\BUFFNAS\share /X
Datenträger in Laufwerk \\BUFFNAS\share: ist SHARE
Verzeichnis von \\BUFFNAS\share
01.01.2008 00:01 <DIR> .
01.01.2008 00:01 <DIR> ..
26.09.2008 18:56 1.105.920 slm.exe
11.12.2009 20:40 148 slm.ini
09.12.2009 22:04 <DIR> Bilder
10.12.2009 15:36 <DIR> Sicherung 7PC
11.12.2009 07:03 <DIR> BMOD
11.12.2009 20:07 <DIR> Daten
2 Datei(en), 1.106.068 Bytes
6 Verzeichnis(se), 848.008.380.416 Bytes frei
Here is the same folder over USB without /X:
D:\NAS_Sicherung>dir F:\share Datenträger in Laufwerk F: ist HD-CELU2 Verzeichnis von F:\share01.01.2008 00:01 <DIR> .01.01.2008 00:01 <DIR> ..26.09.2008 18:56 1.105.920 slm.exe11.12.2009 20:40 148 slm.ini09.12.2009 22:04 <DIR> Bilder10.12.2009 15:36 <DIR> Sicherung 7PC11.12.2009 07:03 <DIR> BMOD11.12.2009 20:07 <DIR> Daten 2 Datei(en), 1.106.068 Bytes 6 Verzeichnis(se), 848.008.380.416 Bytes frei
And over USB with dir /X command:
D:\NAS_Sicherung>dir F:\share /X Datenträger in Laufwerk F: ist HD-CELU2 Verzeichnis von F:\share01.01.2008 00:01 <DIR> .01.01.2008 00:01 <DIR> ..26.09.2008 18:56 1.105.920 slm.exe11.12.2009 20:40 148 slm.ini09.12.2009 22:04 <DIR> BILDER Bilder10.12.2009 15:36 <DIR> SICHER~1 Sicherung 7PC11.12.2009 07:03 <DIR> BMOD11.12.2009 20:07 <DIR> DATEN Daten 2 Datei(en), 1.106.068 Bytes 6 Verzeichnis(se), 848.008.380.416 Bytes frei
So I think the problem is, that the current firmware over the LAN does not treat the longfilename support right, while the files (over the LAN) has been correnctly writen with the "Windows Explorer".
How to fix this?
Thank you!
By the way, the windows port of rsync works on the shell with the HD-CELU2 over LAN and USB...
rsync.exe -a -v //BUFFNAS/share/Bilder /cygdrive/D/NAS_Sicherung