This discussion is archived
3107 Views 2 Replies Latest reply: Jan 27, 2008 8:02 PM by tmoney468
Currently Being ModeratedJan 27, 2008 6:09 PM (in response to tmoney468)It generally is easier than having to do all that you have tried. When you add a printer, by selecting Windows, you should see the printer sharing PC. Then when you double click the PC name, you should be prompted to authenticate (unless you have enabled the Guest account on the PC). The printer share name should then be displayed and when you select it, you will then have to browse to the Gutenprint 2200 driver, as you generally cannot use the vendor provided drivers for connecting to Windows shares.
If the above doesn't work then a couple of suggestions.
1. Create an account on the PC that the Mac can use. Then you can follow the advanced procedure and for the smb user name and password, you can use this new account. Note that when you do enter the details into the smb printer queue, you should not have to authenticate to the PC again.
2. Change the share name on the PC so that there are no spaces as they can cause problems.MacBook Pro, Mac OS X (10.4.11), Mac Pro (10.5), G4's, G3's, G5's, Mini's, iMac's, Xserve G5
Currently Being ModeratedJan 27, 2008 8:02 PM (in response to PAHU)Hi PAHU, thanks for the quick reply.
When I click on the Windows tab, I do see the Windows workgroup of my home network in the leftmost box, but the name of the PC that the printer is connected to never shows up in the boxes to the right (it's like it is never able to see the PC name).
Perhaps I should mention too that any Windows shared folders never show up under the "Shared" section in Finder, I always have to do the "Connect to Server" option and then directly input the IP address for the computer.
The name of my PC workgroup is home2, and the shared printer name is epson2200 (without any spaces). I also have an admin account on my Windows machine that I've been able to use with the advanced method I detailed in my first post to connect my MBP to the shared printer, but the same method doesn't seem to work on the macbook.
Perhaps I'll try re-naming the workgroup back to workgroup and see if that helps any.Intel Macbook Pro / Macbook, Mac OS X (10.5.1)