Is there a way to change a printer’s IP address in OSX (Lion) without having to add a new printer? I did find Printer IP Remedy, but was curious if there was an ‘official’ method.
A
You can do this in the CUPS web interface with the following steps:
Open Terminal.app and run cupsctl WebInterface=yes. This enables the CUPS web interface
Open http://127.0.0.1:631/printers in your web browser
Click on the printer you want to change. From the “Administration” drop down, select “Modify Printer”.
Log in with your local admin account
Select the new printer IP either from “Discovered Network Printers” or add it manually with “Other Network Printers”. Make sure that you keep the same connection protocol as it says in “Current Connection” (for me, this was LPD).
Once you’re done with this, Mac OS X will directly print to the new IP address. There is no need to reboot or so. If you want to disable the CUPS web interface again, run cupsctl WebInterface=no.
The web interface is currently disabled. Run “cupsctl WebInterface=yes” to enable it.
After enabling it like the CUPS web interface wit cupsctl WebInterface=yes, you can see I have the same printer configured multiple times with different communication protocols and output languages:
Check the modifications (optionally change Description/Location)
Click “Continue”
Keep the driver
Click “Modify printer”
For LPD, note the current address (like lpd://192.168.71.52/), then follow the IPP steps, but choose “LPD/LPR Host or Printer” and enter a valid lpd address.
This is also the place where you can change “Default options”, like paper size (which – for all but the first – somehow defaulted to US Letter 11 inch, while it is actually filled with A4 paper).
At the end, disable the web interface: cupsctl WebInterface=no.
So I created this alias to connect from my Mac to the internal address of my ESXi rig:
alias ssh-esxi-X10SRH-CF-internal='TERM=xterm ssh -p 22 root@192.168.71.91'
The trick is the bold part: TERM=xterm (which you can also replace by export TERM=xterm; if you want future ssh sessions to use the same [wayback] TERM setting).
The reason is that the Mac defines the TERM variable as containing xterm-256 which is defined on the Mac itself, but ESXi has a hard time coping with it.
It seems I already did something similar on ESXi itself to get esxtop working: ESXi: when esxtop shows garbage. That was on the ESXi side and works as well for this problem too.
However, it is a bit harder to have a script run during ESXi boot time that sets this, so it is easier to fix this on the Mac side.
It works for all OS X and ESXi versions I’ve tested so far.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
For now I’ve added the below alias to my ~/.bash_profile which only works if you have “require a password immediately after sleep or screensaver begins”. I have that enabled (with a 5 second delay, not immediate so that when I’m behind my laptop and it starts the screensaver I can still move the mouse or touch a key to keep it awake).
The Wiert Corner - irregular stream of stuff 