Shared vista printer access denied unable to connect to xp machines

Hello,
Yesterday I set up my local printer on a Vista machine to be shared with all the other PC's & laptops in the house which run XP. Worked like a champ yesterday... Today all XP machines show printer OFFLINE...Tried r-click..Select "use printer online" and get message peration could not be completed"... Left click to bring up job status window and on top where the printer name is, it says "Access denied, unable to connect"... Tried uninstalling, reinstalling, updating drivers, no help.... Checked in the Vista machine under Admin Tools- Services and the print spooler is Started, and set to Automatic, as well as the Print Spoolers Dependencies are all Started & Automatic too.... Yesterday I was pretty proud of myself, now I have a headache..... Help please!

check this,
http://social.technet.microsoft.co [...] aba202fb2/

also try this,
go to printer properties in vista machine open security tab & give full permissions to everyone groups & also try this
http://windows.microsoft.com/en-US [...] -a-printer

have you turned off " Password protected sharing "

& give full permission to every groups..

STILL UNRESOLVED...Anyone Else out there have any other suggestions?.... Here's the setup: HP LaserJet 1200 on USB to 64 bit Vista Home Premium.... Network- Multiple units on XP (sp3).... All worked on install day with drivers loaded directly on the XP boxes, then next day-POOF! all in OFFLINE status & unable to connect..............ONE EXCEPTION-NEW DEVELPOMENT- When my daughter comes over with her Vista (unsure version) laptop- she can find and print to the printer... AND- I even bought a Linksys wireless print server ($20-craigslist) thinking it would be the cure, and the ethernet or the wireless connection dissappears after approx 2 minutes after setup... It's hard to comprehend this issue has gone on for so long for so many... PLEASE HELP!

So I had this same problem last week on an XP machine in one of my remote locations. Weird thing was that it was working just fine the day before. After doing a lot of research and following many suggestions on several sites I found a note that removing the machine from the domain and re-adding it solved the issue. Digging in a littler further i found that the DNS record for that machine was missing it's reverse pointer. Added the reverse pointer and rebooting the users machine solved this issue. Hope this helps anyone else out there baffled by this one