Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.3: Update URIs for Samba printing to Windows' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Update URIs for Samba printing to Windows
Authored by: storwalle on Nov 28, '03 03:10:13AM

I have tried the tips but it resulted in the below:

Alt-clicking the Add Printer button doesn't result in anything else than the ordinary clicking on the Add Printer button. Choosing Windows Printer leaves me with no option to add a URI like the proposed.

Using IP-printing leaves me with the message saying "Inaccurate address reference" or similar. I can only put in the domain name there without the prefix "smb://" or "cifs://".

Trying to reach the Samba server through the browser on port 631 left me clueless. Couldn't reach the server, was the message...

Using IP printing with an accurate domain name and a printer qeue name leaves me with the Print Center stopping at "Trying to reach... at port 631". Could this be a firewall problem at the Samba server? But the Shorewall firewall is set up to ACCEPT TCP on port 631...

Someone that has any good hints?

Kind regards
Michael

---
Mr Michael says:



[ Reply to This | # ]
10.3: Successful printing to Windows!
Authored by: strikeman on Sep 21, '04 05:38:14AM

I had the problem where my Windows box couldn't be seen in the Windows Printing list.

After much research and trial and error, I finally managed to successfully print from OSX 10.3.5 to a windows shared printer:

1) Turn on Print Services for UNIX on the windows box (http://www.ifelix.co.uk/tech/3002.html?artnum=19652)
2) On the Mac, in Printer Setup, add a printer
3) Choose IP printing, and LPD/LPR
4) Type your windows server name in Printer Address:
5) Type your windows shared printeer name in Queue Name:
6) Choose the appropriate printer. If your printer is not Postscript enabled, use one of the GIMP print drivers. Go to gimp-print.sourceforget.net to lookup which driver is appropriate.

This worked for me, but really should have been a *lot* easier.

NT Cheung
Hong Kong



[ Reply to This | # ]