Re: Vista -> Personal Folder -> Unix NAS BUG
- From: "Nick" <a@xxxxx>
- Date: Fri, 12 Dec 2008 12:05:02 -0000
Hi Kerry,
So I guess there's no chance of escellating this as a bug then? Or
should I be reporting it some other way?
Otherwise this thread has just stopped at a dead end and I have no
solution to the problem. Thanks for your time.
Nick.
"Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m> wrote in message
news:ujEtj1uVJHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
"Nick" <a@xxxxx> wrote in message
news:eqGCz4kVJHA.1788@xxxxxxxxxxxxxxxxxxxxxxx
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
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.
I've already explained the difference. The mapped drive only exists for
your account. It does not exist for system accounts. It may be a system
account that is accessing the NAS. Explicitly setting your account in the
cached credentials MAY allow the other accounts to access the NAS. It is
worth a try.
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/archive/2007/03/16/using-offline-files-with-samba-emc-servers-nas-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.
I think this is just a symptom of the fact that Vista is trying to setup
offline files when you redirect a folder from your profile. Offline files
in Vista work differently than they did in XP. They are not compatible
with older versions of Samba. You could try disabling offline files but I
don't know if this will work with folders from your profile. I've never
experimented with it.
--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/
.
- Follow-Ups:
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Nick
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Brontosaurus Burger AKA Vista!
- Re: Vista -> Personal Folder -> Unix NAS BUG
- References:
- Vista -> Personal Folder -> Unix NAS BUG
- From: Nick
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Kerry Brown
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Nick
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Kerry Brown
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Nick
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Kerry Brown
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Nick
- Re: Vista -> Personal Folder -> Unix NAS BUG
- From: Kerry Brown
- Vista -> Personal Folder -> Unix NAS BUG
- Prev by Date: Re: Subject changes
- Next by Date: Re: Vista doesn't boot, no BIOS screen
- Previous by thread: Re: Vista -> Personal Folder -> Unix NAS BUG
- Next by thread: Re: Vista -> Personal Folder -> Unix NAS BUG
- Index(es):
Relevant Pages
|