Vista -> Personal Folder -> Unix NAS BUG

Hi there,

I've found what I can only presume is a bug. If I map a network drive to my
NAS, which happens to be an ICYBOX-IB4220-B, the network drive works
perfectly. When I delete files, they disappear, the drive does not use the
recycle bin, I am okay with this.

If I then map one of my personal folders, lets say "My Music" to the newly
created network drive, I start recieving recycle bin errors.

"The Recycle Bin on M:\My Music is corrupted. Do you want to empty the
Recycle Bin for this drive?"

This happens pretty much any time the recycle bin is used, as if it's
enumerating all bins in order to see what's there.

Any idea on how to resolve this as it's getting quite annoying now?

BTW. I've verified this on 2 separate systems, both running Vista Business.

Thanks in advance.

Nick.

Hi there,

Unfortunately that didn't help, I've tried deleting the folder many
times, it still comes back any time the main recycle bin is accessed, and
even with the recycle bin *disabled* for that Network drive.

Nick.

"Brontosaurus Burger AKA Vista!" <> wrote in message
news:4937ba08$...
> make sure you can see hidden files folders and system files
>
> then go to all drives and delete the: $RECYCLE.BIN
>
> folders that are hidden and should be located in each root of the drive.
>
> Restart,
>
> see if the problems goes away... the $RECYCLE.BIN will be recreated so
> don't worry about that
>
> tell me if this helps
>
> "Nick" <> wrote in message
> news:...
>> Hi there,
>>
>> I've found what I can only presume is a bug. If I map a network drive to
>> my NAS, which happens to be an ICYBOX-IB4220-B, the network drive works
>> perfectly. When I delete files, they disappear, the drive does not use
>> the recycle bin, I am okay with this.
>>
>> If I then map one of my personal folders, lets say "My Music" to the
>> newly created network drive, I start recieving recycle bin errors.
>>
>> "The Recycle Bin on M:\My Music is corrupted. Do you want to empty the
>> Recycle Bin for this drive?"
>>
>> This happens pretty much any time the recycle bin is used, as if it's
>> enumerating all bins in order to see what's there.
>>
>> Any idea on how to resolve this as it's getting quite annoying now?
>>
>> BTW. I've verified this on 2 separate systems, both running Vista
>> Business.
>>
>> Thanks in advance.
>>
>> Nick.
>>

"Nick" <> wrote in message
news:...
> Hi there,
>
> I've found what I can only presume is a bug. If I map a network drive to
> my NAS, which happens to be an ICYBOX-IB4220-B, the network drive works
> perfectly. When I delete files, they disappear, the drive does not use
> the recycle bin, I am okay with this.
>
> If I then map one of my personal folders, lets say "My Music" to the newly
> created network drive, I start recieving recycle bin errors.
>
> "The Recycle Bin on M:\My Music is corrupted. Do you want to empty the
> Recycle Bin for this drive?"
>
> This happens pretty much any time the recycle bin is used, as if it's
> enumerating all bins in order to see what's there.
>
> Any idea on how to resolve this as it's getting quite annoying now?
>
> BTW. I've verified this on 2 separate systems, both running Vista
> Business.
>


Instead of mapping a drive try redirecting to the UNC path as in
\\ICYBOX-IB4220-B\My Music

It's a guess but give it a try and post back with the results.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/

Hi Kerry,

> Instead of mapping a drive try redirecting to the UNC path as in
> \\ICYBOX-IB4220-B\My Music
>
> It's a guess but give it a try and post back with the results.

The NAS is Unix based, and if I refer to it as a network share there are no
options for me to enter alternate credentials so referring to a network
share just isn't an option.

The network drive itself is not a problem, that works great, it's the
mapping of a personal folder onto the network share, for some reason that
forces the destination to become included in some kind of enumeration for
the recycle bin.

I have noticed there is a similar issue for XP and 2000 with a hotfix
available, but not for Vista. I think it's fair to presume the bug exists
in Vista as it does in XP, it's not as if Vista was delivered to us with les
bugs than XP unfortunately.

http://support.microsoft.com/kb/297760

The NAS is going to be used as my primary source of storage as I do not
trust hard drives in my case anymore, 2 failures in 1 year is enough for me
to make the transition.

Nick.

"Nick" <> wrote in message
news:...
> Hi Kerry,
>
>> Instead of mapping a drive try redirecting to the UNC path as in
>> \\ICYBOX-IB4220-B\My Music
>>
>> It's a guess but give it a try and post back with the results.
>
> The NAS is Unix based, and if I refer to it as a network share there are
> no options for me to enter alternate credentials so referring to a network
> share just isn't an option.
>
> The network drive itself is not a problem, that works great, it's the
> mapping of a personal folder onto the network share, for some reason that
> forces the destination to become included in some kind of enumeration for
> the recycle bin.
>
> I have noticed there is a similar issue for XP and 2000 with a hotfix
> available, but not for Vista. I think it's fair to presume the bug exists
> in Vista as it does in XP, it's not as if Vista was delivered to us with
> les bugs than XP unfortunately.
>
> http://support.microsoft.com/kb/297760
>
> The NAS is going to be used as my primary source of storage as I do not
> trust hard drives in my case anymore, 2 failures in 1 year is enough for
> me to make the transition.
>


If the NAS is using Samba for windows file sharing you should be able to
access it using a UNC path. Are there any updates for the NAS firmware to a
newer Samba version? If not you could try this

http://www.jimmah.com/vista/content.aspx?id=33

You could also try entering the credentials needed for the NAS here:

Control Panel =>User Accounts =>User Accounts =>Manage your network
passwords

The NAS also uses hard drives :-) I've found some NAS' more prone to drive
failures than PCs due to overheating issues.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/

Hi Kerry,

> If the NAS is using Samba for windows file sharing you should be able to
> access it using a UNC path. Are there any updates for the NAS firmware to
> a newer Samba version? If not you could try this
>
> http://www.jimmah.com/vista/content.aspx?id=33
>
> You could also try entering the credentials needed for the NAS here:
>
> Control Panel =>User Accounts =>User Accounts =>Manage your network
> passwords

I have not said that I can't access the drive via a UNC Share, that is
how it's mapped to the network drive in the first place, there is no other
way to map it afaik. What I am referring to is other applications accessing
the mapped drive and automatically being granted access due to the
credentials being cached in the network drive configuration. I am not so
sure that simply adding a network location and "remembering the password"
will enable low level enough access to all applications which is 100%
critical for my use.

The correct way to use a NAS is via a mapped drive, which as I said
*works*. The bug is with the personal folder mapping deciding top enforce a
recycle bin upon the target when it has not been requested, and has even
been disabled.

> The NAS also uses hard drives :-) I've found some NAS' more prone to drive
> failures than PCs due to overheating issues.

Yes, indeed it does use a hard drive, but my Dell E520 case is poorly
designed and the 2 hard drives being so close together with no space for air
circulation has resulted in 2 hard drive failures this year, 1 last year and
the current hard drive is in the process of failing. Hence why I purchased
a NAS caddy that has an independent thermostat controlled cooling fan and is
stored in an aluminium caddy. It's also capable of Raid, something which I
can't do in my current case because I do not have enough space for 3 hard
drives unless I use a 5 1/4" drive bay.

Nick.

BTW, just so you know, referring the personal folder to the network share
results in exactly the same problem as if it was referring to a Mapped
Network Drive.

I can't help thinking this is just simply a bug.

"Kerry Brown" <*a*m> wrote in message
news:%...
> "Nick" <> wrote in message
> news:...
>> Hi Kerry,
>>
>>> Instead of mapping a drive try redirecting to the UNC path as in
>>> \\ICYBOX-IB4220-B\My Music
>>>
>>> It's a guess but give it a try and post back with the results.
>>
>> The NAS is Unix based, and if I refer to it as a network share there are
>> no options for me to enter alternate credentials so referring to a
>> network share just isn't an option.
>>
>> The network drive itself is not a problem, that works great, it's the
>> mapping of a personal folder onto the network share, for some reason that
>> forces the destination to become included in some kind of enumeration for
>> the recycle bin.
>>
>> I have noticed there is a similar issue for XP and 2000 with a hotfix
>> available, but not for Vista. I think it's fair to presume the bug
>> exists in Vista as it does in XP, it's not as if Vista was delivered to
>> us with les bugs than XP unfortunately.
>>
>> http://support.microsoft.com/kb/297760
>>
>> The NAS is going to be used as my primary source of storage as I do not
>> trust hard drives in my case anymore, 2 failures in 1 year is enough for
>> me to make the transition.
>>
>
>
> If the NAS is using Samba for windows file sharing you should be able to
> access it using a UNC path. Are there any updates for the NAS firmware to
> a newer Samba version? If not you could try this
>
> http://www.jimmah.com/vista/content.aspx?id=33
>
> You could also try entering the credentials needed for the NAS here:
>
> Control Panel =>User Accounts =>User Accounts =>Manage your network
> passwords
>
> The NAS also uses hard drives :-) I've found some NAS' more prone to drive
> failures than PCs due to overheating issues.
>
> --
> Kerry Brown
> MS-MVP - Windows Desktop Experience: Systems Administration
> http://www.vistahelp.ca/phpBB2/
> http://vistahelpca.blogspot.com/
>
>
>

"Nick" <> wrote in message
news:...
> Hi Kerry,
>
>> If the NAS is using Samba for windows file sharing you should be able to
>> access it using a UNC path. Are there any updates for the NAS firmware to
>> a newer Samba version? If not you could try this
>>
>> http://www.jimmah.com/vista/content.aspx?id=33
>>
>> You could also try entering the credentials needed for the NAS here:
>>
>> Control Panel =>User Accounts =>User Accounts =>Manage your network
>> passwords
>
> I have not said that I can't access the drive via a UNC Share, that is
> how it's mapped to the network drive in the first place, there is no other
> way to map it afaik. What I am referring to is other applications
> accessing the mapped drive and automatically being granted access due to
> the credentials being cached in the network drive configuration. I am not
> so sure that simply adding a network location and "remembering the
> password" will enable low level enough access to all applications which is
> 100% critical for my use.
>
> The correct way to use a NAS is via a mapped drive, which as I said
> *works*. The bug is with the personal folder mapping deciding top enforce
> a recycle bin upon the target when it has not been requested, and has even
> been disabled.
>


Our opinion differs here. After many years of administering networks I
believe whenever possible UNC paths should be used. You never know what
account context will be used to access a network share. It may not be your
account but a system account that needs access. That may be what is
happening in this case. The mapped drive will not exist for the system
account. Adding your account to the cached passwords sometimes gets around
the permissions issue but it won't get past a non-existing mapped drive for
a system account.

If the NAS device allows you low level access to the NAS OS you can try the
following Samba config changes and file system permissions.

http://blogs.technet.com/filecab/arc...s-devices.aspx

Most consumer NAS' don't allow these types of configuration changes. You are
reliant on the NAS manufacturer to come out with a Vista compatible firmware
update.

You are trying to do something that is explicitly not supported so it can't
really be called a bug. You could just as easily call it a bug in the NAS
firmware. It's a problem with networking mixed OS' in general. I know it's
frustrating but not everything works when you mix OS' on a network. After a
while you learn to work around it. I quit using consumer NAS devices for
these reasons. FWIW I had similar problems when using newer versions of
Linux accessing a NAS with an older version of Samba. XP worked but not
Ubuntu 8.04 or Vista. I also couldn't access the NAS from an Acronis Linux
based restore CD.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/

Hi Kerry,

> Our opinion differs here. After many years of administering networks I
> believe whenever possible UNC paths should be used. You never know what
> account context will be used to access a network share. It may not be your
> account but a system account that needs access. That may be what is
> happening in this case. The mapped drive will not exist for the system
> account. Adding your account to the cached passwords sometimes gets around
> the permissions issue but it won't get past a non-existing mapped drive
> for a system account.

The same path is resolved ultimately, so what's the difference? The
main differences for me; is having the data accessible via a drive for ease
of use and also assurance that credentials have already been authenticated
during the connection process. Either way, this is *not* a problem with
mapping a network drive, or referring to a UNC share, this is a problem with
mapping said path to a *personal folder*. Both mapped drive and UNC share
work great on their own, the problem occurs when changing the location of a
personal folder, such as "My Music" to said location, then the error occurs.

> If the NAS device allows you low level access to the NAS OS you can try
> the following Samba config changes and file system permissions.
>
> http://blogs.technet.com/filecab/arc...s-devices.aspx

Unfortunately I'm not sure I have low enough level access to be making the
above changes.

> Most consumer NAS' don't allow these types of configuration changes. You
> are reliant on the NAS manufacturer to come out with a Vista compatible
> firmware update.

Or for Microsoft to fix the obvious bug that's occuring here. If I
apply a setting in any application, I expect that setting to take effect,
this is not happening in Vista. I'll give you a perfect example,

1. Right click recycle bin
2. Locate mapped drive, this appear the second you map the drive to a
personal folder.
3. Click on "Do not move files to the Recycle Bin. Remove files
immediately when deleted."

The above does not get applied and the error continues. It's quite
obvious that the NAS does not support trashing to a recycle bin because
before it is mapped to the personal folder it works correctly and deleted
files are removed without being recycled, this is automatically configured
this way. Vista is trying to be clever and presuming that just because it's
a personal folder that I want Recycle bin capabilities, I don't it's not
working with this drive.

I've tested this in XP and it works just fine, no tedious error messages
appear as the recycle bin knows it can't work for that location.

Just to clarify this entire problem, this bug is not with mapping
network drives or referring to UNC locations, it only occurs once you have
mapped said location to a personal folder. Upon this mapping an entry for
the mapped drive / UNC appears in the recycle bin tree, all settings for
this location are completely ignored and it insists on creating a recycle
bin folder, and attemping to use it. Unmap the location as a personal
folder and the bug goes away.

Nick.

Hi B.B.,

> does this NAS have FTP?
>
> if so you can perhaps use that route to connect by creating a share on
> vista

Indeed it has FTP, although I'm not sure that it's a good choice in
protocol for a heavy use file system as traversing the tree can be quite
lengthy at times. Although I have used an FTP client to transfer the
majority of the files, simply because the options for existing files is just
allot nicer than what Explorer offers.

Also, accessing in this way looses allot of functionality such as ID3 Tag
enumeration and thumbnailing.

> You know you can connected external shared locations and they appear as
> folders on vista (and xp)
>
> just a thought...

I'm not sure I understand what you mean, isn't this what I'm doing anyway?

Nick.