There should be an image here!I have been avoiding setting up network printing on my wife’s Mac and her Eee netbook for as long as possible. The reason being, in both cases previously when I tried what should be reasonably simple, the affected OS failed hard to finalize the connection.

On the OS X front, it was due to a known bug with select HP printers and the available drivers at the time for Snow Leopard. Comical, as setting up the same printer in Ubuntu was literally plug and play.

Then with Windows 7, it was a bit more mysterious. IPP printing was completely out of the question and was not going to cooperate at all, despite this being brain-dead easy in other instances. In the end though, it was only a matter of time before I had to sit down in both instances and address the problem head on.

After spending a few hours with the two machines, I have discovered the following. The Mac is a total fail trying to connect the specific HP all-in-one from a Linux host using an IPP connection, but with the proper SAMBA configuration, it did indeed work as needed.

On the Windows front, things were even more strange. My printer server was at the machine named blah-blah-blah. For some reason though, Windows 7 only found this PC/server as blah-blah-blah. During my SAMBA connection, I had simply not noticed this and was baffled why Windows was seeing my printer yet refused to connect. On a hunch, I added it manually as \blah-blah-blahprinter and sure enough, bingo… we had printer action.

Moral of the story? After laughing at the official help documentation, look at the issues a bit deeper. Ports, firewalls, IPP, or SAMBA, don’t be afraid to go mixing things up a bit.

[Photo above by dmuth / CC BY-ND 2.0]

[awsbullet:using samba eckstein]