Just so I understand what you did:
The Vista machine is in workgroup mode as opposed to being a domain
member and you're logged into it locally with credentials that don't
exist on the domain at work. So when you tried to access a share at
work, it prompted you for credentials, and after you entered a name and
password, it worked?
Here's the results of another test I did:
My machines are all in a workgroup, not a domain. Neither has even been
joined to a domain. I've been using the same username/password on both
the XP and Vista machines but for this test, I logged onto Vista using a
name and password that don't exist on the XP machine.
Logged on the Vista with this other name/password, I entered the UNC
name of the XP machine into the address bar and a list of its shares
came up, but I couldn't open any of the shared folders. It didn't ask me
for a name and password. It just said access denied until I granted the
guest account priveleges on this share from the XP machine.
So I went to a command prompt and issed the following:
net use p: \\xp_machine\share_name /user:mike *
It prompted me for mike's password (Mike is my main admin account on the
XP machine) and it created the mapped drive. But I had the same problem
copying files from it as I had before when I was simply logging on to
Vista as Mike. *sigh*
Oh, I also tried right clicking the command prompt and running it as
Administrator. I mapped my xp share to a drive and got the same thing. I
can only copy a file from it if it was created on the Vista machine. So
it doesn't seem to be a permission, UAC, or Explorer issue.
I did some more Google searching and found one hit about someone having
the same problem on Vista x64 but no solution.
In article <3788B5AF-A8B3-4192-A577-58E27A202856@microsoft.com>,
> I've got some breaking news on this problem! I took my laptop to our
> office.. I unjoined it from my home domain as I would rather it not be on
> one anyway.. So I'm in a workgroup setup now everything is still bugging out
> at home with the shares.
> I connect to the office network UNC over to a share off our file server to
> Prompted for username and password and poof I'm on..
> So far the same as home.
> Now I try and copy off something from the share and you know what.. It
> worked.. Just copied right over!! I was so happy and pissed off all the same
> So with that said I've not had time to look at what's different between the
> domains yet.. I will however on Saterday and let you know what I find out..
> Benjamn VH
> "MDaniel" <email@example.com> wrote in message
> >I have an XP Pro machine with a folder shared with full control for
> > everyone. All other machines, regardless of Windows version, have no
> > problem accessing this share with full control. I've installed Vista
> > Ultimate RTM on two machines and have had the following problem on both:
> > Both Vista machines can read/write/execute files that are in that
> > network share. For example, if its a .pdf, .txt, or .doc, I can double
> > click it from the Vista machines and it opens just fine with the
> > appropriate application. If its an .exe, like the installer for Firefox,
> > it'll launch and install the program. I can also save and delete files
> > and folders on that network share from the Vista machine. So far so
> > good.
> > The problem is with simply trying to copy a file from that share TO the
> > Vista machine. I get an error message titled "Destination Folder Access
> > Denied" that reads "You need permission to perform this action". It
> > doesn't matter where I copy the file to. Desktop, Public, Documents,
> > etc. Same thing. So I can open/execute it, but I can't copy it.
> > This happens on both Vista machines. I have enabled the Public folder on
> > both Vistas and they can copy files to/from each other. And the XP
> > machine can copy to/from the Vistas' Public folders.
> > I am an using the same administrator account on all machines. The
> > problem is the same whether I use Vista's explorer or command prompt.
> > I haven't found much on Google but I did try disabling UAC, firewalls on
> > all machines, and even IE7's Protected Mode without any success.