It was Apples Security Update 2009-001 that caused this issue however not trying to blame them and it's just a fact!

You do not necessarily need to use Bridged if you want to print to a Printer if it's Shared on the Mac so have a look at my reply Re: Workaround for Printers Sharing not working after Mac OS X Security Update 2009-001 as a work-a-round until VMware has a fix. Otherwise start your own discussion thread to resolve your issue of why Bridged is not working on your system.

Thank you for posting this information so quickly. You guys really jumped on this. If I can make one suggestion though - it would be to notify customers by email, too.

This is Apple's fault. Unfortunately VMware gets blamed and has to solve the problem. It would be great if Apple gave 3rd party developers time to test updates before publicly releasing them, on the other hand this is a security update and maybe they felt it too important to wait.

The best solution is for Apple to provide a way to uninstall updates. I'm a road warrior so I'll have to figure out if it's possible (and practical) to use Time Machine with a portable hard or USB drive in the future.

Thanks again.

If you've installed the Mac OS X Security Update 2009-001 and you did not have Time Machine setup to be able to revert OS X to a previous state then you have to basis choices.

1. Reinstall Mac OS X and do not install the Mac OS X Security Update 2009-001.

2. Turn off the Printer in the Virtual Machine's Settings and then install the Printer in Windows just as you would have to if the feature never existed.

Obviously 2 is the easiest and quickest solution until this issue is resolved.

Note: A word of warning... Before doing anything I'd make absolutely sure that you have proper user data backups independent of anything Time Machine related and that exist outside of the Virtual Machine itself as well as having a copy of the Virtual Machine itself on storage media other then where it now resides as a means of being able to recoverer without having to reinstall everything in the Virtual Machine from scratch and not having to rely solely on Time Machine as there have been plenty of reports that Time Machine fails to properly backup and restore Virtual Machines.

Also if you do not understand what I'm saying or how to do these things then because you using this to earn a living then I'd suggest you contact a professional that knows that they're doing and can advise you or do what is necessary so you are covered in the event of a disaster or any unforeseen circumstances.

BTW Uninstalling/reinstalling Fusion or recreating the Virtual Machine is not going to resolve this issue if you've applied the Mac OS X Security Update 2009-001 so that is not the direction you need to proceed if this is applicable.

Just to clarify... Are you saying you had no problem applying the Mac OS X 10.5.6 Combo Update even though all additional post Mac OS X 10.5.6 Combo Update updates had been applied and then did you have to reply other updates except for the Mac OS X Security Update 2009-001 and all is well?

If that is so then that certainly is easier/faster then a total clean build however I'd caution anyone from reapplying the Mac OS X 10.5.6 Combo Update if they have work to get out and first use the work-a-round of installing the printer as one would just as if the feature didn't exist as that would be faster and safer until you have the time to reapply the Mac OS X 10.5.6 Combo Update and post updates, if applicable, up to but not including the Mac OS X Security Update 2009-001. I'm only advising this if one is in the middle of a project and isn't prepared to deal with a failed Mac OS X 10.5.6 Combo Update if that were to happen. Anyway as always before applying/reapplying a major OS update be sure that at a minimum your user data is backed up off of the system before applying/reapplying the update.

Have a look at the following replies...

Re: Workaround for Printers Sharing not working after Mac OS X Security Update 2009-001

Re: Workaround for Printers Sharing not working after Mac OS X Security Update 2009-001

Woody,

For me, my mac was up to the latest patches, etc. I then downloaded and
applied the combo update. Now everything works. Literally, this is all I
did.

Steve

My cupsd access_log is littered with the following errors

localhost - - [23/Feb/2009:20:23:00 -0500] "GET / HTTP/1.1" 400 0 - -
localhost - - [23/Feb/2009:20:23:00 -0500] "GET / HTTP/1.1" 400 0 - -

and the error_log is also littered with

W [21/Feb/2009:15:59:34 -0500] Request from "localhost" using invalid Host: field "/private/var/run/cupsd"

when the Printer setting is enabled.

This tells me that whatever is talking to cupsd (my best guess, ThinPrint) is not sending a correctly formatted request to CUPS. That would make some sense out of the vmware logging saying it couldn't determine the version of CUPS in use.

Hopefully VMware has ThinPrint involved to help figure this out.