Setting up a printer in OS X using the CUPS interface – brief!

-

Recently I had to setup a connection to a shared printer in OS X.  The printer was being shared on a TCP/IP network by a HP server running Windows Server 2008 Foundation.  I had some trouble setting up the printer using the printer set wizards in System Preferences and discovered that Mac OS X has a built in web server for CUPS (the Common Unix Printing System) that allows you to setup a printer with much greater granularity and, it would appear, a greater chance of success!

Open up Safari and browse to the following address:  http://localhost:632

The wizards are then relatively straightforward as shown in the samples below…

Picture 2 Picture 4 Picture 5 Picture 6

Picture75

Comments

Post a Comment

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

-
Image
I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
Read more

APC PowerChute Network Shutdown - Authentication Phrase

-
Image
​Was installing  APC PowerChute Network Shutdown (PCNS) on a customer’s server and couldn’t find a record of the Authentication Passphrase that I set ages back on their Smart UPSes Network Management 2 Card. So I went to reset it on the card and start anew… it took a lot of digging to find it on their particular release of firmware: Go into the UPS tab, then into “shutdown” inside the “Configuration” category: You may then need to change the passphrase being used on other servers. To do this, open up PCNS in your browser and click into the area shown below:
Read more

WSUS Issues

-
Image
Was configuring WSUS on a Server 2016 VM for a customer recently and found the performance to be very sluggish and most of the time the client PCs would time-out and throw an error message when trying to check for updates. After much digging on different forums I came across a fix that worked nicely: Open Internet Information Services (IIS) Manager and click on Application Pools Then Right-Click on your WsusPool instance and choose Advanced Settings Scroll down to Private Memory Limit (KB) and change it from the default of 1843200 to 0 which means unlimited. Then right-click and stop the WsusPool and then start it again. Hope this works for you.
Read more