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.

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

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

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.

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

Obviously not since you were unwilling to follow directions!

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

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

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!

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.