Unable to map XP Share in Vista - Authenication Fails

[MadMax1412]

Adding Test to the Administrator's group now allows me to map using "test" as the username and "testing" as the password and I've since Robocopied my laptop docs to Vista.

Still can't map using the username and password I log onto the laptop with, and probably has something to do with the "maxs" username not being in the Administrators group.

Anyway, I can map using "test" and back up my laptop, so at least my end result is achieved.

Thanks for your help.

 

[duucfho]

Did you by chance try to logon using the machine_name\userid?

As in NECAU\maxs

 

[MadMax1412]

Yep but it didn't work.

 

[AngLee]

I know this thread is a bit old but I'm going to post my solution to this in case someone comes across it and needs the same wacky solution I found.

I had the same problem of trying to connect my VISTA laptop to a shared external HD (or any drive for that matter) connected to my WIN XP box. It had been working for over a year and then my XP machines graphics card went bad and I had to power down the box to replace it. No problem and I was back up and running. BUT I could no longer connect to the shared drives. Reboots, new accounts, new share names, o/s updates, all that crap and it didn't work. I could remote desktop connect to the XP machine so I was baffeled. For days I looked into it and then one late night I checked the time and saw that it was 1:00am 2002!! WTF? I realized the cmos battery was dead and had reset everything. So, I set the date to the correct time and year and it worked just like before! What a wacky solution eh? Anyway, I hope this helps someone out there.

 

[Cursed]

I had a very similar problem:
Vista workstation attempting to map to a windows XP (SP3) machine (difference being there was a NAT Firewall in between so i was using IP addresses instead of machine names) and was getting repeated authentication failures regardless of what details where used. Other XP devices had no problems connecting to the shares on the device in question, just my Vista workstation.

the solution:
the clock was out of date by 4 months for some totally legit and no way connected to software licensing reasons. re-setting it back to the current time/date solved the problem instantly. i guess Vista has issues with getting responses from a network resource originating from the past huh?