Vista - Can connect Vista laptop to XP Desktop ONLY if not logged on as Admin

Hi:
I have successfully managed to connect a laptop running Vista Business
to a desktop running XP Pro, and share files on the latter, with one
hitch. When I log onto the XP machine with an account that has admin
rights, the sharing gets disabled in Vista, i.e, I get a "cannot
access" error. However if no users are logged on to the desktop OR if
I log on with an account that is NOT an admin, then the Vista laptop
can access all the shared folders on the desktop.
Any solutions?
Thanks - Ram

http://technet.microsoft.com/en-au/l.../bb727037.aspx

Have a read.

"Ramkumar Ramaswamy" wrote:

Thanks this is a great intro article and I did go through it to get
things set up. As of now file sharing IS working perfectly both
ways ... EXCEPT... I need to figure out why sharing stops working
(both ways!) if I merely log in with an Admin account on the XP
machine, This article does not help with that.
-Ram

On Nov 27, 3:06 pm, Mick Murphy <MickMur...@xxxxxx>
wrote:

Hi Ram. Apparently if you have password protected turned on in Vista Network
and Sharing, you have to have the exact same user accounts set up on both
machines.

I may have read it wrong; don't quote me!!!!!

"Ramkumar Ramaswamy" wrote:

Already done! That's why everything works both ways perfectly to start
with. I seem to be turning OFF something when I log into the XP
desktop as admin, which makes everything stop working. The moment I
log off as admin things work again both ways. In fact I checked the
security logs too and it shows a successful logon from Vista when I am
logged in as admin on the XP, but Vista shows an error saying "not
accessible". So it is not a problem with logon credentials.

On Nov 28, 2:34 am, Mick Murphy <MickMur...@xxxxxx>
wrote:

Solved this problem. There was a startup process that was blocking
ports. I used msconfig to do a "selective startup", shutting down all
non-MS services, and everything worked fine. Repeated restarts by
adding more services to the selective startup list allowed me to
figure out which one was causing the problem. It was a piece of third-
party software.
-Ram

On Nov 28, 7:11 am, Ramkumar Ramaswamy <ramkumar.ramasw...@xxxxxx>
wrote: