Vista Backup to NAS error 0x80070534

I keep getting an error message "No mapping between the account names and
security ID was done 0x80070534" when trying to run Back up Configuration to
NAS (Buffalo Link Station) on my home network. Prior to receiving the error
I am asked for user name and password to access the NAS which doesn't
require a users name or password. There are literally hundreds of kb
articles related to the same error (not the error number) but, none of the
articles are related Vista or my specific problem. I am running Vista
Business on Dell Inspiron (at work I am connected to sbs2000 domain).



any and all ideas are appreciated.



Thanks,



RichC593

 

Can you map a drive to the NAS and access it normally other than when doing
a backup?

--
Kerry Brown
Microsoft MVP - Shell/User



"RichC593" <drofwrac@iwon.com> wrote in message
news:14C40A22-458C-48CD-8AF2-FFDF190A05A0@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> I keep getting an error message "No mapping between the account names and
> security ID was done 0x80070534" when trying to run Back up Configuration
> to NAS (Buffalo Link Station) on my home network. Prior to receiving the
> error I am asked for user name and password to access the NAS which
> doesn't require a users name or password. There are literally hundreds of
> kb articles related to the same error (not the error number) but, none of
> the articles are related Vista or my specific problem. I am running Vista
> Business on Dell Inspiron (at work I am connected to sbs2000 domain).
>
>
>
> any and all ideas are appreciated.
>
>
>
> Thanks,
>
>
>
> RichC593
> <!--colorc--><!--/colorc-->

 

Exactly the same problem, although with a fancy new Western Digital
MyBook NAS 500GB drive. Using Vista Business Edition running in the
Administrator Account mode.

Never had this problem with XP Pro SP2 backup program using a variety
of Western Digital NAS drives under the exact same scenario.


--
Travis
Posted via

 

I have the same problem, and with a Buffalo LinkStation. I can log on to
the NAS using Explorer, and have it set up as a networked drive (Z.

Thanks,
Gene


--
Gene

 

What firmware do you have? Aparently you need to upgrde to the latest
available from Buffalo.

"Gene" <Gene.353mt1@no-mx.forums.net> wrote in message
news:Gene.353mt1@no-mx.forums.net...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> I have the same problem, and with a Buffalo LinkStation. I can log on to
> the NAS using Explorer, and have it set up as a networked drive (Z.
>
> Thanks,
> Gene
>
>
> --
> Gene <!--colorc--><!--/colorc-->

 

G.Mester;621056 Wrote: <!--coloro:blue--><span style="color:blue <!--/coloro-->
> What firmware do you have? Aparently you need to upgrde to the latest
> available from Buffalo.
>
>
> We have a very old (first generation) LinkStation. However, later last
> night I solved the problem! I disconnected from the network drive so
> that Vista did not try to logon to the LinkStation when it started. Then
> I rebooted and tried the backup again. This time it worked. This
> morning, from my Standard user account it successfully ran the backup I
> had set to run at 10:00 AM.
>
> I read a post somewhere that rebooting would solve the problem. Since I
> both disconnected from the drive and rebooted I do not know what solved
> the problem, but it works. And from the Standard User Account (my daily
> account) I automatically log on to the LinkStation.
>
> Thanks for your suggestion.
>
> Kind regards,
> Gene<!--colorc--><!--/colorc-->


--
Gene

 

The error is caused by the Samba configuration on your nas, and should
be fixed accordingly. This might help you:



--
svg
------------------------------------------------------------------------
svg's Profile:
View this thread:

 

They probably didn't wait 19 months for your reply.

--
..
--
"svg" <svg.3zd9fb@DoNotSpam.com> wrote in message
news:svg.3zd9fb@DoNotSpam.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> The error is caused by the Samba configuration on your nas, and should
> be fixed accordingly. This might help you:
>
>
>
> --
> svg
> ------------------------------------------------------------------------
> svg's Profile:
> View this thread:
>
>
> <!--colorc--><!--/colorc-->