VMware Communities: Message List - 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

SPED75 — Tue, 21 Apr 2009 06:53:41 GMT

I've gone back to version 2.0.2 and my printer works fine now. Plus, in Sage, I was also unable to export to pdf and that has also been fixed now I'm using the older version of Fusion.

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

DLMIVRN — Mon, 20 Apr 2009 14:08:30 GMT

Thanks for the help. I just installed the VMWare Fusion 2.0.4 and my printers are working great!! I wish I had come here before spending several hours yesterday reinstalling printer drivers on the Windows side!

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

davidliu — Thu, 09 Apr 2009 17:01:35 GMT

We fixed printing passthrough in VMware Fusion 2.0.3: **Free** VMware Fusion 2.0.3 now available.

-David

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

SPED75 — Thu, 09 Apr 2009 08:56:41 GMT

I have a wireless network printer that has stopped working on my virtual machine, I have tried your workaround by unchecking the enabled option in Fusion Printer Settings and changed to NAT. However, I have not managed to enter a recognised URL in the Add Printer Wizard. In OSX, System Pref, Printer & Fax, Options the URL is mdns://EPSON64A7DF._printer._tcp.local. Any suggestions?

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

JBSYR — Tue, 31 Mar 2009 15:37:46 GMT

Hello Woody,

Thanks for the information that you and mudaltsov have provided on this issue. I am in the same collective "boat" as most on it and will likely try one of the workarounds you have suggested. I was curious on the status of a permanent fix to the problem. Would you happen to have a feel for when that will be ready?

Thanks for your support!

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

ronbeattie — Tue, 31 Mar 2009 09:48:52 GMT

Can you tell me if my problem is linked with the Mac osx security update 2009-001 debacle.

My setup: Canon MP610 printer attached to pc laptop via USB. Laptop on wireless network.

Imac connected to wireless network. Printing from Mac ok.(Printer URL is smb://lap1:139/canonmp6)

Printing from within VMWare Fusion 2 NOT OK.

How should I set up printer details in Virtual Machine running XP pro?

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

WoodyZ — Thu, 26 Mar 2009 02:37:35 GMT

Have a look at my reply in Re: Workaround for Printers Sharing not working after Mac OS X Security Update 2009-001

Or apply mudaltsov's workaround shown in 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

jaxoh — Thu, 26 Mar 2009 02:23:47 GMT

Hi,

I am VERY new at this VMWare thing with Mac. I suddenly was unable to print in the VMWare environment. Followed the instructions for setting up with Bonjour. The printer activates, but only to print out reams of code. I could use some help on this. Only use one program, Quickbooks, in the WindowsXP/VMWare environment and I have to do payroll soon! What have I done wrong? Isn't there a patch for this?

Thanks.

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

wjohnston — Wed, 18 Mar 2009 14:48:20 GMT

I have tried Bridged and used Bonjour from Windows (which discovers printer) but cannot get through wifi when I send print data. I also DO NOT see "printers" in Fusion. Is there something that needs to be reconfig'd in Fusion? I can see Windows pinging router but not getting any response then it times out.

Thanks,

Bill

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

tvincy — Wed, 18 Mar 2009 01:11:22 GMT

thanks for the advice - i figured it out on my own.

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

WoodyZ — Wed, 18 Mar 2009 00:16:38 GMT

tvincy wrote: It seems like I am having the exact same issue as everyone else on this thread, so I would rather keep my post on this thread.

I understand that you might think it's the exact same issue as everyone else on this thread however when you are asked to start your own discussion thread it is being done so for good reasons and I wish you would have done so! Even if you have the exact same issue there are times that it make it easier to branch to ones own discussion thread to keep from needless cluttering up an already lengthy thread and in a case like this where you have been unable to follow the known good working directions that have been published then it's time for you be in your own discussion thread when you are asked to do so.

Need hand holding

Just one of several of the good reasons under the conditions to be in your own discussion thread.

Willing to try anything as printing essential to my business.

Obviously not since you were unwilling to follow directions!

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

tvincy — Tue, 17 Mar 2009 23:32:40 GMT

So far I've tried these iterations to no avail:

NAT / vmnet8 inet address
NAT / vmnet1 inet address
Host-only / vmnet8 inet address
Host-only / vmnet1 inet address

I also wasn't sure if it was vmnet or vmnetx and then the inet address, so I tried both for each iteration.

Each time received message "Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server."

As a last resort I tried http://mycomputername.local:631/printers/QUEUE name and oddly enough I received a different error message (and delay was much longer). "Windows Cannot Connect to this Printer. Operation could not be completed."

Do you have any other suggestions?

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

tk1234 — Tue, 17 Mar 2009 17:49:19 GMT

It is not "printer_name_on_mac" it is "Queue_Name_of_target_Printer"

Point taken - it turned out to be the same thing, once the underscores were inserted

The vmnetn that is use is based on the Network configuration of the Guest and if the Guest is configured as NAT then vmnet8 is used and if Host Only then vmnet1 is used.

My VMware Fusion session based on Bootcamp is indeed configured as NAT. However, the vmnet8 address was not accepted by Windows (could not connect the printer), but vmnet1 did work. I am running Fusion 2.02, OS X 10.5.6 with all updates, Windows XP SP2 on Bootcamp partition. Sharing is turned on for the printer in question, Network is NAT, Printer is disabled. Any guess why vmnet8 does not work and vmnet1 does? Should I look for anything in ifconfig to understand this? For the record, I also tried to input the computer name as many different ways as I could, and it wouldn't accept them in any form. Where should I be looking for that in it's correct form?

Message was edited by: tk1234
Update: Was able to get the "computer name" working, but only by adding ".local" to it. ie, http:/MyComputer.local:631/printers/etc

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

WoodyZ — Tue, 17 Mar 2009 17:25:08 GMT

tk1234 wrote: 3. Type as follows: http://vmnetx inet address:631/printers/printer_name_on_mac

It is not "printer_name_on_mac" it is "Queue_Name_of_target_Printer" The Queue Name is not the same as the Printer Name and one must use the Queue Name and that can be found by doing the following...

Apple Menu > System Preferences... > Print & Fax > select the target printer and click Open Print Queue... button > then click the Info icon on Toolbar > On Info sheet look at "Queue Name:" (Hint: You can actually highlight it and copy and paste it.)

4. In (3) above, note that vmnet1 worked for me (vmnet8 did not)

The vmnetn that is use is based on the Network configuration of the Guest and if the Guest is configured as NAT then vmnet8 is used and if Host Only then vmnet1 is used.

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

tk1234 — Tue, 17 Mar 2009 15:00:23 GMT

tvincy

I also had problems connecting under NAT to a network printer (USB on Airport extreme) - a lot of addresses mentioned here didn't work - I did the following to make it work:

1. Start "Terminal" utility on Mac and run "ifconfig" - take note of the vmnet8 and vmnet1 "inet" addresses

2. In your virtual machine windows, run "add printer", and per woody's tutorial, set up a printer connected to the network

3. Type as follows: http://vmnetx inet address:631/printers/printer_name_on_mac

4. In (3) above, note that vmnet1 worked for me (vmnet8 did not), and that the printer name on mac MUST be put in exactly as spelled with caps, with underscore between words, even though it doesn't appear that way on the mac

Good luck.

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

tvincy — Tue, 17 Mar 2009 13:29:31 GMT

Woody,

It seems like I am having the exact same issue as everyone else on this thread, so I would rather keep my post on this thread.

Here's my info:
VMWare Fusion 2.0
Imac (2008 build)
Virtual Machine = Windows XP Service Pack 1
Unable to print on my Virtual Machine after installing Security Update 2009-001 on 3/14
Worked perfectly (with no tweaks) before security update.
I have installed a network printer so I followed the steps in the workaround (#1) - but received an error message "Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server."
Need hand holding
Willing to try anything as printing essential to my business.

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

WoodyZ — Tue, 17 Mar 2009 05:42:36 GMT

There are several different ways to setup printing in a Guest and you should start your own thread using Start a discussion after you've read HOWTO: Ask (and Answer) Questions so you can provide the relevant information regarding your situation.

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

tvincy — Tue, 17 Mar 2009 05:23:20 GMT

I set up a network printer for my mac, but I am unable to install under method 1) using the bridged or NAT modes. I'm using http://Default Mask:631/printers/Queue Name or http://IP Address:631/printers/Queue Name and its unable to connect. I have enabled sharing on Mac OSX but disabled on VMWare. Am I doing something wrong? Or is it time to try hardwiring the printer via USB? I never have any issues printing in MAC mode but unfortunately I need to print from the software I use in windows.

Any assistance would be much appreciated.

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

divalasvegas — Sat, 14 Mar 2009 02:13:40 GMT

Duh ... just figured it out. (Private messages.) Thanks.

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

divalasvegas — Sat, 14 Mar 2009 02:10:51 GMT

Dob;t kill me ,,, new to the forum. How do I do that (Private messages?)

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

divalasvegas — Sat, 14 Mar 2009 02:09:56 GMT

Okay thanks,

One more question ... what if I screwed up and installed the combo update because I am such a genius? How can I fix that so my computer is still secure?

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

WoodyZ — Sat, 14 Mar 2009 02:07:58 GMT

Check your Private Messages.

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

WoodyZ — Sat, 14 Mar 2009 02:04:29 GMT

You do not install the combo update if you have already installed the Mac OS X Security Update 2009-001.

You follow the direction to backup the cupsd binary file and then install only the cupsd binary file from one of the .dmg files as noted by mudaltsov's directions.

Yes after copying and pasting one command line at a time in Terminal you press Enter and wait for the $ prompt to return before proceeding to the next command.

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

divalasvegas — Sat, 14 Mar 2009 01:43:11 GMT

Thanks ... just confused by what to do once I put the commands in. I have never used terminal before. I am very green at this. Do I just press return when I am done in terminal and then install the combo? Sorry ... layman here!

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

WoodyZ — Sat, 14 Mar 2009 01:32:25 GMT

divalasvegas wrote: what do I do once I copy and paste the info you provided in there line by line?

Just follow the steps under the one that applies to you and that's what you have to do.

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

fuzzy-wan — Sat, 14 Mar 2009 01:31:39 GMT

I haven't had to do it myself (yet), but pasting mudaltsov's lines of code into Terminal is what does the actual work — once you've finished the last step, you should be all done.

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

divalasvegas — Sat, 14 Mar 2009 01:24:35 GMT

Unfortunately I am old enough (lol) but what do I do once I copy and paste the info you provided in there line by line?

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

divalasvegas — Sat, 14 Mar 2009 01:01:14 GMT

Hi mudaltsov,

I am a laymen, albeit an ambitious one and while I probably shouldn't even be on this forum, I have printed out your workaround for changing the cuspsd. I get everything except something embarrassingly basic. Once I click on the dmg of the Mac OS X Update Combined, how do I copy the text you showed and where? In the terminal window? I just figured out how to open the terminal utility. Is that what you mean by terminal. I copied the information line by line in there. Now what?

Help?!

Thanks

Michelle

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

fuzzy-wan — Sat, 14 Mar 2009 01:13:23 GMT

divalasvegas wrote:
I get everything except something embarrassingly basic. Once I click on the dmg of the Mac OS X Update Combined, how do I copy the text you showed and where> I don't know what terminal means.

If you're old enough to remember MS-DOS, Terminal is similar — you type in commands and things happen. It's what computers were like before the Mac turned everything upside down, but with OS X we've gone full circle. Best of both worlds...

You'll find Terminal in Applications/Utilities/. Hopefully that will help you get started, but keeping asking questions if it doesn't.

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

mudaltsov — Tue, 10 Mar 2009 19:22:22 GMT

Generally, keeping an old cupsd binary shouldn't cause any problems with OS X updates, since it would be either left alone or overwritten by the update. The workarounds I posted will keep a backup copy of the newer cupsd binary, so that it can be restored if necessary (or you can re-apply the security update to do it).

We're working with ThinPrint to fix the issue and allow printer sharing to work with the new cupsd binary, and will be releasing an update when it's ready.

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

scampa1234 — Mon, 09 Mar 2009 17:46:49 GMT

Will this mess things up with future Mac OS updates? Is this the recommended approach? Will VMWare be putting out an update that does this?!?

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

polyceph — Sat, 07 Mar 2009 00:33:17 GMT

Thanks again Guys,
I had been trying to do it by copying and pasting the whole paragraph into terminal, rather than doing it one line at a time. After doing it one line at a time, shared printing miraculously came back to life. Hooray!!!
cheers
David

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

davidliu — Fri, 06 Mar 2009 22:59:48 GMT

After you ran these command lines, you have already replaced your cupsd file with the older one. This particular line copies the old cupsd from unpacked 10.5.6 dmg location to your system binary folder:

sudo cp /tmp/package/MacOSXUpd10.5.6.pkg/usr/sbin/cupsd /usr/sbin/cupsd

The only thing you need to do next is to restart cupsd (reboot would be the easiest).

-David

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

WoodyZ — Fri, 06 Mar 2009 22:54:32 GMT

Just follow the steps under the one that applies to you and that's what you have to do.

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

polyceph — Fri, 06 Mar 2009 22:47:37 GMT

Hi There,
Thanks so much for getting a workaround to this very frustrating problem.
Once you have performed these terminal actions
"2. If you have already installed Security Update 2009-001, and have Mac OS X 10.5.6 Update (not Combo) (372 MB):

(First double-click on MacOSXUpd10.5.6.dmg to open the disk image)

pkgutil --expand /Volumes/Mac\ OS\ X\ 10.5.6\ Update/MacOSXUpd10.5.6.pkg /tmp/package/
cd /tmp/package/MacOSXUpd10.5.6.pkg
cpio -izd -I Payload ./usr/sbin/cupsd
sudo cp /usr/sbin/cupsd /usr/sbin/cupsd_backup
sudo cp /tmp/package/MacOSXUpd10.5.6.pkg/usr/sbin/cupsd /usr/sbin/cupsd
sudo chown root:wheel /usr/sbin/cupsd
rm -r /tmp/package/"

What do you do then to install the old cupsd file - Sorry if that's a basic question but I'm not that terminal savvy.
Thanks

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

hbg — Thu, 05 Mar 2009 21:21:50 GMT

Parallels was not broken in its ability to print by the security update.

Plus, vmware's support is awful. My partner had to pay $20+ for email support on the printing problem, not knowing this was the issue. For what he paid, he got one email, to which he responded did not work, and he has yet, two days later to hear back. I later found out the hard way online that printing was broken. He paid for support he has yet to receive and they have yet to even tell him what I found out. Vmware is not friendly to business and we'll be leaving fully for Parallels, where at least for a support fee you can get someone on the phone.

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

WoodyZ — Fri, 27 Feb 2009 21:45:02 GMT

It's obvious from this reply and the other reply to the other thread I posted in that you just rather complain instead of going through a logical troubleshooting process and resolve your issue so it really doesn't matter whether it's relegated or not and by your reasoning alone the fact that I can upgrade from 2.01 to 2.02 and have no problems would mean it's not a VMware issue. Anyway if you want some help then start your own discussion thread and provide the appropriate information to allow a logical troubleshooting process to take place and see if we can help you resolve your issue. Or just go back to 2.0.1 since it worked for you.

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

Technogeezer — Sat, 28 Feb 2009 16:43:53 GMT

For those who are more mechanically inclined...

There's an interesting post in the cups.general forum on www.cups.org that looks suspiciously like what's happened to Fusion's Printer Sharing functions. The post can be found here

What appears to be happening is that in the latest CUPS release that's being included in Apple's security update, CUPS is doing more robust error checking than it used to. According to the CUPS engineer, the request that is being passed to cupsd does indeed contain improper content (the host field doesn't contain a valid host name). This would explain why reverting to the old version of cupsd works.

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

fuzzy-wan — Fri, 27 Feb 2009 22:00:04 GMT

Miller101 wrote:
I AM trying to solve the problem and I do think it is relevant because it is the same problem which occurred only after the 2.0.2 update. Perhaps this is a different problem, but it IS a problem and it may be related IMO.

Oh, come on! You're not even running the same version of OS X as the rest of us, and no one here has blamed it on the 2.0.2 upgrade. If you've got a problem you've got a problem, but take it to a thread of your own (like I did). Don't muddy the discussion.

In this case, "same problem" just means that you can't print. Have you any idea how many other things could go wrong to produce a result so broadly defined? This issue has been isolated because people have done testing, not jumping to conclusions. Come back when you've downgraded to 2.0.1.

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

Miller101 — Fri, 27 Feb 2009 21:26:00 GMT

Actually, I DID upgrade the VMTools and I still had the issue.

As to your other comments, I do fault VMWare if I use their software and a simple update issued by that company breaks its prior function. Should I have to waste my time to reinstall apps after updates? I don't hack my system or alter it in any way. I only use my Mac for business applications. I AM trying to solve the problem and I do think it is relevant because it is the same problem which occurred only after the 2.0.2 update. Perhaps this is a different problem, but it IS a problem and it may be related IMO.

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

WoodyZ — Fri, 27 Feb 2009 20:46:36 GMT

Miller101 wrote: Sorry to disagree with VMWare's diagnosis, but I am still running
10.5.5 and now am no longer able to print from either my Win95 or WinXP
Pro SP3 VM. This only happened after updating to Fusion 2.0.2. This is most definitely VMWare's problem! Don't blame Apple for your problem VMWare.

OTOH, I would like to know if there is
a way to go back to 2.0.1?

This issue of the subject of this thread is most definitely an Apple Mac OS X Security Update 2009-001 issue and your situation doesn't prove any different if you do not have this update installed!

Now that not to say you don't have a legitimate issue however I have no problem printing using 2.0.2 having upgraded from 2.0.1 without the security update installed nor do most other users under the same conditions. Okay, so you do however did you upgrade the VMware Tools in the Virtual Machine after upgrading Fusion if they were automatically upgraded? Did you try uninstalling/reinstalling VMware Tools and or uninstalling/reinstalling Fusion 2.0.2 in an attempt to correct your printing issue? What, if anything, did you try to correct the issue other then to jump into a couple threads saying "Sorry to disagree with VMWare's diagnosis"?

Anyway if you don't have the Mac OS X Security Update 2009-001 installed then you aren't not experiencing the same issue as the subject of this thread so you really have no standing in what you're saying to begin with and besides that the issue of the subject of this thread has already been proved to be an Apple issue! Also this issue is reproducible at will with/without the presence of this update which is one of the many tests use to determine what is at fault and had you actually read and comprehended the entire thread you'd know that it comes down the single binary in the security update and with the security update installed and the target binary replaced with the previous version it works and this is proof positive that this particular issue is indeed caused by Apple not VMware! Although VMware and or ThinPrint may be left to make changes in their applications to accommodate changes that Apple made to OS X!

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

Miller101 — Fri, 27 Feb 2009 19:39:37 GMT

Sorry to disagree with VMWare's diagnosis, but I am still running
10.5.5 and now am no longer able to print from either my Win95 or WinXP
Pro SP3 VM. This only happened after updating to Fusion 2.0.2. This is most definitely VMWare's problem! Don't blame Apple for your problem VMWare.

OTOH, I would like to know if there is
a way to go back to 2.0.1?

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

macernie — Fri, 27 Feb 2009 13:35:45 GMT

Hello all, I have just come across this problem and fixed it quite quickly after seeing this thread. I Run a MacBook Pro, wireless network connection to a Time Capsule, I have three printers but the one I wanted to use is a HP Laserjet 4L connected to the Time Capsule via USB hub and a parallel to USB convertor cable. This setup is a bit more messy than most. Having used Bonjour on a Windows PC to use this printer over the network before, I decided to use it on my VMWare Windows PC. I turned off printer sharing, changed the network connection to "Bridged", Restarted the virtual machine (to get the network connection), downloaded Bonjour for windows from the Apple website. Ran the Bonjour print wizard and it all works.

I think I might leave it this way, it is less likely to be affected by updates and the problem if one occurs will be all Apple and Microsoft (one less variable). Perhaps VMware might consider this for the future.

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

fuzzy-wan — Wed, 25 Feb 2009 19:29:05 GMT

Urk. I've got a machine running 10.5.6, security update 2009-001 is not installed, VMware Tools version is 7.9.3, and after turning on printer sharing I see zilch in the guest's Printers control panel (Windows 2000 SP4).

I've confirmed that cupsd is the 10.5.6 version.

Have I missed something in the docs? Is there a down & dirty way to troubleshoot this?

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

fuzzy-wan — Wed, 25 Feb 2009 17:29:53 GMT

Ooo, I lucked out — she doesn't have the 2009-001 update installed yet. I'll deal with that and the CUPS issue if/when I can get the printer working.

Now I'm just waiting for her ungodly slow DSL connection to download 2.0.2 — five minutes on the cable line at the office, 30 minutes for her. I could drive it to her place faster than that, but I'd like to do this remotely and save myself a housecall.

And I still think Hoolitt Packurd is evil.

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

homagetogorto — Wed, 25 Feb 2009 17:29:01 GMT

I can confirm another instance where simply replacing /usr/sbin/cupsd works. Instead of downloading the (huge) Combo update and extracting cupsd from it, I got the previous version from time machine. I don't know how to get at /usr/sbin from Time Machine's space interface, but it was easy enough to find in Terminal. (Look for the 758,112 byte version, probably dated December 8th.)

$ cd /Volumes/My Time Machine Drive/Backups.backupdb/My Computer/
$ ls -l */*/usr/sbin/cupsd

Then back up the original /usr/sbin/cupsd and copy in the one you found in Time Machine.

One additional tip. VMWare may have automatically disabled printer sharing in your settings if it failed enough times. It did for me. So after replacing cupsd, check your VM configuration and re-enable printer sharing if necessary.

And since cupsd is a daemon, best to restart your Mac after replacing it to make sure the new (old) version is running. (Or restart cupsd any way you know how - probably launchctl.)

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

fuzzy-wan — Wed, 25 Feb 2009 16:47:07 GMT

I do hope this cupsd workaround does the trick, as I just discovered that a client's new printer doesn't have Windows 2000 drivers ("Curse you, evil Hoolitt Packurd!!!"). I'm hoping that "driverless printing" means I can get around this small impediment. Gah.

I'll find out tonight, one way or another...

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

WoodyZ — Wed, 25 Feb 2009 06:27:27 GMT

Steve no one was accusing you of anything.

I only followed up with your original post because of what I though might be an issue after replying the Mac OS X 10.5.6 Combo Update and had not had any time to do any testing on this issue beyond telling users that setting up the printers as before this feature existed was a viable workaround which I believe to be the safest way around after one has applied Mac OS X Security Update 2009-001. However one solution doesn't necessarily fit all users needs and mudaltsov has now provided a way of just replacing the cupsd binary and while there remains a risk with this I believe it's less then not having the Mac OS X Security Update 2009-001 at all or possible issues of replying Mac OS X 10.5.6 Combo Update after having applied the Mac OS X Security Update 2009-001.

Anyway I know some users that use VPN's and replacing just the cupsd binary gives them to ability to apply the Mac OS X Security Update 2009-001 and then still use ThinPrint with Network Printers while connected to the VPN which they couldn't do connected directly while connected to the VPN and were forgoing applying the security update in total.

It's not a perfect work-a-round however it's only temporary and it's better then applying the entire Mac OS X 10.5.6 Combo Update after having applied the Mac OS X Security Update 2009-001.

Users are just going to have to remember to replace the cupsd binary once VMware comes up with a fix if Apple doesn't do anything although I think they may address this as well but we'll just have to wait and see who has to do what but until then there are now several different opting to choose from depending on ones needs.

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

WoodyZ — Wed, 25 Feb 2009 05:57:07 GMT

Michael, thanks for taking the time to do this as I'm sure some users would prefer to do this even though this has some risk it has less risk then not having the Mac OS X Security Update 2009-001 installed at all and gives the users another option to choose from.

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

stevesp64 — Wed, 25 Feb 2009 05:34:08 GMT

Woody,

Obviously, I would not want to advise people to make their computer
insecure, in my particular incident printing is quite important, so I am
taking a chance. Please let me know if there is an easier workaround.

Steve

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

DMcc — Wed, 25 Feb 2009 01:48:05 GMT

I was able to use the workaround to get my network printer to work. Using the "bridged" network setting and then resetting the network IP address (just to be sure I restarted my windows and VMware too). THE ONE DETAIL LEFT OUT WAS THAT THE WINDOWS PRINTER DRIVERS NEED TO BE LOADED TO GET THE PRINTER TO WORK IN WINDOWS. HAVING TO ADD THESE DRIVERS COST ME 500MB OF DISK SPACE.

I am EXTREMELY SISSED OFF AND WILL OPENLY DISCOURAGE ANYONE INTERESTED IN BUYING THIS SOFTWARE !! The lack of software support and especially the INTERNET TEC SUPPORT REEEEEEELY SUCKS !!!!

Telephone customer support employees are uninformed and TOTALLY USELESS.

I am a business owned that was inconvenienced, with out any tec support, for a day and a half. Unable to get support for a obvious software problem is TOTALLY UNACCEPTABLE FOR ANY REASON.

I try to avoid any software that use internet tec support, because it's like being left out in the cold and this is a PERFECT EXAMPLE OF REALLY BAD SOFTWARE SUPPORT.

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

mudaltsov — Wed, 25 Feb 2009 00:55:25 GMT

I agree that replacing just cupsd is better than not installing the Security Update at all, or reverting using the Combo Update. I just wanted to make sure people realize the potential security risk.

Here are the commands (for Terminal) to get the older version of cupsd and backup the original to /usr/sbin/cupsd_backup:

1. If you have not installed Security Update 2009-001 yet and printing works correctly - make a backup of cupsd and restore it after updating:

sudo cp /usr/sbin/cupsd /usr/sbin/cupsd_original

# (Install Security Update 2009-001 and restart)

sudo cp /usr/sbin/cupsd /usr/sbin/cupsd_backup
sudo mv /usr/sbin/cupsd_original /usr/sbin/cupsd

2. If you have already installed Security Update 2009-001, and have Mac OS X 10.5.6 Update (not Combo) (372 MB):

# (First double-click on MacOSXUpd10.5.6.dmg to open the disk image)

pkgutil --expand /Volumes/Mac\ OS\ X\ 10.5.6\ Update/MacOSXUpd10.5.6.pkg /tmp/package/
cd /tmp/package/MacOSXUpd10.5.6.pkg
cpio -izd -I Payload ./usr/sbin/cupsd
sudo cp /usr/sbin/cupsd /usr/sbin/cupsd_backup
sudo cp /tmp/package/MacOSXUpd10.5.6.pkg/usr/sbin/cupsd /usr/sbin/cupsd
sudo chown root:wheel /usr/sbin/cupsd
rm -r /tmp/package/

3. If you have already installed Security Update 2009-001, and have Mac OS X 10.5.6 Combo Update (668 MB):

# (First double-click on MacOSXUpdCombo10.5.6.dmg to open the disk image)

pkgutil --expand /Volumes/Mac\ OS\ X\ Update\ Combined/MacOSXUpdCombo10.5.6.pkg /tmp/package/
cd /tmp/package/MacOSXUpdCombo10.5.6.pkg
cpio -izd -I Payload ./usr/sbin/cupsd
sudo cp /usr/sbin/cupsd /usr/sbin/cupsd_backup
sudo cp /tmp/package/MacOSXUpdCombo10.5.6.pkg/usr/sbin/cupsd /usr/sbin/cupsd
sudo chown root:wheel /usr/sbin/cupsd
rm -r /tmp/package/

For reference, here is the file size and MD5 sum of /usr/sbin/cupsd on my system:
With Security Update 2009-001: 762224 bytes, MD5 = b381c745a8f0576614deaa7af3fd71cf
After reverting to the 10.5.6 version: 758112 bytes, MD5 = f0d734907eb2be74a6e9beb33e1cb925

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

WoodyZ — Tue, 24 Feb 2009 23:53:43 GMT

mudaltsov wrote: but it still has the possibility of re-opening any security issues that Apple has fixed in cupsd with Security Update 2009-001.

That certainly is understandable however if just replacing the cupsd binary can act as a temporary work-a-round while having the other aspects of the latest security updates in place that IMO would be better then not having the update at all and I'm just look at this as another solution of users to choose from based on the merits of each and then at least they can make an informed decision and go from there.

Without a doubt the safest thing to do is be fully updated in all respects and then just turn off ThinPrint and reinstall the printers just as if this feature never existed and that is my recommendation. However it's nice to have other options if/when necessary. I know the users that need to VPN would like to be fully updated and have this feature working and if just replacing the cupsd binary can be a temporary fix this issue I think some of the VPN users would like that. Just a thought.

I'm looking into extracting cupsd from the update package...

Thanks for looking into this even if it's not the best or safest temporary solution to this overall issue.

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

mudaltsov — Tue, 24 Feb 2009 23:23:18 GMT

I just tried replacing the updated cupsd with the version from 10.5.6, and ThinPrint works again, so the change that breaks ThinPrint is indeed localized to the cupsd binary. So replacing a single file is definitely a better workaround than applying the entire Combo Update, but it still has the possibility of re-opening any security issues that Apple has fixed in cupsd with Security Update 2009-001.

I'm looking into extracting cupsd from the update package...

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

WoodyZ — Tue, 24 Feb 2009 22:49:12 GMT

This is why I was asking Steve what he saw if he went to Apple menu > Software Updates and when he it said "is up to date" I was concerned about that and hadn't had time to investigate. What I'm wondering is if there is a way to just extract and replace cupsd from the Mac OS X 10.5.6 Combo Update as a work-a-round to this issue? Anyone have any though on this or is it deeper then just cupsd?

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

mudaltsov — Tue, 24 Feb 2009 19:41:25 GMT

A warning about using the 10.5.6 Combo Update - it actually reverts the CUPS daemon (and other system files) to the versions that are older than the ones installed by Security Update 2009-001. And afterwards, the Security Update is no longer visible in Software Update because the system thinks it's already installed, so you may have difficulty installing it in the future.

Edit: You can download and manually reinstall the Security Update (and other updates that may have been overwritten) from http://support.apple.com/downloads/

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

jonsamson — Tue, 24 Feb 2009 13:49:57 GMT

Jupiterfish - what was the workaround you found that worked for the adobe pdf as I am unable to get mine working. Thanks

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

heronaddict — Tue, 24 Feb 2009 09:58:09 GMT

thanks woody.

much appreciated.

I'll get some professional boffin to come in and sort it out for me given that it's my sole income source!!

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

stevesp64 — Tue, 24 Feb 2009 04:14:08 GMT

Woody,

It says that my software is up to date. I got this idea from the apple
support forums, http://discussions.apple.com/thread.jspa?messageID=9018258

It worked for me, I don't know why it doesnt work for others.

Steve

A new message was posted in the thread "Workaround for Printers Sharing
not working after Mac OS X Security Update 2009-001":

http://communities.vmware.com/message/1179941#1179941

Author : WoodyZ
Profile : http://communities.vmware.com/people/WoodyZ
Message:

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

Technogeezer — Tue, 24 Feb 2009 03:47:10 GMT

Sorry Woody, should have been to the OP...

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

WoodyZ — Tue, 24 Feb 2009 03:18:47 GMT

Not sure why you're responding to me with this as it has nothing to do with my reply to Steve.

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

Technogeezer — Tue, 24 Feb 2009 03:02:40 GMT

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.

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

WoodyZ — Tue, 24 Feb 2009 02:35:54 GMT

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, can I ask what you see if you go to Apple menu > Software Updates?

Thanks,

Woody

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

stevesp64 — Tue, 24 Feb 2009 02:24:06 GMT

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

A new message was posted in the thread "Workaround for Printers Sharing
not working after Mac OS X Security Update 2009-001":

http://communities.vmware.com/message/1179761#1179761

Author : WoodyZ
Profile : http://communities.vmware.com/people/WoodyZ
Message:

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

jupiterfish — Tue, 24 Feb 2009 00:35:46 GMT

adding the combo update did nothing for me. its still the same.

found a work around. thatnks
nice videos.

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

WoodyZ — Tue, 24 Feb 2009 00:28:12 GMT

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

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

jupiterfish — Mon, 23 Feb 2009 23:54:15 GMT

i figured out my standard usb printers but my adobe pdf printer still doesn't show up even tho its shared, i have full acrobat on my mac. i make allot of pdf's from my vm xp.

any help?

thanks

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

WoodyZ — Mon, 23 Feb 2009 21:59:18 GMT

stevesp64 wrote: The easiest way I found to fix this is to install the combo update here: http://support.apple.com/downloads/Mac_OS_X_10-5-6_Combo_Update

It fixed the issues.

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.

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

stevesp64 — Mon, 23 Feb 2009 21:40:47 GMT

The easiest way I found to fix this is to install the combo update here: http://support.apple.com/downloads/Mac_OS_X_10-5-6_Combo_Update

It fixed the issues.

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

WoodyZ — Mon, 23 Feb 2009 21:24:58 GMT

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.

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

heronaddict — Mon, 23 Feb 2009 20:50:38 GMT

Thanks for the plain english explanation. To make it plainer for the completely non IT person like me:

1 what do you do if your printer is attached to the time capsule, and

2 can I just uninstall the updates without completely goosing my virtual windows pc on my Mac as it worked perfectly fine before. As a tax consultant who's primary software only runs on Windows, being unable to print accounts, tax returns etc rather stems my ability to invoice.

3 or can I just reinstal the disc that I originally purchased box and go back to the happy state where i was before?

Cheers

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

Piggy — Mon, 23 Feb 2009 11:26:10 GMT

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.

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

jviss — Sun, 22 Feb 2009 21:13:13 GMT

Sorry, I'm packing for a trip, and wanted to print my itinerary and directions - hardly ever print anything, but when I need it - well, I need it to work! Understand it was Apple's update that killed it, not sure who's problem - that is, design flaw - it may be. Doesn't matter, I still like the technology, it's just not ready for prime time for me, if so basic a feature can be knocked out by so apparentrly innocuous and necessary OS update.

Bridged works now, but only after I restarted the XP VM. "Repairing" the network didn't work after switching from NAT to bridged.

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

WoodyZ — Sun, 22 Feb 2009 20:12:00 GMT

jviss wrote: This is just great! The only reason I bought this product was for Outlook, Word, and Powerpoint, and now one of the most fundamental fearures is broken. I can't get bridged connections to work, plus, besides the fatc that I don't like the security aspect of bridged. Yet another failed experient, $80 for VM Ware Fusion and more for the XP license down the drain. What a waste of time, waste of money, and a pain in the ass.

I'm sure you'll say it's Apple's fault, and they probably don't care anyway.

Now what???

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.

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

jviss — Sun, 22 Feb 2009 20:01:54 GMT

This is just great! The only reason I bought this product was for Outlook, Word, and Powerpoint, and now one of the most fundamental fearures is broken. I can't get bridged connections to work, plus, besides the fatc that I don't like the security aspect of bridged. Yet another failed experient, $80 for VM Ware Fusion and more for the XP license down the drain. What a waste of time, waste of money, and a pain in the ass.

I'm sure you'll say it's Apple's fault, and they probably don't care anyway.

Now what???

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

WoodyZ — Sat, 21 Feb 2009 02:13:29 GMT

anchor3n1 wrote: Conclusion? 2.02 apparently has a problem with print through OSX and the security update isn't the issue.

I have no problem with using ThinPrint in 2.0.2 without the Mac OS X Security Update 2009-001 nor do all the users I've talked to since the update so there certainly isn't enough evidence to support your conclusion.

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

anchor3n1 — Sat, 21 Feb 2009 01:05:42 GMT

I have been experiencing the same printer (thinprint) issue. I have tried the various work arounds including OSX archive and install to 10.5.4 (which removed the latest security update. None worked . I then decided to uninstall fusion 2.02 and reintal 2.01. Print through works like a charm.

Conclusion? 2.02 apparently has a problem with print through OSX and the security update isn't the issue.

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

scampa1234 — Fri, 20 Feb 2009 20:18:24 GMT

Thanks David, I was hoping that would be your response!

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

davidliu — Fri, 20 Feb 2009 19:34:15 GMT

Yes, we are working to get this issue fixed for our customers, even when the underlying components are from different companies (ThinPrint and Apple).

David Liu
Product Manager
VMware

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

scampa1234 — Fri, 20 Feb 2009 19:23:30 GMT

This is truly dissappointing to me since this VMWare feature made it possible for me to print to my local-netowrk printers while my VMware guest was VPN'd into my corporate network. This was something I could neve do before and now I cannot do it again....I assumed this was due to VMWare handing off the guest print notification to the underlying host print system via API call vs network....I'm not sure why a security fix would break something at that level....

Does VMWare plan to "fix" this or does this mean we will never have this feature back the way it was?

Thanks!

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

WoodyZ — Fri, 20 Feb 2009 01:50:58 GMT

davidliu wrote: Thanks Woody for the detailed instructions. The same is also documented in the video link in my original post (with my latest edits). Edit: here is the link again: http://tr.im/gwi2

No problem. I always forget about the videos (probably because I don't need them) but I also have foun from the past when I used to point usare to the printer video many of then still need written directions.

Steve, the reason we say use Bridged network is because so that auto discovery works and you do not have to go through these manual process. In your case, follow Woody's steps and you should get it to work in NAT mode.

Steve, I will add that when you go to add the printer in this manner that if the manufacture doesn't have a PostScript Printer Driver for your Model then you can use an Apple LaserWriter PS drive in its place. (That may be in the video although I haven't watched it in over a year and haven't watched the Fusion 2 version.

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

WoodyZ — Thu, 19 Feb 2009 20:44:00 GMT

stevesp64 wrote: So, what is the workaround if you need to print to a network printer, but your network will not work in bridged mode? My company has a 1 ip address per port configuration, this is a security feature, so my mac gets the IP address and windows gets nothing, therefore the VM can't talk to the network, hence the network printers are unavailable.

Please let me know asap, my manager doesn't like the "Fusion is broken because VMWare and Apple can't play nice" excuse for why I am not getting my work done.

1. Set the target Virtual Machine's Network to NAT and if running when you change it then release/renew its IP Address and if you don't know how then reboot the Virtual Machine or make the change when it's off to begin with.

2. Uncheck the Enabled check box under Printers in the target Virtual Machine's Settings.

2. Turn on Printer Sharing in OS X and enable the target Printer to be shared.

3. In Windows add a new Printer and add it as a Network Printer using the following URL Convention.

http://Computer_Name:631/printers/Queue_Name_of_target_Printer

Or

http://Host_vmnet8_IP_Address:631/printers/Queue_Name_of_target_Printer

Examples:

On my MacBook Pro the Network Attached Shared Printer is an HP LaserJet 4050N and the following information is relevant to this.

Computer_Name = MacBookPro

Host_vmnet8_IP_Address = 192.168.51.1

Queue_Name_of_target_Printer = HP_LaserJet_4050

So either of the following examples works in my Windows XP Virtual Machine.

http://MacBookPro:631/printers/HP_LaserJet_4050

http://192.168.51.1:631/printers/HP_LaserJet_4050

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

davidliu — Fri, 20 Feb 2009 01:24:33 GMT

Thanks Woody for the detailed instructions. The same is also documented in the video link in my original post (with my latest edits). Edit: here is the link again: http://tr.im/gwi2

Steve, the reason we say use Bridged network is because so that auto discovery works and you do not have to go through these manual process. In your case, follow Woody's steps and you should get it to work in NAT mode.

-David

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

stevesp64 — Thu, 19 Feb 2009 19:35:26 GMT

So, what is the workaround if you need to print to a network printer, but your network will not work in bridged mode? My company has a 1 ip address per port configuration, this is a security feature, so my mac gets the IP address and windows gets nothing, therefore the VM can't talk to the network, hence the network printers are unavailable.

Please let me know asap, my manager doesn't like the "Fusion is broken because VMWare and Apple can't play nice" excuse for why I am not getting my work done.

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

davidliu — Tue, 17 Feb 2009 21:04:05 GMT

This post is a heads up for those of you using VMware Fusion's Printers Sharing feature (technically ThinPrint. Turned on by VM Settings -> Printers) on a Mac OS X 10.5.x host. This feature will not work if you install the recent Mac OS X Security Update 2009-001. After installing the security update and rebooting your Mac, the shared printers will no longer show up in the Windows virtual machines. We are investigating the issue and I wanted to provide a workaround for now:

1) If your printer is set up as a network printer, switch to Bridged networking (http://communities.vmware.com/docs/DOC-2527), disable Printers Sharing in VM Settings, and configure the network printer directly in the Windows virtual machine.

2) If your printer is connected to the Mac as a local printer on USB port, you can either:

2.1) switch to Bridged networking, grab the USB printer in the virtual machine directly and set it up as if it is physically connected to the VM, or

2.2) share the printer on Bonjour network, install Bonjour for Windows in your virtual machine, and configure it as a network printer in the VM

3) If you absolutely have to use Fusion's shared printer feature (ThinPrint), reinstall Mac OS X 10.5.6 (and not Security Update 2009-001) to get ThinPrint printer to show up. As some pointed out, this is far from an ideal workaround because you will be running your Mac without the latest security update, but I wanted to list it as an option.

Here is a video tutorial from VMware Fusion 1 that walk you through options 1), 2.1), and 2.2): http://tr.im/gwi2

Edit Feb-18: reorg the workaround and added link to the Fusion 1 printing video tutorial.

David Liu
Product Manager
VMware

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

tk1234 — Wed, 18 Feb 2009 16:01:19 GMT

I see that you all feel as strongly as I do on this issue. Given that you point out the security update came out after 2.02 Fusion did, I understand your frustration with the issue.

My frustration is as an end user that this has to happen. I wish to fix the problem, not the blame. I too wish Apple would test their updates using all available popular apps software before their release, especially since they sell Fusion on their website, just as much as I wish that apps software could be bullet proof to any OS changes. Believe me.....I've gone through enough with a popular antivirus/security software package on Windows to fill several forums.

I hope you can fix the printer issue soon.

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

WoodyZ — Tue, 17 Feb 2009 23:43:50 GMT

tk1234 wrote: In the meantime, understand that all we end users want from software we buy is that at least most of the major features work as advertised.

I want all features to work as advertised and while I could reiterate some of my own gripe here I'm not going to waste my time because it will be for nothing however I will say this...

As far as the tests that I've done if reference to this printing issue it is not VMware's fault that Apple's Security Update broke a feature of a 3rd party application and if one hasn't applied this update then there is no issue. Now ultimately who's responsible for fixing it may be another story however VMware is going to have to take the lead and if necessary work in concert with Apple to resolve what in Apples Update causes this feature to break.

That said I see no reason why printers cannot be setup the way they have always been before this feature was introduced unless this update breaks that as well and if it does then there is absolutely no culpability on VMware for this issue.

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

tk1234 — Tue, 17 Feb 2009 23:00:45 GMT

etung

Thanks for the reply. I'm sure you'll understand a fair amount of frustration is built into the comments here. However, as end users of software, we are constantly shuttled between software vendors when problems happen like this. The OS guys blames it on the apps guy, and vice versa. In the meantime, we are left with broken software we can't use properly, and only forums like this in which we can seek solutions.

If you find a solution quickly to fix this and issue another update, that would be great. In the meantime, understand that all we end users want from software we buy is that at least most of the major features work as advertised.

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

etung — Tue, 17 Feb 2009 22:41:43 GMT

1. How does such a major bug NOT get weeded out during beta testing of the upgrade? Driverless printing is a major feature of the software that is occuring with the only OS on which Fusion is supposed to be able to run.

2.0.2 came out February 11. I'm not sure when the security update came out, but Apple's download page says February 12. We don't get early access to updates; even if we did, it would be a question of how early we got it (my guess would be "not very") and how long it takes to test and finalize a Fusion update (which is a nonzero amount of time). I'm not sure how you expect us to have been able to test this.

2. I personally don't think "reinstalling OS X 10.5.6" is a good workaround.

Apple doesn't provide a way to uninstall updates, so short of digging around system folders (which is even less of a good workaround) or using Time Machine (which not everyone has set up), there's no way to revert to a point before the security update. We don't think it's a good workaround either, but it's mentioned as a possibility until we better understand the problem.

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

tk1234 — Tue, 17 Feb 2009 22:28:34 GMT

David,

Thanks for getting on this significant issue. It's too bad that VMWare and Apple can't be in better sync on these things - this is kind of a major bug to miss when debugging the software, especially when "driverless printing" is pushed as a major feature of the Fusion software.

I have a few points to make that I hope VMWare takes constructively:

2. I personally don't think "reinstalling OS X 10.5.6" is a good workaround. Many of your customers are folks who go to the mall and buy their iMac or Macbook from the Apple Store, and then install your software to be able to keep using some Windows apps. They don't know from reinstalling OS's or kernel dumps, etc. - they just want their computer to work. Apple is no help either - I've asked the "genius's" and they're not interested in third party software.

3. Several here have complained about VMWare's practice of free support ONLY for 30 days after the original purchase. As is clear here, if the software breaks after that time, VMWare wants money for support. I propose that, going forward, if bugs like this can't be caught during beta testing, that VMWare consider offering free support for paying customers when major bugs like this emerge after a factory update is issued. Alternately, we need a clear path to make these issues known and get action quickly.

Here's hoping the real fix comes soon.

Thanks.